// p log

Lessons from the FBI’s Trilogy Failure

|Software EngineeringCivics

In the early 2000s, the FBI embarked on a massive IT modernization project called "Trilogy". It was supposed to drag their outdated systems into the modern era, but instead, it became a textbook example of project failure.

When things go this wrong it’s rarely because of bad technology, rather it's due to bad planning. Here are the three critical planning mistakes that sank the Trilogy project, and the simple lessons you can use to keep your own projects on track.

1. Skipping the Roadmap (Inadequate Planning)

After the September 11th attacks, the FBI was under massive pressure to get this system up and running fast. To speed things up, they skipped the normal planning phases and rushed straight into buying contracts.

It backfired completely. Because they didn't take the time to map things out, the project's scope ballooned by a massive 80%.

  • The Communication Gap: The FBI didn't clearly outline their objectives, meaning stakeholders couldn't give helpful feedback to refine the plan.
  • No Common Standards: The FBI lacked "Enterprise Architecture", or a master plan for how their organization's technology should fit together. Without this, contractors had no standard rules to follow, resulting in total chaos.

2. Overestimating Your Team's Superpowers (Bad Resource Planning)

It is easy to look at a project and think, "We'll figure it out as we go." But the FBI completely underestimated the actual skills and manpower needed to support their contractors.

Two specific mistakes doomed their resource management:

  • The Tool Mismatch: The main contractor used a complex scheduling tool that the FBI's internal team couldn't figure out how to use.
  • The "DIY" Integrator Mistake: Instead of hiring a professional, experienced project integrator to manage how different contractor pieces fit together, the FBI tried to use their own unqualified internal staff to save money.
  • Audit your tools first: Never adopt a complex tool or software unless you are 100% sure your team is trained to use it.
  • Know your limits: If your team doesn't have the expertise to manage a complex part of the project, budget for outside help before you start.

3. Building Without a Target (Runaway Requirements)

At the start, the FBI didn't actually know what they wanted from the software. Instead of giving clear guidelines, they just trusted the contractors to guess what was needed.

Because there was no documented baseline, the requirements kept changing. Years into the project, they were still trying to define what they were building. By 2004, the software had turned into an unmanageable "monster".

  • Lock in a baseline: If you don't document your starting requirements, you have no way to measure if you are actually making progress.
  • Hire a dedicated bridge-builder: A major reason Trilogy struggled was the lack of a strong Project Manager early on to act as a buffer and translator between the FBI stakeholders and the technical contractors.

What was the saying... Measure (plan) twice and cut (code) once.