Which cognitive biases were evident in Federal Bureau of Investigation's collapse?

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

Did these cognitive biases cause Federal Bureau of Investigation'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. Planning Fallacy 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.

All case studies

Catastrophic failureGovernment2005

Federal Bureau of Investigation

FBI Virtual Case File Project Failure

Estimated impact: $170M in taxpayer funds with zero usable output

F14

Decision Quality Index (simulated)

Critical · 5 biases detected, 2 toxic combinations

The FBI's Virtual Case File (VCF) project to modernize its case management system was abandoned after spending $170M over three years. The software was deemed unusable. Requirements changed 36 times during development, and the FBI lacked technical expertise to manage the contractor (SAIC).

Decision context

Whether to continue developing a custom case management system with constantly changing requirements, or adopt commercial off-the-shelf solutions.

Deep hindsight-stripped analysis coming soon. This case is part of our ongoing backfill to reconstruct what was flaggable in the record at decision time. The summary and bias profile below are drawn from primary sources.

Decision anatomy

Monetary stakes

Very high

Dissent suppressed

Time pressure

Present

Unanimous consensus

Decision participants

Dissent encouraged

External advisors

Iterative process

Red = risk factor present · Green = protective factor present

Biases present in the decision

★Planning Fallacy

critical

Sunk Cost Fallacy

high

Overconfidence Bias

high

Anchoring Bias

high

Paradox of Choice

medium

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

3D Decision Knowledge Graph

Federal Bureau of Investigation · 5 biases, 2 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

!Sunk Ship

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

!Blind Sprint

Overconfidence combined with planning fallacy creates unstoppable momentum toward failure.

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

Planning fallacy: the FBI assumed custom software could be built in the same timeline as commercial products despite 36 requirements changes
Sunk cost: each milestone payment made abandonment harder, even as the project fell further behind
Government agencies without internal technical expertise cannot effectively manage large custom software projects

Source: DOJ Office of Inspector General Report 05-07 (2005) (Post Mortem)

Pilot slots available

These patterns were flaggable in Federal Bureau of Investigation's own record — before the outcome.

See the full reasoning 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 a deal of your own

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

Audit your own decision

Workflows that fire on decisions like Federal Bureau of Investigation’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 any high-stakes decision, before commitment

Decision pre-mortem

Run a structured pre-mortem before the decision is final — surface failure modes the room cannot see from the inside.

Run a pre-mortem

For CSOs and CEOs presenting to a board

Board deck pre-presentation audit

Audit a board deck before the presentation — predict the toughest questions the room will ask.

Audit your board deck

See the full audit-tool surface.

Related cases in Government

Partial failure2001

US Department of Defense / Lockheed Martin

F-35 Joint Strike Fighter Cost Overruns

Failure2013

UK Department for Work and Pensions

UK Universal Credit IT Disaster

Exceptional success2020

U.S. Federal Government (HHS/DoD)

Operation Warp Speed: COVID-19 Vaccine Development

Failure2013

US Centers for Medicare & Medicaid Services (CMS)

Healthcare.gov Launch Failure

All case studies

Catastrophic failureGovernment2005

Federal Bureau of Investigation

FBI Virtual Case File Project Failure

Estimated impact: $170M in taxpayer funds with zero usable output

F14

Decision Quality Index (simulated)

Critical · 5 biases detected, 2 toxic combinations

Decision context

Whether to continue developing a custom case management system with constantly changing requirements, or adopt commercial off-the-shelf solutions.

Decision anatomy

Monetary stakes

Very high

Dissent suppressed

Time pressure

Present

Unanimous consensus

Decision participants

Dissent encouraged

External advisors

Iterative process

Red = risk factor present · Green = protective factor present

Biases present in the decision

★Planning Fallacy

critical

Sunk Cost Fallacy

high

Overconfidence Bias

high

Anchoring Bias

high

Paradox of Choice

medium

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

3D Decision Knowledge Graph

Federal Bureau of Investigation · 5 biases, 2 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

!Sunk Ship

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

!Blind Sprint

Overconfidence combined with planning fallacy creates unstoppable momentum toward failure.

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

Planning fallacy: the FBI assumed custom software could be built in the same timeline as commercial products despite 36 requirements changes
Sunk cost: each milestone payment made abandonment harder, even as the project fell further behind
Government agencies without internal technical expertise cannot effectively manage large custom software projects

Source: DOJ Office of Inspector General Report 05-07 (2005) (Post Mortem)

Pilot slots available