How to get executives to act on design work

Design teams lose most of their influence in the last mile. The research is solid, the audit is thorough, the findings are real. Then the deck lands in an executive meeting, gets polite nods, and nothing happens. The work was good. The delivery killed it.

I've presented design cases to C-level audiences for years, and the ones that turned into action all followed the same rules. None of them are about the design work itself.

Write it to be read without you

Your deck will travel. It gets forwarded, skimmed on a phone between meetings, and reread weeks later by someone who never saw you present it. So write full sentences and make every page carry its own logic. If a slide only makes sense with you narrating, it fails the moment you leave the room.

Cut the journey

Nobody senior needs the methodology tour. How many screens you reviewed, how many iterations it took, how the team worked. Rigour shows up in the quality of the findings, and the process story just delays the point. Open with what's wrong, what it costs, and what to do about it. Your first page should be the conclusion.

Evidence, not opinion

Every finding gets anchored to something observable. The broken flow itself, a number, the screen exactly as it exists today. Opinion invites debate. Evidence invites a decision. If a claim can't be shown, it doesn't go in the deck.

Recommend one thing

An options menu feels safe, but it hands your job to the audience. Make one recommendation and state the tradeoffs plainly: what it costs, what you're giving up, what you'd watch out for. Executives make decisions all day. Give them one shaped like a decision. If they choose differently, fine. They did it with the tradeoffs in full view.

Show the fixed state

Critique describes a problem. A mockup settles it. Put the current screen next to the fixed one and an abstract argument becomes a before and after that anyone can judge in five seconds. With a decent design system behind you, producing that mockup takes hours, and it does more persuading than every paragraph in the deck combined.

Speak in outcomes

Leave the design vocabulary at the door. No heuristics, no affordances, no information architecture. Translate everything into time, errors, money and risk. "Users can't find the export" matters less than what that costs every week. If a technical term has to stay, define it in the same sentence.

The test for all of this is simple. The last audit I delivered this way left the room with decisions made and owners assigned, instead of a follow-up meeting on the calendar. When the deck is built to be acted on, people act on it.