GCC Build OSv0
/api
Home/bootminds.it/decisions/it.decisions.d01

Confirm federated as the target operating model (not centralised).it.decisions.d01

P0 G

Summary

Anchor decision for all design choices. Decision owner (sheet): IT Head + KC. Sheet target: Wk 1.

Rationale prompt skeleton

Capture the rationale for this decision. Sheet-recorded justification: "Anchor decision for all design choices.". Reference the evidence questions, name the alternatives considered, and explain how this decision propagates to design, BoM, and operating model.

Default options (3)

federated Federated (target)

Group-level standards/policies/governance + subsidiary autonomy where business reality demands.

Pros
  • + Aligns with stated client intent
  • + Preserves subsidiary speed
  • + Enables economies of scale on a named set of services
Cons
  • − Needs a teeth mechanism or drifts to fragmented
  • − Steerco discipline required
centralised Fully centralised

Group IT runs all IT services across subsidiaries.

Pros
  • + Maximum consistency
  • + Simpler vendor leverage
Cons
  • − Conflicts with client signal
  • − Sacrifices subsidiary speed for plant/OT/regulated work
decentralised Status quo (decentralised)

Continue with subsidiary-owned IT, no group standards.

Pros
  • + Zero change management
Cons
  • − Re-creates the problem this engagement exists to solve

Default approval chain

  1. Admin
  2. ExecutiveViewer

Linked evidence questions (7)

id prompt workstream
it.operating_model.q01 Confirm the target IT operating model is federated (group standards + subsidiary autonomy) and not full centralisation. Document explicit boundaries. it.operating_model
it.operating_model.q02 Which decisions belong at GROUP level (e.g., identity, security policy, ITSM, EDR)? Which remain SUBSIDIARY level (e.g., engineering software, OT, local hardware)? it.operating_model
it.operating_model.q03 What is the group's economy-of-scale ambition — naming and standardising 3–5 services (e.g., endpoint mgmt, ITSM, EDR, M365, SOC) versus broader coverage? it.operating_model
it.operating_model.q15 Confirm GCC absorbs only MATURE capabilities. List capabilities considered mature enough to migrate now vs. those that must stabilise centrally first. it.operating_model
it.operating_model.q19 How are disagreements between local IT and Group IT typically resolved? Who decides; what is the escalation path? it.operating_model
it.operating_model.q20 Are there areas where centralised governance may be beneficial today (security, identity, ITSM, vendor mgmt, BCP, data)? Rank by perceived value. it.operating_model
it.operating_model.q37 Are there concerns around scalability of the current IT operating model (specific bottlenecks — people, tooling, vendor, process)? it.operating_model