SCQA Framework: Situation, Complication, Question, Answer

Overview

This section introduces the SCQA (Situation-Complication-Question-Answer) structured communication framework and how to apply it in IoT pre-sales communication, proposal writing, and technical presentations. After completing this section, you will be able to:

Understand the origins and core principles of the SCQA framework
Master the four SCQA variants and their applicable scenarios
Apply SCQA to IoT solution proposals, technical presentations, and customer communication
Combine JTBD, ethnography, and SCQA to build a complete “needs insight → persuasive narrative” pipeline

Prerequisites

Before starting this section, ensure:

Completed sections 01-03 on JTBD methodology and ethnography research
Experience writing technical proposals or pre-sales documents
Understanding of at least one complete IoT project workflow

Key Concepts

What is SCQA?

SCQA originates from Barbara Minto’s The Pyramid Principle and is widely used by top consulting firms like McKinsey. Its core idea is:

Any effective communication should tell a story: first build consensus (S), then create tension (C), spark curiosity (Q), and finally deliver the solution (A).

The four SCQA elements:

Element	Role	Analogy
S	Situation — Establish background context	Story opening
C	Complication — Break the balance, reveal problems	Story twist
Q	Question — Spark curiosity, define the core problem	Pre-climax
A	Answer — Provide the solution, resolve tension	Story resolution

Why Technical People Need SCQA

Common communication problems for IoT practitioners:

❌ Typical technical expression:
"Our solution uses ESP32 + MQTT + Node-RED + InfluxDB + Grafana architecture,
supports QoS 1/2, 1Hz sampling rate, 200+ concurrent device connections..."

→ Customer reaction: Can't understand, don't know how it relates to me

✅ SCQA structured expression:
[S] Your factory has 3 production lines, producing 50,000 units daily
[C] But quality inspection relies on manual sampling with a 3% miss rate,
    last month a customer returned goods costing 500K yuan
[Q] How can we reduce the miss rate below 0.1% to avoid return losses?
[A] We recommend deploying an ESP32 + industrial camera online inspection
    system for 100% coverage...

→ Customer reaction: That's exactly my problem, the solution sounds solid

Core difference: Technical expression starts from “what we have,” SCQA starts from “what you’re facing.”

SCQA Four Elements in Detail

S — Situation

Purpose: Build consensus with the audience, let them “enter the scene.”

Writing tips:

Describe facts the audience knows or easily agrees with
Use specific data, avoid vague descriptions
No problems or controversies, just neutral facts

IoT example:

✅ Good S:
"Your company currently has 3 factory sites, 12 production lines,
monthly capacity of about 2 million units. Each line has temperature/
humidity sensors, with data recorded manually in local Excel files."

❌ Bad S:
"Manufacturing is a trillion-dollar market, digital transformation
is the general trend..."
(Too vague, unrelated to the customer's specific scenario)

C — Complication

Purpose: Break the balance established by S, reveal pain points or challenges, create “tension.”

Writing tips:

Point out problems, risks, or shortcomings of the current situation
Quantify the severity of the conflict with data
Make the audience feel “change is necessary”

IoT example:

✅ Good C:
"But the manual recording approach has three problems:
1. Data lag — anomaly discovery averages 4 hours delay
2. No traceability — 3 quality incidents last year couldn't be root-caused
3. Compliance risk — safety department requires electronic records next month"

❌ Bad C:
"Traditional methods are inefficient and can't meet modern management needs"
(No specific data, can't create urgency)

Q — Question

Purpose: Distill the complication into one clear core question, guide the audience to expect an answer.

Writing tips:

The question should naturally derive from C
Summarize in one sentence when possible
The question should be what the customer truly cares about (link to JTBD)

A — Answer

Purpose: Provide a clear solution, resolve the tension created by C.

Writing tips:

The answer should directly respond to Q
First summarize in one sentence, then expand details
Emphasize “how it solves the conflict,” not “how advanced the tech is”

Four SCQA Variants

Variant	Order	Best For	Effect
Standard	S → C → Q → A	Formal proposals, pre-sales	Clear logical flow
Answer-First	A → S → C → Q	Executive briefings, elevator pitch	Conclusion first, save time
Conflict-First	C → S → Q → A	Urgent issues, immediate attention	Create urgency
Question-First	Q → S → C → A	Training, tech sharing	Spark curiosity

Variant Application Example (Same IoT Scenario)

Scenario: Reporting environmental monitoring solution to a factory manager

Standard (S → C → Q → A):

[S] Our workshop has 8 temperature monitoring points, manually recorded
    by on-duty staff every 2 hours.
[C] Last Wednesday night shift, Workshop 3 temperature rose abnormally
    but wasn't discovered until morning shift handover, resulting in
    300K yuan of raw materials being scrapped.
[Q] How can we ensure temperature anomalies are detected and handled
    immediately?
[A] We recommend an automated monitoring system: ESP32 sensors collect
    data every 30 seconds, exceeding thresholds triggers SMS and
    audible/visual alarms to on-duty staff.

Answer-First (A → S → C → Q):

[A] We recommend immediately deploying an automated temperature monitoring
    system, estimated investment 50K yuan, reducing anomaly response
    time from 2 hours to 30 seconds.
[S] Currently the workshop has 8 monitoring points, relying on manual
    recording every 2 hours.
[C] Last Wednesday's 300K raw material loss was because the night shift
    anomaly wasn't detected in time.
[Q] So the question is: how do we prevent anomalies from being missed?

SCQA Application Matrix in IoT Scenarios

Communication Scenario	Recommended Variant	Audience	Focus
Pre-sales proposal	Standard	Customer decision-makers	Complete logic, professional
Executive briefing	Answer-First	Company management	Conclusion first, save time
Issue report	Conflict-First	Project manager/customer	Create urgency
Technical training	Question-First	Technical team	Spark curiosity
On-site demo	Standard + Conflict	Customer users	Show understanding + solution

SCQA + JTBD + Ethnography Synergy

Combining JTBD (needs framework) + Ethnography (research method) + SCQA (solution expression) creates a complete pre-sales methodology:

Phase 1: Mine needs with JTBD + Ethnography (Sections 01-03)
    ↓
    Output: Customer Job Statements + User behavior insights + Priority ranking
    ↓
Phase 2: Build narrative with SCQA (This section)
    ↓
    S ← Customer status (from ethnography observations + JTBD interviews)
    C ← Pain points/conflicts (from ethnography findings + JTBD "pain")
    Q ← Core question (converted from Job Statements)
    A ← Solution (organized from functional requirements mapping)
    ↓
Phase 3: Prove technical feasibility with C4 Model (Sections 07-12)

JTBD to SCQA Conversion Template

JTBD Interview Data                SCQA Proposal Elements
────────────────────────────      ────────────────────────
Customer business background    → S (Situation)
"Current approach" + "Pain"     → C (Complication)
Job Statement's "so I can"      → Q (Question)
Functional needs + Tech plan    → A (Answer)
Emotional/Social jobs           → Value proposition in A

Practical conversion example:

JTBD Interview Record:
  Customer: Food processing factory manager
  Background: Annual output 80M yuan, supplies 3 large supermarket chains
  Current: QC staff inspects every 4 hours, manual recording
  Pain: Last month temperature exceeded limits, batch scrapped, loss 200K
  Job Statement:
    When workshop temp exceeds limits, I want immediate alerts,
    so I can initiate emergency measures within 5 minutes

Converted to SCQA Proposal:

[S] Your factory's annual output is 80M yuan, supplying 3 major
    supermarket chains with strict quality control standards.
    Currently, QC staff inspects every 4 hours with manual recording.

[C] Last month, undetected nighttime temperature excursion caused
    200K yuan of product waste. The supermarket issued a warning:
    another incident will revoke supplier qualification.

[Q] How to achieve 24/7 real-time temperature monitoring, ensuring
    anomalies are detected and handled within 5 minutes?

[A] We recommend a smart environmental monitoring system:
    1. Deploy 12 ESP32 + DHT22 sensor nodes across key areas
    2. Upload data via MQTT every 30 seconds
    3. Three-level alerts: Warning (±2°C) → Alarm (±5°C) → Critical (±8°C)
    4. Triple-channel notification: SMS + audible/visual + WeChat Work
    5. Auto-store data for 12 months, one-click compliance report export
    Investment: ~80K yuan, 2-week deployment, annual risk cost savings: 2M+

Pre-Sales Guided Discovery: Let the Customer Tell SC, Co-Define Q

The examples above show how to write proposals with SCQA. In actual pre-sales conversations, SCQA can also be used in reverse as a questioning framework — guided discovery:

Pre-Sales Engineer (SE) Guiding Strategy:
    ↓
[Ask S]  Guide the customer to describe their current situation
    ↓
[Ask C]  Guide the customer to articulate pain points and consequences
    ↓
[Co-Define Q]  Define the core problem together (confirm consensus)
    ↓
[Give A]  Engineer presents the solution

Advantages of this approach:

Customer is more engaged: They participate in defining the problem rather than passively listening to a pitch
Stronger consensus: Q is confirmed by both sides — the customer won’t say “that’s not what I needed”
Higher trust: The engineer demonstrates “I’m helping you clarify the problem,” not “I’m selling you something”

Case Study: Chemical Plant Equipment Monitoring

Scenario: Manager Zhang from a fine chemical manufacturing company expressed interest in your IoT monitoring solution at a trade show. Pre-sales Engineer Wang schedules the first meeting.

[Phase 1: Guide S — Let the Customer Describe Their Situation]

❌ Wrong opening: “Our solution uses ESP32 + MQTT architecture supporting 200 concurrent devices…” ➡️ This is the classic “we give the answer first” approach — the customer hasn’t even said what their problem is

✅ Correct approach: Use open-ended questions to let the customer describe their situation

Wang: “Manager Zhang, thank you for your interest in our solution. Could you tell me about your current equipment inspection process? For example, what critical equipment do you have in your plant, and how do you manage it?”

Zhang: “We have 3 workshops with 38 reactors and supporting equipment. Currently, operators inspect every 2 hours, manually recording temperature, pressure, and vibration readings.”

Wang: “How is this data currently stored and accessed?”

Zhang: “All recorded on paper forms, then entered into Excel daily. Looking up historical data means digging through Excel files.”

✅ S information collected:

3 workshops, 38 critical equipment units

Manual inspection, every 2 hours

Paper + Excel records

Historical data hard to trace

[Phase 2: Guide C — Let the Customer Voice Their Pain]

✅ Correct approach: Ask “so what problems have you encountered?” — let the customer admit the complication themselves

Wang: “Have you encountered any issues with this inspection model in practice?”

Zhang: “Quite a few. Last month, bearing temperature on a reactor in Workshop 2 ran high for several hours without anyone noticing. It eventually caused seal failure — we lost 2 days of production.”

Wang: “What was the estimated loss from that incident?”

Zhang: “Direct loss over 300K yuan. The indirect costs from delayed order fulfillment are harder to calculate.”

Wang: “Has this happened more than once?”

Zhang: “Three times this year already. Management keeps pushing for improvement, but we can’t increase inspection frequency — each person already monitors 12 machines on a 2-hour cycle. It’s exhausting.”

✅ C information collected:

3 equipment anomalies went undetected this year

Single incident: 300K+ yuan direct loss

Staff already at full capacity — “increase manual inspection” is not viable

The customer himself said “quite a few problems” — more convincing than us stating it

[Phase 3: Co-Define Q — Define the Core Problem Together]

✅ Correct approach: Confirm consensus with a question — don’t make the customer feel “you’re deciding for me”

Wang: “Let me see if I understand your core need correctly: You want to monitor all 38 critical equipment units 24/7 without adding inspection staff, detect anomalies immediately, and avoid another 2-day production shutdown like last month. Is that right?”

Zhang: “Exactly. Ideally with auto-recorded data that management can check anytime.”

Wang: “And when an anomaly occurs, how quickly would you want the duty staff to be notified?”

Zhang: “At least within 5 minutes — otherwise what’s the point?”

Wang: “Understood. Let me confirm the problem we need to solve: Establish an automated monitoring system across 3 workshops and 38 equipment units, achieving 24/7 data collection with real-time alerts delivered within 5 minutes, and complete historical data retention for traceability and analysis. Does that accurately describe the challenge?”

Zhang: “Yes, that’s it.”

✅ Key techniques for co-defining Q:

Use “let me see if I understand…” to paraphrase and confirm

Let the customer add details (“how quickly should you be notified?”)

State the full Q and get verbal confirmation

Once the customer says “yes,” the A becomes a jointly derived conclusion

[Phase 4: Give A — Present the Solution Based on Consensus]

✅ Correct approach: A is a natural extension of Q, not a “miracle cure”

Wang: “Based on the problem we’ve confirmed, here’s what I’d recommend: Deploy wireless sensor nodes on all 38 equipment units, aggregate the data through an industrial wireless network to a central monitoring server, refreshing every 10 seconds. For each parameter — temperature, pressure, vibration — set up two alert thresholds: warning level notifies the shift leader, alarm level notifies both you and the workshop manager simultaneously. All data is stored automatically for historical curve viewing at any time. This effectively gives you 24/7 virtual monitoring on every machine, without adding headcount.”

Zhang: “What kind of budget are we looking at?”

Wang: “It depends on sensor selection, roughly in the range of X to Y. If it’s convenient, we could arrange a site survey to give you an accurate proposal and quote.”

Zhang: “OK, come take a look first.”

✅ A design principles:

Every point in A responds to a corresponding element (S→equipment count matches, C→timely detection and traceability addressed)

Technical specs (10-second refresh, 2-level alerts) correspond to co-defined Q (24/7 monitoring, 5-minute notification)

Present “solution direction” first, not “detailed configuration” — let the customer confirm direction

Naturally lead to next step: site survey

SCQA Structure Retrospective

Customer's own S:
  "3 workshops, 38 reactors, manual inspection every 2 hours, paper + Excel"

Customer's own C:
  "3 incidents this year, last month cost us 2 days and 300K+ yuan"

Jointly defined Q:
  "24/7 automated monitoring across 3 workshops, 38 equipment units,
   anomalies alerted within 5 minutes, complete traceable data"

Engineer's A:
  "Wireless sensor nodes, 10-second sampling, two-level alerting,
   auto-stored traceable data"

Key Differences: Guided Discovery vs. Traditional Pitching:

Dimension	Traditional (A first)	Guided Discovery (SCQA Questioning)
Problem definition	Engineer assumes the problem	Customer confirms the problem
Customer feeling	”You’re selling me your stuff"	"You’re helping me solve my problem”
Solution fit	Often misaligned, needs revisions	High probability of first-time fit
Trust cost	High (must build trust before going deep)	Low (trust built naturally through dialogue)
Sales cycle	Long (back-and-forth revisions)	Short (direction clarified in one meeting)

Guided Discovery Questioning Template

Phase 1: Guide S
  - "Could you tell me about your current [relevant process]?"
  - "How is [relevant workflow] currently managed?"
  - "How many [assets/people/devices] do you have?"
  - "How is data currently recorded and managed?"
  Goal: Let the customer describe the full situation — don't interrupt, take notes

Phase 2: Guide C
  - "Have you encountered any issues with this model in practice?"
  - "Have you experienced any losses from [related problem] in the past year?"
  - "How frequently does this problem occur?"
  - "Besides direct costs, are there other impacts? (Customer complaints, compliance risks, etc.)"
  Goal: Guide the customer to articulate pain points themselves

Phase 3: Co-Define Q
  - "Let me check if I understand your core need — [paraphrase S+C into Q]?"
  - "Besides this, are there other aspects you're particularly concerned about?"
  - "What standards would you expect? (Frequency, response time, coverage)"
  - "So the problem we need to solve is: [full Q]. Is that correct?"
  Goal: Get the customer to verbally confirm "Yes, that's it"

Phase 4: Give A
  - After confirming Q, naturally transition: "Based on what we've discussed, I'd recommend…"
  - Every point in A should respond to a corresponding S or C
  - Start with direction, then details
  - Use data to demonstrate effectiveness
  - Guide to next step (site survey, technical discussion, POC)

Common Mistakes and Corrections

Mistake	Symptom	Fix
Skip S	Jump straight to “what’s your problem?” — customer doesn’t know where to start	Start with: “How are you currently doing X?”
Speak for the customer	”Your problem is outdated data, right?” — customer may disagree	”What do you find most challenging?” — let them say it
Jump to A without confirming Q	Start presenting before customer confirms the problem — they tune out	”Let me confirm I understand…” — confirm before presenting
Interrogation style	Rapid-fire questions feel like an interrogation — customer gets defensive	Pause every 2-3 questions: “Please go ahead”
Technical premature	Start discussing technical solutions during S phase — wrong Q	Use business language for first 3 phases, switch to technical language for A

Exercise 1: Rewrite Technical Expression

Rewrite the following into SCQA structure:

Original:
"Our IoT platform supports MQTT, CoAP, HTTP protocols,
can connect 10,000 devices simultaneously,
data processing latency under 100ms."

Reference rewrite:

[S] Your group has 28 production bases nationwide, each with 200-500
    devices that need connectivity.
[C] Current systems only support a single protocol, each base operates
    independently, HQ cannot see real-time device data from all bases,
    decisions rely on monthly reports — severely delayed.
[Q] How to unify 28 bases, nearly 10,000 devices into one platform
    for real-time monitoring and centralized management?
[A] Our IoT platform supports MQTT/CoAP/HTTP multi-protocol access,
    10,000+ concurrent device connections, <100ms processing latency,
    all base data converges to HQ dashboards, upgrading from
    "monthly-report decisions" to "real-time decisions."

Verification

Verify mastery of the SCQA framework:

Framework Understanding
- Can accurately explain the role of S, C, Q, A
- Can distinguish four SCQA variants and their scenarios
Writing Ability
- Can rewrite technical descriptions into SCQA structure
- Can build a complete SCQA narrative for an IoT scenario
- Can extract SCQA elements from JTBD interview data
Practical Application
- Can consciously use SCQA in pre-sales communication
- Can select the appropriate variant based on audience and scenario

Best Practices

✅ Recommended: Before writing, draft one-sentence summaries of all four SCQA elements to verify logic
✅ Recommended: Use customer’s real data and scenarios in S, not generic industry descriptions
✅ Recommended: Quantify conflict impact in C (money, time, frequency)
✅ Recommended: In A, give the summary first, then expand (Pyramid Principle)
✅ Recommended: Weave emotional/social jobs into the value proposition in A
❌ Avoid: S being too vague (“Digital transformation is the trend”)
❌ Avoid: C only describing problems without quantifying impact
❌ Avoid: A only discussing architecture without responding to C’s conflicts
❌ Avoid: Using the same variant for all scenarios

Summary

Key takeaways from this section:

SCQA is the core structured communication framework
- S (Situation) → C (Complication) → Q (Question) → A (Answer)
- Start from “what you’re facing,” not “what we have”
Four variants for different scenarios
- Standard: Formal proposals
- Answer-First: Executive briefings
- Conflict-First: Urgent issues
- Question-First: Training/sharing
SCQA + JTBD + Ethnography form a complete pipeline
- JTBD + Ethnography handles “mining needs,” SCQA handles “expressing solutions”
- Ethnography observations and JTBD interview data directly convert to SCQA elements
Good SCQA proposals have three characteristics
- S is specific (real customer scenarios and data)
- C is urgent (quantified impact and consequences)
- A is responsive (directly addresses conflicts, summary first)

References

Minto, B. (2009). The Pyramid Principle: Logic in Writing, Thinking, and Problem Solving
McKinsey SCQA Framework Explained
Barbara Minto’s Pyramid Principle Summary
SCQA Guided Discovery Case Study for IoT Pre-Sales

Building a commercial IoT product?

We provide ESP32 ODM design-to-manufacturing services. From prototype to production — the team behind this tutorial can build it with you.

Talk to us →