A redesign can be objectively better and still die in the room where it is shown. The presentation is not a formality at the end of the work; it is the part that converts weeks of thinking into a decision, and it is the skill most designers and agencies are weakest at. The good news is that the failures are predictable, which means they are avoidable.
Never open with the design
The instinct is to reveal. Resist it, because a design shown cold gets judged on taste, since taste is the only criterion anyone has been given.
Open by restating the problem in their words: what the audit found, what the numbers said, what the sales team reported, what customers could not do. Then state what this design is trying to change, specifically. By the time the first screen appears, the room should already be judging it against a goal rather than against their own preferences.
Two or three minutes is enough. The point is to establish criteria before showing anything that can be liked or disliked.
Before and after, every time
Show the old and the new side by side. Always, even when the old site is embarrassing, especially when the room has stopped seeing how bad it was.
People cannot evaluate a design in isolation. Given only the new version, they compare it to an imaginary ideal and find it wanting. Given the pair, they compare it to reality and see progress. This is also how you make invisible work visible: a faster page, a clearer path, a form with four fields instead of nine.
Annotate the change with its reason. “The old hero never said what you sell, so this one does, in the words your buyers use” turns an aesthetic choice into a business argument, which is the difference between a decision and a preference.
Show it moving, on a phone
Static screens invite pixel level nitpicking and hide everything a website actually is. Whenever possible, present a real staging build in a browser rather than a slide deck.
Scroll it. Hover things. Open the menu. Then pick it up on a phone and use it one handed, because most of their customers will. A design that is defended by scrolling through the real thing rarely gets picked apart, and it prevents the classic post approval shock where someone sees the built site and says “this is not what I approved”, which usually means they had never seen it behave.
If it must be static, show the awkward cases too: long headlines, missing images, the empty state. Confidence comes from showing you have thought about what breaks.
Handle “I do not like blue” properly
It will happen, usually from the most senior person, usually about colour, usually in the last five minutes.
Do not argue and do not immediately comply. Ask what the concern is underneath it: does it feel wrong for the industry, too close to a competitor, different from the brand elsewhere? Half the time there is a real constraint behind it that nobody mentioned in the brief. The other half it is genuine personal taste, which is legitimate but should be named as such so everyone knows what is being decided and on what grounds.
Then answer with evidence where evidence exists: contrast, legibility, distinctiveness in the competitive set, consistency with the brand you already own. And be willing to lose gracefully on things that do not matter. Spending credibility on a hue is a bad trade when you will need it for the structure argument later.
Structure the room
Decide in advance who is deciding. A presentation with six people and no named decision maker produces six opinions and no approval.
Say at the start what you need by the end: sign off on direction, or a list of changes with a date. Ask people to hold comments until each section is finished, so the presentation is not derailed by the first person to react. And give the group a vocabulary for the feedback you want by telling them what stage this is and what is still open.
Close with a decision, not a discussion
Never end on “so, thoughts?”. End by summarising what was agreed, what is open, who is sending consolidated feedback, and by when. Then send that in writing the same day.
Written summaries prevent the most expensive pattern in client work: an approval in the room, a different memory two weeks later, and a rebuild nobody budgeted for. It is the same discipline that makes a brief useful at the start of a project, applied at the other end.
If the answer is not yes, find out what would make it yes, specifically, before leaving. Vague dissatisfaction that goes unexamined becomes three rounds of revisions aimed at a target nobody has described.
Preparing to sell a redesign internally and want the case made properly? That is half of what we do on every project: hello@beconfidency.agency, and the before and afters are on the work.
If you want the whole project run by one team that presents its own work, that is exactly what our web design service is for.