HelloSiteWorks Websites. Branding. Beautiful details.Let’s talk Email us
Start a project
← Back to the journal
Mint paper fox planning a logo brief beside a phone mockup and fictional leaf identity applications on a cup, card and sign.
Original HelloSiteWorks concept illustration with a fictional leaf identity.
HELLOSITEWORKS FIELD NOTES · Design

A better design brief starts with real uses.

Give a design project a useful starting point: the people it serves, the places it appears and the decisions that need to be made.

4 min read · Practical ideas for a stronger first impression

The useful bits.

Describe the first real use before choosing a style.

Separate required details from open preferences.

Agree practical review questions before concepts arrive.

Begin with an ordinary moment.

A design brief becomes easier to discuss when it starts with something the business needs to do. A small coffee shop might need its name to read clearly on a street sign, its mark to fit a profile circle and its takeaway cup to feel related to both. Those are useful starting points. They give the designer a situation to work with before anyone chooses a favourite colour.

Describe who will encounter the design and what they need to understand. Someone walking past a shop has a different amount of attention from someone reading a proposal. Keep the description concrete: where the piece appears, what information matters and what the next sensible action looks like. A brief does not need to predict every future use. It should make the first real uses clear.

Separate the essential from the interesting.

Write down what must be present and what is still open to exploration. The correct business name is essential. An established colour may be essential if the project must work with existing materials. A preference for a particular illustration style can remain a preference until the team has considered how it fits the task.

Keep the first project small enough to judge. If the immediate need is a readable identity for a sign and a profile image, say so. A future packaging range can be recorded without becoming a hidden requirement for the first review. For a fictional neighbourhood coffee shop, two agreed placements give a clearer starting point than a long list of objects nobody has committed to producing.

Bring references with an explanation.

A reference becomes useful when you explain the detail that caught your attention. Perhaps the spacing feels calm, the contrast makes a small label easier to read or the character has an expression that suits the business. Name that detail rather than asking for the whole design to be copied. Different references can contribute different observations.

Include an example that feels wrong for the project as well, and explain why. A playful mascot might be a poor fit for a serious document header while still being useful in a social greeting. These observations help define the work. They do not prove that another business’s identity, illustration or photograph is available to reuse. Keep references distinct from assets you own or have permission to use.

Agree what the review will ask.

Choose a few questions before the concepts arrive. Can the name be read at the intended size? Does the compact version stay recognisable? Do the pieces feel related without forcing the same layout onto every format? Review the plain design and the intended application together. A beautiful mockup can show a direction, but it cannot settle supplier requirements or physical production quality.

Make room for feedback that points to a specific problem. “The small name disappears on the cup” gives the next revision a job. “Make it pop” leaves the designer guessing. Decide who gathers the feedback and who makes the final decision, so the review produces one coherent set of next steps rather than several conflicting instructions.

Leave a clear starting point for the next conversation.

Finish the brief with the materials already available, the questions still unanswered and the first agreed deliverable. Identify who can confirm names, supply existing assets and answer production questions. If a date matters, explain what is happening on that date and what actually needs to be ready. An unresolved supplier specification should stay visible rather than becoming an assumption.

A useful brief is a shared reference, not a prediction that every detail will remain unchanged. Update it when a decision changes the work, and keep the current version easy to find. Before sending it, try reading it as someone meeting the business for the first time. They should be able to explain the immediate task, the intended audience and how the first design direction will be reviewed.

Keep a good idea going.

All field notes →
Websites · 4 min read

Choose website images with their placement in mind.

Review the picture inside its intended layout, with the real words and a phone view, before treating an attractive image as the right fit.

Read the field note
Design · 4 min read

Give each approved design variation a clear use.

Connect the variations in your identity set to real placements, then record where a new format still needs its own review.

Read the field note