Almost every growing organization has them: a spreadsheet in finance, another in programs, one in development, one in operations, and one that only a single person fully understands. Nobody decided to build five parallel systems. Each one was a reasonable answer to a real need on a particular day.
The problem isn't that spreadsheets exist. It's what they tell you about the official systems — and what they quietly cost.
Why spreadsheets appear
A spreadsheet usually appears because the official system can't do something people need. It can't produce the report a funder asked for. It can't hold the extra field a program needs. It's too slow to change, or nobody is sure who is allowed to change it. So someone exports the data, adds what's missing, and carries on. That's a compensating behavior: sensible for the person, costly for the organization.
What it costs
- →Time. Every export, copy, and reconciliation is staff time that doesn't go to the mission.
- →Trust. When two versions disagree, someone has to decide which is right, and people stop being sure.
- →Continuity. The logic of the spreadsheet often lives with one person. When they're away or leave, the process stops.
- →Risk. Sensitive information ends up in files with no consistent access control or backup.
- →Decisions. Leadership reports built from several unreconciled sources are slower to produce and harder to defend.
Read the spreadsheet as a signal
Instead of asking how to eliminate a spreadsheet, ask what it is compensating for. Each one points to a gap in a process, a limitation in a platform, or a decision no one has made about who owns the information. Those are the things worth fixing.
Questions that help:
- 1.What does this spreadsheet do that the official system can't?
- 2.Who built it, who maintains it, and who else understands it?
- 3.Where does its data come from, and where does it go next?
- 4.What happens to the work if this file is lost or this person is unavailable?
- 5.Is there another spreadsheet that overlaps with it?
A shadow process isn't a failure of your staff. It's a message from them about where the official system doesn't fit the work.
What to do about it
Resist the urge to ban spreadsheets or to buy a platform to replace them all. Start by mapping them: what exists, what each one is for, and how they connect. Then decide, one at a time, whether the right answer is to fix a process, adjust the existing system, connect two tools, or leave a spreadsheet exactly as it is. Sometimes the spreadsheet is the right tool.
That mapping — listening to the people who use these files and tracing the information — is a central part of what a PILLAR Assessment does.