Behavioral & Communication · intro
Customer Obsession
User-centered tradeoffs.
Mental model
Customer obsession is not saying yes to whatever they ask. It is taking their underlying problem seriously, sometimes by shipping something they did not ask for. One customer's complaint is a hypothesis, not proof — go check whether it generalizes.
How to study Customer Obsession
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use STAR interview method (Wikipedia), Know Your Customers' Jobs to Be Done (Christensen et al., HBR), Opportunity Solution Trees (Teresa Torres) to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Customer Obsession with the neighboring concepts in its roadmap. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete STAR: acting on customer feedback and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
STAR: acting on customer feedback
Write a STAR about a time you changed a roadmap based on a single customer signal. Address how you knew it would generalize.
Expected evidence: starStory() returns { situation, task, action, result, metric: { name, unit, before, after }, generalizationEvidence (array of 2+ pieces of disqualifying-or-confirming evidence) }. The checker enforces structure only: four distinct sections of 20+ words, action the longest, 150+ words total, before ≠ after, and the result section must name the metric and state its after value. Aim for 250-350 words — that is the interview bar, not the checker’s.
Open the interactive drill →Review prompts
- A customer asks for a specific feature. What do you establish before building it?
Build evidence
Use a roadmap capstone to turn this concept into working evidence.
Prerequisites
None assigned yet.
Related concepts
None assigned yet.