Every organisation eventually hits the same moment. Teams are busy, demand is growing, and leaders realise that the way work flows across the business no longer makes sense. People start talking about operating models. Should everything be centralised for control and consistency? Should teams be federated so they can move fast and stay close to the business? Or should it be hybrid, the elusive middle ground everyone claims to want but few can explain?
This dilemma isn't really about structure. It's about trust, clarity, and the ability to deliver value at scale.
Most companies don't start with a deliberate operating model. They drift into one. A centralised model emerges when a strong technical group forms early, taking responsibility for everything. A federated model tends to appear when business units get tired of waiting and hire their own people to make progress. Neither is inherently wrong, but tension builds when strategy and delivery fall out of alignment.
A centralised model feels safe. One team sets the standards, protects quality, manages risk, and owns common capability. Leaders like the idea that it avoids duplication and keeps the organisation marching in the same direction. The challenge is that centralisation can slow everything down. Local teams feel disconnected from the decisions that affect them. Requests pile up. Prioritisation becomes political. Suddenly, execution lags even though quality is high.
A federated model feels empowering. Business units get the autonomy to build what they need, when they need it. They understand their customers, their processes, their pressures. Delivery is fast and tailored. But this speed comes with a cost. Definitions drift. Processes diverge. Talent is spread thin. The company ends up with pockets of brilliance surrounded by inconsistent practices. Leaders struggle to compare performance, manage risk, or scale what works.
That's where hybrid models come in. On paper, hybrid sounds perfect. In reality, hybrid is simply the name given to whatever messy middle emerges when no one makes the hard choices. Done well, hybrid is not a compromise but a deliberate split between what must be shared and what must be local. Done badly, it's a tug of war between teams who believe they should be in charge.
The truth is that operating models succeed when they are shaped by business priorities, not ideology. Start with asking what the organisation is trying to achieve. If the goals require strong consistency, shared assets, and unified decision making, centralisation will feel natural. If the business needs speed, experimentation, and local variation, a federated model can unlock energy. If the organisation needs both, a hybrid is the right answer - but only if it's designed, not assumed.
The simplest way to cut through the noise is to define who decides, who does, and who is accountable for what. Every capability does not need the same level of ownership. Some things should be governed globally, like data definitions, quality standards, privacy, and shared architecture. Others should be shaped locally, like use case opportunities, delivery sequencing, and operational improvements. The model works when these boundaries are explicit.
Another common problem is assuming that operating models can fix deeper cultural or maturity issues. A company with unclear priorities will struggle no matter how it's structured. A company with inconsistent data, weak governance, or unclear roles will feel the pain whether it is centralised or federated. Structure amplifies clarity - it does not replace it.
When organisations design their operating model with intention, something shifts. Business units feel supported instead of supervised. Central teams feel responsible instead of overstretched. Work moves with more rhythm. People stop fighting the system and start using it. The model fades into the background and outcomes become the focus.
The best operating model is the one that makes it easiest to deliver value in your context. Not the model you inherited. Not the one you saw in a case study. Not the one a leader prefers based on a past employer. The right model is the one that reflects what your organisation is capable of today and what it must become tomorrow.
Begin by defining the outcomes your organisation must deliver and the capabilities required to achieve them. Decide which of those capabilities need consistency and which need autonomy. Make responsibilities explicit so every team knows where it stands. Establish a shared prioritisation process and a clear rhythm for planning, delivery, and measurement. Most importantly, keep the model flexible. As your organisation matures, revisit how work flows and adjust the model to support the next wave of growth.