When Everything Cannot Be Emphasised
I was staring at a staging site at 2:00 AM, nursing a lukewarm coffee, when the email pinged. It was the classic: “I love the layout, but can we just make the hero image and the CTA button… bigger?” I felt that familiar, dull ache in my temples. Everyone tells you that managing expectations is about “soft skills” or “client psychology,” but let’s be real—most of the time, knowing how to handle a client who wants it bigger is actually about preventing a total visual meltdown. They don’t realize that every time they ask for more scale, they’re actually asking me to break the very hierarchy that makes the site readable in the first place.
I’m not here to give you a lecture on “empathetic communication” or some expensive course on managing egos. I’ve spent nine years un-building the mess left behind by people who thought “more” meant “better,” and I’ve learned that you have to treat design like a set of logical decisions, not a buffet. I’m going to show you how to push back using actual design logic rather than just saying “no,” so you can stop being a pixel-pusher and start being the expert they actually hired.
Table of Contents
Managing Client Expectations Through the Lens of Intent
When a client starts shouting about scale, they usually aren’t actually talking about pixels; they’re talking about a feeling. They feel like their brand isn’t being heard, or they’re worried the message is getting lost in the whitespace. Instead of just fighting them on the technicalities of padding and margins, I try to pivot toward managing client expectations by digging into what they actually want to achieve. If they want a hero image to take up the entire viewport, I need to know if they’re trying to create impact or if they’re just terrified of empty space.
Once I understand the why behind the “bigger,” the conversation shifts from a tug-of-war over size to a discussion about hierarchy. I stop being the person saying “no” and start being the person explaining how design principles and scale actually guide a user’s eye. If everything is huge, nothing is important. I’ve learned that the best way to handle these moments isn’t to hide behind a technical wall, but to show them how an oversized element might actually diminish the very authority they’re trying to project. It’s about translating their ego into a functional layout.
The Ego in the Layout Deciphering Scale Requests
When a client says, “Make it bigger,” they rarely mean they want a larger font size. Usually, they’re reacting to a feeling of invisibility. They look at a beautifully balanced, minimalist layout and think it looks “empty,” when in reality, that white space is doing the heavy lifting of guiding the eye. This is where defending design decisions becomes less about being right and more about translation. I’ve learned that a request for scale is often a coded way of saying they don’t feel the hierarchy is working. They aren’t attacking my eye; they’re reacting to a perceived lack of impact.
Instead of just cranking up the padding or the H1 weight, I try to dig into the why. Is the call-to-action getting lost in a sea of secondary content? Is the visual weight of a hero image competing with the text? If I just blindly follow the instruction to increase scale, I’m essentially letting their anxiety dictate the technical architecture of the site. That’s a fast track to a bloated, unreadable mess. My job during the client revision process isn’t to be a human resizing tool, but to figure out if we need more scale, or if we just need better contrast.
Five Ways to Stop the Bloat Before It Kills the Site
- Stop treating “bigger” as a measurement and start treating it as a symptom. When they say they want a larger hero section, they usually mean they’re worried their message isn’t landing. Fix the copy, don’t just scale the container.
- Show them the “Domino Effect” in real-time. If they want a 40px increase on every H2, show them how that pushes the entire fold down and forces a mobile user to scroll through a desert of white space just to find a button.
- Use the “Scale vs. Weight” argument. Most clients confuse size with importance. I tell them we can make the typeface bolder or the contrast higher to grab attention without actually inflating the DOM size and killing the LCP scores.
- Create a “Decision Log” for every enlargement. Every time they insist on a scale change that defies the original design system, I document it. It’s not about being petty; it’s about showing them exactly why the site feels “clunky” three months later.
- Force a trade-off. Design is a zero-sum game. If they want the imagery to be massive, something else has to give—usually the whitespace or the content density. If they aren’t willing to sacrifice one for the other, they aren’t designing; they’re just hoarding pixels.
Stop Scaling the Chaos
At the end of the day, when a client screams for “bigger,” they aren’t actually talking about pixels; they’re talking about a lack of confidence in the design. We’ve looked at how to peel back those layers of ego, how to interpret their actual intent, and why blindly following a request for massive scale is a one-way ticket to a bloated, unreadable mess. My job isn’t just to make things large; it’s to protect the integrity of the layout from being swallowed by bad decisions. If you don’t translate their anxiety into a functional design choice, you’ll end up with a site that looks like a broken page builder experiment rather than a professional product.
Don’t let the fear of a difficult conversation turn you into a glorified resizing tool. You were hired because you understand how elements actually live together on a screen, not because you know how to drag a slider to 150%. Stand your ground, offer a better alternative that solves their underlying problem, and remember that your value lies in the decisions you make—not just the ones you execute. Build something that lasts, even if it means telling a client “no” to a giant headline.
