By September 2004, complexity caught up with memory.

For years, environments ran on tribal knowledge. Someone knew where things were. Someone knew how it worked. And as long as that person stayed, everything was fine.

Until they didn’t.

When “only Bob knows” stopped working

Staff turnover exposed a harsh reality:
If your systems only worked because one person remembered them, they weren’t stable.

As environments grew, so did dependencies:

• More servers
• More applications
• More integrations

Memory didn’t scale.

That’s when documentation stopped being optional.

Audits don’t accept explanations

Undocumented IT failed audits — every time.

Not because the systems were wrong, but because no one could prove how they worked. Auditors didn’t care that things “usually ran fine.” They wanted diagrams. Inventories. Procedures.

Network maps.
Server lists.
Recovery steps.

Microsoft’s tools quietly encouraged repeatability. Standard builds. Consistent configurations. Predictable environments.

And with that came the realization: if you can’t write it down, you can’t reliably support it.

The beginning of process-driven support

September 2004 marked the start of process over personality.

Support stopped being about who you called and started being about what happened next.

Documentation didn’t slow businesses down — it protected them. It made growth possible. It made transitions survivable.

And it marked the beginning of professional IT support as a discipline, not a favor.

The businesses that embraced this shift built resilience.
The ones that didn’t kept hoping Bob wouldn’t leave.

Published by Kevin Fream

Many people don't understand their current situation and become frustrated in business and life, so I created the Delta Method and wrote the #1 Best-Seller "Change Your Game" - as featured at Harvard and NASDAQ as well as national TV news. Streamline your technology for competitive advantage using vetted IT support and take a divergent approach to personal growth. View all posts by Kevin Fream