Two Ways to See Your Product
Product teams need two distinct perspectives:
The Customer Lens: How users experience the product The Product Lens: How the product is structured
These aren't redundant. They reveal different truths and enable different decisions.
The Customer Lens: Journey View
The customer lens shows experience over time:
What it captures:
- Stages of the relationship (awareness → evaluation → adoption → retention)
- Touchpoints across channels
- Emotions and frustrations
- Pain points and moments of delight
- Paths taken (happy path, edge cases, failures)
Questions it answers:
- Where do users get stuck?
- When do users drop off?
- What feelings dominate each stage?
- Where does the experience break?
Artifacts:
- Customer journey maps
- User flows
- Experience timelines
- Emotion curves
Best for:
- Understanding friction
- Identifying intervention points
- Prioritizing by user impact
- Designing onboarding and retention
The Product Lens: Feature View
The product lens shows structure and capability:
What it captures:
- Feature inventory (what exists)
- Feature relationships (dependencies)
- Architecture (how it's organized)
- Coverage (what's possible)
Questions it answers:
- What can users do?
- How do features connect?
- What's missing?
- Where is complexity concentrated?
Artifacts:
- Feature maps
- Product hierarchy
- Capability matrices
- Architecture diagrams
Best for:
- Planning development
- Managing complexity
- Identifying gaps
- Communicating to stakeholders
Why You Need Both
Customer lens alone misses structure: You might solve a journey pain point with a feature that doesn't fit the product architecture, creating technical debt and inconsistency.
Product lens alone misses experience: You might build features that are logical from a product perspective but don't address actual user needs.
Example:
- Customer lens: "Users struggle to find invoices"
- Product lens: "Invoices are in the billing module"
- Insight: The product organization doesn't match user mental models
Neither lens alone reveals this. Together, they show the disconnect.
Connecting the Two Lenses
Mapping features to journey stages:
- Which features support which journey stages?
- Are there stages with weak feature support?
- Are there features that don't map to any journey stage?
Mapping pain points to product areas:
- Which product areas generate the most pain?
- Are pain points concentrated or distributed?
- Do pain points suggest missing features or poor features?
Mapping personas to usage patterns:
- Which personas use which features?
- Are there features built for one persona but used by another?
- Are there persona needs with no feature support?
Practical Application
In roadmap planning:
- Start with journey pain points (customer lens)
- Map to required capabilities (product lens)
- Prioritize by impact and feasibility
In design reviews:
- Evaluate against journey context (where is the user?)
- Evaluate against product consistency (does this fit?)
In stakeholder communication:
- Use customer lens for user impact
- Use product lens for technical scope
- Connect both for complete picture
In competitive analysis:
- Customer lens: How do experiences compare?
- Product lens: How do capabilities compare?
Building Both Views
Customer lens requires:
- Customer research (interviews, feedback)
- Journey mapping exercises
- Experience tracking (analytics at journey stage)
- Regular updates as experience changes
Product lens requires:
- Feature inventory (what exists)
- Architecture documentation
- Capability mapping
- Regular updates as product evolves
Neither view is static. Both need continuous maintenance to remain accurate.
The Combined View
The most powerful artifact combines both:
Horizontal axis: Journey stages (customer lens) Vertical axis: Feature areas (product lens) Cells: Pain points, opportunities, and capabilities at each intersection
This combined view reveals:
- Where features exist but experience is poor
- Where experience expectations exist but features don't
- Where both are strong (competitive advantage)
- Where both are weak (strategic gap)
Teams that maintain both lenses make decisions with full context. Those with only one operate with partial blindness.