Consider a scenario that plays out regularly in large organisations. A CIO invests in a scaling initiative — SAFe, LeSS, or some custom variant — with clear expectations of improved delivery speed, better cross-team coordination, and more responsive IT. The launch is ambitious, the training is thorough, and the teams are initially engaged.

Six months later, the picture is messier. Development has actually slowed during the transition. Middle managers are frustrated by new ceremonies that feel like overhead. Business stakeholders are still waiting on commitments that were supposed to be clearer than they were before. The question — "are we on the right track?" — is being asked more frequently than the question "what are we building?"

The common failure modes

Process overload is almost always one of them. Scaling frameworks introduce a significant number of new roles, events, and artefacts. Teams that were previously operating with a relatively lightweight process suddenly find themselves attending multiple new meetings, producing outputs for multiple new artefacts, and reporting into multiple new structures. The overhead is real, and until the benefits materialise — which takes longer than the overhead — the net experience is negative.

Cultural disconnect is usually the deeper problem. Scaling frameworks are built on assumptions about how authority flows, how decisions get made, and how teams relate to each other. In organisations with strongly hierarchical cultures, those assumptions are not met. Middle managers who have built their authority on being the conduit between strategy and execution experience decentralisation as a threat rather than an improvement. They do not actively sabotage the transformation — they simply do not make the behaviours it requires any easier.

Business misalignment is the third consistent problem. The coordination benefits of scaling depend on meaningful engagement from business stakeholders — clear priorities, timely decisions, genuine availability for review and feedback. In many organisations, these stakeholders continue to operate as if the IT delivery process is still linear: requirements go in one end, software comes out the other. The expectation of iterative engagement has not been set or has not been met.

What CIOs can actually do

Focus on value rather than process compliance. A scaling framework is a tool for delivering business outcomes faster and more reliably. When teams are spending significant energy maintaining framework compliance with limited corresponding improvement in outcomes, that is a signal to simplify — to strip back the elements that are not demonstrably contributing value and focus attention on the ones that are.

Treat cultural change as the main intervention, not a side effect. The frameworks do not create the culture they require — they depend on it. Leadership behaviour, particularly middle management behaviour, is the primary driver of whether the culture shifts or not. Leaders who model the transparency, empowerment, and cross-functional collaboration that scaling requires will get different results from those who continue operating as before while asking their teams to change.

Measure the right things. Velocity is a popular metric but a poor proxy for the business value of a scaling initiative. Metrics connected to business outcomes — time to market for a meaningful capability, customer satisfaction with a delivered product, cycle time for a customer-facing process — tell a more honest story about whether the investment is paying off.

The scaling journey, done well, is iterative. The organisations that succeed at it treat the first six months as a learning phase, not a delivery deadline.