Author: Taylor Warfield, Former Bain Manager and interviewer

Last Updated: October 7, 2026

 

The McKinsey SCR framework is a three-part communication structure that organizes any business message into a Situation, a Complication, and a Resolution, and it is the backbone of how consultants build slides, write client emails, and deliver recommendations. This article breaks down each component, walks through four worked examples including a real McKinsey client deck, and shows you how to use SCR in a consulting interview.

 

Before reading on:

 

Most candidates struggle to land interviews and even fewer turn them into offers. Watch my free training to learn how to triple your chances of landing interviews and increase your chances of receiving an offer by 8x.

 

👉 Watch for free

 

Key Takeaways

 

The McKinsey SCR framework structures a business message into three parts: the Situation your audience already accepts, the Complication that makes it untenable, and the Resolution you recommend.

 

• SCR traces back to Barbara Minto, the first female MBA professional hire McKinsey ever made

 

• The Situation is facts only, and it should be the shortest section you write

 

• The Complication is tension, not more data, and it is the part most people get wrong

 

• The Resolution is one clear recommendation, never a menu of options for the client to pick from

 

• McKinsey's 2010 US Postal Service deck follows the structure exactly, moving from context to a projected $33 billion annual loss to a four-part fix

 

• In an interview, SCR is the fastest way to structure a final recommendation, a behavioral answer, or a written case deck

 

What Is the McKinsey SCR Framework?

 

The McKinsey SCR framework is a three-part storyline structure used to organize business communication: Situation (the facts everyone agrees on), Complication (what changed and why it matters), and Resolution (what you recommend doing about it). Consultants use it to structure presentations, emails, client updates, and case interview recommendations.

 

SCR is not a problem-solving tool. It does nothing to help you figure out the answer, which is what case interview frameworks are for. SCR is what you reach for once you already know the answer and need someone else to accept it.

 

That distinction matters more than it sounds. Most people communicate the way they think, walking their audience through the background, then the analysis, then the conclusion. SCR compresses the first two parts to almost nothing so the audience arrives at your recommendation while they still care.

 

Component	What it is	Question it answers	Space it gets
Situation	Neutral facts your audience already believes	Where do things stand today?	Roughly 10% to 15%
Complication	The change or tension that makes the Situation unacceptable	Why can we not keep doing this?	Roughly 15% to 25%
Resolution	Your single recommendation plus the evidence behind it	What should we do, and what happens if we do it?	Roughly 60% to 75%

 

The Situation has one job: get everyone nodding. State facts the client already knows and accepts, because the moment your audience disagrees with a fact in the Situation, they stop listening to the rest.

 

The Complication is where the argument actually lives. Something has changed, broken, or emerged, and that change is why the meeting is happening at all.

 

A chart showing declining revenue is evidence, not a Complication. The Complication is the sentence that says the current path leads somewhere unacceptable.

 

The Resolution is a decision, not a discussion. "We could consider three options" is not a Resolution. "You should consolidate these 40 stores and renegotiate this contract, which recovers 2 points of margin in 12 months" is.

 

Where Did the SCR Framework Come From?

 

SCR comes out of the work Barbara Minto did at McKinsey in the 1960s and early 1970s. According to McKinsey's own alumni profile of her, Minto was the first female MBA professional hire the firm ever made, joining the Cleveland office in 1963 and moving to London in 1966.

 

Her job was editing reports, and she noticed the same defect over and over. Consultants produced sound analysis but jumbled findings, conclusions, and recommendations together in a way that never led anywhere clearly. In her words, the problem was the thinking rather than the language.

 

Minto started reorganizing every report into a pyramid with the recommendation on top. She also coined MECE along the way, which she pronounces as one syllable rhyming with "niece."

 

She left the firm in 1973 after the oil crisis triggered layoffs in the London office and turned her method into a training business. Minto published The Pyramid Principle in 1985 and a revised edition in 1996. Sixty years later, the structure she built is still taught to incoming McKinsey hires.

 

Why Does McKinsey Use the SCR Framework?

 

McKinsey uses SCR because senior executives do not read or listen sequentially. A CEO with 15 minutes between meetings will interrupt your context to ask what you want them to do. SCR front-loads the reason they should care and gets to the answer before they ask.

 

There are five reasons the structure survives at every major firm.

 

• It matches how decisions get made: people act when they feel a gap between where they are and where they need to be, which is exactly the Situation-to-Complication move

 

• It builds agreement before disagreement: starting with facts the client already accepts means the first thing they do in your meeting is agree with you

 

• It forces you to have a point: you cannot write a Resolution without committing to a recommendation, which surfaces weak thinking early

 

• It scales from an email to a 40-slide deck: the same three beats work in three sentences or three sections

 

• It survives interruption: if the client cuts you off after the Complication, they already understand the stakes

 

In my experience at Bain, the single biggest jump in a new consultant's effectiveness came from this shift. The analysis quality stayed roughly the same. What changed was that partners stopped rewriting their slides.

 

How Do You Use the SCR Framework?

 

Write the Resolution first, then work backward. This feels wrong, but you cannot judge which facts belong in the Situation until you know what you are arguing for.

 

1. Write your recommendation in one sentence: if it takes two sentences, you have two recommendations and need to pick the primary one
   
   
2. Work backward to the Complication: ask what has to be true about the world for your recommendation to be the obvious move
   
   
3. Strip the Situation to facts nobody will fight you on: cut anything the client would push back on, because that belongs in the Complication or the evidence
   
   
4. Test the flow out loud: read Situation, Complication, and Resolution as three consecutive sentences and check that a stranger would follow the logic
   
   
5. Build the supporting evidence under the Resolution: group your analysis into two to four buckets that prove the recommendation and nothing else

 

Step 4 is the one people skip. If your three sentences do not hang together on their own, adding 30 slides will not fix it. That three-sentence version is the storyline, and everything else is proof.

 

One more adjustment worth knowing: when your audience already agrees with your recommendation and just needs reinforcement, flip the order and open with the Resolution. When they are likely to resist, keep the standard SCR order so the Complication does the persuading before you ask for anything.

 

What Are Examples of the McKinsey SCR Framework?

 

The four examples below run from a real McKinsey client deck down to a two-paragraph email. The structure is identical in all four, which is the whole point of learning it.

 

Example 1: How McKinsey Used SCR for the US Postal Service

 

In March 2010, McKinsey delivered a deck to the United States Postal Service on its future business model. The full document is published on the USPS website, and its table of contents is the SCR framework with different labels: recent context, base case, addressing the challenge, and short term requirements.

 

Situation: USPS net income swung from a $0.9 billion profit in fiscal 2006 to a $3.8 billion loss in fiscal 2009. Mail volume fell 17% over that period, retiree health benefit pre-funding consumed roughly 12% of total revenue by 2010, and cost savings could not offset the revenue decline because the network is largely fixed cost.

 

Complication: With no additional management action, the base case projected a $33 billion annual loss in 2020 and $238 billion in cumulative losses. The statutory debt ceiling of $15 billion would be hit in October 2010.

 

Resolution: Actions within Postal Service control cut the 2020 annual loss to $15 billion and cumulative losses to $115 billion. Those actions split into four buckets: roughly $2 billion from product and service initiatives, roughly $10 billion from productivity improvements, roughly $0.5 billion from workforce flexibility, and roughly $0.5 billion from purchasing savings.

 

Notice the proportions. The Situation and Complication together account for about the first third of the deck, and everything after that is Resolution and supporting evidence.

 

Notice also that the Complication does not introduce a new fact. It takes the trend from the Situation and projects it forward to an unacceptable endpoint. That projection is the entire persuasive move.

 

Example 2: How to Use SCR for a Case Interview Final Recommendation

 

Let's say you have just finished a profitability case interview for a regional grocery chain. The numbers below are illustrative, but the shape of the answer is what matters.

 

Recommendation first: "I recommend consolidating scheduling across your 40 Midwest stores and renegotiating the produce supplier contract."

 

Situation: "Your operating margin has fallen from 4% to 1% over three years, and revenue has held roughly flat over that same period."

 

Complication: "Two thirds of that decline comes from labor cost per store, which is up 18% while sales per store stayed flat. At the current rate you reach breakeven in about 18 months."

 

Resolution detail: "Those two moves recover roughly 2 points of margin within a year. The main risk is service quality during the scheduling transition, so I would pilot it in five stores first and read the customer satisfaction scores before rolling out."

 

The recommendation goes first because that is what an interviewer is grading. The Situation and Complication then function as your evidence rather than your setup, which is the one adjustment SCR needs to survive contact with a McKinsey case interview.

 

Example 3: How to Use SCR for a Fit Interview Answer

 

SCR works for behavioral stories because a good story and a good recommendation have the same skeleton. Take a question like "tell me about a time you led a team through a difficult situation."

 

Situation: "Last summer I led a four-person team building the pricing model for a client's new subscription product."

 

Complication: "Three weeks in, the client pulled the launch from Q4 to Q2, cutting our timeline in half. Two of my four analysts were also staffed part-time on another project."

 

Resolution: "I cut the workplan down to the two analyses that actually drove the pricing decision and dropped the other four. I negotiated with the other engagement manager for one analyst full-time for two weeks. We delivered six days before the new deadline and the client launched on schedule."

 

Most candidates spend 90 seconds on the Situation and 20 on the Resolution, which is backwards. Interviewers are assessing what you did, so the Resolution should carry at least half your airtime. If you want to master these answers quickly, my fit interview course covers 98% of the questions you will face in a few hours.

 

SCR and the STAR method overlap heavily, and you do not need both. The practical difference is that SCR puts more weight on the tension that made the story hard.

 

That emphasis is exactly what McKinsey PEI interviewers probe for. They keep asking what made the situation difficult until you either produce real tension or run out of story.

 

Example 4: How to Use SCR in a Client Email

 

The shortest useful version of SCR is three sentences in an email. This is what a day in the life of a McKinsey consultant actually involves far more often than building decks.

 

Subject: Recommend we push the pricing workstream to next Wednesday

 

Situation: "We planned to present pricing findings at Friday's steering committee."

 

Complication: "The client's finance team sent the transaction data yesterday instead of last Tuesday, and the cleaning alone will take two days."

 

Resolution: "I recommend we present the customer segmentation on Friday as planned and move pricing to next Wednesday's session. That keeps the committee cadence intact and gives us a defensible number instead of a rushed one. Let me know by end of day if you would rather I flag this to the client directly."

 

Where Can You Use the SCR Framework at Work?

 

SCR works anywhere you need someone to accept a conclusion, which covers most of what a consultant does in a week. The table below maps the three beats onto five common situations.

 

Context	Situation	Complication	Resolution
Steering committee deck	Where the workstream stands against the plan	What the analysis uncovered that changes the plan	The decision you need approved today
Weekly team update	What the team committed to last week	What slipped and why it matters	The reprioritized plan and who owns each piece
Project proposal	The client's current performance	The gap that is costing them money right now	Your scope and the outcome you commit to
Performance review	Your role and the scope you owned	The hardest constraint you worked through	What you delivered and what you want next
Interview answer	Your role in the story, in one sentence	The obstacle that made the outcome uncertain	The action you took and the measurable result

 

The pattern holds because all five situations have the same job. Someone needs to move from where they are to where you want them, and the Complication is the only thing that makes them willing to move.

 

There is one context where SCR actively hurts you: exploratory working sessions. If you are brainstorming with a client team or pressure-testing a hypothesis, leading with a Resolution shuts down the conversation you were trying to have.

 

The tell is whether you already know the answer. Once you do, SCR is the right tool. Before you do, you want issue trees and open questions instead.

 

How Is SCR Different From SCQA and the Pyramid Principle?

 

SCR, SCQA, and the Pyramid Principle are not competing methods. SCR and SCQA are two versions of the same narrative opening, and the Pyramid Principle is the logic structure that sits underneath whichever opening you choose.

 

Method	Structure	What it adds	Best used for
SCR	Situation, Complication, Resolution	The simplest three-beat storyline	Decks, emails, and spoken recommendations
SCQA	Situation, Complication, Question, Answer	States the governing question explicitly before answering it	Written reports and memos where the question needs naming
Pyramid Principle	Answer on top, grouped arguments below, data at the base	Organizes everything underneath the recommendation	Structuring the body of any document or deck

 

The practical rule is simple. Use SCR or SCQA to get your audience to the answer, then use the Pyramid Principle to structure everything you say after the answer.

 

Other firms use different names for the same three beats, so do not get attached to the acronym. What matters is that the context is short, the tension is explicit, and the recommendation is unmistakable.

 

How Do You Use the SCR Framework in a Case Interview?

 

Use SCR for your final recommendation, for behavioral answers, and for structuring a written case deck. Do not use it for the analytical portion of the case, because SCR organizes conclusions rather than generating them.

 

For the final recommendation, lead with the answer and then deliver Situation and Complication as evidence. Interviewers score the first 10 seconds heavily, so opening with context wastes your best moment. Aim for roughly 60 to 90 seconds total.

 

For a written case interview, SCR is the fastest way to sequence your slides under time pressure. Build one Situation slide, one Complication slide, and three to four Resolution slides, then fill in the analysis. Deciding the storyline before you touch the data is what separates candidates who finish from candidates who run out of time.

 

Where candidates go wrong is treating SCR as a replacement for structure during the case itself. Your case interview structure and your storyline do different jobs, and interviewers notice immediately when you confuse them. If you want to learn both quickly, my case interview course walks you through the strategies I used as a Bain interviewer in as little as 7 days.

 

One more note on the final round. Partners at every firm test whether you can hold a recommendation under pressure, which is why the Resolution has to be one clear action rather than a set of options. Having coached hundreds of candidates through McKinsey final round interviews, the answers that land are the ones that commit.

 

What Are the Most Common SCR Framework Mistakes?

 

Six mistakes account for nearly every weak SCR storyline I have seen, whether in a candidate's mock interview or a first-year consultant's draft deck.

 

Mistake #1: Making the Situation Too Long

 

Candidates and junior consultants both over-invest here because context feels safe. The client already lives in the Situation and does not need you to explain their own business back to them. Two or three sentences is usually enough.

 

Mistake #2: Confusing the Complication With Data

 

A chart of falling revenue is not a Complication. The Complication is the statement that falling revenue puts you below breakeven by a specific date. Data supports a Complication, but it never is one.

 

Mistake #3: Offering Options Instead of a Recommendation

 

"We see three possible paths forward" is the most common failure in the Resolution. Clients hire consultants for judgment, and interviewers grade for it. Pick one, say why, and address the alternatives as risks.

 

Mistake #4: Putting a Fact in the Situation That the Client Disputes

 

The Situation only works if it produces agreement. Put a contested number there and you spend the next 10 minutes defending your baseline instead of discussing your recommendation. Move anything debatable into the Resolution where you have evidence ready.

 

Mistake #5: Saying the Labels Out Loud

 

Announcing "now for the complication" makes you sound like you memorized a template. The audience should feel the progression without hearing the scaffolding. This applies double in interviews, where naming frameworks reads as a substitute for thinking.

 

Mistake #6: Writing the Situation First

 

If you start at the beginning, you end up including every fact you gathered rather than the two that matter. Write the Resolution, then work backward. The Situation is defined by what your recommendation needs, not by what you happen to know.

 

What Tips Help You Master the SCR Framework Faster?

 

Tip #1: Write the three sentences before you open PowerPoint

 

Type your Situation, Complication, and Resolution as three plain sentences in a blank document. If they do not flow, no amount of slide design will save the deck.

 

This habit costs 10 minutes and saves hours of rework. It is also the fastest way to catch that you do not actually have a recommendation yet, which is worth knowing before you build 30 slides. The same discipline carries directly into a case interview presentation, where you have 30 minutes total and no time to rebuild.

 

Tip #2: Borrow the Complication from the client's own words

 

The strongest Complications are the ones the client already said out loud in a steering committee or an interview. Write them down verbatim during the engagement and use them.

 

When the tension in your storyline came from the client's mouth, nobody argues with it. You skip the entire debate about whether the problem is real and go straight to what to do about it.

 

Tip #3: Put a number in the Resolution

 

"Improve pricing discipline" is a direction. "Recover 2 points of margin in 12 months by consolidating scheduling across 40 stores" is a recommendation. The number is what makes it a decision the client can approve or reject.

 

In an interview, a quantified Resolution also proves you actually did the math rather than pattern-matched to a familiar answer.

 

Tip #4: Read the Situation to someone who disagrees with you

 

Find the person on the client team most likely to resist your recommendation and test the Situation on them first. If they nod, the Situation is doing its job.

 

If they push back on anything in it, that item is not a Situation fact. Move it into the Resolution where you can defend it with evidence.

 

Tip #5: Rehearse the 30-second version

 

Every storyline needs a version that fits in an elevator. Practice delivering Situation, Complication, and Resolution in 30 seconds until it sounds natural.

 

You will use this version constantly: when a partner asks what the case is about, when a client stops you in a hallway, and when an interviewer cuts your recommendation short. Having coached hundreds of candidates one-on-one, the ones who can compress their answer are the ones who actually understand it.

 

The McKinsey SCR framework rewards discipline more than cleverness, and the single habit that pays off most is writing your Resolution before anything else. Do that consistently and the Situation and Complication almost write themselves, because you finally know which two facts out of 50 actually matter.

 

Frequently Asked Questions

 

What does SCR stand for?

 

SCR stands for Situation, Complication, Resolution. The Situation states the facts your audience already accepts. The Complication explains what changed and why the Situation can no longer stand. The Resolution gives your recommendation for what to do about it.

 

Is the SCR framework the same as the Pyramid Principle?

 

No. SCR is the narrative opening that gets your audience to your recommendation. The Pyramid Principle is the logic structure that organizes everything underneath that recommendation. Both trace back to Barbara Minto, and consultants use them together rather than choosing between them.

 

What is the difference between SCR and SCQA?

 

SCQA inserts an explicit Question between the Complication and the Answer. SCR skips the question and moves straight from the Complication to the Resolution. Use SCQA in written documents where the governing question needs stating, and SCR when you are speaking or building slides.

 

Can you use the SCR framework in a case interview?

 

Yes, and the final recommendation is the best place for it. Lead with your recommendation, then give the Situation and Complication as your supporting evidence, then close with risks and next steps. SCR also works for behavioral answers and for structuring a written case deck.

 

How long should each part of the SCR framework be?

 

Keep the Situation and Complication short and give the Resolution the most space. In a deck, that often means two or three slides of Situation, one or two of Complication, and the remaining bulk on the Resolution. In a verbal recommendation, aim for roughly 15 seconds each on Situation and Complication.

 

Do you say the words situation, complication, and resolution out loud?

 

No. SCR is a planning structure, not a script. Your audience should feel the logical progression without hearing you label the parts. Announcing the labels in an interview signals that you memorized a template rather than thought through the problem.

 

Everything You Need to Land a Consulting Offer

 

Need help passing your interviews?

• Case Interview Course: Become a top 10% case interview candidate in 7 days while saving yourself 100+ hours
  
  
• Fit Interview Course: Master 98% of consulting fit interview questions in a few hours
  
  
• Interview Coaching: Accelerate your prep with 1-on-1 coaching with Taylor Warfield, former Bain interviewer and best-selling author

 

Need help landing interviews?

• Resume Review & Editing: Craft the perfect resume with unlimited revisions and 24-hour turnaround

 

Need help with everything?

• Consulting Offer Program: Go from zero to offer-ready with a complete system

 

Not sure where to start?

• Free 40-Minute Training: Triple your chances of landing consulting interviews and 8x your chances of passing them