Somewhere in your organization, someone is doing data work that nobody hired them to do.
Maybe it's the Executive Director (ED), pulling spreadsheets together at 11pm before a board meeting. Maybe it's the development coordinator who built the donor tracking system because nobody else would. Maybe it's a program manager who keeps their own Excel file because the main database can't be trusted.
This person is your de facto data manager. They just don't know it, and neither does anyone else.
What a data manager actually does
In large nonprofits, the data manager role is formal. They own the CRM, set entry standards, run quality audits, build reports, and train staff. It's a full-time job.
In small nonprofits, those same tasks still need to happen. They just get distributed invisibly across whoever has the skill and the time, which is usually the wrong combination of both.
Here's what ends up on someone's plate, whether they know it or not:
Record maintenance. Someone has to make sure donor records are accurate and deduplicated. Someone has to decide how names and addresses get formatted. Someone has to catch the duplicates before they compound.
Reporting. Board reports, grant reports, program outcome summaries. Someone builds these. If they're built from scratch every time, that's a data management failure masquerading as a reporting task.
Standards. How does your organization define a "served client"? What counts as a completed program? What's the difference between a lapsed and an inactive donor? If nobody has written these down, nobody is enforcing them, and your data is inconsistent.
System ownership. When your CRM has a problem, who calls the vendor? When a new staff member needs access, who sets them up? When the data looks wrong, who investigates? In small orgs, this often falls to whoever is least afraid of technology.
Why the ED ends up holding it
Small nonprofits rarely hire for data skills. They hire for program knowledge, fundraising relationships, and operational capacity. Data is treated as something that comes with the systems, not something that requires active management.
So when nobody is assigned to it, it floats upward. And the person at the top of most small nonprofits is the ED.
This isn't a failure of leadership. It's a predictable outcome of how small organizations grow. The problem is that EDs are also responsible for strategy, fundraising, board management, and culture. Data work competes with all of that, and it usually loses.
The result: reports that take hours instead of minutes. Databases that staff don't trust. Grant applications that require two weeks of data cleanup to complete.
What to do about it
You don't need to hire a data manager. Most small nonprofits don't have the budget, and that's fine.
What you do need is someone who officially owns it, even at 10% of their time. A named person who sets entry standards, runs a quarterly cleanup, and is the first call when something looks wrong.
A few things that make this work:
Make it explicit. Add data stewardship to someone's job description. Even one line. It changes the psychology of the role.
Start with the most important system. You don't need to fix everything at once. Your donor CRM matters more than your program tracking spreadsheet. Start there.
Write down the standards. A one-page document covering how your organization enters names, addresses, gift types, and program codes prevents 80% of future data quality problems.
If you're not sure where the gaps are, our free Nonprofit Data Health Checklist is a good place to start. It covers the six areas where data management problems show up most often in small nonprofits.
Download the free Nonprofit Data Health Checklist
If you work through it and want to talk through what you find, I'm happy to do a free 30-minute discovery call.
Joshua Barillas is the founder of Prismatic Consulting, a data services firm built exclusively for nonprofits. Learn more about our services or get in touch at hello@prismaticconsulting.us.