During a series of interviews I conducted with nonprofit leaders about how they stay on top of data and make day-to-day decisions, I started with a very practical assumption: maybe the problem was workspace design.

Do leaders use one monitor or two? Do they work mostly from laptops or phones? Do they check dashboards every morning? Do they use spreadsheets, CRM systems, email reports, Slack, or something else?

But after several conversations, a different pattern became more interesting than the hardware. The issue was not whether a leader had a perfect setup. The issue was that most leaders already had an information system — but it was not always designed intentionally. It was built from habits.

Some leaders lived in email. Some used Slack, Asana, CRMs, fundraising platforms, spreadsheets, and shared documents. Some relied heavily on direct reports. Some preferred written summaries. Some still took handwritten notes. Some worked from a home office, some from a laptop, some from a phone while moving between meetings.

In other words, the real operating system was not the dashboard. It was the leader's behavior.

That creates a problem for anyone trying to build better tools for nonprofit organizations. A dashboard may be beautifully designed, but if it requires leaders to change how they already work, it may fail before it becomes useful. The problem with many dashboards is not that they show the wrong chart. The problem is that they assume people want to change.

I am not sure they do.

Most leaders do not wake up thinking, "I need a new workflow." They wake up thinking, "What needs my attention today?" If a tool helps answer that question inside their existing habits, it has a chance. If it demands a new habit first, it becomes one more thing competing for attention.

Nonprofits can build better data practices by paying less attention to ideal workflows and more attention to actual behavior. Here are four ways to start.

1. Stop assuming that "best practice" means "real practice."

There are many good recommendations for how leaders should work with information: use a dashboard, centralize data, create a single source of truth, review metrics regularly, avoid managing through email, and standardize reports.

All of these can be useful. But they are not always how leaders actually work.

One leader I interviewed had access to dashboards and fundraising systems, but still relied on short written updates from department heads to understand what had happened during the week. Another preferred monthly financial reports, staff updates, and email because those channels were already part of the organization's rhythm. Another used a mix of laptop, phone, Zoom, email, news, board conversations, and team meetings.

None of this looks like a clean best-practice diagram. But it is real. And real behavior matters more than ideal behavior.

If a leader already trusts email, then email is not just a bad habit to eliminate. It may be the place where the organization's most important signals already arrive. If a leader relies on staff updates, that may not be inefficiency. It may be the way context travels. If a leader uses a spreadsheet, it may be because the spreadsheet is familiar, flexible, and "good enough" under pressure.

Before asking leaders to adopt better practices, we should ask what practices they already use — and why those practices survived.

2. Recognize that workflows are usually accumulated, not designed.

In theory, an organization chooses its systems logically. In practice, many workflows are inherited.

A board prefers email. A development director uses one fundraising platform. A finance team sends monthly reports. A program team tracks participants in a spreadsheet. A staff member creates a useful document, and three years later everyone still depends on it. A leader starts checking one report every Friday, not because it is perfect, but because it became part of the week.

Over time, these pieces become the organization's information culture.

A new tool may promise clarity, but it also asks for new behavior: log in here, check this daily, update this field, trust this source, stop asking that person, stop using that spreadsheet, stop forwarding that email.

That is not a small request. It is a cultural request.

For many nonprofits, the better starting point may not be replacing existing habits. It may be lightly improving them. Make the staff update more structured. Make the email summary clearer. Make the spreadsheet easier to interpret. Bring the most important signal into the meeting where decisions already happen.

Change is easier when it does not begin by insulting the old way.

3. Design for attention, not just access.

Many data tools are built around access: give leaders access to more information, more metrics, more dashboards, more filters, more real-time updates. But access is not the same as clarity.

In several interviews, the real tension was not a lack of information. It was too much information arriving through too many channels: email, phone, meetings, Slack, spreadsheets, dashboards, news alerts, board updates, staff updates, and donor systems.

That means the scarce resource may not be data. It may be attention.

This is especially important for nonprofit leaders, who often carry multiple roles at once. They are not only reviewing numbers. They are managing people, donors, programs, board relationships, community needs, grants, operations, crises, and public events. In that context, "more visibility" can become more noise.

A useful data system should not simply answer, "What can we show?" It should answer, "What deserves attention now?" What changed? What is late? What is risky? What is improving? What needs a decision? What can safely wait?

The best dashboard may not be the one with the most information. It may be the one that protects the leader from unnecessary information.

4. Build around trust.

In nonprofits, data does not travel alone. It travels with trust.

A leader may trust a finance report because of the person who prepared it. They may trust a program update because it comes from someone close to the work. They may trust a board email because it reflects political reality. They may trust a spreadsheet because they know exactly how it was built.

This is why purely technical solutions can miss the point. A dashboard may show the correct number, but the leader may still ask, "Where did this come from?" or "Who checked it?" or "Is this what the program team is actually seeing?"

Data culture is not only about measurement. It is about confidence.

If leaders do not trust the source, the format, the timing, or the interpretation, they will fall back on old habits. They will ask a person. They will search email. They will open the old spreadsheet. They will wait for the monthly meeting. That is not irrational. It is how people protect themselves when decisions matter.

So the goal should not be to remove people from the data process. In many cases, the goal should be to make human judgment and organizational data work together. A good system should show the number, but also preserve context: who updated it, what changed, why it matters, and what decision it supports.

Ultimately, the question is not whether nonprofits need dashboards. Many do. The question is whether dashboards are designed around how leaders actually behave.

Some of the most important practices in nonprofit leadership cannot be reduced to a chart: trust, judgment, urgency, relationships, timing, and experience. But the way leaders consume information can be observed. And once we observe it honestly, we may see that the future of nonprofit data is not just better visualization. It is better fit.

The next generation of nonprofit tools should not begin with the assumption that leaders want to become different people. It should begin with the habits leaders already have — and then make those habits clearer, lighter, and more useful.