Building a moodboard fast when the client won't brief you

You ask what they want and you get "something premium." You ask for a reference and you get a competitor's homepage with no explanation of what about it they like. You ask for a second meeting to nail down specifics and their calendar is full until a date that's after your deadline. This is not a rare client, this is most clients, and the sooner you stop expecting a real brief to arrive the sooner you can start getting the information you actually need.

The instinct is to treat the missing brief as a blocker — something you have to chase down before real work can start. Flip that. The moodboard isn't what happens after the brief. It's how you get one, out of a client who was never going to write it down for you.

This isn't a workaround you settle for when a project is under-scoped. Plenty of clients genuinely don't know what they want yet — they know what they're reacting against, they know the vague shape of a feeling, and they're hoping you'll do the work of turning that into something specific. Waiting for them to hand you clarity they don't have is a losing bet. Building the clarity together, using images instead of adjectives, is a service you're providing, not a corner you're cutting.

Stop asking questions they can't answer

"What's your vision for the brand" is a question almost nobody can answer cold, and every hour you spend waiting for a good answer to it is an hour wasted. Clients aren't bad at describing what they want because they're careless — they're bad at it because most people think in images and reactions, not adjectives. "Premium" means something specific and idiosyncratic in their head. Your job isn't to get them to translate it into words. It's to build the thing that lets them point.

So skip the open question. Go straight to pulling six to ten references from the space they're already in — their industry, their stated competitor, adjacent categories that share a tone — and send them over with almost no framing. Not "here's some inspiration," just: which two of these feel closest, and which one feels completely wrong. A reaction is faster to produce than a description, and it's more honest, because there's no vocabulary problem standing between what they feel and what they tell you.

Keep the set deliberately uneven. If every reference you send already leans premium, you'll get a pile of soft yeses that tell you nothing. Throw in one or two that are cheap-looking, one that's aggressively minimal, one that's loud — the contrast is what makes the useful reaction show up. A client who shrugs at eight similar options will visibly recoil at the one that's wrong, and that recoil is data you didn't have five minutes earlier.

Use the competitor mention as a wedge, not an answer

"Something like [Competitor]" is the most common non-brief you'll get, and treating it as a finished instruction is a mistake — it's a starting point disguised as an answer. Pull four or five different things from that competitor's world: their color usage, their typography weight, their photography style, their layout density, their copy tone. Show the client each one in isolation and ask which of these, specifically, is the thing they meant.

Almost every time, they meant one or two of the five, not all of them. Maybe they love the confident, oversized type and could not care less about the photography. Maybe it's the whitespace and nothing else. Once you know which slice of "something like them" is doing the work, you've turned a vague pointer into an actual design decision, and you've done it faster than a follow-up call would have.

It's worth saying the quiet part out loud here: half the time, the client hasn't actually looked closely at the competitor they named. They remember a feeling from the last time they visited the site, not the specifics. Splitting it into pieces does something else useful, too — it stops you from accidentally cloning a competitor wholesale when the client only meant to borrow one idea from them.

Save in front of them, not for them

Whenever you can get fifteen minutes of a client's actual attention, don't spend it explaining your process — spend it saving images together and watching what happens. Pull up a broad set across styles and start collecting the ones that get any reaction at all, positive or negative. Say the words out loud as you save: "this one feels heavier," "this one feels colder." You're not asking them to design anything. You're narrating so they start narrating back, and the narration is the brief.

This works because live reaction beats retrospective explanation almost every time. A client who can't tell you in the abstract what "premium" means to them will absolutely tell you, in real time, that the glossy render feels cheap and the matte one feels expensive. That distinction — glossy versus matte, in their own words, said out loud while looking at real images — is worth more than a page of brand adjectives.

Track the rejections as carefully as the picks

Most people building a moodboard for a client only keep what gets approved. That throws away half your information. What a client rejects, and specifically why, narrows the space you're working in just as much as what they accept — sometimes more, because rejection reactions tend to be sharper and less polite than approval ones.

Keep a running note next to the board: not just "cut" but "cut — felt corporate" or "cut — too playful for what they said about their customers." After eight or ten of these, patterns show up that no single approved image would have told you. You start to see the shape of the no as clearly as the shape of the yes, and a shape built from both sides is a lot more reliable than one built from picks alone.

Rejections are also where you catch the thing clients rarely volunteer directly: their fear. Nobody opens a kickoff call by saying "I'm worried this will look cheap" or "I don't want this to feel like every other app in our category." But they'll say it in the margins, as a reason for cutting an image, almost every time. Write those reasons down verbatim if you can — they tend to be more useful than anything from the actual brief, if there was one.

A brief you extract through reactions is more trustworthy than a brief you're handed, because nobody had time to perform an answer they thought you wanted to hear.

Turn the board back into their words before you present anything

Before you show a single mockup, show the moodboard back to the client with a plain-language caption underneath: "based on what we've looked at, premium means confident type, low-saturation color, and almost no stock photography — is that right?" This costs five minutes and saves you from the worst version of client feedback, the kind that arrives after real design work is already done and sounds like "this isn't what I meant" with no clearer explanation than you started with.

Getting a yes to that caption is the actual brief. It's not as tidy as a document with sections and bullet points, but it's grounded in things they reacted to rather than things they tried to articulate cold, which makes it far less likely to shift under you halfway through the project.

Treat the first board as a draft of the brief, not the final board

Because you built this board through questions and reactions instead of a stated direction, expect to revise it once, quickly, after the client sees it whole. That's not a sign you did it wrong — it's the natural second pass any brief goes through once someone can see the shape of their own answer reflected back at them. Build the revision into your timeline from the start instead of treating it as scope creep, and the whole process stays fast instead of feeling like it's dragging.