Structuring Problem-Focused Presentations with SCQA

Hello. In the previous lesson, you built a message map: one governing recommendation supported by three decision-relevant reasons. This module now adds a second structure that is especially useful when executives need to understand why a problem requires a decision, not merely what you recommend.

In this lesson, you will structure a problem-focused executive presentation using Situation, Complication, Resolution, and Action. The first three moves create a coherent narrative; the final move makes the meeting useful by stating exactly what you need leaders to decide, approve, or do. Plan for about 30–35 minutes, including a short watch, a focused reading, and a practical draft.

---

From a message map to a problem narrative

A message map begins with the answer: “Approve this initiative because it protects value, improves economics, and enables strategy.” That answer-first discipline remains valuable.

But executives also need enough context to judge whether the recommendation is warranted. SCR supplies that logic:

1. Situation — the relevant current reality.
2. Complication — what has changed, failed, or become risky; why the status quo is no longer acceptable.
3. Resolution — the proposed response.
4. Action — the specific decision or commitment you require from this audience.

The core distinction is simple:

• Situation says what is.
• Complication says what is wrong, at risk, or no longer sufficient.
• Resolution says what the organization should do.
• Action says what the executives in the room must do now.

The framework image ends at Resolution because SCR is the standard name. In an executive setting, however, stopping there is a common failure mode. You may have explained a good plan, but if you do not state the requested approval, priority change, or sponsorship, leaders may offer general feedback instead of making the decision you came to secure.

For a very time-constrained executive meeting, you may state your governing message as the title or opening headline before the SCR narrative:

Decision requested: approve a phased payments-platform modernization.

Then use SCR to make that recommendation feel earned rather than asserted. This is not a contradiction of answer-first communication. The headline tells executives where you are headed; SCR gives them the problem logic that supports the decision.

---

The four moves in executive language

1. Situation: establish a shared baseline

The Situation is not the entire history of the system, program, or organization. It is the small set of facts the audience must accept to understand the problem.

A strong situation is:

• Relevant to the decision rather than generally informative
• Factual rather than interpretive
• Bounded, making clear what system, customer segment, time period, or initiative is in scope
• Brief, often one or two spoken sentences

For a software-engineering initiative, useful situation content may include:

• The business capability the system supports
• Its current scale or importance
• A current target, operating model, or strategic commitment
• The stakeholders or customers affected

For example:

“Our checkout platform supports 35 percent of online revenue and is a dependency for the planned expansion into two new markets next year.”

This is a situation statement. It tells the audience why the platform matters. It does not yet claim that the platform is failing.

Avoid turning Situation into a technical architecture tour:

“The platform was originally built in 2017, uses six services, has a legacy data store, and was migrated twice…”

Some of that may later become evidence. At the beginning, it delays the point.

2. Complication: create legitimate urgency

The Complication is the disruption to the baseline: a constraint, risk, missed target, external change, or conflict that makes action necessary. It answers the executive’s silent question:

“Why should we act now rather than continue as we are?”

A useful complication has three parts:

Component	What it establishes	Example
Change or issue	What is no longer working	Peak-volume demand now exceeds reliable platform capacity.
Consequence	Why it matters	Failed transactions expose revenue and customer trust.
Cost of inaction	What happens if leaders defer	The market launch remains high-risk and operational cost continues to rise.

The complication should be concrete enough to be credible. “The system is fragile” is a technical judgment; it does not yet explain the business consequence. Compare it with:

“During the last two peak events, checkout errors exceeded our operating threshold, creating avoidable revenue exposure and requiring manual intervention from engineering and customer support.”

This makes the link between a technical condition and a business concern visible.

Do not make the complication a catalog of every defect, dependency, and historical incident. Pick the central tension. Supporting data can substantiate it later.

3. Resolution: recommend a proportionate response

The Resolution is the strategic answer to the complication. It is not a vague aspiration such as “improve reliability,” nor is it a full implementation backlog.

It should state:

• The recommended course of action
• The scope or phasing that makes it credible
• The key outcome it is designed to deliver
• The major trade-off, if one is material to the decision

For example:

“We recommend a phased modernization over 12 months, beginning with the highest-volume payment flows, to reduce checkout-failure exposure while preserving capacity for the market launch.”

This resolution is specific enough to evaluate but not overloaded with implementation detail. The design patterns, service boundaries, migration sequencing, and observability work belong beneath the recommendation as evidence and execution detail.

Your message map from the previous lesson fits naturally here. The resolution may be supported by the three reasons you already developed:

1. It protects revenue and customer trust.
2. It reduces operating cost and engineering drag.
3. It enables the planned growth initiative.

4. Action: make the executive ask unmistakable

The Action is the audience’s required next move. It must be more explicit than “Any thoughts?” or “We would welcome feedback.”

Compare these two endings:

“We will continue to refine the plan and keep you updated.”

“Today, I am asking for approval to fund the first phase this quarter and to confirm Product and Finance sponsorship for the business case by 30 June.”

The first is an update. The second is an executive decision request.

A strong Action normally includes:

• A decision verb: approve, prioritize, fund, endorse, choose, assign, unblock
• The object of the decision: the phase, option, budget, staffing change, or policy
• Any constraint or timing that matters
• The owner or follow-up, when relevant

Keep one distinction clear:

Element	Meaning
Resolution	What the organization should do: “Use a phased modernization.”
Action	What this audience should do now: “Approve phase-one funding and sponsor the dependency decision.”
Execution plan	What the team will do after approval: “Migrate the highest-volume flows first and report progress monthly.”

---

A worked engineering example

Imagine you are presenting to a VP of Product, a CFO, and a CTO. You need approval to prioritize reliability work on a customer-facing payment service over a lower-value feature initiative.

Here is a compact SCR&A narrative. The numbers and dates are illustrative; replace them with validated facts from your own initiative.

Situation: “The payments service supports a significant share of digital revenue and is required for the Q4 market expansion plan.”

Complication: “Its peak-volume error rate has risen above our operating threshold, and each incident requires extensive manual recovery. If we retain the current architecture, we carry material revenue exposure and increase the risk to the Q4 launch.”

Resolution: “I recommend a phased reliability modernization focused first on the highest-volume transaction paths. This reduces failure exposure, lowers operational effort, and creates the capacity needed for expansion.”

Action: “I am asking for approval today to prioritize the first phase in Q3, reallocate two teams from the lower-return feature work, and confirm the Q4 launch dependency.”

Notice several choices in this version:

• It does not start with the database, service topology, or migration plan.
• The complication translates engineering instability into revenue exposure, operating effort, and launch risk.
• The resolution is a recommendation, not a promise of perfection.
• The final sentence identifies the exact executive actions: priority approval, capacity reallocation, and dependency confirmation.

For a three-minute briefing, a reasonable starting allocation is:

Section	Approximate time	Purpose
Situation	30 seconds	Establish the relevant baseline.
Complication	60 seconds	Explain urgency and cost of inaction.
Resolution	60 seconds	Present the recommendation and its rationale.
Action	30 seconds	Secure the decision and clarify what happens next.

The complication and resolution deserve most of the time. If you over-explain the situation, the meeting can become a status update. If you under-explain the complication, the recommendation can feel like a preferred engineering project rather than a business need.

---

Build an SCR&A outline for a real presentation

Use the same initiative from your message map if possible. Working with one real decision across lessons will make the structures easier to compare and easier to recall under pressure.

Draft on a single page before opening PowerPoint. Write a short claim for each section, then add only the evidence you need beneath it.

Your one-page structure

Governing message or decision headline

Decision requested: [approve / prioritize / fund / choose] [initiative or option].

Situation

[Business capability, target, current state, and scope.]

Complication

[What changed or is constrained] creates [business consequence], putting [priority] at risk.

Resolution

We recommend [specific approach] because it will [primary outcome] while [material trade-off or constraint].

Action

I am asking this group to [specific decision] by [timing], with [sponsor, resource, or follow-up] confirmed.

A 12-minute drafting routine

1. Write the Action first.
   Name the actual decision. If you cannot write a decision verb, clarify whether this is really a decision briefing or only an update.

2. Write the Resolution second.
   State the recommended response in one sentence. Use a scope, phase, or guardrail if it makes the recommendation more credible.

3. Write the Complication third.
   Identify the central tension that makes the resolution necessary. Add one or two evidence placeholders, such as a trend, cost estimate, customer impact, or strategic dependency.

4. Write the Situation last.
   Retain only the context needed to understand the complication. Cut historical detail that does not change the decision.

5. Read only the four lines aloud.
   The narrative should make sense even without the supporting evidence. If it does not, revise the logic before adding slides.

A useful self-editing test is to label every sentence in your draft with S, C, R, or A. If a sentence cannot be labeled, it may be unnecessary detail, an unsupported assertion, or a point that belongs later in the presentation.

---

Deliver it without sounding formulaic

SCR&A is a thinking structure, not a script you must announce. You do not need to say, “The situation is…” during the actual presentation. Use natural verbal signposts instead:

• Situation: “Today, the service supports…”
• Complication: “The issue is that…”
• Resolution: “To address that risk, I recommend…”
• Action: “The decision I need from this group is…”

These phrases are deliberately plain. Under pressure, plain language is easier to recall and generally sounds more confident than elaborate transitions.

For your first rehearsal, speak from only five cues: headline, S, C, R, A. If you lose your train of thought, return to the next letter rather than trying to recover a missing sentence. That is the practical advantage of a clear structure: it gives you reliable places to resume.

---

Key takeaways

SCR&A turns a problem presentation into a decision narrative:

• Situation establishes the relevant factual baseline.
• Complication explains the business-relevant problem and the cost of inaction.
• Resolution states a specific, proportionate recommendation.
• Action makes the executive decision, approval, or commitment unmistakable.
• Your earlier message map supplies the reasons and evidence that make the Resolution credible.

Keep your one-page SCR&A outline. In the next lesson, you will sequence technical detail by executive relevance rather than implementation chronology, so the evidence supports the decision without burying the audience in engineering detail.