Why it matters
What this principle is for.
Customer Obsession is where the energy comes from. You can invent impressive technology, solve hard problems, and still fail if you are not meeting a real customer need. Competitor-watching is limiting. Learn from competitors. Live for customers.
At every meeting, the customer is the person who is not in the room. Someone has to advocate for them. If you do not, the room will optimize for the people who showed up.
Many jobs never touch the end customer. That does not let you off. Your customer may be another team. You still work backwards from their need, and you still understand how their work reaches the person who pays.
Mature teams get arrogant. They start believing they know better than the people they depend on. The habit that prevents that: in every decision, ask how this affects the customer.
Calibration
Under, just right, over.
Look for a named customer and a real tradeoff. A story that starts with an internal plan and retrofits a customer line is not this principle. Neither is making a process exception for every loud person, or ignoring a complaint because it is only one.
| Situation | Under | Just Right | Over |
|---|
Examples
What it looks like in the work.
Keep a broken promise in person
A customer was promised a gift by a hard date. The system failed. Someone bought the item locally and put it in the customer's hands. That is not a scalable process. It is a signal: the promise mattered more than the org chart. The next question is what they did so it would not happen again. Heroics without a fix is theater. Heroics that produce a process change are Customer Obsession plus Ownership.
Treat clumsy feedback as an audit
Customers write short, messy, even "simple minded" reviews. Teams that are not obsessed discard them. Teams that are obsessed research each one, because a real person just audited your process for free. The person who can tell you what they changed after a clumsy comment is the one who is actually obsessed.
Say no to a request that would hurt them later
A loud customer wants a shortcut that would help this week and damage the experience for everyone else. The under move is to hide. The over move is to say yes and churn the team. The just-right move is to explain the tradeoff, ship the thing that is best for the collective good, and stay in the conversation. That is how you earn trust with customers without becoming a vending machine.
In the role
Individual and manager.
Individual
You can name who consumes your work and how it shows up in their week. You close the loop when something breaks. You do not wait for an escalation to discover a problem you could have seen in the product.
Manager
You do not let the team hide behind "the business asked for it." You force the doc to name the customer. You kill work that is internally elegant and customer-useless. You teach the team when to say no to one customer so you can say yes to the customer set.
Go deeper
Questions that make the principle concrete.
- Who is your customer, and who is not your customer but should be?
- If your customer is internal, how does their work reach the person who pays?
- When did you last sit with a customer using the product, and what friction did you see?
- Are you implementing the request they asked for, or solving the problem they are actually trying to solve?
- What did you say no to because it would have been a short-term win and a long-term loss for the customer?
- How do customers reach you, and how are you doing against the response time you promised?
- When a problem sits outside your area, what do you do to make sure it stays fixed?
- How will you know the customer had a good week because of your team's work?
- What part of your system causes the most customer pain, and what is the root cause?
- If you cannot hit the date, how do you renegotiate with the customer instead of going silent?
From the blog
Writing that goes deeper.
- Focusing on users is not Customer Obsession
A customer pays you for value. A user is someone you force, addict, or sell.
- Work Backwards From The Customer
Start with the customer outcome, not the technology you already built.
- How To: Write a Working Backwards Doc
The mechanism: write the press release and FAQ before you pick a stack.
Related