There is a paradox that strikes anyone working in data transformation in Africa. On the one hand, awareness is real: leaders know their organisations need consolidated dashboards, reliable data, and informed decision-making. On the other, a significant proportion of BI projects never reach sustainable production.
It is not a technology problem. Power BI, Fabric, Tableau — the tools are mature and accessible. The root causes lie elsewhere, and they tend to be the same from one project to the next.
With over 90 combined years of experience across our team — in contexts as diverse as government institutions, multi-site accounting firms, telecom networks, and multi-country agricultural cooperatives — we have identified five recurring patterns. These are not judgements: they are situations we have lived through, sometimes discovering them from the inside when a client called us after an initial setback.
1 The pitfall of an overly broad scope
The scenario is classic and understandable: an organisation decides on its data transformation and wants to cover finance, HR, sales, supply chain, and production all at once. The ambition is legitimate. But experience shows that an organisation's capacity to absorb change is limited.
The broader the scope, the more stakeholders are involved. The more complex the trade-offs become. The longer the timeline stretches. And the greater the risk of fatigue — not from lack of will, but because day-to-day operations take over when results are slow to materialise.
"What makes the difference is not the scale of the project — it is how quickly the first visible result arrives."
What we have learned
The projects that succeed start with a focused scope — a single domain, the one with the most visible impact — and deliver a working dashboard within 6 weeks. The executive sees concrete results. Teams gain confidence. And expansion happens progressively, domain by domain, over 6 to 18 months. It is less spectacular at the outset, but it is what lasts.
2 Executive sponsorship — an often underestimated factor
A BI project driven solely by the IT department struggles to gain traction across the organisation. Not because IT lacks competence — they build the infrastructure. But without an active relay at the executive committee, the project is perceived as just another technical initiative.
The role of the executive sponsor — CEO, Deputy Director, Secretary General, Minister — goes beyond budget approval. They embody the data culture on a daily basis. When they check the dashboards every morning, when they challenge their directors on the indicators, they send a clear signal to the entire organisation. This dynamic is what turns a tool into a reflex.
We have observed, project after project, that the variable which best predicts success at 12 months is neither the budget nor the technology: it is the level of involvement of the sponsor.
What we have learned
We have made it a practice, from the diagnostic phase, to identify the executive sponsor and ensure their concrete commitment. Our initial presentations address the CEO as much as the CIO. And we deliver an "executive dashboard" within the first 6 weeks, so the sponsor immediately has something tangible to use and to show.
3 Start from the decision, not from the tool
Many BI projects begin with a statement like "we are going to implement Power BI" or "we are going to deploy Fabric." It is a natural approach, but it puts the means before the end. The question that should guide the entire project is different: "What decision do you want to make faster?"
A CFO does not want "a Power BI dashboard." They want to know, every morning, where their budget stands, what their outstanding commitments are, and whether their cash flow will hold through the month. An operations director wants to see delivery delays and anticipate shortages. Technology is the means; the decision is the purpose.
"The right question is never 'which tool?' It is 'which decision do you want to make faster?'"
When you start from the decision, everything falls into place naturally: what data is needed, where it comes from, how to transform it, and how to present it. When you start from the tool, you risk ending up with technically flawless dashboards that no one uses day-to-day.
What we have learned
Our diagnostic systematically begins with 5 questions to each decision-maker: What decisions do you make every week? What information are you missing? How long does it take you to get it? What prevents you from deciding faster? What would you look at if you could see everything in one click? The answers shape the requirements. Technology comes after.
4 The African context is not a degraded European context
This may be the most important lesson. Too often, BI deployment methodologies are designed for environments with permanent connectivity, structured data, digitised processes, and tool-trained staff. Applying these methodologies as-is on African ground means ignoring a fundamentally different reality.
In Africa, connectivity is intermittent — and sometimes non-existent in rural areas. Data is often on paper or in non-standardised Excel files accumulated over years. Processes are built on human relationships and oral transmission, not on digital workflows. And professional mobility means the person trained today may be reassigned within two years.
These are not handicaps. They are design parameters. A BI solution designed for this context — applications that work offline, automated cleansing pipelines, built-in documentation — performs as well, if not better, than a solution designed for an ideal environment that does not exist on the ground.
What we have learned
We design our solutions for the real terrain. Power Apps works offline with deferred synchronisation. Our data pipelines include automatic cleansing and validation layers upstream of every dashboard. And our training programmes are built so the organisation remains autonomous: when a staff member is reassigned, the next one finds a documented and intuitive system, not a black box.
5 Skills transfer — the long-term success condition
A pattern we have encountered multiple times: an organisation invests in an ambitious BI deployment, dashboards are delivered, teams receive a few days of training… then the service provider leaves. Six months later, dashboards are outdated, new requirements are unmet, and the organisation faces a system it does not master.
This is not inevitable. It is the sign that a project was designed to deliver a product, not to install a competency. The difference is fundamental: a product starts ageing the day after delivery; a competency helps the organisation evolve for years.
"The true success of a BI project is not delivery day. It is 12 months later, when the internal team evolves its dashboards on its own."
What we have learned
Skills transfer is embedded in every phase of our projects, not relegated to a final two-day training session. By the end of deployment, the organisation is able to maintain, modify, and extend its dashboards without our help. And with NJIADATA Academy, we take this further by training the next generation of African BI consultants, so the entire ecosystem grows in capability.
In summary: three principles that guide our approach
After dozens of projects and thousands of hours in the field, our conviction rests on three principles. First, start with a focused scope and deliver a visible result quickly — a 6-week quick win anchors the project in reality and creates momentum. Second, start from the decision, not from the technology — it is the decision-maker's need that shapes the solution, not the vendor's catalogue. Third, transfer know-how at every stage — a project that leaves the organisation dependent has not succeeded, no matter how polished the dashboards.
Africa has a unique advantage in this transformation: it carries no massive legacy. Where European organisations must migrate systems that are 20 years old, many African organisations can leapfrog directly to the latest generation of tools — Microsoft Fabric, Power BI, cloud-native. It is a historic opportunity.
This opportunity will be fully realised when projects are led with method, pragmatism, and intimate knowledge of the terrain. That is the mission we have set for ourselves.