To explain a design decision in English, say four things in this order: what you decided, why, what supports it, and what you gave up. Keep each part to one or two short sentences. You don't need advanced vocabulary. You need a clear order and a few phrases you can rely on.
Why it feels harder in English
Most designers I coach read and write English well. The hard part is when someone asks, "Why did you design it this way?" and they have to answer right then. In their own language it takes a minute. In English, they either freeze or talk in circles.
In your own language, you think and speak at the same time. In English, part of your brain is busy finding words, so structure is the first thing to go. That's why a simple structure helps more than new vocabulary.
A simple structure: Decision, Reason, Evidence, Trade-off
- Decision: what you chose.
- Reason: the problem it solves for users or the business.
- Evidence: what supports it (research, testing, data, a known pattern).
- Trade-off: what you gave up, and why it's worth it.
Here's an example:
"We moved the filters to the top of the page. Users weren't finding them in the sidebar. In testing, 4 out of 5 people missed them. We lose a bit of space for results, but people find what they need faster."
That's four sentences. Short sentences sound confident, not simple.
Phrases for each step
| Step | Phrases you can use |
|---|---|
| Decision | "We went with…" / "I chose X over Y." / "We decided to…" |
| Reason | "The main reason is…" / "This makes it easier for users to…" / "We were trying to solve…" |
| Evidence | "In testing, 4 out of 5 users…" / "The data showed that…" / "Users already know this pattern from…" |
| Trade-off | "The downside is…" / "We gave up X to get Y." / "It's not perfect, but…" |
| Next step | "Next, we want to test…" / "If it doesn't work, we can…" |
Numbers make your evidence much stronger. If you're not sure how to say them naturally, read How to talk about numbers in English.
What to say when someone pushes back
Acknowledge first, then explain. Acknowledging doesn't mean you agree. It shows you're listening, so people listen back.
- "That's a fair point."
- "Can I walk you through why we went this way?"
- "We looked at that option. The problem was…"
- "What would you need to see to feel comfortable with this?"
- "Why don't we test both and let the results decide?"
Before and after
One of my students knows her work inside out. But when someone pushed back on her design, she'd give in straight away:
- Avoid: Before: "Yes, you're right."
- Better: After: "I see what you mean, but the bigger issue is…"
She didn't change her opinion. She just stopped giving it up.
Adjust it to your audience
The structure stays the same. What changes is which part you lead with.
| Audience | What they care about | Example |
|---|---|---|
| Developers | How it works, edge cases | "When the list is empty, we show a message instead of a blank screen." |
| Product managers | Impact, scope, timing | "This should cut support tickets about filters, and it's a small change." |
| Executives | The outcome, in one sentence | "This makes it faster for customers to find products." |
Habits that make you sound less sure
None of these are mistakes. They just change how people hear you.
Starting with an apology
- Avoid: "Sorry, but I think…" sounds like you expect to be wrong.
- Better: Try "Here's another way to look at it."
Too many softeners
- Avoid: "Maybe we could possibly try…"
- Better: Try "I recommend we try…"
An opinion with no reason
- Avoid: "I think it's better."
- Better: Add "because…" and the evidence.
Telling the whole process first
- Better: Start with the decision. The story can come after, if people ask.
Practice
Pick one decision from your last project. Say it out loud using the four steps. Aim for under 30 seconds. Then try the activity below.
Frequently asked questions
How do I justify a design decision without data?
Use other kinds of evidence: user interviews, usability principles, accessibility standards, patterns users already know, or business goals. Say what you're basing it on, for example "We don't have data yet, but this follows a pattern users know from checkout pages." Then say how you'll measure it.
How can I sound more confident when I present my design in English?
Put the decision first, use short sentences and cut extra softeners. Prepare your first sentence before the meeting. Confidence comes more from structure than from vocabulary.
What do I say when a stakeholder disagrees with my design?
Acknowledge their point, ask what's behind it, then give your reason and evidence. If you still disagree, offer a way to test it.
Do I need advanced English to present my design work?
No. A clear structure and a small set of reliable phrases will take you most of the way.
