What Makes a Design Actually Work (Not Just Look Good)
I have reviewed hundreds of design portfolios over the past decade. Some of them are genuinely beautiful. Stunning typography. Careful color choices. Compositions that look like they belong in a design museum.
Nitin Monga
Designer · Developer · 3D Artist
And some of those beautiful portfolios represent work that completely failed the clients who paid for it.
This is the thing design education gets backwards. It teaches aesthetics — what looks good — without enough emphasis on function — what works. The two are related but they are not the same thing, and confusing them is expensive for everyone involved.
The gap between beautiful and effective
A website that wins a design award but has a 90% bounce rate is not a good website. It is an expensive mistake with good photography.
A logo that looks stunning in Behance presentations but becomes illegible at 32 pixels is not a good logo. It is an impressive file that fails at its actual job.
A brand identity with a perfectly constructed color palette that a print shop cannot reproduce accurately is not a good brand identity. It is a beautiful system that breaks in the real world.
These failures are more common than the design industry wants to admit. And they happen because designers are trained — by portfolio culture, by award shows, by social media — to optimize for how their work looks in a controlled presentation, not how it performs in the messy reality of actual use.
I am not exempting myself from this. Early in my career I made these mistakes too. I prioritized what would look good in screenshots. I made decisions that served the Behance post, not the client brief. I had to learn, through real projects and real feedback, what the difference actually felt like.
What "working" actually means in different contexts
Before anything else, a designer needs to answer a specific question for every brief: what does success look like for this particular thing?
For a website, success might mean time-on-page. Or conversion rate. Or the number of contact form submissions per month. Or how fast it loads on a 4G connection in a Tier 2 Indian city. None of these show up in a screenshot.
For a logo, success might mean recognition at a distance. Or legibility at 16 pixels. Or reproducibility in single-color ink. Or how it feels embossed on a business card. None of these show up in a Behance mockup.
For an event branding system — the kind I designed for the SRH × CUB Meet & Greet or the CSK × CUB event — success means how every element reads on camera, under stage lighting, in a wide-angle shot, and in a closeup simultaneously. A backdrop that looks great in isolation can look wrong the moment three players sit in front of it.
The job of a working designer is to define what success looks like before the first mark is made, and then design toward that definition. Everything else — the aesthetics, the style, the creative choices — should serve that definition.
The five properties that separate working design from pretty design
After 12 years of delivering work that had to function in the real world — not just look good in presentations — I have arrived at five properties that I check every piece of work against.
Property one: does it communicate the right thing in the right amount of time?
Every piece of design communicates something. The question is whether it communicates the right thing, to the right person, in the right amount of time.
A billboard has about three seconds of attention from a driver. A business card has about five seconds of attention before being pocketed. A website hero section has about four seconds before a visitor makes their first judgment about whether to stay.
Design that takes too long to communicate what it is doing has failed, regardless of how beautiful it is. If I look at a landing page for thirty seconds and am still not certain what the company does, the design has failed — even if the typography is perfect and the photography is stunning.
Property two: does it work at the scales it will actually be used at?
This is the one I see ignored most often in digital design work.
A logo designed only at the size it will appear in the designer's Figma file is incomplete. It needs to work at 512 pixels for an app icon, at 200 pixels for a website header, at 60 pixels for a business card, and at 16 pixels for a favicon. If it falls apart at any of those sizes — if the details become muddy, if the letterforms merge, if the mark becomes unrecognisable — it is an unfinished logo.
The same principle applies to responsive web design. A layout designed only on a 1440px desktop monitor and never tested on an actual phone in someone's actual hand has not been properly designed. It has been partially designed.
I built a free tool called Logo Scale Tester at nitinmonga.in/tools/logo-scale-tester specifically because this check is so rarely done properly. Upload a logo, see it at ten real-world sizes from billboard to favicon, in one screen. It is a check that should be standard on every logo project. It is not.
Property three: does it hold up when things go wrong?
Real design gets used in conditions the designer never anticipated.
Brand colors get approximated by printers who do not have the right inks. Logos get placed on backgrounds the brand guidelines did not account for. Websites get used by people on devices from 2018 with slow internet connections. Event backdrops get photographed by cameras with different white balance settings under fluorescent lights instead of the warm studio lighting assumed during design.
A design that only works in ideal conditions is fragile. Working design anticipates imperfection.
When I design event branding — standees, backdrops, entry boxes — I think constantly about how these pieces will look on a phone camera under whatever lighting the venue has, not how they look in my Photoshop file. The design decisions I make because of that thinking are different from the ones I would make optimizing only for the presentation.
Property four: does the visual hierarchy guide attention correctly?
Every design has an implicit reading order. The viewer's eye goes somewhere first, then somewhere second, then somewhere third. A working design controls that sequence deliberately. A poorly considered design lets the eye wander and leaves the viewer doing work they should not have to do.
In print: does the headline read first? Does the call to action appear at the right moment in the reading sequence? Is the most important information also the most visually dominant?
In digital: does the primary action compete with secondary information for attention? Is the navigation taking up cognitive space that should be given to the content?
In event branding: in a wide shot with five people on stage, where does the camera-viewer's eye go? Does it land on the brand elements at the right moment? Or does an overly busy backdrop compete with the speakers for attention?
Hierarchy is not a design principle. It is a function. A design with broken hierarchy is a design that makes the viewer work harder than they should. Working design removes that friction.
Property five: does it behave consistently across all its parts?
This is the property that separates good design from great design over time.
A brand identity with nine fonts, seventeen accent colors, and no internal logic breaks down at scale. Each new application — a new social post, a new print piece, a new team member applying the guidelines — introduces more inconsistency until the brand looks like it was designed by a committee over five years.
A design system with clear rules, constrained choices, and documented decisions gets stronger over time. Every new application reinforces the identity instead of diluting it.
This applies at the micro level too. A website where every button has slightly different border radius, every card has slightly different shadow, and every heading has slightly different font weight is a website that feels vaguely wrong to users without them being able to name exactly why. The inconsistency registers as unprofessionalism even when the individual elements are well-designed.
How I use these five properties on actual projects
I want to be clear that this is not a checklist I consciously run through on every project. After twelve years, these considerations are woven into how I approach any brief. But for new designers, making them explicit is useful.
Before I design anything: I answer the question of what success looks like for this piece. Not in general — specifically. What metric, what behaviour, what outcome tells me this worked?
During the design: I check visual hierarchy before I refine anything else. If the reading order is wrong, refinement is waste.
Before I call anything finished: I test it at the actual sizes and in the actual contexts it will be used. Not in my Figma file. Actually. A phone in my hand. A print test on the right paper. A photograph under actual lighting.
Before I deliver: I look at the full system — all the parts together — and check for consistency. Not just visual consistency, but behavioral consistency. Do all the buttons behave the same way? Do all the headings follow the same hierarchy logic? Do all the cards have the same structure?
Why this matters more than it used to
In 2026, the tools for making things look good have never been more accessible. AI can generate aesthetically impressive images in seconds. Design templates are everywhere. Canva exists. Any reasonably focused person can produce something visually competent without much training.
What AI cannot do is understand the context a piece of design will live in, anticipate the real-world conditions it will be used under, or make the judgment calls that turn competent-looking work into work that actually achieves what it was made to achieve.
That judgment — contextual, experienced, calibrated to the specific brief and the specific client — is what professional design is. And it is becoming more valuable, not less, as the bar for making things look presentable drops to near zero.
The designers who will continue to earn well in this environment are the ones who can clearly articulate the difference between their work and a competent AI output. That difference is function. It is context. It is the five properties above applied with real experience to a real brief.
Looking good is easy now. Working is still hard. That is where the value lives.
A final note
This post is not a criticism of designers who prioritise aesthetics. Aesthetics matter enormously. Beautiful work earns attention, builds trust, and signals the quality of what it represents. I care deeply about how things look.
But beautiful and working should not be in tension. The best design I have done — the work I am most proud of, the work that clients remember and come back for — is work where those two things were the same thing. Where the visual choices were so well-suited to the function that you could not separate them.
That is the goal. Not beautiful design. Not functional design. Design where the beauty and the function are the same decision.
If you want to see this thinking applied to real projects, the case studies at nitinmonga.in/work show the process behind the finished work. And if you have a project where the stakes are real — where the design actually has to work, not just look good in a presentation — the contact page is open.
Tagged
Nitin Monga
Graphic Designer, 3D Artist & Full-Stack Developer based in Punjab, India. 10+ years building websites, CGI ads, and digital platforms.