Field guide · Preview
One center, many operating companies
A governance pattern for centralized IT teams that need shared direction without pretending every entity works the same way.
The design tension #
Centralized IT needs enough consistency to manage shared risk, investment, and evidence. Operating companies need enough discretion to respond to different customers, regulations, systems, and stages of growth.
A practical pattern #
- Set the group minimum
Name the decisions, controls, and evidence every entity must share.
- Record local context
Capture the risks, obligations, operating model, and technology estate that make an entity different.
- Tailor locally
Allow priorities and capability targets to respond to that context without weakening the group minimum.
- Review as a portfolio
Roll up common gaps while keeping entity-level ownership visible.
What this pattern does not prove #
This is a design pattern, not a customer case study. Outcomes will depend on authority, funding, data quality, and whether each entity accepts the decision model in practice.
Publication record
Evidence & limits
- Method
- A proposed operating pattern for multi-entity governance discussions.
- Limitations
- This is not an observed customer implementation or an outcome study.
- Sources
- Source review pending before publication
- Customer approval
- Not required