Most products start with a hypothesis that feels right on the surface. The real test is whether you can reimagine that hypothesis when the data pushes back.
Blinder was a dating app that set out to solve a problem Tinder and others left untouched: the superficiality of photo-based matching. Instead of focusing solely on physical attributes, Blinder aimed to connect people through hobbies, lifestyle, and personality.
The stakes were high. In 2018, online dating was a $1.38 billion industry globally, growing steadily as social stigma faded and mobile access expanded. Millennial and baby boomer users were increasingly open to digital matchmaking. Yet, trust in dating apps remained low, and many treated them as entertainment rather than serious tools for relationships.
This lesson shows you how product managers must resist first information bias — the temptation to build what feels obvious at first glance — and instead dig deeper into user behavior, emotions, and motivations. You will see how research, empathy mapping, and affinity diagrams shaped Blinder’s design, and how its key features aimed to foster long-term connections, not just quick swipes.
First information bias: the trap of surface-level assumptions
The story of Blinder begins with a simple insight: users want more than just photos when choosing a match. Photos remain the first thing people see, but they are not the final decision driver. Many users expressed distrust toward dating apps, often using them casually or for entertainment rather than serious dating.
This is the trap most new PMs fall into — building a product that reflects the obvious first impression rather than probing the underlying user needs.
Chris Paterson, Blinder’s UX designer, recognized this early. He knew that relying solely on photos led to superficial matches and low trust. His hypothesis was that matching people based on hobbies, personality traits, and lifestyle preferences could enable more meaningful, long-term relationships.
But hypotheses are just the start. The actual product decisions depend on testing these assumptions rigorously.
Empathy mapping and affinity diagrams: tools to understand users deeply
Chris began by creating an empathy map. This tool helped him chart users’ emotions, thoughts, pains, and gains related to online dating. The empathy map surfaced emotional barriers — distrust, fear of rejection, the desire for deeper connection — that guided the product’s direction.
Next, Chris used affinity diagrams to group users with similar characteristics and needs. This clustering revealed common patterns and helped prioritize features that could address multiple user segments effectively.
This approach is a model for you as a PM: start by empathizing with real users, then organize insights to find patterns that inform product design.
Survey findings: validating the interpersonal matching hypothesis
Chris conducted multiple surveys to test his assumptions. Key findings included:
- Users want interpersonal matching beyond photos.
- Photos are still the initial attention grabber but not the deciding factor.
- Trust in dating apps is low; users often treat the apps as entertainment.
- If matches were based on deeper attributes, users would consider them for long-term relationships.
These findings challenged the prevailing product logic in dating apps and justified Blinder’s unique positioning.
Key features designed to build trust and connection
From research, Chris identified two standout features to implement:
1. Story cards behind photos:
Each user’s profile included a story card — a narrative or description that gave context beyond the image. This aimed to humanize matches and enable users to understand personality, hobbies, and lifestyle, improving the quality of connections.
2. Dating ideas powered by third parties:
Blinder integrated a free service offering curated date ideas from companies like Groupon or Woot. This feature served two purposes: enhancing the user experience by suggesting activities and generating revenue through third-party financial support.
These features were designed to support Blinder’s core value proposition: facilitating meaningful, long-term matchmaking instead of casual swipes.
Measuring UX success: defining metrics aligned with product goals
To track whether Blinder’s design succeeded, Chris and the team defined metrics that reflected interpersonal connection, not just user activity:
- Number of matches created and messages exchanged (engagement quality).
- Number of active users and user retention.
- Average length of user stories and number of hobbies/interests listed (profile richness).
- Number of deleted accounts (churn rate).
- Conversion to premium subscriptions (monetization).
- Average matches per user (matchmaking effectiveness).
This metric set is a reminder: measure what matters to your product’s unique value, not just generic activity stats.
Sketching the key features: visualizing the user experience
The design team created mockups to bring these features to life:
- Story card interface: A profile view showing the user’s photo alongside a narrative section detailing interests and personality traits.
- Dating ideas interface: A curated list of date suggestions, categorized by type (food, travel, activities), integrated into the app to inspire users and encourage real-world meetings.
These sketches informed development and helped align stakeholders on the product vision.
User flows: mapping how users interact with Blinder’s unique features
Designing user flows made it clear how the new features integrated into the existing matchmaking process:
- Users sign up via Facebook or phone number to minimize fake accounts.
- They create rich profiles including stories and interests.
- The app surfaces matches not only by photos but also by shared hobbies and preferences.
- Users can swipe through profiles, view stories, and like or message matches.
- The dating ideas feature offers suggestions for first dates, which users can send as invitations or use as conversation starters.
This flow supports Blinder’s goal of fostering genuine connections rather than fleeting interactions.
The challenge of blending product and business needs
Blinder’s dating ideas feature also served as a revenue stream through partnerships with third-party companies. While it added value, it risked diluting the core matchmaking proposition if not integrated carefully.
This is a common challenge for PMs: balancing user experience with monetization without confusing the product’s purpose.
Blinder’s approach was to keep the dating ideas relevant and aligned with the goal of encouraging real dates, rather than a distracting marketing gimmick.
Overcoming first information bias: the PM’s critical task
Blinder’s story teaches a vital lesson for you as a PM: never settle for the obvious first solution. Your actual job is to question initial assumptions, test hypotheses with real users, and design products that solve the deeper problems.
The trap is building a product based on surface-level signals — photos in this case — that feel easy to measure but don’t create lasting value.
Instead, dig into user emotions, motivations, and behaviors. Use tools like empathy maps, affinity diagrams, and surveys. Define metrics that reflect real outcomes, not vanity stats. Sketch and map user flows that align with your product’s unique value.
That is the entire profession in one line.
Test yourself: Blinder’s product design challenge
You are the PM for a new matchmaking app inspired by Blinder’s concept. Your team has just completed surveys showing users want more than photos but are skeptical about trusting dating apps. The CEO wants to prioritize a flashy photo-based swipe interface to attract users quickly. You have limited engineering bandwidth and must choose between developing the story card feature or improving the photo swipe experience.
The call: Which feature do you prioritize and why? How do you justify your decision to the CEO and engineering team?
Your reasoning:
Where to go next
- Learn how to conduct effective user research: User Research Methods
- Master empathy-driven product design: Design Thinking Fundamentals
- Build metrics that matter: Metrics and KPIs
- Create compelling user stories: Storytelling for PMs
- Balance user needs and business goals: Product Strategy