top of page

The Most Important System is Carrie's Spreadsheet - Stefani's Breifs

Carrie's spreadsheet knows why. - 1 min read

The Most Important System is Carrie's Spreadsheet - Stefani's Breifs

By Stefani Markov

Authors

IMG_20240221_092528bright.jpg

Stefani Markov

Lean Six Sigma Black Belt, PMP, and MOS: Expert(Microsoft)

Founder & CEO

Stefani@metrixltd.com

  • LinkedIn
Photo OM.jpg

Orlin Markov

Lean Six Sigma Black Belt, PMP

Founder & CEO

Orlin@metrixltd.com

+359 876 153 098

  • LinkedIn

8/7/26, 8:00 AM





If you've spent any time around process improvement or transformation projects, you've probably come across the awkward moment where somebody quietly says, "We don't actually use the system for that".


Instead, there's an Excel file. Usually with a reassuringly authoritative name like Final_FINAL_v7_Updated_USE_THIS_ONE.xlsx, because nothing inspires confidence quite like version control implemented through optimism.


Nobody set out to make it important, but it became important because it solved a problem the official process didn't. Over time it learned who to chase, which invoices needed escalating, which approvals always stalled, and which exceptions could wait until Friday. Eventually, people stopped asking the system and started asking the spreadsheet.


Meanwhile, the enterprise platform sits exactly where it was intended to sit. It was implemented over eighteen months, governed through steering committees, supported by change management, and proudly demonstrated in town halls. It can produce excellent dashboards.


Carrie's spreadsheet, on the other hand, knows why invoice 457812 is still blocked, that Procurement forgot to request an update to the vendor master again, and that if you don't email Brian before lunch, the payment run will quietly become tomorrow's problem.


When this eventually gets noticed, the spreadsheet is usually treated as the problem. That's a reasonable concern. Critical processes shouldn't depend on one spreadsheet, one macro, or one person remembering not to delete column G.

The more interesting question isn't whether the spreadsheet should exist. It's why somebody needed to build it in the first place.


Carrie didn't create it because she objected to governance. She created it because the work still had to get done, and the official process wasn't quite managing it. The spreadsheet wasn't competing with the process; it was compensating for it.



That's why these files have an uncanny ability to outlive the people who created them. Carrie leaves. The spreadsheet doesn't.


Five years later it's still called Carrie's Spreadsheet, still opened every Tuesday by people who've never met Carrie, still running a macro nobody wants to touch because nobody is entirely certain what would happen if it stopped.



That's the awkward thing about workarounds. They begin as someone solving a problem the official process hasn't quite solved yet. Leave them alone for long enough and they stop looking like exceptions altogether. The documented process describes how the organisation thinks work happens. Carrie's spreadsheet describes how it actually does.



#ProcessManagement #OperationalExcellence #ContinuousImprovement #DigitalTransformation #ChangeManagement




Ready? Let's talk.




bottom of page