You Were Great at Your Job. Then You Got Promoted
You were good at your job. Really good. And the company noticed. You knew the work, and you solved problems. Nobody had to keep telling you what to…
Most organizations know when they have a staffing problem. They know when they have a funding problem. They know when demand exceeds capacity. But there is another problem that can quietly affect every one of those areas without ever appearing as a line item on a financial statement: poor data.
A duplicate record does not send you an invoice. An outdated spreadsheet does not show up as an expense. An incorrectly entered number does not appear in your budget. But poor data costs money. It costs time, wastes resources, creates unnecessary work, and leads to bad decisions. Perhaps most dangerously, it can convince leadership that something is true when it isn’t. That is the hidden cost of poor data.
Bad Data Creates a False Version of Your Organization
Every decision you make is based on what you believe to be true. How many people did we serve? Which programs are growing? Where is demand coming from? How much does it cost us to provide a service? Which donors are still active? How many volunteers do we need? Where should we invest additional resources? Those questions are answered with data. If the data is wrong, leadership isn’t simply missing information. Leadership is operating from a false picture of the organization.
That distinction matters. Imagine a program reports serving 1,000 people. Leadership sees that number and makes decisions based on it. Staffing levels may change, funding may be redirected, a grant proposal may cite the number, and the board may use it to evaluate performance. But what if the actual number was 750? Or 1,300? The problem isn’t simply that the report was inaccurate. Every decision that followed the report may also have been wrong.
Poor Data Multiplies
One of the reasons poor data becomes so expensive is that a single error rarely stays in one place. Someone enters information incorrectly. That information gets exported into a spreadsheet. The spreadsheet feeds a monthly report. The monthly report feeds a dashboard. The dashboard feeds a board presentation. The board presentation influences next year’s budget. One incorrect piece of information has now traveled through the organization and become part of multiple decisions.
And because each new report appears professional and organized, the original error becomes increasingly difficult to see. A polished dashboard built on bad data is still a bad dashboard. It just makes the bad information easier to believe.
Then Comes the Cost of Cleaning It Up
Organizations often underestimate how much staff time is spent fixing information. Someone notices two records that appear to be the same person. Someone else has to determine which record is correct. An address is missing. A phone number is formatted incorrectly. A program name was entered three different ways. A spreadsheet contains information that doesn’t match the database. Someone has to investigate, then someone has to correct it, then someone has to determine whether the incorrect information was already used somewhere else.
Ten minutes here, twenty minutes there, an hour reconciling two reports, three people exchanging emails trying to determine which number is correct. None of that work advances the mission. It is rework, and rework is one of the most expensive forms of waste because you are paying someone to do work that should not have been necessary in the first place.
The Spreadsheet Problem
Spreadsheets are incredibly useful tools. They are also very good at creating multiple versions of the truth. Consider a familiar situation: a staff member creates a spreadsheet and emails it to someone. That person makes a change. Another copy gets saved to a shared drive. Someone downloads it and makes another change. Soon the organization has Final.xlsx, Final Updated.xlsx, Final Updated 2.xlsx, and Final USE THIS ONE.xlsx. And somewhere, someone is still using the first version.
The problem isn’t Excel. The problem is that the organization never established a single source of truth. When multiple systems contain different answers to the same question, staff members are forced to decide which answer they believe. That isn’t data management. That is guessing.
Poor Data Creates Labor
One of the easiest ways to find the financial cost of poor data is to look at the labor surrounding it. Think about how often people in your organization enter the same information more than once, manually reconcile two systems, correct reports before they can be used, search for information that should be easy to find, or ask another employee what a number means. How often do you rebuild reports because the original information wasn’t reliable?
Every one of those activities has a labor cost. Suppose five employees each spend just 30 minutes per day searching for information, correcting records, reconciling spreadsheets, or entering the same information into multiple systems. That is 2.5 hours per day, approximately 12.5 hours per week, and more than 600 hours per year. And that is before considering the cost of decisions made using incorrect information. Poor data can quietly consume the equivalent of weeks or even months of staff capacity.
The Cost Gets Bigger When the Data Leaves the Organization
Internal mistakes are expensive. External mistakes can be worse. Nonprofits routinely provide data to funders, government agencies, boards, auditors, donors, community partners, and the public. Once you report a number externally, you are attaching your organization’s credibility to it.
If different reports contain different numbers, people notice. Why does the annual report say one thing while the grant application says another? Why did last month’s board report show 4,200 people served while this month’s historical report shows 3,700? Why can’t anyone explain where the number came from? The issue quickly stops being about data. It becomes an issue of trust.
Better Data Does Not Mean More Data
This is where organizations frequently make another mistake. They recognize that their data isn’t good, so they start collecting more of it: more fields, more forms, more spreadsheets, more reports, more required information. But collecting more data does not improve bad data. Sometimes it makes the problem worse.
Every piece of information you collect creates a responsibility. Someone has to enter it. Someone has to maintain it. Someone has to validate it. And, ideally, someone should actually use it. If nobody uses a piece of information to make a decision, operate a program, satisfy a requirement, or measure something meaningful, ask why you are collecting it.
The goal is not to have more data. The goal is to have the right data and be able to trust it.
There Should Be One Answer
One of the simplest tests of an organization’s data systems is to ask the same question in different departments: How many people did we serve last month? If operations gives one answer, development gives another, and finance gives a third, you don’t have three answers. You have a data problem.
Every important organizational metric should have a clear definition, a defined source, a consistent method of calculation, an owner, and a process for correcting errors. If you cannot explain exactly where a number came from, you should be very careful about making decisions with it.
Data Quality Is an Operations Issue
Data is often treated as an IT responsibility. It isn’t. Technology can help store information, validate entries, automate calculations, and reduce mistakes. But technology cannot decide what your organization means by “served.” It cannot determine which information actually matters. It cannot create consistency if every department follows a different process.
Data quality begins with operations. Define the process. Define the information the process creates. Determine where that information lives. Decide who owns it. Then build technology around that structure, not the other way around.
Start With the Decisions
If you want better data, don’t begin by asking what data you should collect. Start with what decisions you need to make, then work backward. If you need to decide whether to expand a program, what information would help you make that decision? If you need to determine staffing levels, what information would you need? If you need to understand whether a program is effective, what would you need to measure?
Those questions tell you what data actually matters. Everything else should have to justify why it exists.
Data Is King — But Only If You Can Trust It
Organizations increasingly talk about becoming data-driven. That sounds sophisticated. But being data-driven isn’t automatically a good thing. If your data is wrong, becoming more data-driven simply allows you to make bad decisions faster and with greater confidence.
The goal should not be to create more reports. It should not be to build more dashboards. And it certainly should not be to collect information simply because software gives you a place to put it. The goal is much simpler: know what is happening inside your organization well enough to make good decisions about what should happen next.
That requires accurate information, consistent definitions, reliable systems, clear ownership, and processes designed to prevent errors instead of constantly correcting them afterward. Because poor data doesn’t just create bad reports. It creates wasted labor, wasted resources, missed opportunities, incorrect decisions, and eventually lost trust.
Those costs may never appear on your financial statements. But you are paying them anyway.