Twenty-two answers to the questions you actually get in the meeting — the polite, specific way to defend the work.
How do I actually say no to ‘make the logo bigger’?
Don’t argue taste — argue the goal. ‘The user is here to do X; every pixel the logo takes, that action loses.’ If they push, show the bounce rate or a quick heatmap. Hierarchy is zero-sum, and a number ends the debate a feeling can’t.
How do I stop feedback round 14?
You can’t fix it at round 14 — you prevent it at round 0. Get one sentence signed before any pixels: the single thing this design must achieve. Name one decider for ties. After that, every note gets filtered: does it serve the goal, or is it a preference? Preferences get parked.
The client wants their brand colour on everything. What do I do?
Explain that an accent is a pointing finger: point at everything and you’ve pointed at nothing. Show them 60-30-10 — the brand colour as the rare 10% that makes the action unmissable. They want impact; rarity is the impact.
How do I push back on ‘just one more thing’?
Make ‘no’ the default and ‘yes’ earn its place. Keep the one job of the screen visible. Each ask: does it serve that job today? If not, it goes behind an advanced view or a menu — not on the wall. Twenty reasonable yeses are how simple becomes complicated.
How do I defend whitespace to someone who wants it ‘filled’?
Whitespace isn’t empty, it’s the thing that makes the one element you want seen impossible to miss. Show the before/after: same content, crammed vs. given room. Cluttered reads as panic; spacious reads as confidence. They’re paying for attention, and attention needs the silence around it.
The dev says it’s ‘basically the same.’ How do I get pixel-accuracy?
Stop handing over pictures. Hand over tokens (colour, spacing, type) and the real component with every state. When the build inherits the decisions instead of re-guessing them, ‘pixel-perfect’ stops being a fight and becomes the default. Drift is a handoff problem, not a dev problem.
The CEO doesn’t like it but can’t say why. Now what?
‘Don’t love it’ is usually an unaligned goal, not a design flaw. Re-surface the one thing you agreed this design must do, and ask: is it failing that, or is this a preference? Often the discomfort is a missing north star, and naming it dissolves the vague ‘no.’
How do I handle two stakeholders giving opposite feedback?
Don’t average them — that pleases no one and breaks the design. Name one decider, put both asks in front of them with the trade-off made visible (‘add this and we lose that’), and let them choose. Your job is to show the cost clearly, not to split the difference.
Is dark mode just inverting the colours?
No — that’s the trap. Pure-black backgrounds vibrate, copied shadows vanish, and a saturated accent glares like a hazard light. Dark mode is a second design: start from dark grey, rebuild elevation (lighter = higher), soften the text and desaturate the accent.
How light can grey text actually be?
Light enough to look calm, dark enough to clear about 4.5:1 against its background (3:1 for large text). ‘Looks fine on my laptop’ isn’t the test — a contrast checker is. Then sanity-check it on a cheap screen in daylight, because that’s where your users actually are.
How many fonts is too many?
Two, tops — one workhorse for text, optionally one display for headlines. Past that it’s a ransom note. Most ‘I need another font’ moments are really asking for a different weight, an italic, or some tracking. Give them that instead.
When is it actually OK to break the grid?
Once, on purpose, for the one thing that matters most. A grid earns its power by being kept — which is exactly why a single deliberate break becomes an instant focal point. Break it twice and you don’t have a grid, you have noise.
Nobody gave me content for the empty states. How do I design them?
Empty states are the most-seen screens you never design — every new user starts there. Don’t ship ‘No data.’ Write one line on what the space is for and add the single button that gets them started. It’s the cheapest onboarding you’ll ever build.
Real copy isn’t ready — design with lorem or wait?
Neither — design with the realest draft you can write, including the worst case. Lorem is always the perfect length, which is exactly why it lies: it builds a layout that only works for content that doesn’t exist. The 40-char name and the empty list are where users live.
How do I stop the design system becoming 40 near-identical buttons?
The moment a component is ‘just this once’ detached and tweaked, it stops being the source of truth. Audit the strays, define the real variants you need, re-attach everything, delete the orphans, and tokenise colour/radius/spacing so one change still reaches everywhere.
My mood board has 200 pins and no direction. How do I get to one?
A board’s job is to remove options, not collect them. Name the feeling in three words, cull anything that doesn’t obviously serve them (most of it goes), and get to five images that genuinely agree. Caption each so the board argues for itself in the meeting.
The site breaks at tablet width. How do I prevent it?
Because nobody designed the in-between. A site isn’t two layouts, it’s every width between them — and the middle is where real users are. Design the awkward seams (~768, ~834), constrain children (minmax(0,1fr), max-width on text/media), and slowly drag-resize to find where it snaps.
How do I make a layout look ‘professional’ with zero budget?
Put everything on one shared edge. Alignment is the single cheapest way to look expensive — it switches off a hundred tiny ‘this feels off’ alarms at once, costs nothing, and quietly says ‘an adult made this.’ Do that before reaching for shadows or a pricier font.
They want every feature on one screen. How do I argue for simple?
Simple isn’t how little you start with — anyone can draw a clean v1. It’s the discipline of a hundred small noes afterwards. Reframe the ask: power features live behind one door (an advanced view), not on the wall. A screen that does one thing well beats one that does ten things badly.
My PM wants it shipped Friday and it’s not ready. What do I cut?
Cut scope, never quality. Ship a smaller thing that’s right rather than a big thing that’s broken — because ‘fix it later’ is how the broken version becomes permanent and breeds forty more shortcuts. Decide the one must-work flow and make that flawless.
How do I get sign-off before round 1, not after round 14?
Make the goal a deliverable, not an assumption. Before you design, write the one outcome this must achieve and the one decider who breaks ties, and get both agreed in writing. It feels slow; it saves the three weeks that ‘actually, go back to v1’ costs.
Why does my layout feel ‘cheap’ when nothing is obviously wrong?
Because lots of tiny things are slightly wrong — a 13px margin, a 4px misalignment, a 17px that should be 16. None is a visible bug, but together they’re a constant low hum of ‘rushed.’ Round the spacing to a grid, snap to one edge, collapse the type sizes; the hum stops.