A target operating model only becomes real when it shows up in what you measure, how you review performance, and what you reward. If those stay wired to the old operating model, people will quietly keep doing what they’ve always done, no matter how good your TOM decks look.
This chapter focuses on making performance management an integrated part of your TOM:
- Link the TOM to a small, sharp set of enterprise KPIs and value drivers
- Design metrics for value streams, functions, and teams
- Establish review cadences and management routines
- Align incentives so people are rewarded for working in the new way, not the old one
10.1 Linking the TOM to Enterprise KPIs and Value Creation
Your TOM exists to advance the value agenda you set in earlier chapters: growth, cost, risk, customer, and organizational health. Performance management is where you hard-wire that link.
Start by stating, in simple terms, how the TOM is supposed to create value:
- Which costs it should structurally reduce (and how)
- Which growth levers it should unlock (and where)
- Which risk losses or compliance issues it should prevent
- Which customer outcomes it should improve
- How it should simplify and strengthen the organization
Then translate that into a short list of enterprise-level KPIs. Think 8–12, not 40.
Common families:
- Financial
- Revenue growth, margin, cost-to-serve, cost/income ratio, ROIC
- Customer / stakeholder
- NPS or equivalent, on-time delivery, complaint rates, churn
- Operational
- End-to-end cycle times, first-time-right, rework, automation rate, digital adoption
- Risk / control
- Operational incidents, audit findings, losses, breaches, near-misses
- People / organization
- Engagement, regretted attrition in critical roles, filling key roles internally, spans/layers simplification
Not every KPI needs to be new. But you should be clear which ones are most sensitive to the TOM changes. For instance:
- If your TOM heavily centralizes and automates operations, you should expect:
- Lower cost per transaction
- Shorter and more stable lead times
- Fewer manual errors and control failures
- If your TOM reorients around journeys and segments, you should expect:
- Better experience metrics for those journeys
- Higher conversion, cross-sell, or retention in focus segments
For each enterprise KPI, ask three questions:
- What TOM levers affect this most?
- E.g., process simplification, shared services, new platforms, journey ownership.
- Where in the TOM roadmap will we see changes first?
- Certain BUs, regions, or journeys will move earlier.
- What’s the plausible impact range?
- You don’t need perfect precision, but you do need a view of whether TOM choices are material.
- You don’t need perfect precision, but you do need a view of whether TOM choices are material.
You’re building a mental value map: from TOM design levers ➜ operational metrics ➜ enterprise KPIs.
Use that value map to:
- Decide which TOM initiatives are worth prioritizing
- Structure the TOM business case
- Keep leaders honest when projects drift away from what actually moves KPIs
If you can’t show a clear line from a TOM choice to at least one enterprise KPI, reconsider whether that choice is necessary.
10.2 Designing Metrics for Value Streams, Functions, and Teams
Enterprise KPIs alone are too high-level to steer day-to-day behavior. You need a cascade of metrics that make sense for value streams, functions, and teams—without creating reporting overload.
A useful way to think about it:
- Enterprise KPIs – what the company must deliver
- Value stream / journey KPIs – how end-to-end flows perform
- Functional KPIs – how specialized capabilities perform
- Team-level metrics – what people can influence directly
If you design this well, everyone can answer:
“What should I manage every week that, if improved, will genuinely help the company hit its goals?”
Value stream / journey metrics
For each priority value stream, define 5–8 core KPIs that describe end-to-end performance. Typical categories:
- Speed
- Total lead time (e.g., from application to decision, order to delivery)
- Time in each major stage
- Quality / reliability
- First-time-right rate
- Rework and defect rates
- SLA adherence
- Customer / user experience
- Journey-level satisfaction or NPS
- Drop-off points (e.g., where customers abandon onboarding or purchase)
- Contact rates after process completion (complaints, “where is my order?” contacts)
- Efficiency
- Cost per case, order, or transaction
- FTE per unit of volume, or per revenue unit linked to the stream
- Risk / control performance
- Exceptions, overrides, and breaches tied to the journey
- Control failures or near-misses in key steps
These metrics should be:
- End-to-end: not just functional fragments
- Owned by the journey owner
- Reported regularly (e.g., monthly at executive level, more frequently for operations)
If a “journey owner” doesn’t have a small, clear KPI set, the role is a title, not a real accountability.
Functional metrics
Functions (Sales, Operations, Risk, Finance, HR, IT, etc.) still need their own metrics, but these should support, not contradict, value stream metrics.
Examples:
- Sales: opportunity coverage, win rates, pipeline health, forecast accuracy
- Operations: productivity per FTE, backlog, schedule adherence, utilization
- Risk: adherence to limits, timeliness and quality of reviews, model performance
- Finance: close quality and timeliness, forecast accuracy, working capital metrics
- IT: availability and incident resolution for systems that underpin key journeys, change success rates
Check that:
- Functional KPIs don’t push behavior that works against journey targets (e.g., Ops maximizing utilization while harming lead time and NPS).
- Functions have at least a few shared metrics with journeys and other functions (e.g., Sales and Operations both tracking on-time delivery or “promise kept”).
Team-level metrics
At team level, abstract KPIs must translate into something tangible and actionable. Good team metrics are:
- Clearly influenced by the team’s daily work
- Measured frequently (weekly or even daily for some operations)
- Tracked in simple visuals (whiteboards, simple dashboards, daily huddle boards)
Examples:
- For a claims team: claims closed per day, backlog, % within SLA, rework rate
- For a contact center team: average handle time and first contact resolution, customer satisfaction, adherence to schedule
- For a dev squad: cycle time, deployment frequency, escape defect rate, availability of the services they own
Aim for 3–5 metrics per team, not 20. And insist that they are visible where the work happens.
Avoiding metric overload
A pattern that works:
- Define an official KPI tree from enterprise ➜ value stream ➜ function ➜ team.
- Mark a small subset as “North Star” at each level (the ones discussed with senior leadership).
- Allow local metrics for internal improvements, but keep them clearly secondary.
The rule of thumb:
- If employees tell you “we track about 40 things, but only 3 really matter,” that’s a design failure. Those 3 should be the ones designed and agreed in the TOM, not discovered informally.
10.3 Performance Review Cadence and Management Routines
Metrics only matter if they’re used. The way you review performance and act on it is core to the TOM.
You are designing a management rhythm: the regular meetings and routines through which leaders and teams understand performance, solve problems, and adjust.
A practical hierarchy:
- Enterprise and BU reviews – monthly/quarterly
- Journey and functional reviews – monthly
- Operational reviews and huddles – weekly / daily
Enterprise and BU reviews
Typically monthly for operational focus and quarterly for strategy/value focus.
Content:
- Enterprise KPIs and a small set of leading indicators.
- Focus on exceptions and trends, not reading through every metric.
- TOM-linked changes: progress on key journeys, platforms, and capability builds.
Decisions:
- Resource shifts across BUs or programs.
- Acceleration, redesign, or stopping of major initiatives.
- Structural changes where patterns show persistent issues.
Governance: this should build on the forums defined in your TOM governance (Chapter 6). The key is to anchor the agenda in the TOM KPI set, not in legacy reports.
Journey and functional reviews
Monthly or bi-weekly, depending on volatility.
For each priority value stream:
- Review the end-to-end KPI set.
- “Walk” a few concrete recent cases through the journey, using data and examples.
- Identify structural obstacles: unclear ownership, broken handovers, system constraints, policy issues.
- Define and track improvement actions with owners and timelines.
For functions:
- Review functional KPIs, but always link them back to how they support journey performance.
- Coordinate with journey owners on priorities and trade-offs.
These reviews are where you turn TOM from “design” into continuous improvement engine.
Operational reviews and daily/weekly huddles
At team level, performance management is about short feedback loops:
- Daily or shift huddles (15 minutes):
- Yesterday’s performance vs targets.
- Today’s plan: volumes, staffing, issues.
- Quick escalation of blockers.
- Weekly operational reviews (30–60 minutes):
- Trends in KPIs (backlogs, quality, customer feedback).
- Root-cause discussion on recurring problems.
- Small, concrete improvement actions.
Your TOM should specify:
- Which teams are expected to run huddles and with which metrics.
- Standard templates for simple visual boards or dashboards.
- Manager expectations: e.g., “front-line leaders run daily huddles using TOM metrics and coach on problem-solving, not just distribute tasks.”
If your management routines don’t change, your operating model won’t either. The routines are the behavioral scaffolding of the TOM.
10.4 Aligning Incentives with the Target Operating Model
The last piece is making sure that rewards and consequences encourage the behaviors the TOM needs.
Incentives do not only mean money. They include:
- Variable pay and bonuses
- Promotion and career opportunities
- Recognition and visibility
- Access to interesting work and resources
But variable pay is where misalignment bites hardest, so start there.
Linking incentives to TOM metrics
You don’t need to overhaul all compensation schemes at once. But you should:
- Review current incentive plans
- Which metrics drive bonuses for executives, BU heads, sales, operations, and key functions?
- Which of those metrics map to your TOM KPIs, and which are tied to old priorities or silo performance?
- Introduce or rebalance metrics towards TOM outcomes
For example:- Add end-to-end journey KPIs (e.g., onboarding time, first-time-right, NPS) into the scorecards of leaders across Sales, Operations, and IT.
- Include standardization and automation goals for functions that own processes and platforms.
- Factor in risk and control quality for leaders whose areas carry significant risk (not just volume or cost).
- Ensure cross-functional alignment
- Avoid having one function’s bonus depend on a metric that directly conflicts with another function’s metric.
- Consider shared metrics across teams that must collaborate (e.g., both Sales and Operations sharing a delivery reliability KPI).
A simple rule: if a journey owner is measured on NPS and cycle time, but the functions in that journey are measured only on volume and local cost, the journey will lose.
Qualitative performance criteria
Not everything that matters can be measured cleanly. Your performance management system should also explicitly evaluate:
- Contribution to TOM implementation and adoption
- Collaboration across units and functions
- Building of capabilities and teams aligned with the TOM
- Adherence to TOM-aligned cultural behaviors (e.g., data-driven decisions, use of standard processes, escalation discipline)
Include these in:
- Leadership performance reviews
- Promotion panels
- Talent discussions
Make it normal to say, “X delivered their numbers, but did so by fighting the new operating model and creating local exceptions. That is not what we reward.”
Recognition and symbolic rewards
In change, symbolism matters as much as mechanics:
- Publicly recognize teams that improve journey performance using TOM ways of working.
- Celebrate decommissioning of legacy processes and tools when replaced by TOM-consistent ones.
- Highlight leaders who standardize “their” area for the greater good, even at the cost of some local autonomy.
These signals help people understand that the TOM is not a side project but the way the company now works and wins.
Guardrails when changing incentives
While aligning incentives, watch for:
- Over-complexity: scorecards with 10+ metrics dilute focus. Keep core incentive metrics to a handful.
- Short-termism: don’t push quarterly targets that encourage gaming the system or under-investment in TOM foundations (e.g., tech and capability).
- Unintended consequences: pilot changes in a few units where possible, and monitor behavior closely.
A quick incentive alignment checklist:
- Are the executive and BU scorecards visibly linked to TOM KPIs and journey outcomes?
- Do journey owners, functional heads, and platform leaders share at least some common metrics?
- Are team-level metrics used in regular performance dialogues and coaching, not just stored in a dashboard?
- Does your performance and promotion process explicitly consider TOM adoption and collaboration, not just individual business results?
If you can answer “yes” to most of these, your performance system is working with your target operating model, not against it.
