Structuring Situation-Complication-Resolution Arcs: Give Every Architecture Diagram a Point of View

The problem: a diagram that shows everything and says nothing

You are asked to walk a mixed room through the architecture. The slide has forty boxes. The architects read the connectors, the operations VP reads nothing, and nobody can say afterward what changes for their team. The diagram was accurate, and it still failed.

A diagram is an argument only when it has a point of view. The situation-complication-resolution structure gives it one: where the buyer is today, what is going wrong there, and what the future state looks like once it is fixed.

Build the arc from discovery notes, not from the product

Before you draw, write three sentences from your discovery notes, in the buyer’s words.

• Situation: how the current workflow runs today.
• Complication: the bottleneck, risk or cost that makes it fail.
• Resolution: the future state and what it changes for them.

Every element in your diagram should earn its place by serving one of these three sentences. If a box does not, move it to an appendix slide.

Draw the complication, not just the target

Most architecture diagrams show only the future. Start with the current state and mark the bottleneck visibly, for example with one highlighted node. The room should see the problem before they see the answer. When the resolution arrives, the same layout shifts and the highlighted node disappears, so the improvement is visible without a speech.

Adjust the depth to the audience

The same situation-complication-resolution arc works for a lightning talk and for a security review, but the detail changes. For executives, keep three to five elements and name the business effect. For architects, keep the arc and add the interfaces, failure paths and constraints they will ask about. For a skeptical engineering team, show where the design is weak first. Credibility comes from naming limits.

Decision and check

Pick your next diagram and write the three arc sentences before you open the slide tool. The check is simple: cover the diagram and read only your three sentences aloud. Does a person who was not in discovery understand the problem and the change? Then show the diagram, and remove any element that none of the three sentences needs.

At SE Ignite, we teach this in a free curriculum built on the 80% philosophy: master the repeatable structures that carry most of what you will present.