Amazon
Amazon Fire Phone Failure
Estimated impact: $170M write-down
Amazon's Fire Phone launched at $199 with exclusive AT&T distribution, featuring a gimmicky "Dynamic Perspective" 3D effect. It sold poorly — Amazon took a $170M write-down on unsold inventory. Jeff Bezos personally drove the project, and internal skeptics were overridden.
Decision context
Whether to launch a premium-priced smartphone differentiated by a 3D interface gimmick rather than app ecosystem, in a market dominated by iOS and Android.
What the record already said
The document below predates the decision. Everything after it is read from that document alone, so a reader can check each line against the words above it rather than take the reading on trust.
2014 internal product review document showing 3D 'Dynamic Perspective' as primary differentiator over price or ecosystem
Source: Amazon Lab126 Product Team
What a reader could have found without knowing the ending
- Primary differentiator was a gimmick feature no users requested
- Price point ($199 with contract) matched iPhone without matching ecosystem
- No exclusive content or services strategy
- Internal usability testing showed confusion with 3D features
Decision intelligence would have detected confirmation bias in the product team's fixation on Dynamic Perspective despite negative usability signals. The absence of any price disruption strategy — Amazon's core competency — would have flagged a fundamental strategic misalignment.
Written after the outcome was known. Nothing here can be falsified, which is why it sits below the document rather than above it.
What the company’s own filing already carried
Not our reading of a memo. Amazon's own 10-K, filed 2013-01-30 (12 months before the 2014 decision), was read by the audit engine's deterministic structural layer: the same detectors that run on every audit, with no language model involved. Everything below is drawn from the company's own disclosure, before any knowledge of what followed, and never from the decision itself.
Survivable as structured: if the flagged risk fires, the deal has the exits, cushions, or staging to absorb the hit and continue.
The structural layer flagged no unabsorbed condition in this filing.
- This reads the company's own 10-K (filed 12 months before the decision), not the decision memo itself, so it can only understate what a full audit of the memo would surface.
- It reads the structure of the situation, not the trigger: whether a shock to the flagged conditions would be absorbed, never that a shock arrives.
- A reading of a dated filing, not a prediction: every condition can be checked against the company's own 10-K.
Decision anatomy
Red = risk factor present · Green = protective factor present
Biases present in the decision
★ Primary driver · Severity estimated from bias type and decision outcome
Toxic combinations
The curated library this case sits in
Across all 155 curated case studies in our library, by documented outcome:
The library is curated toward documented failures, so this split describes the library, not the base rate of deals. The case above is one row in it.
Lessons learned
- Authority bias: when the CEO personally champions a product, internal dissent is suppressed even at Amazon
- Hardware differentiation through gimmicks (3D effect) cannot overcome ecosystem disadvantages (app gap)
- Exclusive carrier distribution limits addressable market for a product that already has adoption challenges
Source: Austin Carr, "The Real Story Behind Jeff Bezos's Fire Phone Debacle" (Fast Company, 2014) (News Investigation)
These patterns were flaggable in Amazon's own record — before the outcome.
See the full hindsight-stripped audit we ran — no login, no card. Then run the same audit on a deal you have already closed.
Or leave your email, we'll run the audit on a deal of your choosing and send the readout within a business day.
Workflows that fire on decisions like Amazon’s
The same Recognition-Rigor Framework that documents this case audits memos in the same shape — before the outcome forces the lesson.