How to describe the website you want without design jargon
Showing examples instead of describing an aesthetic
The notes app on your phone has the word "modern" typed into it, then deleted, then typed again. It isn't getting any more useful the third time either.
A designer can't build from an adjective. "Clean," "professional," and "modern" mean something different to every person who says them. What actually works is showing three or four sites you like, and pointing at what you like about each one specifically.
One might be the way another homepage loads a single big photo before anything else. Another might be how a menu tucks away until you tap it. Point at the specific detail, not just the site as a whole, since a whole site earns your approval unevenly, piece by piece.
Save the examples somewhere before the first meeting, not while you're sitting across from someone trying to remember a site you saw once. A folder of screenshots, even a messy one, says more in five minutes than a paragraph of adjectives ever will.
A single site won't get everything right, either. It's fine to pull one example for the photography and a completely different one for how the contact page is laid out. Naming the specific piece each time keeps a designer from guessing which detail actually caught your eye.
Deciding whether to build the site yourself or bring someone in comes before this step for a lot of people, but the brief matters just as much either way.
Saying what the site has to get a visitor to do, before how it should look
Before you describe how anything should look, write down what a visitor actually has to do once they land on the page. Call the number. Fill out a form. Book a slot. Read one paragraph and trust you enough to reach out.
That's the job the design is working for. A beautiful page that buries the phone number is a worse outcome than a plain one that puts it right where a visitor's eye actually lands first.
What a small business site actually has to accomplish is worth sorting out before you're deep into color choices and fonts, since the look should follow the job.
Write this part down in plain sentences. "A first-time visitor should be able to book an appointment within two clicks" gives a designer something to build toward. "It should feel welcoming" does not.
If you're not sure yet what that single action even is, sit with the question a while longer before you move on to color choices. Everything else on the page exists to support that one job, whether the design ever says so out loud or not.
Naming what you dislike and the reason underneath it
Dislikes are easier to name than preferences, and they're just as useful once you attach a reason. "I don't like that" tells a designer almost nothing. "I don't like that because the text is too small to read on my phone" tells them exactly what to fix.
Go through a few sites, including ones you don't like, and write down what bothers you about each. A cluttered homepage. A menu that takes three taps to find. Type that is too pale to read in bright light.
The reason is the part that actually transfers to your own project. Without it, a designer can only guess what to avoid, and a guess is exactly what you're trying to skip by describing this at all.
Feedback somebody can act on against feedback nobody can
"I don't love it" is a feeling. A designer hearing that has no next step, only a vague sense that something needs to change without knowing what. "The header feels too big compared to the photo below it" is a direction. Somebody can act on it right away.
Before you send any note back, ask yourself one question: could a stranger read this and know exactly what to change? If the answer is no, the note needs one more sentence attached to it.
This habit pays off past the first draft too. How much of your own time a build actually takes comes down in large part to how many rounds of vague feedback a project has to survive before it lands somewhere close to right.
Who in the business gets an opinion on the design
Decide, before the first draft even arrives, who actually gets a say. A partner, a manager, a whole staff meeting — every extra voice adds a round of feedback and a chance for conflicting notes to arrive on the same day.
One clear decision-maker, gathering input from others before sending anything to the designer, keeps the process moving. Everyone can have an opinion. Only one person should be the one actually sending it forward.
Say this out loud early, even if it feels obvious. "I'll gather feedback from the team and send one combined note" sets an expectation a designer can plan around, instead of guessing whose comment carries the final word.
A staff vote on ten small choices during the build slows everything down and rarely improves the outcome. Save real group input for the priorities you set at the very start, not for every font and photo along the way.
Writing the brief down so it survives the third meeting
Memory is unreliable by the third meeting, and everyone's memory of the first conversation drifts a little differently. Write the brief down: the examples, the priorities, the dislikes and their reasons, who signs off. One page is enough.
What to bring alongside that written brief rounds out the picture — logos, existing photos, any copy you've already got — so the first real meeting starts from something concrete instead of a blank page.
Send the written brief before the meeting, not during it. That gives a designer time to actually read it, rather than skimming while you're both sitting there. A document beats a memory every time somebody circles back weeks later, and somebody always does.
Update it once the designer sends a first draft back, too. A brief that only exists in your head on day one is no help by week three, when the details that mattered most have already blurred together.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go