The OSCAR Model: A Practitioner’s Guide to Structured Decision-Making in Projects and Operations
Introduction: Why Decision Conversations Break Down
In project management, the most expensive problems rarely start with a technical failure. They start with a conversation that lost its structure. A stakeholder review that meandered without resolution. A team discussion where options were debated but no decision was made. A planning session that ended with everyone nodding and nobody accountable.
The OSCAR Model offers a remedy. Originally developed as a coaching framework, OSCAR has found widespread application in project management, operations leadership, and Business Process Management (BPM) environments — precisely because it mirrors the way well-run projects already think: define the goal, understand the context, evaluate options, commit to action, and review outcomes.
This guide goes beyond the basics. It explains each component of the model with practical depth, shows how it applies in real project and BPM delivery contexts, and gives you the questions and structure you need to run OSCAR-style conversations with confidence.
| PART 1: WHAT IS THE OSCAR MODEL? Framework overview and origins |
What Is the OSCAR Model?
OSCAR is a structured conversation and coaching framework. The acronym stands for:
The elegance of OSCAR lies in its sequence. Each step is dependent on the previous one. You cannot make a good choices decision without first understanding the situation. You cannot define actions without first selecting from the choices. And review only has value if it traces back to the outcome defined at the start.
Where Did the OSCAR Model Come From?
The OSCAR model was developed by Andrew Gilbert and Karen Whittleworth as a structured coaching framework. It draws on established goal-setting research and the broader GROW model family, but adds the Choices and Review steps to create a fuller decision loop.
While it originated in executive coaching, practitioners in project management and operations quickly recognized that its structure maps well to how structured project conversations — risk reviews, issue resolution sessions, planning workshops, and retrospectives — ought to work. Unlike rigid methodologies, OSCAR is a guiding sequence, not a script. It can be scaled from a five-minute check-in to a two-hour governance session.
| PART 2: HOW OSCAR WORKS IN PRACTICE Step-by-step practitioner breakdown |
Breaking Down Each Step: A Project Management Lens
O — Outcome: Define Before You Discuss
The first and most important step is establishing what the conversation is actually for. This sounds obvious, but in practice, most discussions in project environments begin with the problem rather than the desired end state. The result is that the conversation meanders, solutions are proposed before the problem is understood, and the meeting ends without a clear outcome.
Defining the outcome upfront does three things. It focuses attention on what matters. It gives you a measure against which all subsequent choices can be evaluated. And it prevents the conversation from being hijacked by the loudest voice rather than the clearest thinking.
| 💡 Practitioner Tip In a project kickoff or planning session, start with: “Before we look at how to approach this, can we agree on what success looks like in three months?” That single question can save hours of misaligned work. |
S — Situation: Diagnose Before You Prescribe
Once the outcome is clear, the Situation step maps the current reality. This is where you surface assumptions, identify constraints, clarify dependencies, and acknowledge what you do not yet know.
In project delivery, inadequate situation analysis is one of the most common sources of rework. Teams jump to solutions before understanding the risk landscape, the stakeholder dynamics, or the technical constraints. OSCAR enforces the discipline of diagnosing before prescribing.
The Situation step is also where the OSCAR model distinguishes itself from simple decision trees. It is not just about gathering facts — it is about understanding the context that will determine which facts matter most.
| 💡 Practitioner Tip Use structured questions: “What do we know for certain? What are we assuming? What could change that assumption?” This triad is borrowed from risk management and adapts well to the OSCAR Situation step. |
C — Choices: Resist the First Good Idea
The Choices step is where OSCAR diverges most sharply from how most decisions actually get made in practice. In project environments under time pressure, teams often adopt the first option that seems workable. OSCAR requires you to map all realistic options before committing to any.
This does not mean generating an infinite list. It means being deliberate enough to articulate at least two or three genuine alternatives, even if the final choice was already the obvious one. The discipline of naming alternatives guards against groupthink, surfaces options that might be superior, and builds confidence in the chosen path because it was selected — not defaulted to.
For project managers, this step aligns with the decision analysis techniques in PMBOK, including tools such as multicriteria decision analysis and cost-benefit analysis.
A — Actions: From Decision to Commitment
The Actions step is where OSCAR converts intent into accountability. This is the step most frequently skipped or under-defined in practice. Teams leave meetings with a decision but without clarity on who owns the first action, what done looks like, and when it should happen.
Good action definition in the OSCAR model requires three things: a named owner, a specific next step (not a vague direction), and a deadline or trigger condition. In project management terms, this is the difference between a decision log entry and an action register item. Both matter, but the action register is what drives delivery.
| 📋 For more on how to capture structured decisions in your project, see our guide to Decision Logs and Assumption Logs. |
R — Review: The Step Most Often Abandoned
Review is the step that separates the OSCAR model from simpler decision frameworks. It closes the loop between the outcome defined at the start and the actions taken to achieve it.
In project and BPM environments, review serves three functions: it validates whether the chosen action delivered the intended outcome, it surfaces adjustments needed in the current cycle, and it feeds learning back into future decisions. This mirrors the check-and-act phases of PDCA (Plan-Do-Check-Act) and the retrospective ceremonies in Agile delivery.
The practical challenge is that review requires discipline to schedule and follow through. In fast-moving delivery environments, there is always another priority. The OSCAR model makes review non-optional — it is not an optional debrief, it is the final step of the framework.
| PART 3: OSCAR IN PROJECT MANAGEMENT Applying the model across delivery contexts |
Where OSCAR Fits in the Project Management Lifecycle
The OSCAR model is not limited to coaching conversations. It maps naturally to decision points throughout the project delivery lifecycle. The following table illustrates where each step adds the most value in a typical project context:
| OSCAR Step | Project Context | Goal | Who Leads |
| Situation | Stakeholder misalignment or scope ambiguity | Achieve shared understanding of project constraints | All relevant stakeholders |
| Choices | Multiple delivery approaches under evaluation | Select the approach that best balances risk, time, and cost | Project Manager + sponsor |
| Actions | Decision paralysis during planning or execution | Commit to a course of action with clear owners | Team leads and workstream owners |
| Review | Post-decision governance and lessons learned | Verify outcomes and capture institutional knowledge | PMO or delivery lead |
Scenario: Using OSCAR to Resolve a Scope Escalation
A mid-project scope escalation arrives from a senior stakeholder requesting additional features with no corresponding timeline or budget adjustment. The project manager calls a structured resolution session using OSCAR:
- Outcome: Define what a resolved situation looks like: stakeholder expectations are reset, or scope is formally adjusted.
- Situation: The project is 60% complete, contingency has been partially consumed, and team capacity is committed through the next sprint.
- Choices: (A) Absorb the request with no change. (B) Formally raise a change request. (C) Defer the feature to Phase 2. (D) Descope an existing item of equivalent size.
- Actions: The PM raises a change request within 24 hours. Sponsor review is scheduled for Day 3. A decision is communicated to the team by end of week.
- Review: Two weeks post-decision: did the agreed approach resolve the escalation? Was the stakeholder relationship maintained? What would we do earlier next time?
This structured approach prevents the scope escalation from becoming a political issue and keeps the decision visible, auditable, and time-bound.
OSCAR as a Meeting Structure
One of the most underused applications of the OSCAR model is as a meeting agenda template. Rather than running open-agenda team sessions or stakeholder reviews that meander toward inconclusive summaries, use OSCAR to structure the conversation from the outset:
- Opening five minutes: agree the Outcome of this session
- Ten to fifteen minutes: review the Situation — what do we know, what has changed, what are the constraints?
- Twenty minutes: examine the Choices — what options are on the table?
- Ten minutes: agree Actions — who does what, by when?
- Five minutes: set the Review — how and when will we follow up?
This structure works for risk workshops, planning sessions, retrospectives, and escalation reviews. It is particularly useful in distributed or cross-functional project teams where alignment is harder to achieve and meeting time is expensive.
| PART 4: OSCAR IN BUSINESS PROCESS MANAGEMENT Application in BPM and operations delivery |
The OSCAR Model in Business Process Management Environments
Business Process Management (BPM) organizations face a particular set of decision challenges. Operations are complex, interdependent, and often running simultaneously across multiple client programs and delivery geographies. In this environment, decisions about process redesign, workforce allocation, technology adoption, and service level management cannot be made casually.
The OSCAR model provides a structured lens that BPM leaders and Operations Managers can use consistently across these decision types — without requiring a separate methodology for each context.
| OSCAR Phase | BPM Application |
| Outcome | Define SLA improvement target before reviewing workforce options |
| Situation | Map current process pain points: queue spikes, handoff delays, exception volumes |
| Choices | Evaluate automation vs. upskilling vs. headcount vs. hybrid approach |
| Actions | Pilot selected solution with measurable KPIs and governance checkpoints |
| Review | Compare actuals to baseline; feed findings into the next planning cycle |
Scenario: A BPM Operations Manager Reviews a Staffing Model
An Operations Manager overseeing a multi-client delivery environment is reviewing whether to redesign the staffing model for a process with increasing exception volumes and declining throughput. Using OSCAR:
- Outcome: Restore throughput to contracted SLA levels within 45 days without exceeding budget by more than 10%.
- Situation: Exception volume has increased by 22% over three months. Two senior processors have resigned. Automation is partially deployed but not covering edge cases.
- Choices: (A) Cross-train existing staff. (B) Introduce a temporary resource layer. (C) Expand automation coverage. (D) Renegotiate the SLA while implementing a fix.
- Actions: Cross-training begins Week 1. Automation vendor is briefed on edge-case scope by Day 3. SLA renegotiation is tabled as a parallel track with governance approval.
- Review: At Day 30: review throughput trends, exception rate, and staff confidence. At Day 45: final SLA compliance check and decision on whether automation expansion continues.
This is a pattern that Operations Managers across BPM environments will recognise. OSCAR adds the discipline that prevents reactive decisions from creating downstream problems.
| PART 5: OSCAR VS OTHER FRAMEWORKS How it compares and when to use it |
OSCAR vs. GROW vs. PDCA: Knowing Which Framework to Use
Project management and operations professionals often encounter multiple structured thinking frameworks. Understanding how they differ helps you select the right tool for the context.
| PART 6: FREQUENTLY ASKED QUESTIONS Common questions from practitioners |
FAQ: The OSCAR Model
Is the OSCAR model only for one-on-one coaching conversations?
No. While it originated in individual coaching, OSCAR works equally well in group settings — team workshops, project reviews, and operations governance sessions. The structure simply needs to be visible and agreed by participants at the start of the session.
How long does an OSCAR conversation take?
It scales to context. A routine decision conversation might run through all five steps in fifteen minutes. A major project governance decision might require a structured half-day session. The framework does not dictate time — it dictates sequence.
Can OSCAR be used in Agile project environments?
Yes. OSCAR maps naturally to Agile ceremonies. It is particularly useful in sprint reviews (Situation and Review), backlog refinement sessions (Choices and Actions), and retrospectives (Outcome and Review). Its flexibility makes it compatible with both waterfall and iterative delivery.
What is the most common mistake when using OSCAR?
Skipping or rushing the Situation and Choices steps. In time-pressured environments, teams often jump from Outcome directly to Actions. This shortcuts the analysis and frequently leads to decisions that need to be revisited. The Situation and Choices steps are where most of the quality is built into the decision.
How does OSCAR integrate with project governance frameworks like PMBOK or PRINCE2?
OSCAR does not replace these frameworks — it operates within them. In PMBOK-aligned environments, OSCAR can structure the conversations that feed decision logs, change requests, and risk responses. In PRINCE2 environments, it supports stage boundary reviews and exception management. Think of OSCAR as a conversation protocol that sits above the documentation layer.
Is the Review step the same as a lessons-learned session?
Related but not identical. A lessons-learned session is typically a project-level retrospective. The OSCAR Review step operates at the level of an individual decision or action: did this specific choice produce the intended outcome? The insights from multiple OSCAR Reviews can feed into a broader lessons-learned exercise.
Explore More on ProjInsights
The OSCAR model is one of dozens of decision-making and operational frameworks covered in depth across ProjInsights. Whether you are preparing for a PMP exam, navigating a complex delivery challenge, or building stronger operations discipline, you will find structured, practitioner-written guides across the following areas:
| Further Reading on ProjInsights Decision-Making & Strategy → Leavitt’s Diamond Model — aligning people, process, technology, and structure during change Operations & Process Improvement → Operations Managers’ Top Challenges in the BPM Industry Project Management → Assumption Logs and Decision Logs — embedding structured thinking into your project governance Tools & Calculators → Standard Time Calculator, Attrition Rate Calculator, and more at projinsights.com/project-management-calculators |
| CONCLUSION Key takeaways |
Final Thoughts: Structure Is a Competitive Advantage
The OSCAR model is not a complex tool. Its power comes from its insistence on sequence. In project management and BPM environments where the pressure to act quickly often overrides the discipline to think clearly, having a structured conversation framework is a genuine competitive advantage.
Leaders who use OSCAR consistently find that their teams make fewer decisions twice, align faster in stakeholder sessions, and produce better-documented rationale for the choices they make. For project managers and Operations Managers managing complex, multi-stakeholder environments, that discipline is not a nice-to-have — it is what separates delivery from drift.
Use OSCAR the next time you are running a planning session, mediating a scope discussion, or coaching a team member through a decision they cannot seem to make. Run through the five steps. Insist on the sequence. You will notice the difference.
Sources and References
- Gilbert, A. and Whittleworth, K. (2009) The OSCAR Coaching Model. Originated in executive coaching literature.
- Project Management Institute (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) — Seventh Edition. PMI.
- ProjInsights internal editorial standards and practitioner research, 2024–2026. projinsights.com