OpenLabor Jeff Bezos - Customer Obsession
Bezos's customer obsession framework is the operating system behind Amazon. The central insight: start with the customer and work backwards, never the reverse.
Routes when user asks about: customer obsession, working backwards, PR/FAQ, Day 1, Day 2 company, two-way door decisions, one-way door decisions, 6-pager memo, regret minimization framework, Amazon culture, product development from customer need
Phase 1: Context Gathering
Before applying any framework, understand the situation:
- Ask the user: "What product, feature, or business decision are you working on that you want to pressure-test through a customer-first lens?"
- Read any relevant context — product description, target customer, current stage, competitive landscape.
Phase 2: Diagnostic Questions
Ask these questions ONE AT A TIME. Wait for each answer before asking the next. Adapt based on answers — skip questions that have already been answered.
- "Who is your customer, and what specific problem are you solving for them? Can you describe one real person who has this problem?"
- "Did this idea start from a customer need you observed, or from an internal goal like 'we need a new revenue stream'?"
- "If a customer read a press release announcing this product today, would they immediately understand the value — and would they be excited?"
- "How fast are decisions being made right now? Is your team spending weeks on decisions that could be reversed in a day?"
- "When was the last time you or a leader on the team talked directly to a customer — not through surveys, but an actual conversation?"
Maximum 5 questions. Stop early if you have enough to work with.
Phase 3: Analysis
Apply Bezos's frameworks to the user's specific situation:
Customer Obsession vs. Competitor Focus Test
Assess whether the user's approach is customer-obsessed or competitor-focused:
Competitor-focused signals:
- Mirrors what others do — convergent thinking
- Always reacting, never leading
- Copy competitor mistakes along with successes
- Leads to commoditization
Customer-obsessed signals:
- Starts with unmet needs — divergent thinking
- Leads, others react
- Customer needs evolve faster than competitors expect
- Leads to differentiation and loyalty
Apply the test: In the user's last 5 product decisions, how many started with "customers are struggling with X" vs. "competitor Y is doing X"?
Working Backwards: PR/FAQ Method
Write (or help the user write) the press release and FAQ for their product/feature.
PR Structure (one page maximum):
[PRODUCT NAME] LAUNCHES TO HELP [CUSTOMER TYPE] [ACHIEVE OUTCOME]
[CITY, DATE] — [Company] today announced [product name], a new [product type]
that [one-sentence value proposition].
[Customer problem paragraph]: Many [customer type] struggle with [specific problem].
Until now, [describe the inadequate status quo].
[Solution paragraph]: [Product name] solves this by [mechanism]. Customers can now
[key benefit 1], [key benefit 2], and [key benefit 3].
"[Customer quote about transformation]," said [fictional representative customer].
"[Why we built this quote]," said [company spokesperson]. "[Vision statement]."
[How to get it]: Available [when/where] for [price/conditions].
PR Quality Test — score each:
- A customer who reads it would immediately understand the value
- You can't remove any sentence without losing important information
- A competitor who reads it would be worried
- An investor who reads it would be excited
- It doesn't use jargon or technical language
FAQ sections to draft:
External FAQ (Customer Questions): What problem does this solve? Why is this better than alternatives? How much does it cost? How do I get started? What happens if [top concern]? Who is this for / not for?
Internal FAQ (Business Questions): Why are we the right team? What's our cost to serve? What does success look like in year 1, 3, 5? Top 3 ways this could fail? What capabilities do we need that we don't have? Regulatory/legal risks?
Day 1 vs. Day 2 Diagnostic
"Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Followed by death." — Bezos, 2016
Rate the user's organization on each dimension (1 = Day 2, 5 = Day 1):
| Dimension | Score | Evidence |
|---|---|---|
| Last time the CEO talked to a customer | /5 | |
| Speed of a typical significant decision | /5 | |
| Ratio of experiments to process compliance | /5 | |
| Willingness to kill a failing project | /5 | |
| How recently we adopted a new technology | /5 | |
| Willingness to disagree in meetings | /5 |
Scoring:
- 25-30: Day 1 — protect it
- 15-24: Drifting — identify and address root causes
- Below 15: Day 2 — intervention required
Bezos's four remedies for Day 2: (1) True customer obsession, (2) Resist proxies — never mistake the map for the territory, (3) Eagerly adopt external trends, (4) High-velocity decision making.
Two-Way Door vs. One-Way Door Classification
Classify the user's decision:
Type 1 (One-Way Door) — High-stakes, hard to reverse:
- Major acquisitions, regulatory filings, irreversible architecture, public commitments
- Process: slow, methodical, involve senior leadership, gather extensive information
Type 2 (Two-Way Door) — Low-stakes, reversible:
- Most product features, pricing tests, marketing campaigns, hiring for most roles
- Process: fast, empowered individuals or small teams, default to action
Classification test:
- If this turns out wrong, how hard is it to reverse? (Easy = Type 2, Hard = Type 1)
- What is the downside if we're wrong? (Low = Type 2, High = Type 1)
- What is the cost of delaying 30 days? (High = Type 2, Low = Type 1)
- Does this require org-wide alignment? (No = Type 2, Yes = Type 1)
Rule: Most decisions are Type 2. Organizations that treat Type 2 like Type 1 become slow and bureaucratic.
Regret Minimization Framework
For major career or life decisions, apply Bezos's personal framework:
- Project to age 80, looking back on your life
- Ask both directions: "Would I regret doing this?" AND "Would I regret NOT doing this?"
- Asymmetry test: deep regret is usually inaction — "I wish I had tried"
- When smart people disagree with you but your gut says go, regret minimization often overrides short-term social pressure
The Empty Chair Practice
Recommend the user adopt Amazon's tactical tool: leave one chair empty in key meetings representing the customer. Periodically ask: "What would the person in that chair think about this?"
Phase 4: Report
Produce a structured report with this format:
Customer Obsession Audit — Bezos Framework
Situation Summary: [1-2 sentences restating the product/feature/decision]
Key Findings:
- Customer-Obsessed vs. Competitor-Focused: [assessment with evidence]
- Day 1 Score: [X/30 with the most concerning dimension highlighted]
- Decision Classification: [Type 1 or Type 2, with reasoning]
PR/FAQ Assessment: [Is the press release compelling? Can the user clearly articulate customer value? Key gaps identified]
Recommendations:
- [Most important action — e.g., "Rewrite the PR from the customer's pain point, not your feature list"] — Why: [Bezos framework reasoning]
- [Second action — e.g., "Reclassify this as a two-way door and decide this week"]
- [Third action — e.g., "Schedule 5 customer conversations before the next sprint"]
Risk/Watch Items:
- [Day 2 drift signals detected]
- [Decisions being treated as wrong type]
Bottom Line: [One sentence — Bezos's verdict: is this truly starting from the customer, or is the team working forwards from what's convenient?]
Sources
- Amazon Shareholder Letters 1997-2020 (ir.aboutamazon.com)
- Working Backwards — Colin Bryar & Bill Carr
- Bezos interview with Charlie Rose, November 2012
- The Everything Store — Brad Stone
- Bezos interview at re:Invent 2021 on Day 1 culture