SCQA
For writing to someone who will decide in ninety seconds.
What is SCQA?
SCQA builds an argument in four moves: the Situation everyone agrees on, the Complication that disturbs it, the Question that follows, and the Answer. It is the structure behind most consulting documents, and it exists for readers who are senior, busy, and will decide whether to keep reading in the first two sentences.
SCQA works because it earns the question before answering it. Open with a recommendation and a sceptical reader has nothing to hang it on. Open with a Situation they already accept, add the Complication they have been half-aware of, and the Question forms in their head before you ask it — so the Answer lands as a resolution rather than a request. That is the whole mechanism: you are not persuading them, you are letting them arrive.
Where SCQA Came From
Barbara Minto, and the Pyramid Principle
SCQA is part of the Minto Pyramid Principle, developed by Barbara Minto at McKinsey and published as a book in 1985. Minto joined McKinsey in 1963 as its first female MBA hire and went on to run the firm’s training — the pyramid was her answer to the problem of consultants who could analyse well and write badly.
Older sources than consulting
Minto drew on Aristotle, Jean Piaget and Mortimer Adler rather than on business writing, and it shows. SCQA is closer to classical rhetoric than to a template: establish common ground, introduce tension, let the audience form the question, resolve it. That lineage is why it does not feel like a formula when it is used well.
Its sibling is <a href="/frameworks/mece">MECE</a>
Minto invented both, and they do different halves of the job. MECE governs how you group your analysis; SCQA governs how you order it for a reader. A deck built with one and not the other is either well-structured and unpersuasive, or compelling and full of holes.
The 4 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
Situation must be uncontroversial — its job is agreement, not information. If the reader can dispute your first sentence you have lost the mechanism. It should also be relevant: a Situation that could open any document ("the market is changing rapidly") does no work.
The engine of the whole structure. A Complication is not a restatement of the problem — it is the specific tension that makes the Situation untenable. The best ones use facts the reader already half-knows, so that the discomfort feels like recognition rather than accusation.
The slot people delete, and deleting it is what turns SCQA into a report. Written well, the Question is one line and already in the reader’s head — it should feel obvious rather than clever. If your Question does not follow inevitably from the Complication, the Complication is wrong.
Answer is a position, not a summary of options. It should be stated flatly and early — the pyramid’s core claim is that a reader who knows your conclusion reads the evidence better. Naming the axis of the argument helps: not just "hire two", but "the argument is the cost of the delay, not the cost of the team".
One Task, Before and After
The task: Make the case for hiring two platform engineers. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.
Write a business case for hiring more engineers.
Seven words. You will get a generic case with invented headcount costs and invented productivity percentages — numbers a CFO will ask about and you cannot defend.
Situation: Our platform team is four engineers supporting nineteen product teams, a ratio that has held since 2024 while the product teams doubled. Complication: Deploy pipeline changes now queue for three weeks. Two product launches slipped last quarter waiting on platform work, and the team lost one engineer to burnout in November. Question: Do we hire two platform engineers now, or keep absorbing the delay? Answer: Hire two. The argument is the cost of the delay, not the cost of the team. Write a one-page business case of 400-500 words for the executive team, who see the delay as an engineering complaint rather than a commercial cost and have already declined this once. It must lead with the recommendation, then the evidence. Use four short headed sections following SCQA in order, and a three-row table comparing hire now, hire in six months, and do nothing across cost, launch risk and attrition risk. Weigh the do-nothing option honestly before concluding. The tone should be commercial rather than technical. For example, the opening line should read like this: ``` We should hire two platform engineers this quarter. Waiting cost us two launches last quarter and one engineer. ``` Do not invent financial figures beyond those given, and do not use the word headcount.
Ninety-two, and the highest-scoring worked example on any of these pages. The line earning the most is not part of SCQA at all: "have already declined this once" tells the model it is writing to a sceptic, which changes every paragraph.
What a 92 is made of
Only one check falls short, and three specific instructions are doing disproportionate work. Both are worth copying:
SCQA has no persona slot. Adding "you are a management consultant" produces consulting register — the deck-speak SCQA is supposed to prevent.
"…who have already declined this once" is a single clause and reframes the whole document from proposal to rebuttal.
"Weigh the do-nothing option honestly before concluding" stops the model producing a strawman, which is what kills business cases in the room rather than on the page.
The general lesson: SCQA gets you the shape, and the shape is not the argument. Four labelled sections with no audience, no comparison table and no instruction to steelman the alternative produce a well-organised document that a sceptical executive declines for the second time.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
Situation: [A fact the reader already accepts, specific to this decision] Complication: [What changed, and what it has cost. The tension they half-know already] Question: [The one-line question now in their head] Answer: [Your recommendation, and the axis the argument turns on] Write [format] of [N] words for [who decides, and what they already believe or have declined]. Lead with the recommendation, then the evidence. Weigh the do-nothing option honestly before concluding. Do not invent figures beyond those given.
When SCQA Fits — and When It Does Not
- Business cases, board updates and executive summaries — the use it was built for.
- Any document read by someone who will decide quickly and has declined before.
- Bad news: SCQA is the most humane structure for a delay or a missed target.
- Consulting-style recommendations, and the opening of a deck or a strategy memo.
- Long emails to senior people, where the Answer belongs in the first two lines.
- Instructional and reference writing. Use CLEAR — SCQA argues, it does not explain.
- Consumer persuasion. Use AIDA or PAS; SCQA assumes a reader obliged to consider your case.
- Recounting what you personally did. Use STAR — SCQA ends on a recommendation, not an outcome.
- Situations with no genuine Complication. Forcing one manufactures a crisis, and readers notice.
10 Ready-Made SCQA Prompts
Every prompt below was produced by the Frompting generator with SCQA selected — not written by hand for this page. Each is scored by our prompt checker; the median is 94/100. Click one to open it, then copy.
Business case: hiring two engineers 74
You are a senior business analyst tasked with drafting a concise, executive‑level business case to recommend hiring two additional engineers. The recommendation will be presented to [AUDIENCE: e.g., CEO, CTO, or Board] and must persuade decision‑makers by clearly outlining the current context, the emerging challenge, the key question to resolve, and a compelling answer with supporting rationale. Produce a business case of approximately 350 words, formatted as a single flowing narrative (no headings or bullet lists). Ensure the writing is clear, data‑driven, and uses a professional tone appropriate for senior leadership. The case should: 1. Begin by describing the present situation, including the existing engineering team size ([CURRENT_TEAM_SIZE: number of engineers]) and the primary projects or product areas they support. 2. Explain the complication that threatens performance, such as capacity constraints, missed deadlines, or market opportunities, referencing any relevant metrics ([KEY_METRIC: e.g., backlog size, time‑to‑market, revenue impact]). 3. Pose the central question that the decision‑maker needs to answer regarding staffing. 4. Provide a concise answer recommending the addition of two engineers, outlining expected benefits (e.g., reduced delivery time, increased feature velocity, risk mitigation) and an estimated cost impact ([ANNUAL_COST_PER_ENGINEER: salary + overhead]). Quality criteria: - The narrative must be logically coherent, with each part naturally leading to the next. - All quantitative statements should be realistic estimates; label any figure that is an assumption as “approximate.” - The tone should be persuasive yet balanced, avoiding hyperbole. If any of the required details are unknown, state your assumptions explicitly and ask up to three clarifying questions before finalizing the business case.
Executive summary: a pricing change 95
You are a senior business consultant tasked with drafting a concise executive summary that recommends a pricing change. The summary should be written for senior leadership and must be clear, persuasive, and structured to flow logically from the current context through the problem, the key question, and the recommended solution. The document should be approximately 410-540 words, presented as a single paragraph or short blocks of text without headings. Deliver a summary that: - Clearly describes the present situation of [COMPANY NAME] and its [PRODUCT/SERVICE]. - Highlights the specific complication or challenge prompting the need for a pricing adjustment. - Poses the central question that leadership must answer regarding the pricing strategy. - Provides a well-justified answer recommending the pricing change, including the expected impact on revenue, market positioning, and customer perception. Quality criteria: 1. Logical flow that naturally leads the reader from context to recommendation. 2. Use of concrete, data-driven language (e.g., percentages, revenue impact) where available, and flag any approximations. 3. Tone that is professional, concise, and aligned with McKinsey-style executive communication. If any of the following details are unknown, insert a placeholder in the format [PLACEHOLDER: brief hint]: - [CURRENT PRICING: current price or pricing model] - [PROPOSED CHANGE: new price or pricing model] - [DRIVING FACTOR: reason for change, e.g., cost increase, competitive pressure] - [TARGET MARKET: primary customer segment] - [EXPECTED OUTCOME: desired result, e.g., revenue growth, margin improvement] State any assumptions you make and ask up to three clarifying questions before finalizing the summary. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Board update: missing a quarterly target 75
You are a senior corporate communications specialist tasked with drafting a concise board update that explains why the company missed its quarterly target and outlines the path forward. The update should be written for the board of directors of **[COMPANY NAME]** and must be clear, factual, and actionable. Structure the memo in a logical narrative flow: begin with a brief overview of the current performance context, then describe the specific shortfall and its underlying causes, pose the key question the board needs to consider, and finish with a concrete response that includes recommended actions and metrics for tracking progress. The memo should be approximately 300 words, written in a professional yet approachable tone, and formatted as a single block of text with short paragraphs (no headings or bullet lists). Ensure the following quality criteria are met: 1. All statements are supported by the data you have or clearly identified as assumptions. 2. The language is precise, avoids jargon, and defines any technical terms at first use. 3. The recommended actions are specific, time‑bound, and assignable to responsible parties. If any essential details are missing—such as the exact target amount, actual results, primary reasons for the shortfall, or the timeline for corrective actions—state your assumptions explicitly and ask up to three clarifying questions before finalizing the memo.
Proposal: consolidating software vendors 95
You are a senior management consultant specializing in vendor strategy. Your client is a [COMPANY TYPE: e.g., mid‑size manufacturing firm] that wants a formal proposal to consolidate its software vendors. The proposal must persuade senior leadership to adopt a streamlined vendor portfolio, highlighting cost savings, risk reduction, and operational efficiency. Produce a concise, executive‑level document of approximately 350–400 words, formatted as a single flowing narrative without headings. The content should: - Clearly describe the current vendor landscape and why it is suboptimal. - Explain the emerging challenges (e.g., overlapping contracts, integration complexity, hidden costs). - Pose the central strategic question the leadership must answer. - Deliver a compelling answer that outlines a step‑by‑step consolidation plan, expected financial impact (use ranges if exact figures are unknown), governance model, and timeline. Quality criteria: 1. Persuasive tone with data‑driven arguments (use approximate figures where precise data is unavailable). 2. Logical flow that naturally leads the reader from problem to solution. 3. Actionable recommendations with measurable outcomes. Boundary: Do not include detailed technical specifications of individual software products; focus on strategic and financial aspects only. If any critical details are missing, state your assumptions explicitly and ask up to three clarifying questions before drafting the proposal. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Memo: sunsetting an old product 95
You are a senior business strategist tasked with drafting a concise executive memo that recommends discontinuing an outdated product. The memo will be addressed to [RECIPIENT: senior leadership or specific decision-maker] and should persuade them that retiring the product is the optimal strategic move. Your memo must: - Open by describing the current market and internal context of the product, including its role and performance metrics (e.g., sales, profit margin, customer usage). - Highlight the emerging challenges or changes that make the product’s continued existence problematic (e.g., declining demand, high maintenance cost, competitive pressure). - Pose the key decision question that senior leadership needs to resolve. - Provide a clear, actionable recommendation to sunset the product, outlining the primary steps (e.g., communication plan, customer migration, resource reallocation) and the expected benefits (e.g., cost savings, focus on growth areas). Write the memo in a professional tone, using short paragraphs and bullet points where appropriate. Limit the total length to **300 words**. Quality criteria: 1. Argument is logically coherent and follows the described structure. 2. Recommendation is specific, actionable, and supported by the presented data. 3. Language is concise, free of jargon, and suitable for an executive audience. Boundary: Do not include detailed implementation schedules, financial forecasts, or technical specifications beyond what is needed to justify the recommendation. If any essential details (product name, performance figures, stakeholder concerns) are unknown, state your assumptions explicitly and ask up to three clarifying questions before finalizing the memo. Note on length: this supersedes any word count given above. Covering the 3 sections needs roughly 445–585 words in total. Use that range rather than compressing any section to fit a smaller one. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Project status update for stakeholders 81
You are a senior‑level business communication specialist. Create a concise project status update intended for senior stakeholders. First, set the context by briefly describing the current state of the project, including its purpose and recent progress. Next, highlight any emerging issues or risks that could affect the project’s timeline, budget, or outcomes. Then, pose the central question that senior stakeholders need answered to make informed decisions. Finally, provide a clear answer that includes recommended actions, next steps, and any decisions required from the audience. The update should be written in a professional tone, be no more than 300 words, and use short paragraphs or bullet points where appropriate for readability. Ensure the language is precise, avoids jargon unless defined, and focuses on facts and actionable insights. Include at least two of the following quality criteria: - Accuracy of key metrics (e.g., budget variance, schedule variance) - Clarity of recommended actions and decision points Leave out any detailed technical specifications or background information that is not essential for senior decision‑making. If any critical details are missing, state your assumptions explicitly and ask up to three clarifying questions (e.g., project name, reporting period, specific metrics to highlight) before finalizing the update.
Recommendation: build or buy 95
You are a senior strategy consultant advising an executive audience on a technology decision. Your task is to produce a concise recommendation memo that evaluates whether the organization should build a new feature in‑house or purchase an existing solution. The memo should be organized as a clear narrative: start with a brief description of the current context and need, then explain the emerging challenge that makes the decision critical, pose the central decision question, and finally present a well‑argued recommendation with supporting points. Write the memo for a senior decision‑maker (e.g., CTO, VP of Product) and keep the total length between 250 and 300 words. **Quality criteria** 1. Use data‑driven reasoning and cite at least two relevant industry benchmarks or case examples (you may approximate if exact figures are unavailable). 2. Present at least three key criteria (e.g., cost, time‑to‑market, strategic fit) and compare build vs. buy for each. 3. Conclude with a clear, actionable recommendation and a brief implementation next step. **Boundary** – Do not include detailed technical specifications, vendor contract language, or pricing tables. If any essential information is missing, state your assumptions explicitly and ask up to three clarifying questions (e.g., target market size, existing development capacity, budget constraints) before finalizing the recommendation. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Explaining why a project is delayed 92
You are a concise business analyst tasked with drafting a brief executive summary that explains why a project is delayed. Write a clear, structured narrative that first sets the current context, then outlines the emerging issue, poses the key question the audience needs answered, and finally provides the explanation and next steps. The summary should be addressed to [AUDIENCE: e.g., senior leadership, client sponsor] and limited to 200–250 words. **Quality criteria** - Logical flow that naturally leads the reader from context to explanation. - Use specific, factual language; avoid vague statements. - Highlight any immediate actions or decisions required. **Boundary** Do not include unrelated project details or speculative future forecasts beyond the immediate delay explanation. If any essential information (project name, primary cause of delay, critical deadline, or required decision) is missing, state your assumptions clearly and ask up to three targeted clarifying questions before completing the summary.
The case for reducing technical debt 94
You are a senior business strategist tasked with crafting a compelling investment case for reducing technical debt. Your audience is [AUDIENCE: specify the decision‑makers, e.g., CEO, CTO, board]. The organization operates in [INDUSTRY: specify sector] and has a current technical debt estimate of [DEBT_LEVEL: approximate amount or percentage of codebase]. Your goal is to persuade the audience that allocating resources to technical debt reduction will deliver measurable business value. Write a concise executive brief of 300–350 words, organized as a logical narrative that first sets the context, then highlights the emerging challenge, poses the critical question, and finally presents a clear, actionable recommendation. The brief should: - Use data‑driven arguments and concrete examples relevant to the specified industry. - Quantify expected benefits (e.g., faster release cycles, reduced outage risk, cost savings) and outline a high‑level roadmap. - Maintain a professional, McKinsey‑style tone with crisp sentences and no filler language. If any of the placeholders above are unknown, state your assumptions explicitly and ask up to three clarifying questions before finalizing the brief. Do not include any disclaimer, citation, or unrelated content.
Strategy memo: entering a new market 89
You are a senior strategy consultant drafting a concise executive memo for a company planning to enter a new market. Your memo should be organized as a clear narrative that first sets the current context, then highlights the emerging challenge, poses the central strategic question, and finally delivers a focused recommendation with actionable steps. Write the memo for **[AUDIENCE: senior leadership team or board]** and tailor it to the **[COMPANY: name of the organization]** launching **[PRODUCT/SERVICE: description of what is being offered]** into **[TARGET MARKET: geographic region or industry segment]**. The memo must be between 410-540 words, use professional business tone, and include: - A brief opening that outlines the present situation. - A concise paragraph describing the complication that creates urgency. - A clear statement of the key strategic question to be answered. - A well-structured answer offering 3-4 concrete recommendations, each with a short implementation step. Quality criteria: 1. Logical flow that naturally leads the reader from context to recommendation. 2. Recommendations are specific, feasible, and tied to measurable outcomes. 3. Language is precise, avoids jargon unless defined, and maintains executive-level brevity. Exclude any discussion of alternative markets, detailed financial models, or unrelated product lines. If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before completing the memo. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Scores range from 74 to 95. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.
SCQA vs the Alternatives
The sibling, same author. MECE structures the analysis; SCQA orders it for a reader. Use both — they were designed to work together.
Frequently confused because both start with Situation. STAR recounts what you did and ends on an outcome; SCQA makes a case and ends on a recommendation.
Faster and blunter, and it leads with the conclusion outright. Better for a verbal answer or a short message; SCQA earns the question first, which is worth the extra length in writing.
More explicit about options and execution. Use SCOPE when the decision is genuinely open; SCQA when you have a recommendation and need it accepted.
A general writing framework rather than an argument structure. Combine them: SCQA in the body, CO-STAR’s Audience and Response thinking around it.
Five Ways People Get SCQA Wrong
The mechanism depends on agreement in sentence one. If they can argue with your opening fact, everything after it is being read defensively.
The commonest edit and the most damaging. Without it the Answer is an assertion; with it, the Answer is a resolution to something the reader was already wondering.
Complication should introduce tension the Situation did not contain. "This is causing problems" adds nothing — name what changed and what it cost.
A list of options is not an Answer. If you genuinely have no recommendation, you are writing an options paper, and SCQA is the wrong structure for it.
Executives have usually already thought of the do-nothing option. Handling it honestly is what makes the recommendation credible; dismissing it in a clause is what makes the whole document look like advocacy.
SCQA Questions
What does SCQA stand for?
Situation, Complication, Question, Answer. Establish common ground, introduce the tension, let the question form, then resolve it.
Where does SCQA come from?
Barbara Minto’s Pyramid Principle, developed at McKinsey and published in 1985. Minto drew on Aristotle, Piaget and Mortimer Adler rather than on business writing, which is why it reads as rhetoric rather than as a template.
Should the Answer really come first?
In the document, yes — lead with the recommendation, then use SCQA to structure the supporting argument. That is the pyramid: conclusion at the top, evidence beneath. SCQA is how the section under the headline is built.
Is SCQA the same as STAR?
No, though both open with a Situation. STAR recounts a past contribution and ends on a Result. SCQA builds a case and ends on a recommendation about the future.
How long should each section be?
Situation and Complication together should be about a third. The Question is one line. Everything else is the Answer and its evidence.
What if there is no real Complication?
Then you probably do not need the document. Manufacturing tension to justify a recommendation is the failure mode senior readers detect fastest.
Generate a SCQA Prompt Instantly
Skip the manual template — Frompting applies SCQA to your topic in one click.
Try it FreeFramework Details
| Name | SCQA |
| Stands for | Situation-Complication-Question-Answer |
| Domain | Strategy & Planning |
| Steps | 4 |
| Access | Pro |