Operating Model Design Consulting: Decision Rights, RACI, KPIs, and Weekly Cadence
Decision rights, RACI, KPIs, and a weekly cadence
A practical article for leaders who need the work, roles, and decisions to run cleanly after strategy is approved.
Quick answer
Operating model design turns strategy into how work actually gets done. Define decision rights, role ownership, governance forums, KPIs, and weekly routines so leaders can see what is moving and what is stuck. A strong operating model is not only an org chart. It is the way decisions, work, data, and accountability move through the business.
Related pages
Who this operating model design article is for
This page is for executives, transformation leaders, operating leaders, PMO teams, private equity portfolio teams, and functional heads who need cleaner decision making and stronger accountability.
| Reader | What they need | Best section to use first |
|---|---|---|
| CEO or COO | Clear owners, faster decisions, fewer escalations | Decision rights matrix |
| Transformation leader | A practical design that can be implemented | Templates and checklists |
| Functional leader | Clear roles, handoffs, and measures | RACI for roles and responsibilities |
| PMO or strategy team | Weekly cadence and KPI tracking | Weekly operating cadence |
Templates and checklists
Operating model one page template
Business unit or function: Strategy this model supports: Current pain points: Critical decisions: Critical workstreams: Key roles: Governance forums: Weekly cadence owner: KPIs: Decision rights gaps: RACI gaps: Top dependencies: Risks: First 30 days:
Decision rights matrix
Decision | Decision owner | Input required from | Consulted | Informed | Escalation path | Cadence Pricing exception | | | | | | Hiring approval | | | | | | Vendor selection | | | | | | Customer credit exception | | | | | | Product roadmap change | | | | | | Capital spend approval | | | | | |
RACI template
Work or decision | Responsible | Accountable | Consulted | Informed Monthly performance review | | | | Budget variance action | | | | Customer escalation | | | | Process change approval | | | | New system access approval | | | | Cross-functional handoff | | | |
Operating model readiness checklist
Design readiness [ ] Strategy link is clear [ ] Critical decisions are listed [ ] Decision owners are named [ ] RACI is complete for priority work [ ] Handoffs are documented [ ] Governance forums have clear agendas [ ] KPIs have owners and sources Launch readiness [ ] Leaders can explain what changed [ ] Managers know new decision paths [ ] Weekly cadence is scheduled [ ] Scorecard is ready [ ] First 30-day action list is approved [ ] Risks and escalations have owners
Sources: McKinsey operating model explainer, Bain winning operating models, PMI RACI reference
How to run it weekly
The weekly operating cadence is where the operating model becomes real. Use the meeting to clear decisions, fix handoffs, and track whether the new model is improving speed, quality, and accountability.
Weekly operating model review agenda
1) KPI review (10 minutes) - What moved? - What missed target? - What needs a decision? 2) Decision log review (10 minutes) - Which decisions are stuck? - Who owns each decision? - What escalation is needed? 3) Handoff and role clarity review (10 minutes) - Where did work slow down? - Which RACI line is unclear? - What needs to be updated? 4) Actions and owners (10 minutes) - Top 5 actions - Owner - Due date - Expected result
The weekly review should not become a broad status meeting. Keep it focused on decisions, handoffs, ownership, KPIs, and blockers.
What operating model design means in practice
Operating model design defines how a company turns strategy into work. It covers roles, processes, governance forums, decision rights, technology, data, talent, and measures. The value comes from making the model usable by leaders and teams every week.
In practice, operating model design should answer:
- What work matters most?
- Who owns each decision?
- Who performs the work?
- Which forums decide, review, or escalate?
- Which KPIs prove the model is working?
- What changes in the first 30 days?
Sources: McKinsey, McKinsey operating model redesign
The core pieces of an operating model
A useful operating model is simple enough to run, but complete enough to stop confusion.
| Piece | What it defines | Common failure |
|---|---|---|
| Structure | Teams, reporting lines, and business ownership | Boxes move, but work stays unclear |
| Decision rights | Who decides, who gives input, who is informed | Too many approvals and no single owner |
| RACI | Who is responsible, accountable, consulted, and informed | Multiple accountable owners for the same output |
| Governance cadence | Forums, agendas, decisions, and escalation paths | Meetings happen, but decisions do not |
| KPIs | How leaders know the model is working | Too many metrics with no action owner |
| Ways of working | How teams plan, decide, hand off, and improve | Old habits continue after the new model launches |
Decision rights matrix: who decides what
Decision rights are often where operating models fail. Teams may know the work, but not who has final decision authority. A decision rights matrix fixes this by naming the decision owner, required inputs, and escalation path.
| Decision type | Common owner | Input needed | Escalation trigger |
|---|---|---|---|
| Pricing exception | Commercial leader | Finance, sales, legal | Margin below threshold |
| Capital spend | Business unit leader | Finance, operations, procurement | Spend above approval limit |
| Customer escalation | Account owner | Operations, legal, service team | Revenue or legal exposure |
| System change | Process owner | IT, risk, impacted teams | Security or operational risk |
Sources: Bain decision roles, McKinsey decision rights
RACI for roles and responsibilities
A RACI matrix helps clarify which role is responsible, accountable, consulted, and informed for priority work. It is most useful when work crosses teams and decisions slow down because ownership is unclear.
| RACI role | Meaning | Practical rule |
|---|---|---|
| Responsible | Does the work | Can be more than one person or team |
| Accountable | Owns the outcome | Keep this to one owner when possible |
| Consulted | Gives input before the decision or work is complete | Limit to needed expertise |
| Informed | Needs to know the decision or result | Inform after the decision, not before every step |
Sources: PMI, PMI Lexicon
Operating model KPIs that matter
Operating model KPIs should show whether the model improves speed, clarity, quality, and results. Do not track every activity. Track the signals that prove the model is working.
| KPI | What it tells you | Review cadence |
|---|---|---|
| Decision cycle time | How long priority decisions take | Weekly |
| Escalation volume | Where decision rights are unclear | Weekly |
| Handoff rework | Where roles or process steps are breaking | Weekly |
| KPI owner coverage | How many scorecard items have clear owners | Weekly |
| Business result movement | Whether the model is improving the outcome it was built for | Monthly |
Red flags your operating model is not working
Watch for these signs after launch:
- Leaders keep escalating routine decisions.
- Meetings produce updates but few decisions.
- Teams use the old approval path because it is faster.
- RACI exists, but no one uses it in weekly work.
- Managers cannot explain what changed.
- KPIs are reported, but no actions are assigned.
- There are multiple owners for the same outcome.
Operating model design examples
Example 1: Growth company with role confusion
A fast-growing business has added teams faster than decision rules. Product, sales, and operations all make customer commitments. The operating model fix is a decision rights matrix for pricing, product changes, service exceptions, and customer escalations.
Example 2: Private equity portfolio company
A portfolio company has a strong value plan but weak weekly control. The operating model fix is a KPI owner map, a weekly operating review, and clear escalation rules for margin, working capital, and headcount decisions.
Example 3: Post-merger organization
Two companies combine, but legacy approvals remain. The operating model fix is a single role map, a shared governance calendar, a decision log, and manager briefings that explain what changed.
FAQs
What is operating model design?
Operating model design defines how strategy becomes work. It covers decisions, roles, governance forums, processes, technology, data, people, and KPIs.
What is a target operating model?
A target operating model is the future way the business should run. It shows how work, roles, decisions, governance, data, and measures should operate after the change.
What should an operating model include?
It should include structure, decision rights, RACI, governance forums, priority processes, KPIs, technology and data needs, talent impacts, and a launch plan.
What is the difference between an operating model and an org chart?
An org chart shows reporting lines. An operating model shows how work gets done, who decides, how teams coordinate, and how performance is managed.
How do you measure if an operating model is working?
Measure decision cycle time, escalation volume, rework, KPI owner coverage, handoff quality, and the business result the model was designed to improve.
How often should an operating model be reviewed?
Review the working parts weekly after launch: decisions, handoffs, KPIs, and blockers. Review the overall design monthly or quarterly, depending on how much change the business is managing.
What is a decision rights matrix?
A decision rights matrix names who owns each important decision, who gives input, who is informed, and when escalation is required.
What is RACI in operating model design?
RACI is a role clarity tool. It defines who is responsible, accountable, consulted, and informed for work, decisions, or deliverables.
If you want an operating model design with decision rights, RACI, KPIs, and a weekly cadence:
contact NMS Consulting.
Sources
