Don’t Bury Your Talent: The Centralisation vs. Federation Trap
There’s a question that quietly shapes the fate of technology talent in almost every organisation, and most businesses never ask it directly. Instead, they stumble into an answer through a series of incremental org design decisions, budget cycles, and leadership preferences. The question is this: is technology a support function to the business, or is it a first-class citizen within it? How you answer that, consciously or not, determines whether your best technologists thrive, stagnate, or eventually leave.
1. The Hidden Cost of Full Federation
On the surface, federating technology into business units makes intuitive sense. Put the tech close to the business, make it accountable to outcomes, and remove the ivory tower. But there is a quiet and damaging side effect that rarely makes it into the org design presentation: you bury career paths. When a technologist sits inside a business unit, the next hop up the structure is typically a generic business manager, a commercial head, or a domain leader whose frame of reference has little to do with software engineering, architecture, data, or platform thinking. That person cannot meaningfully assess whether the technologist is exceptional or merely adequate, promotion conversations become abstract, recognition becomes accidental, and the technologist, talented, ambitious and aware, starts to do the maths. They are alone and unheard, and the ceiling above them is made of the wrong material. Over time they leave, not always loudly, sometimes they just stop raising their hand.
2. The Hidden Cost of Full Centralisation
The overcorrection is equally damaging. Pull all technology into a central function and you risk creating a service desk mentality, a team that processes tickets for the real business rather than co-creating its future. Distance from business context grows, relevance erodes, and talented people who want to build things that matter find themselves in queues. Neither extreme works, and the answer lies in the intentionality of the design that sits between them.
3. The Structural Sweet Spot
The goal is federation with coherence, technology that is genuinely embedded in business domains but organised in a way that preserves identity, comparability, and career trajectory for the people doing the work. This means creating reporting lines where groups of technologists roll up into technology leadership, even when those groups are operationally close to business units. It means technologists have peers, their work can be assessed by someone who understands it, and there is scope to move, laterally, upward, across domains, within a recognisable professional structure. This is not just good for talent retention, it is good for quality. When technologists can be compared to peers, standards emerge. When career paths exist, investment in craft follows. When there is domain, there is depth.
4. Why Leaders Resist This
It is worth being honest about the dynamics that push against this model. Heads of technology groups embedded in business units will frequently advocate for full federation, and it is worth understanding why. Full federation often insulates them from comparison with other technology areas, reduces external scrutiny of their team’s output, and places them under a business head who may not know enough to challenge them. That suits certain leadership styles well. This is not a cynical observation, it is a structural one. Org design creates incentives and those incentives shape advocacy, so when you hear a strong internal argument for full federation it is worth asking who benefits most from the absence of comparison.
5. Be Intentional
The right answer for your organisation is not a universal template. The size of your technology investment, the maturity of your business units, and the strategic role of technology in your industry all shape what the right balance looks like, but the worst outcome is arriving at that balance by accident. Don’t bury your technology talent inside structures that cannot see them, and don’t centralise so completely that technology loses its connection to purpose. Build the reporting lines that allow technologists to belong to the business and belong to a professional community at the same time. Ask the question directly, because your best people are already asking it, and they are not waiting long for the answer.