The SCQA Framework¶
The opening of a report decides whether anyone reads the rest. Two failures are common. One buries three pages of background before the reader learns what you want. The other opens with a conclusion so abruptly that the reader's only reaction is "says who?". The SCQA framework solves both: it walks the audience to your conclusion so that by the time they hear it, they already agree the question is worth answering.
Barbara Minto introduced SCQA in The Pyramid Principle as the "introduction" to a pyramid. The Pyramid Principle governs how to organize support after the conclusion; SCQA governs how to set up the conclusion before it. Together they make a complete, persuasive piece of communication.
The four elements:
- S — Situation: a fact your audience already knows and accepts.
- C — Complication: what changed and disturbed that situation.
- Q — Question: the question the complication raises (often left implicit).
- A — Answer: your conclusion, the top of the pyramid.
Key takeaways
- Four steps: situation (shared ground) → complication (what changed) → question → answer.
- The situation must be uncontroversial: its job is to make the reader nod, not to show how much research you did.
- The complication is the engine: with no complication, nobody needs your answer.
- The question is usually left unwritten; a good S and C make the reader think of it themselves.
- The order is adjustable: lead with the answer for senior audiences, lead with the complication to create urgency.
The Four Elements¶
S — Situation¶
State a fact the audience already knows and will accept. Its purpose is to establish common ground and get the first nod.
- Be specific: "We planned to launch the new checkout on 1 June" beats "the company has long valued user experience".
- Be short: one or two sentences. The situation is the starting line, not the race.
- Avoid anything contested: if the audience disagrees with your first sentence, everything after it is an uphill battle.
C — Complication¶
State what disturbed that situation: a problem that appeared, a change in the environment, new information. The complication is the engine of the whole piece — without it, the reader has no reason to want your answer.
Common types:
| Type | Example |
|---|---|
| A problem appeared | Testing found a 3% failure rate on one card type |
| Conditions changed | A major competitor cut prices by 20% last month |
| An opportunity opened | New regulation allows us into a previously closed market |
| New insight emerged | Data shows 70% of churn happens within 7 days of signup |
Q — Question¶
The complication naturally raises a question: "So what should we do?" "Should we still launch on schedule?"
In most cases you don't write it down. If S and C are well written, the question forms in the reader's mind; stating it adds words without adding meaning. Write it explicitly only when the question could be misunderstood, so the audience knows you're answering the one they care about.
A — Answer¶
Give your conclusion directly: one sentence, a clear position, something the audience can act on.
- ✗ "We need to consider several factors carefully" (not an answer)
- ✓ "We recommend moving the launch from 1 June to 15 June" (an answer)
The answer is the top of the pyramid; everything that follows supports it.
Four Ordering Variants¶
The standard order is S-C-Q-A, but it should adapt to the audience:
| Variant | Order | When to use | Effect |
|---|---|---|---|
| Standard | S → C → Q → A | Regular reports and written documents | Smooth, logical build-up |
| Answer first | A → S → C | Senior audiences, short on time | Conclusion first, context second |
| Complication first | C → S → A | Creating urgency, driving change | Opens on the problem and grabs attention |
| Question first | Q → S → C → A | The audience is already asking | Directly addresses their concern |
How to choose: how much time the audience has, how familiar they are with the problem, and how much urgency you need. Executives usually get "answer first"; a change that will meet resistance usually needs "complication first".
Before and After¶
Before (chronological)
"Last Monday we started regression testing, on Tuesday the payment team raised some issues, on Wednesday we investigated with the provider, on Thursday we traced it to a timeout on one card type under certain conditions… so I think we may need two more weeks, and we'd also need help from the payment team."
The reader learns the point last, and "may need" signals no position.
After (SCQA)
(S) The new checkout was scheduled to launch on 1 June. (C) Regression testing last week found a 3% payment failure rate on one card type during peak hours, which at current volumes would affect about 1,200 orders a day. (A) We recommend moving the launch to 15 June, with three steps to get there.
- The provider has committed to a fix by 8 June;
- We complete regression testing 9–12 June;
- We need two engineers from the payment team for one week.
In ten seconds the reader knows what happened, what you want and what they must decide.
Templates¶
Report / email opening
| Element | What to write | Check |
|---|---|---|
| S Situation | One or two sentences the audience accepts | Will they nod? |
| C Complication | What changed, with data | Will they think "that's a real issue"? |
| Q Question | Usually unwritten | Will the reader form it themselves? |
| A Answer | One-sentence conclusion plus 2–4 supporting points | Can they decide based on this? |
Common scenarios
- Requesting a delay: S original plan → C obstacle with data → A new plan and support needed
- Proposing a project: S current state → C new opportunity or threat → A what to start
- Incident review report: S original goal → C gap in actual results → A root cause and countermeasures
- Job interview introduction: S my background → C the challenge I see in your company → A what I can contribute
Examples¶
Example 1: Requesting budget from executives (answer first)
(A) We recommend adding $110k this quarter to upgrade the support platform. (S) The current platform was bought three years ago and was sized for 50,000 monthly active users. (C) Since we passed 120,000 last quarter, average response time has risen from 2 hours to 9, satisfaction has fallen from 85% to 71%, and renewal rates are starting to slip.
Executives have little time: say what you want and what it costs first, then why.
Example 2: Driving a change that will meet resistance (complication first)
(C) In the past six months, four releases slipped because of mismatched interfaces between modules, costing 23 working days in total. (S) Today, interface design relies entirely on engineers talking to each other, with no required review step. (A) We recommend adding a cross-module technical review before development starts: about one hour each time, and it would prevent most of these delays.
Leading with the pain makes "keep things as they are" feel more uncomfortable than changing.
Example 3: Opening a product requirements document
(S) New users go through a six-step onboarding flow after signing up. (C) 62% abandon it at step 3, and users who finish onboarding retain at 3.1× the rate of those who don't. (A) We recommend cutting onboarding from six steps to two, moving the remaining settings to the moment the user first needs them.
Common Mistakes¶
- An overlong situation. Entire industry backgrounds and company histories in S leave the reader three paragraphs in with no idea of the topic. One or two sentences is enough.
- A contested situation. If the audience disagrees with S, everything after it becomes an argument.
- No real complication. "We have always worked hard on service quality" isn't a complication because nothing changed. No complication, no need for your answer.
- An answer that isn't an answer. "Further study is required" and "we must weigh many factors" avoid taking a position. If you can't state a one-sentence conclusion, you aren't ready to present.
- Forcing the question into the text. S and C usually raise it already.
- Never varying the order. Building up slowly for a CEO often means being interrupted before the point.
SCQA vs. Related Frameworks¶
| SCQA | Pyramid Principle | STAR Method | |
|---|---|---|---|
| Purpose | Set up and deliver a conclusion | Organize the support beneath it | Tell the story of one experience |
| Structure | Situation-Complication-Question-Answer | Conclusion first, grouped arguments | Situation-Task-Action-Result |
| Where used | Openings of reports, emails, proposals | The body of a report or presentation | Interviews, performance reviews, case sharing |
| Relationship | The A becomes the top of the pyramid | Follows SCQA | Different purpose; not part of the pyramid |
SCQA and STAR are easy to confuse: SCQA is for making a recommendation (here's what we should do); STAR is for recounting an experience (here's what I did). Use STAR in interviews, SCQA when proposing to a manager.
Frequently Asked Questions¶
What is the difference between SCQA and SCR?
SCR (Situation-Complication-Resolution) is a simplified version that drops the explicit question. Since the question is usually left implicit anyway, the two are effectively the same approach under different names.
How do I tell the situation from the complication?
A simple test: the situation is what the audience already knows; the complication is the new information that disturbs it. If they'd say "yes, I know", it's S. If they'd say "wait, when did that happen?", it's C.
Must I always use the S-C-Q-A order?
No. All four elements should be present, but the order adapts to the audience. Answer-first works well for executives; complication-first helps when driving change.
Does SCQA work for spoken updates?
Very well. Elevator updates, meeting contributions and weekly status reports can all be done in three sentences of S-C-A. For spoken settings, answer-first is usually safer because listeners interrupt.
Can SCQA be used for long reports?
Yes. SCQA belongs to the opening (usually under a page) and leads to the core conclusion; the body that follows is organized with the Pyramid Principle.
Extensions and Connections¶
- Pyramid Principle: SCQA is its introduction, and the Answer is the top of the pyramid.
- STAR Method: another common structure, for recounting experience rather than proposing action.
- Logic Tree: after the answer, use a logic tree to structure the supporting arguments without overlaps or gaps.
- ORID Focused Conversation: a question structure for facilitating discussion; complements SCQA's presentation structure.
- After Action Review: when reporting review findings upward, SCQA makes the best opening.
Reference: Barbara Minto introduced the SCQA structure in The Pyramid Principle: Logic in Writing and Thinking, as the way to write the introduction to a pyramid-structured document. The book is standard reading for new consultants at firms such as McKinsey.