Offers
Post go-live ownership setup
So that after rollout it is not an open question who actually carries the system.
“Things get delivered, but nobody answers for the overall result.”
- Format
- 3–6 weeks alongside the rollout
- Who it is for
- Projects shortly before or after go-live
How you notice it
- After go-live, requests land with whoever happens to be reachable.
- There is no defined path for failures — only chat groups and shouting.
- Evolution happens on the side and is prioritised by volume, not value.
- The project counts as done, but nobody can say whether it works.
- The external vendor is gone and the internal team was never onboarded.
Outcome
- Role and responsibility model for operations, evolution and support
- Onboarding material and internal communication
- Operating routines: incidents, releases, feedback loops
- Impact measurement with a few reliable metrics
How we work
01
Week 1 — reality check
Conversations with operations, support, the business and engineering. We write down who is responsible in practice — not who should be according to the org chart.
02
Week 2 — roles and routines
A responsibility model for operations, evolution and support, plus routines for incidents, releases and feedback. Few rules that are actually followed.
03
Weeks 3–4 — enablement
Onboarding material, runbooks and guided runs: first incident, first release, first feedback round under real conditions.
04
Then — measure impact
Three to five metrics that show whether the system holds. After four to six weeks we review them together and adjust.
Frequently asked
- Isn't that the project manager's job?
- Project management ends with the project. Ownership starts afterwards and needs different roles: operations, evolution, support. That is the gap we close.
- Do we need new positions for this?
- Usually not. Most of the work is making existing responsibility explicit and reserving capacity for it instead of letting it run invisibly on the side.
- How does this fit ITIL or our existing processes?
- We build on what exists. If a service process is in place, we plug the product into it instead of adding a second system next to it.
- Which metrics do you recommend?
- Few and reliable ones: time to respond to incidents, lead time for a change, actual usage by the business. No dashboards nobody reads.
- What happens after the six weeks?
- The team works independently. If you like, we stay in reach with a monthly review — no minimum term.
When this does not fit
If the software is not yet operable, the ownership setup comes too early. Production readiness is the better first step then.
Often combined with
Background in the article Ownership instead of roles: who is really accountable after go-live.