Short answer
Product sense connects a clear customer problem to a product decision and the outcome that decision should change.
About Product sense
Product sense is the ability to interpret customer evidence, frame the underlying problem, and choose a product response that can produce a meaningful outcome.
Use this competency for
- Product roles that decide which customer problems deserve investment.
- Work that requires tradeoffs between customer value, business value, and delivery constraints.
Do not use this competency for
- Roles that execute predetermined solutions without responsibility for product decisions.
Important distinctions
Customer research
Customer research produces evidence about people and contexts. Product sense uses that evidence to make a product decision.
Expectations by level
IC1
Individual contributor 1
With guidance, frames a well-defined customer problem for one product area and explains how a proposed change could affect it. Handles familiar evidence and checks assumptions before recommending action.
Observable behaviors
- Summarizes customer evidence without turning requests directly into solutions.
- States the customer problem and intended outcome in a product brief.
- Identifies one assumption that needs validation before delivery.
Examples
- After several users request a button, groups the requests by the task users are trying to complete.
- Before refining a feature, documents the expected user change and asks a reviewer to check the reasoning.
IC2
Individual contributor 2
Independently frames ambiguous problems within a product area and compares possible responses using customer, business, and delivery evidence. Owns the recommendation and its tradeoffs.
Observable behaviors
- Combines evidence from more than one source before defining the problem.
- Compares options against the intended customer and business outcomes.
- Changes or stops a proposal when evidence weakens its rationale.
Examples
- When usage falls in a workflow, compares interviews and product data before choosing what to investigate.
- When two solutions address the same problem, records why one offers a better outcome for the effort.
IC3
Individual contributor 3
Sets problem-framing direction for a team across connected product areas. Handles competing needs and incomplete evidence, and enables others to make coherent product decisions.
Observable behaviors
- Defines decision principles the team applies across related product choices.
- Surfaces conflicts between segment needs before they become roadmap commitments.
- Reviews product decisions for problem clarity, evidence, and intended outcome.
Examples
- When adjacent workflows compete for investment, defines the customer and business tradeoff used to sequence them.
- When evidence remains mixed, narrows the decision and sets a learning step that the team can act on.