The Capability / Complexity Gap

Put the complexity score and the capability score side by side and you have the capability/complexity Indicator: the relative complexity of your project in the context of your organisation's ability to absorb it. Where complexity exceeds capability, you have a predicted failure — and, more usefully, a specific statement of by how much and on which side.

In complex conditions, new ways of working emerge. People invent workarounds, informal networks and new roles that fit their real constraints. These emergent patterns are attuned to the culture of the organisation, which is precisely why they work — and they need to be recognised, supported and embedded.

• Conventional change management attempts to design and control the outcomes.
• That imposes changes in behaviour and overrides the individual's need to invent their own route to the future.
• It blocks the naturally emergent patterns, so people disengage, fall back on 'what's in it for me', and the project fails.

“The goal of sociotechnical design is to produce a system capable of self-modification, of adapting to change, and of making the most of the creative capacities of the individual for the benefit of the organisation.”

If you cannot design the outcome, you can design the conditions. What does an individual need in order to contribute their creativity to a change?

• An environment of trust.
• Confidence in one's identity and role in the organisation.
• An infrastructure that encourages and rewards sharing and innovation.

1. 1Reduce complexity first. Phase the programme, cut the number of stakeholder groups per release, standardise processes before automating them, shorten the time to the first real proof point.
2. 2Raise capability in parallel, on its own timeline. Culture and process maturity move over years, so start before the business case and continue after go-live.
3. 3Govern on evidence, not assurance. Replace 'the project is on track' with demonstrated readiness: real load, real data, real users, rehearsed rollback.
4. 4Design conditions, not behaviours. Fund the trust, the networks and the recognition that let new ways of working emerge and stick.
5. 5Re-run both assessments at each stage gate. complexity grows with every accepted change request; capability does not grow by itself.

• Projects fail when the COMPLEXITY of the project exceeds the CAPABILITY of the organisation to cope.
• complexity is exponential and is typically underestimated.
• Conventional change management that designs and controls outcomes can itself cause failure.
• capability barriers — culture and process management weaknesses — can be assessed.
• A gap analysis will predict whether a project is likely to fail, and what to do about it.
• The barriers cannot normally be overcome inside the implementation lifecycle. You have to start earlier and continue after the project completes.