You Probably Don't Need a Data Person Yet

Most social impact organizations hire their first data person too late or too early. Both are expensive mistakes.

Hire too late and your program director is spending eight hours a week pulling reports that should take forty minutes. Hire too early and you have a full-time salary going toward dashboards nobody opens and reports nobody asked for. Getting the timing right is not that complicated. But it does require being honest about what stage your organization is actually in.

In the beginning, you are the data team

If your organization is in its early years, the honest answer is that a dedicated data hire is not one of your first ten hires. Maybe not your first twenty.

That is not a knock on data. It is a reflection of what early-stage organizations actually need. You need program delivery. You need fundraising capacity. You need operational stability. Data infrastructure built before those foundations are solid tends to get rebuilt anyway. What you do need, even early on, is the ability to answer basic questions about your work: How many students are we serving? Are they showing up? Are they progressing? What are we telling funders?

AI-assisted tools have made this genuinely manageable for a founder or executive director who is willing to invest a few hours learning how to use them. You can draft surveys, clean data in spreadsheets, generate summary analyses, and produce funder-ready visuals without a data team. It is not perfect, but it is good enough for where you are.

The important addition at this stage is fractional expert support. Not a full-time hire. An engagement with someone who can review your data model, sanity-check your analysis, and tell you when something does not add up. Think of it as an editor for your data work. You write the draft. They make sure it holds up.

The signal that it is time to hire

There is a specific moment when your data needs cross a threshold. You will recognize it because it feels like a slow leak. The executive director is spending real hours on data tasks that are not strategic. Program staff are being pulled into data collection and cleanup that is eating into delivery time. Reporting cycles feel like a crisis every single time.

When data work is consistently pulling senior people away from their primary roles, it is time to hire.

The hire that punches above its weight

The right first data hire for a social impact organization is not a data analyst in the traditional sense. You are looking for someone whose core competency is program evaluation and impact measurement, who is also comfortable with data visualization, data systems management, and light data modeling.

This sounds like a lot. It is, and that is the point.

A skilled evaluator with strong technical instincts, equipped with AI tools, can genuinely do the work that used to require two or three people. They can own your data systems, produce your reports, design your measurement frameworks, and communicate findings to a board or a funder. Over time, this role should evolve toward a more strategic function: less time on production work, more time translating data into decisions.

That evolution is only possible if you hire someone who understands the "so what" of your data, not just the mechanics of producing it.

What you should not hire for

Do not hire a data engineer as a full-time employee.

This is not a comment on data engineers. It is a comment on incentive structures. When you hire a full-time data engineer, you are paying them to build things. Once the things are built, you are paying them the same rate to maintain what already exists. The work contracts, but the cost does not.

For most school networks and social impact organizations, data infrastructure needs are better met through off-the-shelf products and project-based engagements. Hire a firm or a freelancer to set up the pipeline. Pay for the outcome, not the ongoing presence. Your internal data hire should not be spending their time on infrastructure. They should be spending it on insight.

Start with the question, not the org chart

Before you write a job description, ask yourself what questions your organization most needs to answer and how long it currently takes to answer them. That gap, between the question and the answer, is what you are actually trying to close.

Sometimes the gap is a hiring problem. More often it is a design problem that a new hire will not fix.

If you are not sure which one you are facing, that is a good place to start a conversation.