Operating Model & Process Design / 01 · Differentiation → motions → operating rules

Designing a global commercial operating model for fundamentally different sales motions

The first question was not how opportunities should be configured, but whether everything called an “opportunity” was the same kind of work. It was not—so the operating model and its decisions were designed first, and the technology after them.

The case in brief

Current reality

Everything the business pursued was called an opportunity and ran through one process—first orders from new distributors, range introductions, account development, indirect demand and multi-year OEM projects alike.

What must become true

Each way the business really sells runs on its own operating path—its own qualification, evidence, authority, cadence and definition of won—inside one shared frame leadership can compare, with named owners who keep it working after go-live.

Design question

Are all of these commercial opportunities actually the same business process?

01Reality

One label was hiding fundamentally different commercial work.

An industrial B2B business sells through several subsidiaries into aftermarket distribution and to equipment makers. One opportunity process carried everything: a first order from a new distributor, an existing customer entering a new product range, account development, demand generated for partners, and multi-year OEM and private-label projects involving engineering, quality and plants. Stages, forecasts and approvals meant different things depending on who used them.

  • One stage list served a two-week reorder and a three-year OEM programme
  • “Qualified” meant a friendly conversation in one team and a priced technical specification in another
  • Project opportunities looked stale after 90 days and were pushed out of the forecast by rule
  • A standard price-list offer and a customer-specific product with new tooling went through the same approval
  • Engineering, quality and plants joined some deals by email, invisible to the pipeline
  • “Won” meant a signed order, a nomination or a first series delivery, depending on the team

One label covered work with radically different time horizons, decision processes, technical complexity, teams, risk, evidence, pricing and post-win behaviour. The process treated them as one; the business did not.

02Differentiation

What actually changes the way the work behaves?

The analysis looked at how each kind of opportunity actually moved—before any stage was named. Twelve variables changed the process on their own. They act through five forces, and the forces are what a leader needs to see first.

  1. Commercial purpose

    What is the work trying to achieve, for whom, with what—and through whom?

    • Commercial intent
    • Customer maturity
    • Product familiarity
    • Direct or indirect
  2. Time & uncertainty

    How long until a result, and what must be proven before a price means anything?

    • Execution horizon
    • Technical and commercial uncertainty
  3. Organizational involvement

    Who has to take part—and who has to decide?

    • Teams involved
    • Decision authority
  4. Commitment & evidence

    What is put at risk, what must exist before committing, and on what price basis?

    • Risk and strategic weight
    • Evidence and documentation
    • Pricing and negotiation
  5. Operating rhythm

    How is the work reviewed and forecast—and what starts once it is won?

    • Cadence, forecast and post-win life
The 12 dimensions underneath
  1. Commercial intentAcquire, develop, recover—or enter a new range?
  2. Customer maturityExisting customer, potential customer, or a relationship still being proven?
  3. Product familiarityAn existing product, a new range, or a customer-specific development?
  4. Direct or indirectDoes the party creating the demand also fulfil the sale?
  5. Execution horizonWeeks to an order, or years to a series award?
  6. Technical and commercial uncertaintyWhat must be proven before a price means anything?
  7. Teams involvedSales alone—or engineering, quality, plants, finance and project management?
  8. Decision authorityWho may commit the company: a sales manager within a price band, or a cross-functional Go / No-Go?
  9. Risk and strategic weightWhat is exposed if it goes wrong: margin, capacity, investment, a strategic account?
  10. Evidence and documentationWhat must exist before the next step: a sample, a specification, a feasibility study, an agreement?
  11. Pricing and negotiationA price list with a discount band, a customer-specific price, or a cost-based project quote?
  12. Cadence, forecast and post-win lifeWho reviews it, how often, how is it forecast—and what starts once it is won?

03Segmentation

Seven commercial motions emerged from the reality.

The variables clustered. Opportunities that shared purpose, horizon, uncertainty and participants behaved alike, and each cluster became a candidate motion. Seven survived the test below; the rest stayed variants of the motion they resembled.

The segmentation ruleA difference became a separate motion only when it changed how the work had to be qualified, decided, governed or managed. Otherwise it stayed a variant of an existing motion.

FromEverything called an “opportunity”

Select a motion to see how it runs inside the shared frame. Arrow keys move between motions.

Shared frame: the questions every motion answers
  1. Identify
  2. Qualify
  3. Shape
  4. Decide
  5. Close
  6. Post-win

01New Customer

Acquire a new relationship.

Lifecycle
  1. Discover
  2. qualify
  3. propose
  4. first order
Intent
Acquire
Information
Company, need, decision-maker
Approval
Credit and price band
Pricing and documents
Discount band; offer letter
Forecast and ageing
Commit at negotiation; stage ageing
Management cadence
Weekly pipeline
After it is won
First-order follow-up, onboarding
Horizon
Months
Technical complexity
Low
Teams
Sales

02New Product / Range

Expand an existing relationship into a new range.

Lifecycle
  1. Identify
  2. sample
  3. approve
  4. first order
Intent
Enter a range
Information
Range, volumes, sample result
Approval
Price band
Pricing and documents
Range price list; sample protocol
Forecast and ageing
Commit after sample approval
Management cadence
Monthly range review
After it is won
Range activation tracked
Horizon
Weeks to months
Technical complexity
Samples, fitment
Teams
Sales, product management

03Account Management

Develop, defend or recover the relationship over time.

Lifecycle
  1. Plan
  2. review
  3. act, each period
Intent
Develop, defend, recover
Information
Potential, targets, plan
Approval
Plan sign-off
Pricing and documents
Account agreement
Forecast and ageing
Plan against target, not deals
Management cadence
Monthly account review
After it is won
Next-period plan
Horizon
Rolling year
Technical complexity
Low
Teams
Account and sales manager

04Cross / Up-Sell

Expand a defined transaction inside an active account.

Lifecycle
  1. Identify
  2. propose
  3. order
Intent
Expand
Information
Product, quantity
Approval
Price band
Pricing and documents
Existing conditions
Forecast and ageing
Commit at acceptance
Management cadence
Weekly
After it is won
Order inside the account plan
Horizon
Weeks
Technical complexity
Low
Teams
Sales

05Demand Generation / Indirect

Create demand that another party fulfils.

Lifecycle
  1. Create
  2. accept
  3. fulfil
Intent
Create demand for a partner
Information
Origin, partner, attribution
Approval
Partner acceptance
Pricing and documents
Partner price
Forecast and ageing
Not forecast; sourced pipeline
Management cadence
Weekly handoff review
After it is won
Attribution to origin
Horizon
Handoff clock, then partner cycle
Technical complexity
Low
Teams
Marketing, partner, sales

06OEM / Strategic Project

Win a long-horizon technical programme.

Lifecycle
  1. RFI
  2. RFQ
  3. nomination
  4. series
Intent
Win a programme
Information
Specification, volumes, ramp-up, investment
Approval
Cross-functional Go / No-Go gates
Pricing and documents
Cost-based quote; technical offer; agreement
Forecast and ageing
Volume ramp over years; milestone dates
Management cadence
Monthly project; quarterly portfolio
After it is won
Milestones to start of production and ramp-up
Horizon
One to three years
Technical complexity
High: specification, validation
Teams
Sales, engineering, quality, plant, finance, project

07Private Label Project

Develop and launch a customer-specific branded product.

Lifecycle
  1. Brief
  2. develop
  3. approve
  4. launch
Intent
Build a customer-brand line
Information
Specification, brand, compliance
Approval
Go / No-Go and compliance
Pricing and documents
Customer-specific price; product sheets
Forecast and ageing
Launch volumes; milestone dates
Management cadence
Monthly project
After it is won
Launch, then account plan
Horizon
Months to over a year
Technical complexity
Medium to high: product, packaging
Teams
Sales, product, quality, compliance

Compare the operating rules7 motions × 11 dimensions

Seven motions against eleven operating dimensions: the evidence behind the segmentation, for readers who want to inspect it.

Compare the operating rules
DimensionNew CustomerNew RangeAccount Mgmt.Cross / Up-SellIndirectOEM projectPrivate Label
IntentAcquireEnter a rangeDevelop, defend, recoverExpandCreate demand for a partnerWin a programmeBuild a customer-brand line
HorizonMonthsWeeks to monthsRolling yearWeeksHandoff clock, then partner cycleOne to three yearsMonths to over a year
Technical complexityLowSamples, fitmentLowLowLowHigh: specification, validationMedium to high: product, packaging
TeamsSalesSales, product managementAccount and sales managerSalesMarketing, partner, salesSales, engineering, quality, plant, finance, projectSales, product, quality, compliance
LifecycleDiscover → qualify → propose → first orderIdentify → sample → approve → first orderPlan → review → act, each periodIdentify → propose → orderCreate → accept → fulfilRFI → RFQ → nomination → seriesBrief → develop → approve → launch
ApprovalCredit and price bandPrice bandPlan sign-offPrice bandPartner acceptanceCross-functional Go / No-Go gatesGo / No-Go and compliance
InformationCompany, need, decision-makerRange, volumes, sample resultPotential, targets, planProduct, quantityOrigin, partner, attributionSpecification, volumes, ramp-up, investmentSpecification, brand, compliance
Pricing and documentsDiscount band; offer letterRange price list; sample protocolAccount agreementExisting conditionsPartner priceCost-based quote; technical offer; agreementCustomer-specific price; product sheets
Forecast and ageingCommit at negotiation; stage ageingCommit after sample approvalPlan against target, not dealsCommit at acceptanceNot forecast; sourced pipelineVolume ramp over years; milestone datesLaunch volumes; milestone dates
Management cadenceWeekly pipelineMonthly range reviewMonthly account reviewWeeklyWeekly handoff reviewMonthly project; quarterly portfolioMonthly project
After it is wonFirst-order follow-up, onboardingRange activation trackedNext-period planOrder inside the account planAttribution to originMilestones to start of production and ramp-upLaunch, then account plan
Path 01New Customer
Intent
Acquire
Horizon
Months
Technical complexity
Low
Teams
Sales
Lifecycle
Discover → qualify → propose → first order
Approval
Credit and price band
Information
Company, need, decision-maker
Pricing and documents
Discount band; offer letter
Forecast and ageing
Commit at negotiation; stage ageing
Management cadence
Weekly pipeline
After it is won
First-order follow-up, onboarding
Path 02New Range
Intent
Enter a range
Horizon
Weeks to months
Technical complexity
Samples, fitment
Teams
Sales, product management
Lifecycle
Identify → sample → approve → first order
Approval
Price band
Information
Range, volumes, sample result
Pricing and documents
Range price list; sample protocol
Forecast and ageing
Commit after sample approval
Management cadence
Monthly range review
After it is won
Range activation tracked
Path 03Account Mgmt.
Intent
Develop, defend, recover
Horizon
Rolling year
Technical complexity
Low
Teams
Account and sales manager
Lifecycle
Plan → review → act, each period
Approval
Plan sign-off
Information
Potential, targets, plan
Pricing and documents
Account agreement
Forecast and ageing
Plan against target, not deals
Management cadence
Monthly account review
After it is won
Next-period plan
Path 04Cross / Up-Sell
Intent
Expand
Horizon
Weeks
Technical complexity
Low
Teams
Sales
Lifecycle
Identify → propose → order
Approval
Price band
Information
Product, quantity
Pricing and documents
Existing conditions
Forecast and ageing
Commit at acceptance
Management cadence
Weekly
After it is won
Order inside the account plan
Path 05Indirect
Intent
Create demand for a partner
Horizon
Handoff clock, then partner cycle
Technical complexity
Low
Teams
Marketing, partner, sales
Lifecycle
Create → accept → fulfil
Approval
Partner acceptance
Information
Origin, partner, attribution
Pricing and documents
Partner price
Forecast and ageing
Not forecast; sourced pipeline
Management cadence
Weekly handoff review
After it is won
Attribution to origin
Path 06OEM project
Intent
Win a programme
Horizon
One to three years
Technical complexity
High: specification, validation
Teams
Sales, engineering, quality, plant, finance, project
Lifecycle
RFI → RFQ → nomination → series
Approval
Cross-functional Go / No-Go gates
Information
Specification, volumes, ramp-up, investment
Pricing and documents
Cost-based quote; technical offer; agreement
Forecast and ageing
Volume ramp over years; milestone dates
Management cadence
Monthly project; quarterly portfolio
After it is won
Milestones to start of production and ramp-up
Path 07Private Label
Intent
Build a customer-brand line
Horizon
Months to over a year
Technical complexity
Medium to high: product, packaging
Teams
Sales, product, quality, compliance
Lifecycle
Brief → develop → approve → launch
Approval
Go / No-Go and compliance
Information
Specification, brand, compliance
Pricing and documents
Customer-specific price; product sheets
Forecast and ageing
Launch volumes; milestone dates
Management cadence
Monthly project
After it is won
Launch, then account plan

Everything in the matrix belongs to the motion. Outcome states, reason codes, forecast categories and the review format belong to the shared frame.

The pointThe motions were not created to configure the CRM more neatly. The business already sold in fundamentally different ways; the design made those differences explicit and gave each one its own operating path.

04Design decision

One shared frame. Different operating paths.

Once the motions were visible, the structural question was how far apart they should be. Four designs were credible. Each solves part of the problem—and creates a cost somewhere else.

  1. Option A

    One global opportunity process

    Benefit
    Simple configuration and apparent standardization.
    Cost
    Different work is forced into common stages whose meaning changes by team: “qualified” and “won” stop meaning one thing.
  2. Option B

    One process per subsidiary

    Benefit
    Fits each local reality.
    Cost
    Turns organizational boundaries into process boundaries: the same motion runs differently by country, and global comparability is lost.
  3. Option C

    Fully separate models for every motion

    Benefit
    Maximum specialization for each way of selling.
    Cost
    Duplicated concepts, fragmented reporting, and seven models to govern and evolve instead of one.
  4. Selected design

    One shared frame with differentiated operating motions

    Benefit
    Shared semantics where comparison matters; different rules where the business actually behaves differently.
    Cost
    Requires explicit motion definitions, named owners and disciplined governance—or the motions drift back into one process.

Design decision

One shared commercial frame with differentiated operating motions: common semantics where leadership must compare—outcomes, reasons, forecast categories, customer identity—and motion-specific lifecycle, evidence, authority and cadence where the work genuinely differs. Systems encode the model only after it is agreed.

Why it fitsThe problem was never too much variation or too little; it was variation in the wrong place. The subsidiary is not the unit of difference—the kind of commercial work is. The selected design puts difference where the work differs and keeps it out everywhere else.

05Operating model

What remains common—and what belongs to the motion.

The shared operating frame

These six steps are not stages every motion shares. They are the questions every motion must answer—and what stays common in the answer, so leadership can compare. Each motion answers them with its own lifecycle.

  1. Identify

    Every motion answers: What kind of commercial work is this?

    What stays common
    The motion is declared on entry—never left blank, never inferred later
    Answered by
    Opportunity owner
  2. Qualify

    Every motion answers: What evidence makes it worth pursuing?

    What stays common
    “Qualified” means the motion’s own evidence exists—one meaning per motion, recorded the same way
    Answered by
    Opportunity owner
  3. Shape

    Every motion answers: What must be defined before commitment?

    What stays common
    Solution, price basis and required assessments agreed and visible
    Answered by
    Owner with the teams the motion requires
  4. Decide

    Every motion answers: Who must authorize what?

    What stays common
    Every approval or gate recorded as a decision, with its owner and evidence
    Answered by
    Decision owner set by the motion
  5. Close

    Every motion answers: What constitutes the commercial outcome?

    What stays common
    One outcome list and one set of reason codes across all motions
    Answered by
    Opportunity owner
  6. Post-win

    Every motion answers: What operating process begins next?

    What stays common
    The downstream path is declared: first order, account plan or project milestones
    Answered by
    Set by the motion

Seven different lifecycles

One frame, answered seven ways. Each motion’s lifecycle is its own; what it must record at each step is common.

  1. New Customer
    1. Discover
    2. qualify
    3. propose
    4. first order
  2. New Product / Range
    1. Identify
    2. sample
    3. approve
    4. first order
  3. Account Management
    1. Plan
    2. review
    3. act, each period
  4. Cross / Up-Sell
    1. Identify
    2. propose
    3. order
  5. Demand Generation / Indirect
    1. Create
    2. accept
    3. fulfil
  6. OEM / Strategic Project
    1. RFI
    2. RFQ
    3. nomination
    4. series
  7. Private Label Project
    1. Brief
    2. develop
    3. approve
    4. launch

Shared across motions, or specific to one

Shared across motions

  • Outcome semantics: what won, lost and No-Go mean
  • Common reason codes
  • Common forecast vocabulary
  • One management comparison frame
  • One customer and opportunity identity
  • Core reporting semantics
  • Core governance principles

Specific to each motion

  • Lifecycle
  • Qualification evidence
  • Decision rights and approvals
  • Pricing logic
  • Documents
  • Management cadence
  • Definition of won
  • Post-win transition
  • Stage-ageing expectations

Local configurationOnly where a real operating difference exists, and within governed boundaries—language, local document templates, thresholds inside the bands a motion sets. A subsidiary never redefines what a stage, “qualified” or “won” means.

Who owns the model itself

Who owns the model itself
LayerOwned byDecides
Shared frameGlobal commercial governance: commercial leadership with sales operationsOutcome semantics, reason codes, forecast categories, the review format—and the motion catalogue itself
Motion definitionA named motion owner for each motionThe motion’s lifecycle, evidence, approvals, cadence and definition of won—inside the shared frame
Local executionSubsidiary commercial leadershipHow the motions are run locally, within the boundaries the catalogue marks as local
New motion or structural changeThe governance forum, on evidenceWhether a motion is added, merged or retired, or the frame changes—never by configuration first
System encodingThe platform teamHow an approved decision is held in the systems; it never changes a motion on its own

06Decisions & exceptions

Different motions require different authority.

Authority follows the motion: a price band for a reorder, a cross-functional Go / No-Go for an OEM programme. Exceptions do not bypass the model; they expose where authority and recovery must be designed.

Who authorizes the commitment, by motion

New Customer
Credit and price band
New Product / Range
Price band
Account Management
Plan sign-off
Cross / Up-Sell
Price band
Demand Generation / Indirect
Partner acceptance
OEM / Strategic Project
Cross-functional Go / No-Go gates
Private Label Project
Go / No-Go and compliance

Exceptions and return paths

When
WhenThenOwnerReturns to
An opportunity changes nature—a reorder turns into a customer-specific developmentRe-classified to the right motion; the history is kept and the new motion’s evidence becomes requiredOpportunity owner, confirmed by the sales managerQualify, in the new motion
No motion fitsRecorded as a motion request instead of being forced into the closest type; decided in the governance forumSales operations, for the governance forumIdentify
Required evidence is missing at a stage exitThe stage cannot be left; the gap is visible in the review instead of being bypassed by editing the stageOpportunity ownerThe current stage
A project fails a Go / No-Go gateClosed as No-Go with the gate and the reason—never left to age in the pipelineDecision owner of the gateClosed, with a decision record
2 more exceptions
When
WhenThenOwnerReturns to
The receiving partner rejects generated demandReturned with a reason to the originator; attribution closesOriginating teamIndirect demand: qualify
An opportunity exceeds its motion’s ageing benchmarkFlagged in the motion’s own review: update, requalify or closeSales managerThe current stage, or closed

07Then, technology

Technology encodes the operating model; it does not define it.

Only when the motions, their rules and their owners were agreed did the question become technical. Each system has one job in the model, and none of them decides what a motion is.

Systems and partiesCRMPricing / CPQERPDocument generationWorkflow and approvalsData platform

  • CRMHolds the motion, its lifecycle, evidence, ownership and operating state—one record per opportunity
  • Pricing / CPQApplies the price basis the motion allows: a band, a customer-specific price or a cost-based quote
  • ERPStays authoritative for the customer account, orders and deliveries once commercial work turns into transactions
  • Document generationProduces the commercial and technical documents each motion requires—offer letter, technical offer, agreement
  • Workflow and approvalsRoutes the decisions the motion declares, brings in the teams it names and keeps the decision record
  • Data platformNormalizes outcomes, forecasts and motion health across motions for leadership

Eight encoding rules

  1. Classification

    The motion is explicit and mandatory.

    One opportunity record, typed by motion—not seven separate models—built on a shared opportunity core (universal states, common fields, one account) that each motion extends instead of copying.

  2. Lifecycle

    Each motion has its own lifecycle and exit evidence.

    A stage set per motion; each stage carries written exit criteria, and validation by motion and stage stops work leaving a stage without its evidence.

  3. Authority

    Approval paths follow the motion and its thresholds.

    Approval as a state machine: commercial and financial decisions kept apart, Go / No-Go gates recorded as decisions, a price or scope change after approval restarts only the decision it affects—and nothing is approved by silence.

  4. Data

    Information appears when the motion requires it.

    Required information is asked for at the stage where the motion needs it, not up front for every opportunity.

  5. Commercial execution

    Pricing, documents and cross-functional participation follow the motion.

    Price basis and document templates selected by motion; engineering, quality, plant or finance brought in on the stage the motion declares, with guidance per motion and stage.

  6. Comparability

    Shared outcome, reason and forecast semantics make motions comparable.

    One outcome list, one set of reason codes and one set of forecast categories; each motion maps its stages to those categories, so a three-year project and a two-week order land in one forecast.

  7. Post-win

    The downstream process is explicit per motion.

    The next path—first order, account plan, nomination and start of production—declared per motion, never inferred from the amount.

  8. Change

    Operating-model changes are approved before system rules change.

    A change reaches configuration as an approved operating-model decision with its owner, and every rule in the system can be traced back to one.

08Execution & governance

How the model becomes the way the business actually works.

Design is not finished when the configuration is deployed. The transition moves existing work, management routines and habits onto the model—and keeps the model able to change.

From the old process to the new model

  1. Classify existing work

    Every open opportunity is mapped to one of the seven motions, by its owner, before anything is configured.

  2. Resolve ambiguity

    Anything that cannot be classified is evidence that a motion definition needs work—not a user to correct.

  3. Stabilize the operating rules

    Qualification, authority, evidence and outcome semantics are agreed with the motion owners before configuration starts.

  4. Encode the model

    The CRM, workflows and supporting systems are configured only once the rules are stable.

  5. Move management routines

    Pipeline and portfolio reviews start using each motion’s own semantics—its stages, its ageing, its definition of won.

  6. Retire generic behaviour

    The old generic stages and rules stop being accepted as a valid way of working.

  7. Measure and evolve

    Re-classifications, ageing, gate delays and outcomes show where the model needs adjusting.

Governing the motion model

Motion ownership
Every motion has a named owner, accountable for its definition, its health measures and the changes it proposes.
Change authority
Changes inside a motion are approved by its owner within the shared frame; changes to the frame, and new, merged or retired motions, go to the governance forum.
Local variation
Subsidiaries vary only what the catalogue marks as local; a need outside it is raised as a change request, not configured.
Evidence for structural change
A new motion needs evidence that its rules genuinely differ: recurring re-classifications, gates or evidence no existing motion can hold.
Review cadence
Motion health is reviewed quarterly with the motion owners; the frame and the catalogue once a year, or sooner when the evidence demands.
From friction to evolution
Re-classifications, motion requests and stalled gates are collected as evidence; each is resolved, rejected or turned into an approved change—and only then configured.

09Measurement

Is the operating model working?

Two kinds of measure: whether each motion is performing, and whether the motion design itself still fits the work.

Metric
MetricWhyOwnerCadenceTriggers
Qualified pipeline by motionComparable only after each motion’s own qualificationSales managementWeeklyGenerate pipeline where a motion is short
Stage ageing against the motion benchmarkDays in stage mean nothing across horizons of weeks and yearsSales managersWeeklyUpdate, requalify or close
Win rate by motionQualification quality differs by motionMotion ownersQuarterlyRevise the motion’s qualification criteria
Gate decisions on timeProject motions stall at cross-functional gatesGate decision ownersMonthlyEscalate overdue assessments
Re-classificationsA health signal for the model itself: work that keeps changing motion shows definitions that do not match realityMotion owners, with sales operationsQuarterlyReview the motion definitions—or bring a structural change to governance

Measuring the designIf opportunities are repeatedly re-classified, the issue may not be user discipline: the motion definitions may be wrong. Re-classifications measure the model, not only the people using it.

10Second layer & outputs

Questions that would change the design—and what the work produced.

The second layer

Segmentation

  1. What makes two opportunities the same business process?
  2. When is a difference a new motion rather than a variant of an existing one?

Comparability

  1. Which semantics must remain common across every motion?
  2. What does “won” mean when the commercial commitment and the operational revenue may be years apart?

Authority

  1. Who owns the cross-functional decisions each motion requires?
  2. Who may change a motion—or re-classify an opportunity—once work has started?

What the work produced

  1. 01Commercial-motion segmentation model
  2. 02Differentiation framework
  3. 03Shared operating frame
  4. 04Motion rule catalogue
  5. 05Decision and authority model
  6. 06Process-to-system mapping
  7. 07Operating-model governance model
  8. 08Motion health measures