Chapter 2 of 4

Designing the Target Operating Model

3 sections · ~6 min read · 3 practice questions · part of Capstone: SC Transformation

Learning objectives

  • Describe the elements of a target operating model: organization, process, technology, and metrics.
  • Sequence capability improvements into a multi-year roadmap that absorbs organizational change.
  • Identify the 'quick wins' that fund the broader program without sacrificing long-term credibility.

What a Target Operating Model Actually Is

A target operating model (TOM) is the end-state design of how the supply chain function will run: organization (roles, decision rights, locations), technology (systems, data, automation), process (S&OP cadence, planning workflow, supplier-collaboration model), and metrics (KPIs and accountability). A common error is to treat the TOM as a technology deployment. Technology is one of four pillars and usually the easiest; organization and process changes are where most programs stall. A good TOM is documented at the level of decision rights—who decides what, when, with what data—not at the level of boxes on an org chart. Decision rights clarify who holds the demand forecast, who overrides the planner, who calls the expedite, who commits to the supplier. When decision rights are ambiguous, every cross-functional meeting becomes a fight about authority. When they are explicit, meetings become decisions. The TOM is the design that makes the strategy executable; without it, the diagnostic findings are a wish list.

Sequencing the Roadmap

Multi-year roadmaps fail when they front-load change. A common pattern is to launch with a big technology deployment, then try to retrofit process and organization around it; the technology goes live but is not used, or is used badly, and credibility evaporates. A better pattern is to sequence: (1) foundational data and governance (master data, KPIs, baseline reporting), (2) process stabilization (S&OP that actually decides, supplier reviews that actually change behavior, planning routines that actually run), (3) capability build (forecast improvement, inventory policy, supplier development), (4) technology at scale (planning platform, S&OP tool, automation). Each phase produces visible value; that value funds the next phase. Early improvements can help staff and sponsors judge whether the program is worth continuing. A common failure is to defer quick wins in pursuit of a 'big bang'; the big bang then loses executive patience before it delivers.

Choosing Quick Wins That Don't Compromise the Long Game

Quick wins must satisfy two tests: they must produce measurable value within 90 days, and they must not lock in choices that the TOM would want to reverse. Examples of good quick wins: standardizing KPI definitions and publishing weekly performance (value in days, no commitments that constrain the future); reducing SKU proliferation in non-strategic categories (savings appear in 6 months, no tooling impact); renegotiating expedite contracts (immediate savings, no future impact). Examples of bad quick wins: implementing a single planning tool ahead of process redesign (locks the process into a tool); outsourcing a function that is central to the TOM (locks the future); promising large fill-rate gains from a single forecast improvement (often does not deliver and burns credibility). The right discipline is to ask, 'will this quick win still be the right answer after the TOM is in place?' If yes, do it; if not, defer it.

Worked example

Problem

A manufacturer has a $4.2M annual expedite bill on $15M of total freight (28% expedite share) and is targeting a $3M/year reduction in run-rate expedite within 18 months. Phase 1 quick wins can plausibly deliver 40% of the target ($1.2M) in 6 months without process redesign. Phase 2 process changes (S&OP, supplier collaboration) deliver another 40% ($1.2M) by month 12. Phase 3 capability (planning tools, safety-stock optimization) deliver the final 20% ($0.6M) by month 18. Compute cumulative savings at each phase end and the implied run-rate at 18 months. Also estimate the one-time program cost at $1.5M and payback.

Step by step

  1. Phase 1: cumulative annual saving at month 6 = $1.2M (40% of $3M).
  2. Phase 2: at month 12, +$1.2M = $2.4M cumulative.
  3. Phase 3: at month 18, +$0.6M = $3.0M cumulative.
  4. Run-rate at 18 months = $3.0M/year.
  5. Phase costs (illustrative): Phase 1 $0.3M (process change, contracts), Phase 2 $0.5M (S&OP, supplier collaboration), Phase 3 $0.7M (tooling, capability). Total program cost = $1.5M, incurred within the phase that spends it.
  6. Convert run-rate to cash carefully, because this is where these models usually go wrong. A run-rate is an annualised figure; cash realised over a six-month window is the average run-rate across that window multiplied by 0.5 years, not the run-rate itself.
  7. Months 1–6: run-rate ramps from $0 to $1.2M, averaging $0.6M. Cash = $0.6M × 0.5 = $0.30M.
  8. Months 7–12: run-rate ramps from $1.2M to $2.4M, averaging $1.8M. Cash = $1.8M × 0.5 = $0.90M. Cumulative at month 12 = $1.20M.
  9. Months 13–18: run-rate ramps from $2.4M to $3.0M, averaging $2.7M. Cash = $2.7M × 0.5 = $1.35M. Cumulative at month 18 = $2.55M.
  10. Net benefit at month 18 = $2.55M − $1.5M = $1.05M. Note this is less than half the $5.1M a run-rate-as-cash shortcut would produce; treating each period's annual run-rate as though it were realised within that six-month period doubles every figure.
  11. Payback: cumulative cost is $0.3M by month 6, $0.8M by month 12, $1.5M by month 18. Cumulative benefit passes cumulative cost at around month 6 and stays ahead, since from month 7 the program earns roughly $0.117M per month against about $0.083M per month of Phase 2 spend.

Answer. Run-rate at 18 months = $3.0M/year. Cumulative cash benefit by month 18 ≈ $2.55M against $1.5M of program cost, for a net of ≈ $1.05M, with the program roughly cash-neutral from around month 6 onward. The steady-state case is strong — $3.0M/year against a one-time $1.5M — but the in-program cash picture is far tighter than the run-rate headline suggests, and a sponsor who has been shown only the $3.0M figure will expect the benefit far sooner than it can arrive. Limitations: the phase split and the linear ramp between milestones are both illustrative, and actual deliverability depends on organisational readiness and on whether each phase's savings materialise at all.

Practice

Work each question before opening the solution.

  1. What are the four pillars of a target operating model?

    Show solution for question 1

    Organization (roles, decision rights, locations), process (S&OP cadence, planning workflow, supplier collaboration), technology (systems, data, automation), and metrics (KPIs and accountability).

  2. Why is sequencing a multi-year transformation important?

    Show solution for question 2

    Because each phase must produce visible value that funds the next. Front-loading change (typically a big technology deployment) creates risk that the program loses credibility before delivering, which kills follow-on phases.

  3. What two tests should a quick win satisfy?

    Show solution for question 3

    It must deliver measurable value within ~90 days, and it must not lock in choices that the long-term target operating model would want to reverse.