Why CIOs Are Quietly Moving Away from the Big SI Model

(And what they’re looking for instead…)

There was a time when bringing in a large global system integrator felt like the obvious choice. It signalled scale, structure, and safety. For many organisations, it was the default path — especially when the stakes were high and the programmes were visible. And for a long time, that model worked. It brought order to complexity and capability to environments that needed both.

But in many of the conversations I’ve had recently with CIOs across Africa, there’s a shift happening. Not loud, not confrontational — but unmistakable. The question is no longer simply “Which big SI do we choose?” It’s becoming something more considered: “Do we need that model at all?”

What I hear isn’t a criticism of capability. Large integrators still bring deep expertise, global reach, and proven delivery frameworks.

The concern is more subtle than that.

It’s about weight — the growing sense that the model itself has become heavier than the problems it was originally designed to solve. Programmes take time to get moving, layers build between the business problem and the people working to resolve it, and decision-making stretches out. Somewhere in that process, momentum softens. What was meant to accelerate transformation can start to feel like something that needs managing in its own right.

That tension becomes most visible not during implementation, but after it. I’ve seen environments where everything is technically complete — the platform is live, workflows are configured, reporting looks right. On paper, the programme is a success. And yet, the business hasn’t fully come along for the journey. Teams adapt in quiet ways, workarounds emerge, and the system exists without quite landing as intended. It’s not failure — it’s friction.

That friction is becoming harder to justify in an environment where CIOs are under increasing pressure to show value earlier and more clearly. Budgets are tighter, expectations are sharper, and tolerance for long cycles between investment and outcome has narrowed significantly. There’s a growing emphasis on progress that can be seen, felt, and measured — not just planned. In that context, the shape of delivery starts to matter as much as the capability behind it.

What I’ve noticed is a gradual shift in how CIOs are thinking about partnership. Not away from partners altogether, but toward a different kind of engagement — one that feels closer, more accountable, and more aligned to the pace of the business. This is where smaller, more focused integrators are starting to find their space. Not because they can outscale the larger firms, but because they often bring something different to the table.

The experience tends to be more direct. Conversations happen closer to decision-makers, the distance between strategy and execution is shorter, and there’s less room for ambiguity around ownership. It changes the dynamic. There’s a consistency that comes from working with a tighter team, where the people shaping the thinking are often the same people responsible for delivering it. The problem stays close; it doesn’t get abstracted into layers of process or passed between structures that dilute context over time. And perhaps most importantly, things move faster — not because corners are cut, but because there is less friction in how decisions are made and acted upon.

This isn’t to suggest that large system integrators are becoming irrelevant. They continue to play an important role, particularly in environments where scale, regulatory complexity, or global coordination demand it. But the assumption that bigger automatically means better fit is being quietly challenged. More organisations are asking whether every initiative truly requires that level of machinery, or whether a more focused, premium approach — one that emphasises proximity, accountability, and speed — might be better suited to the outcomes they’re trying to achieve.

What stands out in all of this is not just an operational shift, but a human one. CIOs are placing greater value on relationships that feel real, on partners who understand the nuance of their environment rather than defaulting to generic models, and on delivery that adapts to the organisation rather than expecting the organisation to adapt to the delivery model. There’s a growing preference for simplicity — not as a reduction in capability, but as a deliberate design choice. A recognition that complexity, while sometimes necessary, should never be the default.

In many ways, this feels less like disruption and more like correction.

A rebalancing of what matters.

A move away from scale as a proxy for confidence toward fit as a measure of effectiveness.

A shift from how much can be delivered to how well it actually works once it’s there. And in the African context, where resources are often more constrained and execution environments more nuanced, that shift feels particularly relevant.

Because ultimately, the role of a partner is not just to deliver a system. It’s to help the organisation move forward — clearly, confidently, and without unnecessary friction. If the model makes that harder rather than easier, it’s only natural that CIOs begin to look for something different — not out of dissatisfaction, but out of pragmatism.