_
Cloud Operating Model & CoE Setup
Deloitte
Last updated on
Measurement shows whether the Target Operating Model creates better outcomes, not merely more process. Use a balanced set of operational signals to improve both shared STACKIT platform capabilities and individual migrated workloads.
| Area | Example signals |
|---|---|
| Reliability | Service-level objective achievement, incident frequency, recovery time, and backup or restore test results. |
| Delivery | Lead time for change, deployment success rate, change failure rate, and time to restore service. |
| Security | Open findings by severity, remediation time, exception expiry, and control-evidence coverage. |
| Cost | Allocation coverage, budget variance, resource utilization, and prioritized optimization opportunities. |
| Adoption | Platform onboarding time, self-service usage, reference-pattern adoption, and workload-team satisfaction. |
Review signals at a regular service cadence. Identify the highest-value operational constraint, assign an accountable owner, prioritize the improvement in the platform or workload backlog, and verify the result with the same metric. Post-incident reviews, migration-wave retrospectives, and security assessments should all feed this cycle.
Avoid measuring teams by activity volume alone. A growing number of tickets, approvals, or manual provisioning tasks can indicate that the operating model needs more automation or clearer ownership.





