Business function
IT operations
Runs runtime, SLO, and change as an IT service — not shopfloor operations and not meaning ownership.
Load-bearing: Access and Lifecycle; Quality is neighbor. Access, Lifecycle · Concept · Shared standard · 8 pillars
Download decision card (PDF) Fill first decision Fill deal card Partial scope / service
Kundenschmerz points and controls
Typical business problems
- Tool sprawl without an SLO
- Incident without an evidence path
- IT operations owns runtime and evidence, not the business KPI definition
Typical controls
- Tool SLO and support path
- Change/incident as evidence
- Handoff operations → platform
How we remove it
- No second mini-CoE per stack
- Shopfloor operations stays orders/inventory
- Semantics handoff sits in data engineering, not here
Related roles
Recommended learning paths
Recommended tools
- Fill first decision Capture decision question, data product, owner, or vacancy for the first workshop. tool
- Fill deal card Clarify customer situation, value claim, offer package, and handoff for this function. tool
- Objection map Typical objections before placement tool
- Customer guide Mandate and non-mandate on one page tool
Recommended stories
1 series 6 stories
Not the full catalog — open Stories filtered to this function