Operating-model case / 05 · Ownership handoff, change authority & versioned evolution

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.

Systems and partiesCRMSupport deskChange backlogData platformVariation register

  1. 03Process

    Stage definitions versioned with the model; friction and requests enter one lifecycle

  2. 04Ownership

    An operating owner per responsibility—process, platform, data, adoption, business outcome—named before go-live

  3. 05Systems

    The platform implements approved changes in releases; it does not decide them

  4. 06Data

    A new field needs a data owner and the decision that will use it

  5. 08Governance

    Change authority per domain; time limits; operating, release and quarterly model reviews

  6. 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

  1. Process decisionsDuring the projectProject design authorityAfter go-liveProcess ownerMonthly process review
  2. Configuration and releasesDuring the projectProject build teamAfter go-livePlatform ownerPer release
  3. Enablement and adoption signalsDuring the projectProject change leadAfter go-liveAdoption ownerMonthly adoption review
  4. Data definitions and qualityDuring the projectProject data workstreamAfter go-liveData owner per conceptMonthly data forum
  5. Local support and feedbackDuring the projectProject super-usersAfter go-liveLocal championsWeekly in the first months

One lifecycle for every change

  1. 01RequestAnyone, with a business owner—or the friction register

    States the problem, not the solution; recurring friction enters as a request with its cause

  2. 02ClassifyOperating-model office

    Which domain: process, system, data, KPI, variation, exception

  3. 03DecideThe domain’s decision owner

    With the required evidence, within the time limit; prioritized in one backlog

  4. 04ImplementPlatform, process or data team

    In a versioned release, on the release cadence

  5. 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 register excerpt: friction, cause, type and action
FrictionCauseTypeAction
Discount approvals wait daysOne threshold for every dealProcessTier approvals by amount
Customer address retypedERP data not shown in the CRMSystem / integrationExpose the authoritative address
Monday pipeline exportsNo review viewUX / operating modelBuild the review workspace

Who may approve which change

Change types: authority, evidence and lead time
ChangeAuthorityEvidenceLead time
New fieldData owner for the conceptWhich decision will use itPer release
New or changed approvalDecision owner (with finance above policy)Risk being controlled; overlap checkNext quarterly review
Stage definitionGlobal process ownerAgeing and conversion dataNext quarterly review
Local ruleGlobal governanceVariation register entry4 weeks
New reportKPI definition ownerMetric contract and forumNext 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.

Decisions: who decides, approves and is consulted, evidence and time limit
DecisionDecidesApprovesConsultedEvidenceWithin
Name the operating ownersBusiness ownerSales leadershipProgramme leadThe responsibilities the project heldBefore go-live
Classify a change request or friction itemOperating-model office—RequesterThe problem statement, or the friction and its cause5 working days
Prioritize the backlogProcess owner—Platform owner, adoption ownerFriction by type and volume, change requestsPer release
Change a stage definitionCommercial process ownerGlobal governanceSales managers, platform ownerStage ageing and conversionQuarterly
Fix a data-quality issueData owner for the concept—Account ownersQuality measures by source5 working days
Release a new model versionGlobal governance—Domain ownersApproved changes and their impactQuarterly
Roll back a changeDomain decision owner—Platform ownerKPI moved the wrong wayNext release

05Governance

The forums that run and change the model.

Forums that run the operating model
ForumDecidesEvidence
Change triageWeeklyClassification and routing of requests and friction to ownersNew requests, the friction register
Operating & adoption boardMonthlyOperating rules, definitions, parallel-tool retirements, friction priorities, adoption escalationsAdoption signals, the friction register, quality measures, change requests
Release boardPer releaseWhat changes in the platform, from the governed backlogChange requests with business owners
Operating-model reviewQuarterlyModel version, core changes, variations to renew or retireException patterns, variation register, change effects

06Measurement

Signals that the model is owned—and improving.

Adoption signals: level, owner, meaning and action
SignalLevelOwnerMeaningAction
Friction items closed by a releaseL5 · ImprovementProcess ownerThe design is improvingReview the release impact on the related signal
Recurring ticket categoriesL5 · ImprovementAdoption ownerFriction the design has not fixedMove to the friction register with a cause
Exports before management reviewsL3 · Management adoptionBusiness ownerManagement drifting out of the systemFind what the view lacks
Changes reviewed against the KPI they namedL5 · ImprovementDomain decision ownersThe model learns from its own changesRoll back or adjust changes that moved the KPI the wrong way

07The trade-offs

Credible options, judged against these premises.

Rejected

Support desk only

Stable processes with few changes

Cost: Friction answered, never fixed
Rejected

Platform team implements requests as they come

Very small organizations

Cost: Configuration drifts; business decisions made by admins
Rejected

Freeze the model after go-live

Stable markets

Cost: Workarounds grow outside the system
Situational

Keep the project team indefinitely

Very early after a large go-live

Cost: Ownership stays temporary
Selected

Named 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 cadence

Design 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

  1. Who may change a stage, a rule, a field or a KPI?
  2. What evidence does each change need?
  3. Who can say no?

Ownership & friction

  1. Who owns each responsibility the project held—named before go-live?
  2. Where are recurring workarounds recorded, and who classifies them by cause?
  3. What can the adoption owner decide—and what belongs to other owners?

Release & learning

  1. How is the model versioned, and how are subsidiaries told what changed?
  2. Which exceptions and frictions changed the model last quarter?
  3. Which changes moved their KPI—and which were rolled back?

09Decisions & outputs

What the work produces.

  1. 01Ownership handoff model
  2. 02Friction register
  3. 03Governed backlog and release cadence
  4. 04Change-authority matrix
  5. 05Change lifecycle
  6. 06Model versioning
  7. 07Operating, release and quarterly review forums
  8. 08Adoption and change-effect review