Owning and evolving the operating model after go-live
The project closed on time; the organization kept changing—and nobody was left to own the model.
The case in brief
Current reality
The project team disbanded at go-live. Support tickets pile up one by one, workarounds spread, every change arrives as a ticket to the platform team—and nobody decides whether it changes the operating model, so the configuration drifts.
What must become true
Every responsibility the project held has a named operating owner before go-live; recurring friction and requests are classified into one governed backlog; every change is decided by its domain owner with evidence and within a time limit, released as a versioned change and reviewed for effect; and adoption and the model itself are reviewed on a schedule that decides.
Design question
Who owns the operating model once the project leaves—and who may change which part of it, with which evidence, released how?
01The reality · current state
How the organization operates today.
The commercial platform went live on schedule and the project team moved to other work. Every responsibility it held—process decisions, configuration, enablement, data definitions, local support—disappeared with it. Since then, the support desk answers requests one at a time, users build workarounds for slow approvals and missing data, managers drift back to exports, and requests arrive as tickets: a new field, a new approval, a new report, a local rule. The platform team implements what is asked. Stage definitions have drifted, three approvals overlap, and nobody can say what the current operating model is. The obvious response—keep a support desk and close the project—answers questions one at a time; without an owner who changes the design, the same friction returns every week.
- Every project role disappeared at go-live
- Support tickets are handled one by one and never analysed
- Workarounds spread with nobody recording them
- Every change is a ticket; nobody asks which layer it changes
- The platform team decides business questions by implementing them
- Stage definitions have drifted and approvals overlap
- No version of the operating model is documented
- Adoption has not been reviewed since the go-live report
02Operating model
The design, layer by layer.
CRMSupport deskChange backlogData platformVariation register
- 03Process
Stage definitions versioned with the model; friction and requests enter one lifecycle
- 04Ownership
An operating owner per responsibility—process, platform, data, adoption, business outcome—named before go-live
- 05Systems
The platform implements approved changes in releases; it does not decide them
- 06Data
A new field needs a data owner and the decision that will use it
- 08Governance
Change authority per domain; time limits; operating, release and quarterly model reviews
- 09Measurement
Adoption signals by level, and each change reviewed against the KPI it named
03Key dimension · Ownership handoff, change authority & versioned evolution
From project roles to operating owners—then one lifecycle for every change
Owners come first: each responsibility the project held is handed over before go-live. Then every request—and every recurring friction—follows one lifecycle. What differs is who decides, which evidence is required and how long it may take.
Who is there to decide: from project roles to operating owners
- Process decisions
Project design authorityProcess ownerMonthly process review - Configuration and releases
Project build teamPlatform ownerPer release - Enablement and adoption signals
Project change leadAdoption ownerMonthly adoption review - Data definitions and quality
Project data workstreamData owner per conceptMonthly data forum - Local support and feedback
Project super-usersLocal championsWeekly in the first months
One lifecycle for every change
- 01RequestAnyone, with a business owner—or the friction register
States the problem, not the solution; recurring friction enters as a request with its cause
- 02ClassifyOperating-model office
Which domain: process, system, data, KPI, variation, exception
- 03DecideThe domain’s decision owner
With the required evidence, within the time limit; prioritized in one backlog
- 04ImplementPlatform, process or data team
In a versioned release, on the release cadence
- 05ReviewDecision owner
Did the KPI it named move? Exceptions feed the next model review
What feeds the first stage: recurring friction, classified by cause
| Friction | Cause | Type | Action |
|---|---|---|---|
| Discount approvals wait days | One threshold for every deal | Process | Tier approvals by amount |
| Customer address retyped | ERP data not shown in the CRM | System / integration | Expose the authoritative address |
| Monday pipeline exports | No review view | UX / operating model | Build the review workspace |
Who may approve which change
| Change | Authority | Evidence | Lead time |
|---|---|---|---|
| New field | Data owner for the concept | Which decision will use it | Per release |
| New or changed approval | Decision owner (with finance above policy) | Risk being controlled; overlap check | Next quarterly review |
| Stage definition | Global process owner | Ageing and conversion data | Next quarterly review |
| Local rule | Global governance | Variation register entry | 4 weeks |
| New report | KPI definition owner | Metric contract and forum | Next monthly forum |
The same three frictions had produced most of the support tickets—and the first question for every ticket became “which layer does this change?”. Most drift came from changes nobody owned or classified.
04Decision rights
Who decides what, with which evidence, within what time.
| Decision | Decides | Approves | Consulted | Evidence | Within |
|---|---|---|---|---|---|
| Name the operating owners | Business owner | Sales leadership | Programme lead | The responsibilities the project held | Before go-live |
| Classify a change request or friction item | Operating-model office | — | Requester | The problem statement, or the friction and its cause | 5 working days |
| Prioritize the backlog | Process owner | — | Platform owner, adoption owner | Friction by type and volume, change requests | Per release |
| Change a stage definition | Commercial process owner | Global governance | Sales managers, platform owner | Stage ageing and conversion | Quarterly |
| Fix a data-quality issue | Data owner for the concept | — | Account owners | Quality measures by source | 5 working days |
| Release a new model version | Global governance | — | Domain owners | Approved changes and their impact | Quarterly |
| Roll back a change | Domain decision owner | — | Platform owner | KPI moved the wrong way | Next release |
05Governance
The forums that run and change the model.
| Forum | Decides | Evidence |
|---|---|---|
| Change triageWeekly | Classification and routing of requests and friction to owners | New requests, the friction register |
| Operating & adoption boardMonthly | Operating rules, definitions, parallel-tool retirements, friction priorities, adoption escalations | Adoption signals, the friction register, quality measures, change requests |
| Release boardPer release | What changes in the platform, from the governed backlog | Change requests with business owners |
| Operating-model reviewQuarterly | Model version, core changes, variations to renew or retire | Exception patterns, variation register, change effects |
06Measurement
Signals that the model is owned—and improving.
| Signal | Level | Owner | Meaning | Action |
|---|---|---|---|---|
| Friction items closed by a release | L5 · Improvement | Process owner | The design is improving | Review the release impact on the related signal |
| Recurring ticket categories | L5 · Improvement | Adoption owner | Friction the design has not fixed | Move to the friction register with a cause |
| Exports before management reviews | L3 · Management adoption | Business owner | Management drifting out of the system | Find what the view lacks |
| Changes reviewed against the KPI they named | L5 · Improvement | Domain decision owners | The model learns from its own changes | Roll back or adjust changes that moved the KPI the wrong way |
07The trade-offs
Credible options, judged against these premises.
Support desk only
Stable processes with few changes
Cost: Friction answered, never fixedPlatform team implements requests as they come
Very small organizations
Cost: Configuration drifts; business decisions made by adminsFreeze the model after go-live
Stable markets
Cost: Workarounds grow outside the systemKeep the project team indefinitely
Very early after a large go-live
Cost: Ownership stays temporaryNamed operating owners, one governed backlog, change authority per domain, versioned releases
Any organization meant to keep improving
Cost: Owners with time, an operating-model office and a review cadenceDesign decision
Hand each project responsibility to a named operating owner before go-live, and run the operating model as a product: recurring friction and requests classified into one governed backlog, change authority per domain, versioned releases, and adoption and model reviews that use friction, exceptions and variation as evidence—not support volume.
08The second layer
Questions that change the design.
Authority
- Who may change a stage, a rule, a field or a KPI?
- What evidence does each change need?
- Who can say no?
Ownership & friction
- Who owns each responsibility the project held—named before go-live?
- Where are recurring workarounds recorded, and who classifies them by cause?
- What can the adoption owner decide—and what belongs to other owners?
Release & learning
- How is the model versioned, and how are subsidiaries told what changed?
- Which exceptions and frictions changed the model last quarter?
- Which changes moved their KPI—and which were rolled back?
09Decisions & outputs
What the work produces.
- 01Ownership handoff model
- 02Friction register
- 03Governed backlog and release cadence
- 04Change-authority matrix
- 05Change lifecycle
- 06Model versioning
- 07Operating, release and quarterly review forums
- 08Adoption and change-effect review