# SCQA, Explained

> The SCQA framework (Situation, Complication, Question, Answer) explained: where it came from, a worked example, when to use it, and a version you can play.

Source: https://www.wavetable.net/frameworks/scqa

[Frameworks](https://www.wavetable.net/frameworks)

CommunicationAlso called Situation, Complication, Question, Answer

# SCQA

A four-part opening for any memo, deck or email: what they already accept, what changed, the question that raises, and your answer.

## In one look

1.  1Start from what they'd agree with.
2.  2Name what changed.
3.  3Answer the question that raises.

It's the other half of Barbara Minto's system at McKinsey: the Pyramid Principle orders the argument, and SCQA opens it. She took the shape from storytelling, where a settled situation and a complication plant the question readers follow.

The problem it solves

## You've rewritten the opening four times.

Version one starts with background nobody needs. Version two jumps to the ask before anyone's ready. Version three tries both. An opening has one job, getting the reader from "why am I reading this?" to "go on," and most of us make it up every time.

## Try it yourself

No sign-up, a few minutes. Four lines of an opening, jumbled. You put them in order.

## The same email, opened two ways

An update on a vendor review, to two people who have to decide.

-   The usual openingQuick update on the vendor review.becomes We committed to choosing a new vendor by the end of the quarter.
-   The usual openingWe've been running the process since March.becomes Our preferred option raised its prices 20% last week. Do we pay, or reopen the process?
-   The usual openingWe've spoken to six providers across two rounds...becomes We recommend paying it. Here's why.

## Good times to run it

-   The first slide of a recommendation deck
-   Memos for people with no context
-   Kickoff emails: why this, why now
-   The first two minutes of a client presentation

## When to skip it

-   Urgent bad news. "The server's down" shouldn't wait for a Situation.
-   An audience with no shared situation to start from.
-   The fifth update in a thread, when everyone already has the context.

Teams we've run sessions with:

-   ![Publicis Groupe](https://www.wavetable.net/logos/publicis-groupe.svg)
-   ![SoundCloud](https://www.wavetable.net/logos/soundcloud.svg)
-   ![WeTransfer](https://www.wavetable.net/logos/wetransfer.svg)
-   ![The New York Times](https://www.wavetable.net/logos/nyt.svg)
-   ![Columbia Business School](https://www.wavetable.net/logos/columbia.svg)
-   ![EY](https://www.wavetable.net/logos/ey.svg)
-   ![Havas](https://www.wavetable.net/logos/havas.svg)
-   ![NYC](https://www.wavetable.net/logos/nyc.svg)
-   ![MCI Group](https://www.wavetable.net/logos/mci-group.svg)
-   
-   
-   
-   
-   
-   
-   
-   
-   

## Run it with your team

That was someone else's email. In front of clients who've stopped listening by the second sentence, it's harder. We run it as a live session on openings like yours, in small groups with a host.

[Storytelling for leaders](https://www.wavetable.net/for/storytelling-for-leaders)[Consulting firms](https://www.wavetable.net/for/consulting-firms)

## More frameworks

-   [Communication**Pyramid Principle**Put your answer first, then group the reasons that support it underneath.](https://www.wavetable.net/frameworks/pyramid-principle)
-   [Structuring thinking**MECE**A test for any list: no item overlaps another, and nothing important is missing.](https://www.wavetable.net/frameworks/mece)
-   [Decision-making**Pre-Mortem**Before the work starts, the team imagines the project has already failed and explains why.](https://www.wavetable.net/frameworks/pre-mortem)
