How to Give Design Feedback in English at Work
ESL English learning: Master the vocabulary tech professionals need to discuss UI mockups, visual hierarchy, and design systems with clarity.
Pronunciation Guide: Design Vocabulary
Mispronouncing design terms in meetings can undermine your credibility. Here are the trickiest words from this article.
hierarchy /ˈhaɪərɑːki/
HI-er-ar-kee
Saying 'hi-RAR-kee' — stress is on first syllable
intuitive /ɪnˈtjuːɪtɪv/
in-TOO-i-tiv
Saying 'in-too-EE-tiv' — the 'i' is short, not 'ee'
sophisticated /səˈfɪstɪkeɪtɪd/
suh-FIS-ti-kay-tid
Saying 'so-fis-ti-KAY-ted' — stress on second syllable
evocative /ɪˈvɒkətɪv/
i-VOK-uh-tiv
Saying 'ee-vo-KAY-tiv' — stress on second syllable, not third
aesthetics /iːsˈθetɪks/
ees-THET-iks
Saying 'ay-STHET-iks' — first syllable is 'ees' not 'ay'
Why Design Vocabulary Matters in Tech
Whether you're a software engineer reviewing a front-end implementation, a PM writing a design brief, or a data scientist suggesting dashboard improvements, you need vocabulary to discuss visual concepts clearly. Vague feedback like 'It looks weird' frustrates designers and slows iteration cycles.
Being visually literate — having an educated understanding of design principles — helps you collaborate more effectively. Teams that share a common design vocabulary ship better products faster because they spend less time clarifying what 'make it pop' actually means.
Culture note: Direct vs. diplomatic feedback
In many tech cultures, overly blunt design criticism can damage relationships. Even if your company values directness, framing feedback as questions ('Have you explored...?') rather than commands ('Change this') keeps collaboration smooth — especially with external contractors or cross-cultural teams.
Key Vocabulary for Design Discussions
The adjectives below help you articulate exactly what's working — or not — in a UI mockup or design system. Each term includes its opposite, so you can describe the full spectrum of design quality.
| Term | Tech Definition | Opposite | Example in Design Review |
|---|---|---|---|
| intuitive | Easy to understand without instructions | confusing | The nav is intuitive — users won't need onboarding tooltips. |
| cluttered | Too many elements competing for attention | clean / minimal | This dashboard feels cluttered; can we reduce the number of widgets? |
| cohesive | All elements feel unified and intentional | disjointed | The colour palette is cohesive across all screens. |
| sophisticated | Showing advanced, polished design skills | primitive / rough | The micro-interactions feel sophisticated — really premium. |
| evocative | Successfully creates the intended mood or feeling | flat / uninspiring | The hero image is evocative; it immediately signals 'enterprise security.' |
| thought-provoking | Makes users stop and engage deeply | forgettable | The empty-state illustration is thought-provoking — it encourages action. |
| pedestrian | Ordinary, lacking creativity (negative) | dazzling | The icons feel a bit pedestrian; can we explore custom illustrations? |
| tongue-in-cheek | Playfully humorous, not meant literally | earnest / serious | The 404 page is tongue-in-cheek — a dinosaur saying 'Page extinct.' |
- Use 'original' when a design feels fresh and innovative — not predictable or derivative.
- Call something 'challenging' when it requires effort to understand but rewards that effort.
- Reserve 'peerless' for designs that genuinely outperform all competitors — overuse weakens impact.
Scenario 1: Giving Feedback on a UI Mockup
Your designer has shared a Figma link in Slack. You need to provide constructive feedback that's specific enough to act on. Here's how to structure your response using design vocabulary.
| ❌ Weak feedback (heard at work) | ✅ Stronger feedback |
|---|---|
| This looks busy. | The card layout feels cluttered — the visual hierarchy isn't guiding my eye to the primary CTA. |
| I don't like the colours. | The colour contrast between the text and background doesn't meet WCAG AA; could we darken the text? |
| Make it more modern. | Could we explore more sophisticated typography? The current font feels a bit dated. |
| It's confusing. | The icon for 'settings' isn't intuitive — users might expect a gear, not a slider. |
| This is boring. | The hero section feels pedestrian; have you considered an evocative illustration that reinforces our brand story? |
Grammar tip: Hedging your feedback
Use modal verbs and conditional structures to soften criticism: 'This might feel more cohesive if...' or 'I wonder whether we could...' These hedges signal collaboration rather than command.
Scenario 2: Design Review Meeting — Visual Hierarchy and Layout
In a synchronous design review, you need to articulate visual concepts quickly. The vocabulary of art criticism — sketchy, shadowy, colourful — has useful metaphorical applications when discussing how elements are portrayed in an interface.
| Art Metaphor | Tech Usage | Example Sentence |
|---|---|---|
| paint/paints | Describe how something presents or frames content | The onboarding flow paints our product in a very enterprise light — is that intentional? |
| sketchy | Incomplete, lacking detail, or untrustworthy-looking | The placeholder copy makes the pricing page look sketchy; users might not trust it. |
| shadowy | De-emphasised, secondary, less visible | Can we make the secondary nav items more shadowy so the primary actions stand out? |
| depict/portray | Show or represent visually | How should the error state depict the problem — icon, colour, or both? |
| illuminate | Clarify, make obvious, highlight | The tooltip illuminates the feature's purpose without cluttering the main UI. |
| mould/shape | Influence or guide user behaviour through design | The visual hierarchy should shape the user's journey from awareness to conversion. |
When discussing visual hierarchy, be specific about what draws the eye: size, colour, contrast, whitespace, and position. Saying 'The CTA doesn't pop' is less useful than 'The CTA's colour doesn't contrast enough with the background to establish clear hierarchy.'
Scenario 3: Writing a Brief for a Designer or Front-End Engineer
A design brief or RFC section on visual requirements should be clear, specific, and use vocabulary both designers and engineers understand. Avoid subjective terms without examples.
| ❌ Vague brief language | ✅ Actionable brief language |
|---|---|
| Make it look premium. | Use sophisticated micro-interactions and a cohesive, muted colour palette (see Stripe's checkout for reference). |
| Users should feel trust. | The UI should evoke trust through clean typography, ample whitespace, and visible security badges. |
| Be creative with the 404 page. | A tongue-in-cheek 404 illustration is on-brand; see our empty-states style guide for tone. |
| Don't make it boring. | The dashboard should feel thought-provoking rather than pedestrian — consider data visualisations that invite exploration. |
Register shift: Slack vs. design doc
In Slack: 'Hey, the mockup looks a bit cluttered to me — maybe we can simplify the card layout?' In a design doc: 'The current card layout presents a cluttered visual hierarchy; recommend reducing element density to improve scannability.'
Common Mistakes: What We Hear vs. Better English
| ❌ Heard at work | ✅ Better English |
|---|---|
| The design is not understandable. | The design isn't intuitive. / The layout is confusing. |
| This is very creative design. | This is a very original design. / This design is dazzling. |
| The page has too much things. | The page is cluttered. / There are too many elements. |
| I want it to look professional. | I want it to feel sophisticated and cohesive. |
| The colours don't go together. | The colour palette feels disjointed. / The colours lack cohesion. |
| This icon meaning is not clear. | This icon isn't self-explanatory. / The iconography is ambiguous. |
Practice Exercises
Multiple choice
Choose the best answer.
A designer shares a UI mockup that feels overwhelming with too many buttons, icons, and text blocks. Which adjective best describes this problem?
Multiple choice
Choose the best answer.
Which phrase is the MOST constructive way to suggest changes in a design review?
Multiple choice
Choose the best answer.
Your team's 404 error page features a cartoon dinosaur saying 'This page is extinct!' Which adjective best describes this design approach?
Complete the sentence
Type the missing word or phrase.
Complete the sentence: 'The visual ______ on this dashboard is unclear — I can't tell which metric is most important.'