You have 20 minutes with the leadership team. You open Figma and begin walking through the flow.
By the third screen, someone asks about a button colour. By the fifth, the meeting has become a design review by committee. The strategy you wanted to discuss has vanished.
The moment you lead with screens, you invite everyone to judge the screens.
Executives are rarely there to approve a layout. They are there to make a decision, and to feel confident it will not blow up.
Why this is hard for designers
We are trained to show the work and let it speak. It does not. McKinsey's design research found that under 5% of the people surveyed said their leaders could make objective design decisions. That number can be read as a criticism of leaders. I read it as a job description for design leaders. It is on us to give them a better way to decide.
That does not make screens unimportant. Early in my career at Silverline Technologies, I built a high-fidelity working prototype of an insurance portal from scratch. It turned business requirements into something the client could experience, secured their buy-in and won $200K in new business. It worked because it answered the client's real question: will this work for us? Screens persuade when they act as evidence for a decision.
The structure I use
1. The decision. Open with what you need. "Today we need a decision on which of two journeys to take to pilot."
2. Why it matters. Name the business number and what is at stake.
3. What we learned. Give one or two insights, with a real user quote.
4. The recommendation. Say what you would do, and be plain about it.
5. The evidence. This is where design finally appears, as proof.
6. The risks and trade-offs. Say them before someone else does.
7. The ask. Repeat what you need, by when, and from whom.
Here is the old way next to the new one:
| Designer-led story | Executive-ready story |
|---|---|
| Here is what we did | Here is what we need you to decide |
| Process first | Conclusion first |
| All the screens | Two or three key moments |
| I think this looks better | This reduces the risk we discussed |
| Hope nobody asks | Risks named up front |
Handling hard moments
"I don't like it." Do not defend it. Ask, "What concerns you about how this will work for customers?" A preference often hides a real worry.
"Can we just copy our competitor?" Bring it back to the goal: "We could. Here is what that would and would not solve."
"How do you know?" Be honest about how strong your evidence is. "This is from eight conversations, and we want to test it" earns more trust than false certainty.
Being cut off at minute three. It happens. Have your answer ready in one sentence, then let the discussion go where they need it to.
This can be taught
I care about this because I have seen what happens when people learn it. Rahul Shaligram, who reported to me at Capgemini, has written about how I helped him build the confidence to present in front of a team of more than 70 people.
Nobody is born comfortable in that room. It takes rehearsal, a clear structure, and someone willing to ask you the hard question first.
Questions people ask
How do you present UX work to executives? Start with the decision you need. Link it to a business goal, offer a clear recommendation, and use design as supporting evidence.
What do executives care about in design? They usually care about growth, risk, cost, customers and speed. Frame your work around the one that matters most to them.
Got a big presentation coming up?
I am happy to be your practice audience, and I will ask the awkward question. Write to pranjal.productmind@gmail.com or connect on LinkedIn.