There is a particular kind of meeting that happens in organizations across Africa and beyond. A report gets presented. The numbers are clear. And then the most senior person in the room says, “I hear what the data is saying, but in my experience…” and the decision goes the other way.

This is not ignorance. This is what happens when data meets power.

When an organization installs a new data system or builds its first real dashboard, it tells itself a clean story: we are becoming more efficient, more evidence-based, more modern. What it rarely admits is the messier truth underneath that every new system comes with a new map of who matters. Who gets visibility. Who gets funded. And whose judgment is suddenly being questioned by a spreadsheet.

Introducing data infrastructure into a traditional organization is never just an IT upgrade. It is, quietly and inevitably, a redistribution of power.

The Dashboard is Never Neutal

Before a single number appears on a screen, someone has to decide which numbers go there. That decision, what to measure, what to display, what to leave out is one of the most consequential political acts in any organization, and it almost never gets treated as one.

Choose to measure community outreach calls and the program team looks productive. Choose to measure cost-per-beneficiary and suddenly the finance department has ammunition. Choose to track response times and IT becomes either a hero or a liability. The dashboard doesn’t just reflect organizational priorities, it creates them. And the department whose work is most legible in numbers will almost always win the budget conversation, regardless of whose work is actually most valuable.

This is what organizational scholars call dashboard diplomacy . The use of curated metrics to secure approvals, justify decisions, and quietly bury inconvenient trends. It is not always deliberate. But it is always present.

The Gatekeepers and their Keys

For most of the history of institutional computing, the IT department held something close to a monopoly on organizational intelligence. They controlled the servers, managed the databases, and were the only people who could run a report. That monopoly was not just technical, it was political. Information is leverage, and they had all of it.

Then came self-service analytics. Leadership began demanding that managers access their own data, build their own reports, make their own decisions without waiting three weeks for IT to generate a spreadsheet. For organizations genuinely committed to efficiency, this was progress. For the teams whose influence depended on being the only people who understood the data, it felt like an existential threat.

The resistance that followed was rarely open. It looked like slow response times, overly complex access procedures, warnings about data integrity, and endless requirements for formal data requests. It looked, from the outside, like bureaucracy. From the inside, it was survival.

When the Junior Analyst Contradicts the Director

In many African public sector and corporate environments, authority is not just organizational, it is cultural. Deference to age, seniority, and title is deeply embedded in how institutions function. A director who has spent twenty years in a ministry does not expect to have their judgment challenged in a meeting. Certainly not by someone who joined eighteen months ago and is holding a laptop.

But that is precisely what data systems enable. A junior analyst with access to the right database can pull numbers that directly contradict what a senior leader has been saying for years. The data may be entirely correct. The analysis may be sound. And the room will still go quiet in a way that has nothing to do with the quality of the work.

This clash between intuitive leadership built on experience and data-driven authority built on evidence is at the heart of why so many digital transformation projects stall. It is not a technology problem. It is a hierarchy problem dressed in the language of modernization.

This does not mean the senior leader is always wrong. Experience carries context that data genuinely cannot capture. The problem arises when neither side is willing to acknowledge the limits of what they know.

When Metrics Stop Measuring and Start Controlling

This problem is especially acute in African NGOs, where the metrics being tracked are often not even designed for internal decision-making. They exist to satisfy foreign donor reporting requirements. The data team produces reports that go to Geneva or London. The fieldwork team operates on a different logic entirely. The two rarely meet in any meaningful way, producing a disconnect that undermines both the data and the work it is supposed to reflect. The PlayPump initiative once celebrated as an innovative solution to rural water access became a cautionary tale precisely because its donor-driven success metrics bore almost no relationship to how communities actually used, or stopped using, the pumps.

There is a principle in organizational management known as Goodhart’s Law: when a measure becomes a target, it ceases to be a good measure. It sounds academic. In practice, it describes something that plays out in virtually every institution that has ever introduced a performance dashboard.

Staff quickly learn which numbers are being watched. And they optimize for those numbers not necessarily because they are lazy or dishonest, but because the incentive structure leaves them little choice. Call center teams close tickets faster, even if the problem isn’t solved. Field officers inflate beneficiary counts to hit quarterly targets. Program managers report activities rather than outcomes because activities are easier to quantify.

The result is an organization that looks excellent on the dashboard and is quietly struggling everywhere else. The metrics have not improved performance. They have simply changed the performance being delivered.

What Needs to Change

None of this means organizations should abandon their dashboards or stop trying to make evidence-based decisions. It means they need to be honest about what data systems actually do when they enter a traditional institution.

Managing a digital transformation means managing the cultural displacement it causes. The departments that lose influence when data becomes democratized will not simply accept their new position, they will find ways to reassert control, slow adoption, or undermine the systems that threaten them. Leaders who ignore this dynamic will spend years wondering why their expensive new platform is not delivering results.

It also means designing metrics with more care and humility. The best measurement systems are built to learn from, not to punish with. When KPIs are attached directly to individual performance reviews, staff stop using them as feedback and start gaming them as targets. Separating diagnostic metrics from evaluative ones using data to understand what is happening rather than to rank who is performing and produces far more honest information.

Most importantly, it means building organizations where both kinds of knowledge are taken seriously. Data without context produces confident mistakes. Experience without evidence produces comfortable ones. The goal is not to replace one with the other, it is to create the conditions where a junior analyst and a twenty-year director can sit in the same room, look at the same dashboard, and actually talk about what it means.

Conclusion

The next time your organization launches a new data system, pay attention to the room. Watch who gets quiet. Watch who suddenly becomes very interested in the methodology. Watch who starts arguing about data quality the moment the numbers don’t support their position.

That tension is not a distraction from the real work of digital transformation. It is the real work. Data becomes power the moment it enters an institution. The question is never whether that power will be contested. It is only whether your organization is honest enough to admit it and wise enough to manage it.

Key Takeaways

• Dashboards Dictate Power: Deciding what to measure isn't an IT task—it's a political act. The metrics you choose to display ultimately determine which departments get visibility and funding.
• Data Challenges Tenure: Democratized data disrupts traditional, age-based hierarchies. When a junior analyst's spreadsheet contradicts a senior director's gut feeling, legacy gatekeepers often push back to protect their authority.
• Targets Ruin Metrics:Per Goodhart’s Law, using metrics as punitive performance goals simply forces staff to game the system. To be effective, data must be used for diagnostic learning, not punishment.