Your data lives in 20 spreadsheets (and that's why nobody can find anything)

We've seen it in volunteering foundations, in early childhood programs, in education nonprofits in Chile and Peru, in social research teams and in organizations that depend on their donors. The cause changes, but the scene is almost identical.

Each program started with its own form. Each form ends up in its own Excel file. Someone copies data from one spreadsheet to another on Friday afternoons. And when the board asks something simple, like how many people we served this year, the answer takes a week and nobody is quite sure it's right.

The problem isn't the tool, it's the mess

When data lives in twenty places, three things happen. First: nobody knows which version is the right one. Second: staff and volunteers wear themselves out doing invisible work, copying, pasting, checking. Third, and most costly: you can't add anything up.

Here's an example we see often. In an attendance spreadsheet, the same person shows up as "Cami", "Camila" and "Camila R.". To Excel, that's three different people. To the team, it's one very committed volunteer. If you can't tell they're the same person, you can't count anything: not how often she came, not how long she's been with you, not whether she also donates.

And then comes the usual temptation: buy a new platform that will fix everything. The problem is that a new platform on top of messy data just moves the mess somewhere more expensive.

Storing data is not the same as looking at it

One idea that helps a lot is to separate two things we tend to mix up. One is where the data is stored. The other is where people look at it.

Once you separate these, a lot opens up. The field team can keep using the form they always use. The finance team can keep looking at their spreadsheet. What changes is that everyone feeds and reads the same database, instead of each keeping their own copy.

That single database makes possible something almost no organization has today: seeing the whole person. The same person who arrived as a volunteer, later joined a program and now donates every month. Today that story is split across three spreadsheets that don't talk to each other. In an organized database, it's a single record.

How to start without breaking anything

Organizing your data doesn't mean switching everything off and starting from scratch. In fact, that usually goes badly. What we recommend is more modest:

• List where your data lives today: every form, every spreadsheet, every folder. Just the list.
• Choose a common format for the basics: name, how to contact the person, program, date. The same everywhere.
• Bring everything into one database, even if at first that database is a well-built spreadsheet. A spreadsheet can be a good bridge.
• Ask each team what they're willing to keep doing by hand. Not everything needs to be automated, and it's better to know up front.
• Start with the 20% of the data that answers 80% of the questions. The rest can wait.

The second-to-last point is the one people skip most, and the one that matters most. Automating something nobody wanted to stop doing creates resistance. Automating what the team hates doing brings relief, and relief is what makes people actually use a new tool.

What happens when your data is in one place

We saw it in an education program that works with preschools and schools. Each center reported in its own spreadsheet, and pulling the progress together took weeks. Before talking about screens, we sorted out what was measured and how. Only then did we build the dashboard.

What matters in that case isn't the technology. It's that the team stopped chasing spreadsheets and started spending its time deciding where to offer support.

If your data lives in twenty spreadsheets today, you're not doing anything wrong. That's how almost every organization grows: one program at a time. But the day you want to tell the full story of your impact, you'll need those twenty spreadsheets to be one.