Which cognitive biases were evident in Hewlett-Packard's collapse?

5 bias patterns are documented in this case, led by Confirmation Bias. The full set: Confirmation Bias, Anchoring Bias, Authority Bias, Overconfidence Bias, Sunk Cost Fallacy. Each is mapped to Decision Intel's 22-bias R²F taxonomy with stable IDs and academic citations.

Did these cognitive biases cause Hewlett-Packard's collapse?

Decision Intel identifies reasoning-risk indicators correlated with poor outcomes — it does not claim to establish causation. That honesty is the procurement weapon: a CSO can defend a score that names the risk indicators a committee should pressure-test, not one that pretends to prove the cause. Confirmation Bias and the other documented patterns were detectable in the reasoning before the outcome was known; whether they caused it is a question no audit can settle — too many other factors (market, timing, execution) are in play. A reasoning audit names the risk indicators a committee should pressure-test, not a verdict it should accept.

What is Decision Intel's reasoning audit?

Decision Intel runs a Recognition-Rigor Framework (R²F) audit on strategic memos, detecting cognitive biases from a 22-bias canonical taxonomy and producing a Decision Quality Index (DQI) score. The audit produces a hashed, tamper-evident Decision Provenance Record (DPR) suitable for audit-committee review.

Was the risk in the Hewlett-Packard decision visible before the outcome?

Yes, in part. HP press release (Aug 18, 2011); Deloitte due diligence report findings (cited in SEC complaint); HP Board meeting minutes (summarized in proxy filings) predates the decision and already described the situation in its own words. Read against that document alone, 4 structural conditions are identifiable without any knowledge of what followed: Paying 12.6x revenue for a software company — extreme multiple requires extreme certainty about revenue quality; Internal due diligence flagged hardware revenue classified as software — a fundamental accounting concern dismissed by leadership; CEO framing Autonomy as "a different kind of platform company" without quantitative justification — vague strategic narrative overriding financial analysis; Deal negotiated rapidly under time pressure after Dell's interest in Autonomy was rumored — competitive urgency distorting valuation discipline. This is a reading of a dated source, not a prediction, and every line can be checked against the quoted passage.

All case studies

Catastrophic failureTechnology2011

Hewlett-Packard

HP Autonomy $11.1B Acquisition Write-Down

Estimated impact: $8.8B write-down

F14

Decision Quality Index (simulated)

Critical · 5 biases detected, 4 toxic combinations

HP acquired British software company Autonomy for $11.1 billion in August 2011, paying a 64% premium. Within 13 months, HP wrote down $8.8 billion — 79% of the purchase price — alleging that Autonomy had inflated revenues through accounting improprieties. Due diligence had flagged concerns about Autonomy's hardware sales being classified as software revenue, but HP leadership dismissed these warnings.

Decision context

Whether to proceed with the Autonomy acquisition at 12.6x revenue despite due diligence red flags about revenue recognition practices and accounting irregularities.

Before the outcome was known

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.

Press release · 2011-08-18

HP's August 18, 2011 press release: "HP today announced it has entered into a definitive agreement to purchase Autonomy Corporation plc for approximately $11.1 billion... Autonomy is a leader in the fast-growing area of information management and next-generation enterprise search... HP expects the acquisition to be accretive to HP's non-GAAP earnings per share." CEO Léo Apotheker stated: "Autonomy will be a different kind of platform company." Internal due diligence teams had flagged that a significant portion of Autonomy's "software" revenue was actually derived from low-margin hardware sales resold as bundled software — a concern that was escalated to leadership but overridden.

Source: HP press release (Aug 18, 2011); Deloitte due diligence report findings (cited in SEC complaint); HP Board meeting minutes (summarized in proxy filings)

Visible at the time · 4 items

What a reader could have found without knowing the ending

Paying 12.6x revenue for a software company — extreme multiple requires extreme certainty about revenue quality
Internal due diligence flagged hardware revenue classified as software — a fundamental accounting concern dismissed by leadership
CEO framing Autonomy as "a different kind of platform company" without quantitative justification — vague strategic narrative overriding financial analysis
Deal negotiated rapidly under time pressure after Dell's interest in Autonomy was rumored — competitive urgency distorting valuation discipline

Interpretation, not evidence

DI Platform would flag: CRITICAL confirmation bias — leadership dismissing internal DD red flags that contradict the strategic thesis. The revenue classification concern is not a minor discrepancy but a fundamental question about whether the business being acquired is actually a software business. Authority bias: CEO Apotheker's conviction overriding expert due diligence findings. Sunk cost: months of deal preparation creating momentum toward closing despite emerging negative signals. Toxic combination "Echo Chamber + Sunk Ship" detected. Recommendation: HALT the deal until an independent third-party auditor re-evaluates Autonomy's revenue breakdown. The due diligence red flags warrant a minimum 60-day pause for forensic accounting review.

Written after the outcome was known. Nothing here can be falsified, which is why it sits below the document rather than above it.

Decision anatomy

Monetary stakes

Very high

Dissent suppressed

Time pressure

Present

Unanimous consensus

Decision participants

Dissent encouraged

External advisors

Yes

Iterative process

Red = risk factor present · Green = protective factor present

Biases present in the decision

★Confirmation Bias

critical

Anchoring Bias

high

Authority Bias

high

Overconfidence Bias

high

Sunk Cost Fallacy

high

★ Primary driver · Severity estimated from bias type and decision outcome

3D Decision Knowledge Graph

Hewlett-Packard · 5 biases, 4 toxic combinations

Drag to rotate · Scroll to zoom · Click to explore

Decision

Critical

High

Medium

Toxic

Bias Intensity Profile

Severity × confidence across 5 detected biases

Toxic combinations

!Echo Chamber

Group members reinforce each other's views, systematically filtering out dissenting signals.

!Sunk Ship

Commitment to a failing course escalates to justify sunk costs, even as evidence mounts.

!Winner's Curse

Auction-dynamic anchoring drives bids above intrinsic value; "strategic necessity" and "competitive process" language flag the deal-fever pattern.

!Synergy Mirage

Synergy claims without a named operational mechanism, accountable executive, or 90-day milestone — the canonical M&A failure mode (70-90% of acquisitions miss projected synergies).

The curated library this case sits in

Across all 155 curated case studies in our library, by documented outcome:

123

documented failures

partial / mixed

documented successes

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.

■ Failure■ Partial■ Success

Lessons learned

When due diligence flags accounting irregularities, dismissing those warnings because of strategic conviction is a textbook confirmation bias failure.
Paying extreme revenue multiples requires extreme certainty about the quality of those revenues — not the opposite.
The sunk cost of months of deal negotiation can create momentum that overrides rational assessment of new negative information.

Source: HP SEC filing (8-K, November 20, 2012); Autonomy acquisition proxy statement (2011); U.S. v. Sushovan Hussain, N.D. Cal. No. 16-cr-00462 (SEC Filing)

Pilot slots available

These patterns were flaggable in Hewlett-Packard'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.

See a live audit · no login Audit your own memo

Or leave your email, we'll run a strategic memo of your choosing and send the readout within a business day.

Audit your own decision

Workflows that fire on decisions like Hewlett-Packard’s

The same Recognition-Rigor Framework that documents this case audits memos in the same shape — before the outcome forces the lesson.

For CSOs and Heads of Strategic Planning

Strategic memo audit

Audit a strategic memo for cognitive bias and forecast errors before the board sees it.

Audit a strategic memo

For Heads of Corp Dev and M&A advisors

M&A bias audit

Audit an acquisition thesis for the three named M&A failure patterns: Synergy Mirage, Conglomerate Fallacy, Winner's Curse.

Audit an acquisition thesis

For Heads of Corp Dev and Investment Committee chairs

IC memo pre-vote stress test

Stress-test an investment committee memo before the vote — catch Synergy Mirage, Winner's Curse, and Conglomerate Fallacy.

Audit your IC memo

See all 6 workflows for the full audit-tool surface.

Related cases in Technology

Failure2011

Google

Google+ Social Network Failure

Exceptional success2012

NVIDIA

NVIDIA GPU Pivot to AI and Deep Learning

Failure2015

IBM

IBM Watson Health Strategic Failure

Failure2021

Zillow

Zillow iBuying Program Shutdown

Toxic combinations

!Echo Chamber

Group members reinforce each other's views, systematically filtering out dissenting signals.

!Sunk Ship

Commitment to a failing course escalates to justify sunk costs, even as evidence mounts.

!Winner's Curse

Auction-dynamic anchoring drives bids above intrinsic value; "strategic necessity" and "competitive process" language flag the deal-fever pattern.

!Synergy Mirage

Synergy claims without a named operational mechanism, accountable executive, or 90-day milestone — the canonical M&A failure mode (70-90% of acquisitions miss projected synergies).

The curated library this case sits in

Across all 155 curated case studies in our library, by documented outcome:

123

documented failures

partial / mixed

documented successes

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.

■ Failure■ Partial■ Success

Lessons learned

When due diligence flags accounting irregularities, dismissing those warnings because of strategic conviction is a textbook confirmation bias failure.

Paying extreme revenue multiples requires extreme certainty about the quality of those revenues — not the opposite.

The sunk cost of months of deal negotiation can create momentum that overrides rational assessment of new negative information.