How to Judge Design Work Without a Designer

You can judge design work without being a designer. The trick is to stop asking whether you like it and start asking five narrower questions: can a stranger say what the page is for in five seconds, does it show the real product, does it hold together when the content changes, does it still work on a phone, and can the studio explain each decision in one sentence. None of those need training. All of them separate good work from work that is only confident.

This matters most for founders with nobody on the team who does design. Without that person, the loudest opinion in the room decides, or the studio with the most polished pitch wins by default. Both are bad ways to spend a design budget.

Why liking it is the wrong test

Most founders review design the way they would review a photo. Does it look nice? Does it feel modern? That test fails in a predictable way. Polished work that says nothing passes easily, and plain work that sells clearly gets marked down for looking simple.

Good design is not the absence of flaws. It is a set of decisions that help a specific person do a specific thing. Once you judge it that way, you do not need taste of your own. You need to know who the person is and what the thing is, which you already do.

Check one: the five second test

Show the page to someone outside the company for five seconds. Then hide it and ask two questions. Who is this for? What does it help them do?

If they cannot answer, the design has failed, however beautiful it is. If they answer with your category but not your difference, such as "some AI tool for sales", the design is competent and generic. The strongest work gets a specific answer back, close to the sentence you would use yourself.

Run it with three people. One confused reader is noise. Three is a pattern.

Check two: is the product actually on the page

Count how much of the first screen shows your real interface, your real output, or a real customer. Then count how much shows abstract shapes, stock gradients, and illustrations that could belong to anyone.

Weak design hides the product because the product is hard to make pretty. Strong design finds the one moment in the product worth seeing and makes that moment clear. If a draft replaces your interface with a glowing orb, ask why, and listen for a reason better than "it looks cleaner".

Check three: break it on purpose

Design that only works with perfect content is fragile. Ask the studio to swap in your longest headline, a customer logo that is wide and ugly, and a pricing tier with a long name. Then look again.

Good systems bend. Spacing holds, type still reads, nothing overlaps. Weak work falls apart the moment real content arrives, which is exactly what will happen three weeks after launch when your team edits it. This is also the quickest way to see whether you are buying a page or a system.

Check four: look at it on a phone first

Many reviews happen on a large monitor in a meeting room. Many of your visitors arrive on a phone. Open every draft on your own phone before you comment on the desktop version.

Look for three things. Can you read the headline without zooming? Is the main button within reach of your thumb? Does the page make its point before the second scroll? A studio that presents only desktop mockups is presenting the easier half of the job.

Check five: ask why, one decision at a time

Pick three specific choices in a draft. Why this headline size? Why is the proof below the fold? Why this color for the button? A good designer answers each in a sentence that refers to your buyer or your goal.

"It is on trend" and "it feels premium" are not reasons. "Your buyers scan for security before anything else, so it sits second" is a reason. You do not need to agree with it. You need it to exist, because a studio that can explain its decisions can also change them sensibly when you push back.

Judging a portfolio before you hire

The same checks work on a studio's past work. Run the five second test on three live client sites, not the case study images. Open them on your phone. Look at whether those sites still look good today, since a site that fell apart after handoff tells you the system was fragile.

Then check the studio's own website. It is the one project where it was the client, with no budget limit and no committee. If that site is generic, slow, or vague, expect the same for yours. We cover the delivery side of this in how to tell if a design agency actually ships.

What to do when the team disagrees

Without a designer, reviews often turn into a vote. Replace the vote with the checks. Anyone can report the five second test results, the phone check, and whether the studio gave reasons. Personal preference can still be said out loud, but it goes last and it breaks ties rather than setting direction.

Name one person who makes the final call on design. It does not need to be the most senior person. It needs to be the person closest to the buyer.

Where to go next

If you are choosing between studios on quality, our shortlist of design agencies that actually have taste compares ten on public evidence, and the boutique design studios for AI startups list covers smaller teams. When the proposals arrive, comparing design agencies with no public prices shows how to line them up. And if you are still deciding whether to hire or partner, read design partner vs hiring an in-house designer.

Studio Maydit is a web and product design studio working with AI founders in the US, UK, and Europe, most of whom have no designer in house. We explain every decision in plain terms and expect to be questioned on it. If you want a second opinion on a draft or a proposal before you commit, book a 30 minute call and bring the work you are unsure about.