The actual design question
Centralized and federated are not binary organization charts. They describe how decision authority and execution are distributed. A centralized model concentrates standards and often platform delivery; a federated model keeps enterprise guardrails while delegating bounded decisions and outcomes to domains.
The right answer may differ by decision class. Risk acceptance can remain central while platform roadmaps and adoption priorities are federated to business domains.
Use explicit delegation contracts
Federation works when each delegated authority has a defined scope, minimum controls, evidence obligation and escalation trigger. Without those elements, the model is decentralized but not governed.
A central CCoE should avoid becoming an approval queue. Its strongest role is maintaining the reference model, orchestrating cross-domain decisions and measuring whether delegated guardrails work.
Choose with evidence
Test the design against domain scale, skills, risk profile and shared-platform dependencies. High domain maturity supports more delegation; scarce expertise or tightly coupled platforms justify more common authority.
Revisit the allocation as capabilities mature. Federation is a governed capability, not a one-time reorganization.