Executive communication and architecture storytelling

Communicating upward means presenting architecture to the executives who hold budget and mandate, in their language and at their altitude, so they can make a decision. The correct technical framing is stakeholder communication: the deliberate work of getting the right message, in the right form, to the people whose backing the architecture needs.

The TOGAF Standard treats this as a first-class part of the method rather than an afterthought. Its Architecture Development Method produces a Communications Plan early and revisits stakeholder management throughout, because an architecture that stakeholders do not understand or support will not survive contact with the organisation. The plan exists to make sure the architecture reaches the people who decide its fate.

Most architects are fluent downward, toward delivery, and quiet upward, toward the board. That imbalance is the root of the opening story. A delivery team can absorb a 40-slide model because it works in that detail every day. A board cannot, and does not need to. It needs the decision, the reasoning behind it, and the risk it is being asked to carry. Communicating upward is the discipline of giving a board exactly that and nothing that gets in its way.

There is a strategic-leadership reading here too. An architecture function that cannot communicate upward is invisible to the people who set direction, and an invisible function is the first to be cut when budgets tighten. The architects who shape enterprise strategy are the ones the board hears from clearly and trusts. Upward communication is how architecture earns a seat at the table where strategy is set.

An executive narrative is a single, ordered account of an architecture that a listener can hold in their head and repeat to someone else. The test is exactly that: if a board member cannot repeat your point to a colleague after the meeting, you did not give them a narrative, you gave them material.

The move from a body of work to a narrative is a change of ordering. Architecture work is produced bottom-up: you gather baselines, analyse gaps, define target states, and sequence transitions. That is the right order to do the work and the wrong order to tell it. A narrative is told top-down. It starts with the point the executive most needs, the decision, and then supplies only the reasoning that supports it.

This top-down ordering is not an invention of this course. It is the same structure Barbara Minto set out in the Pyramid Principle: lead with the answer, group the supporting reasons beneath it, and let the detail sit below that for anyone who wants to drill in. A board reads the top of the pyramid and decides; a delivery lead reads further down. The same architecture serves both when it is told as a pyramid rather than a pile.

Three moves turn a body of work into a narrative. First, decide the one sentence the board must leave with, and say it first. Second, strip everything that does not serve that sentence: the ADM diagram, the tool choices, the internal debates all belong in an appendix, not the story. Third, express the reasoning in the board's terms, cost, risk, obligation, and customer outcome, not in the architecture's terms. The architecture is the same underneath; only its surface changes.

The one-slide architecture story is a single slide that carries the whole recommendation, structured so a board can read it top to bottom and reach a decision without turning a page. It is a forcing device: the constraint of one slide makes you decide what actually matters.

The slide has four parts, read in the order a board expects a recommendation to arrive. The situation states the fact that forces a decision now. The options name the real alternatives that were weighed. The recommendation gives the single option you are asking the board to back, with the one-line reason it wins. The risk states the residual exposure the board is being asked to accept, and who owns it. The figure below lays out the four parts against the board question each one answers and a worked line from London's roadmap.

The order matters as much as the content. Delivery teams are used to situation first and recommendation last, because that mirrors how the work was done. A board wants the recommendation early enough to read the rest as justification for it. The one-slide story keeps situation, options, recommendation, and risk in that sequence on the page, but the spoken version leads with the ask: you say what you want the board to decide, then walk the slide as the case for it.

One slide does not mean one sentence. It means one screen the board can take in at a glance, with the four parts visible together so the shape of the argument is obvious before a word is spoken. Everything that does not fit, the models, the analysis, the alternatives you discarded early, sits behind the slide as backup you reach for only if asked.

The four-part recommendation structure is the backbone of the one-slide story, and it deserves treatment in its own right because each part has a job that boards notice when it is missing.

Situation. One or two lines stating the fact that forces a decision this year. Not the history of the estate, not the eighteen months of work, just the present pressure. If the situation does not create urgency, the board will ask why it is being asked to decide now, and the answer must already be on the slide.

Options. Two or three genuine alternatives, each with an honest trade-off. A board distrusts a recommendation presented with no rejected options, because it looks like a decision already made rather than a judgement offered. Naming the roads not taken, and why, is what earns the recommendation its credibility.

Recommendation. One option, stated plainly, with the single reason it beats the others. This is the sentence the board must leave with. It should be sayable without the slide. Everything above it exists to make this line land; everything below it exists to make it safe.

Risk. The residual risk the board is accepting if it says yes, and the named owner who will manage it. Boards approve risk they can see and own; they refuse risk that feels hidden. Stating the risk plainly, with an owner and a review point, is not a weakness in the case, it is what lets a board say yes with confidence.

Notice that this structure is a specialisation of a pattern the earlier governance modules already used. A decision paper to the Architecture Board and a recommendation to the executive board share the same spine: what is the situation, what were the options, what do we recommend, and what is the residual risk. The board is different and the language is lifted higher, but the shape is the same one architecture governance relies on throughout.

Stakeholder politics is the reality that a board is not a single mind but a room of people with different interests, and a recommendation lands differently with each of them. The correct technical framing, again from the ADM, is stakeholder analysis: understanding each stakeholder's position, influence, and concern before the meeting, not during it.

Reading the room starts with a simple map. For each executive who will be in the room, ask two questions: how much does this decision affect them, and how much power do they hold over it. That gives four broad groups, and each needs a different handling.

• High power, high interest. These are the people you must win before the meeting. Brief them one to one, hear their objections privately, and adjust or answer them so nothing lands as a surprise in the room. A board decision is usually made in the corridors before the meeting; the meeting ratifies it.
• High power, low interest. Keep them satisfied with a short, clear line. They will follow the lead of the high-interest group if nothing alarms them, so give them no reason for alarm.
• Low power, high interest. Keep them informed and use them as allies. They often carry the detailed knowledge that answers a challenge, and their visible support reassures the powerful.
• Low power, low interest. A light touch is enough. Over-communicating here wastes effort you need elsewhere.

Handling politics does not mean bending the architecture to whoever is loudest. It means understanding concerns well enough to address them on their own terms. A finance director who resists a rebuild is usually not against good architecture, they are protecting a budget line, and the answer is to show the option that fits inside the RIIO-ED2 allowance, not to argue that architecture should override cost. A concern met on its own terms turns an opponent into a sponsor. A concern dismissed turns a quiet doubter into a public one.

Power and interest tell you who to brief first; they do not tell you what to say. The figure below maps the concerns that recur across London's stakeholder groups and shows which three each group actually prioritises, which is where the content of a private briefing comes from.

The strategic-leadership point is that politics is not a corruption of the process to be resented, it is the process. Executives are paid to weigh competing interests, and an architect who treats that weighing as an obstacle will lose to one who treats it as the terrain. The most effective architects do the political work before the room, so the room itself is calm.

Here is how London's chief architect took the same transformation roadmap back to the board and won the decision that had been deferred the first time.

The one slide

• Situation. The 11 kV control estate that keeps power flowing to 2.3 million customers cannot carry the forecast electric-vehicle load. A decision is needed this year to stay ahead of demand.
• Options. Patch and defer (cheapest now, highest failure risk by 2028); full replacement immediately (safest, breaches the RIIO-ED2 allowance); phased three-year rebuild (fits the allowance, manages risk).
• Recommendation. The phased three-year rebuild, because it is the only option that stays within the Ofgem allowance while removing the load risk before it bites.
• Risk. Supplier lead times could slip the middle phase. Owned by the programme director, with a quarterly review point and a defined fallback to accelerate a later phase.

The politics, handled before the room

The chief financial officer (high power, high interest) had deferred the first attempt over cost. She was briefed a week ahead, shown the phased option costed against the allowance line by line, and given the chance to shape the funding profile. She arrived a sponsor rather than a sceptic. The chief operating officer (high power, lower interest) needed only the assurance that customer supply was protected during the works, which was a single line on the slide. The head of network operations (lower power, high interest) carried the load forecast that made the situation credible and spoke to it when the board tested the numbers.

The regulatory framing

Because London operates under Ofgem regulation, the recommendation was framed against the RIIO-ED2 allowance from the first line. That framing did two things at once: it answered the finance objection before it was raised, and it turned the architecture decision into a regulatory-fit decision the whole board could evaluate in terms it already owned.

The outcome

The board approved the phased rebuild in twenty minutes. The 40-slide deck still existed, unchanged, as the appendix and the repository record behind the one slide. The architecture had not moved. The story had been rebuilt so the board could reach the decision the architecture had earned all along.