Governance and decision making
Establish decision rights, architecture and security review forums, exception handling, and an escalation model. See Governance and Decision Making.
Cloud Operating Model & CoE Setup
Deloitte
Target Operating Model
The Target Operating Model translates your cloud strategy and STACKIT landing zone into an accountable, repeatable operating model.
Purpose
Section titled “Purpose”The Target Operating Model (TOM) defines how an organization operates its cloud environment after migration. It turns the technical foundations provided by the STACKIT landing zone into clear ownership, repeatable processes, and measurable outcomes.
The model covers the responsibilities shared by platform teams, workload teams, security, service management, and business stakeholders. It should be designed before migration waves start and refined as workloads move into operation.
TOM capability areas
Section titled “TOM capability areas”Roles and responsibilities
Define accountable ownership across platform, application, security, FinOps, and service management teams. See Roles and Responsibilities.
Service management and operations
Make incident, change, problem, request, support, and handover processes operational. See Service Management and Operations.
Platform team and enablement
Operate the STACKIT platform foundation as an internal product with reusable guardrails and self-service paths. See Platform Team and Enablement.
Skills and change management
Build the capabilities, adoption practices, and communication routines needed for new cloud responsibilities. See Skills and Change Management.
Measurement and continuous improvement
Use reliability, delivery, security, and cost signals to improve platform and workload operations. See Measurement and Continuous Improvement.
Relationship to the landing zone
Section titled “Relationship to the landing zone”The landing zone provides technical guardrails for identity, networking, security, cost control, and automation. The TOM assigns who owns those guardrails, who consumes them, and how changes, exceptions, and operational risks are managed. It does not replace the provider responsibilities defined for STACKIT services; it defines the customer-side operating model for the configured platform and migrated workloads.
Connected framework guidance
Section titled “Connected framework guidance”Use the TOM to connect the following detailed guidance into one operational model:
- Landing Zones defines the technical platform foundation and guardrails.
- Account Governance defines customer account, folder, project, and delegation boundaries.
- Cost Management and Control provides the cost-allocation, budgeting, and FinOps practices that the TOM assigns to accountable roles.
- Security and Compliance: Operating Model and Governance defines control ownership and the required security checkpoints.
- Migration Factory: Runbook Readiness and Handover defines the wave-level operational handover package.
- Enablement provides the learning and reference material that supports adoption of the target model.
Implementation sequence
Section titled “Implementation sequence”- Assess the current operating model, existing support processes, skills, and accountability gaps.
- Define the target responsibilities, decision rights, and interfaces for the STACKIT platform and workload teams.
- Align service management processes, support boundaries, and handover criteria with the first migration waves.
- Establish the platform product model, enablement paths, and operational documentation.
- Measure adoption and operational outcomes, then refine the model as migration waves progress.
Related assets
Section titled “Related assets”Asset title
Framework
Asset type
Adoption
Service
Advisory
Service
Advisory
Software
