Keep the preference, then clarify it
“Younger”, “bolder” or “more premium” describes a desired feeling and should not be dismissed. Yet those words are insufficient for evaluating a design. One person imagines darker colour, another more space, while the business may actually want greater professional credibility. Record the preference and ask what prompted it: which part of the current material causes concern, and for whom?
If an owner says a brochure feels unprofessional, ask what causes that impression: an unclear business, weak images or inconsistent information order. Each needs a different response. Dark colours and more white space cannot supply missing product evidence. Connecting a feeling to an observable issue lets the designer choose a response rather than guess a preferred style.
Answer three context questions
Who sees the design, where do they see it, and what should they believe afterwards? Distributor materials may explain a range, a client presentation may establish relevant capability, and packaging may prioritise recognition. Those answers guide hierarchy and visual character. A focused task need not become a full branding programme when the direction is already clear. Resolve upstream uncertainty only where it actually exists.
Translate the answer into a task: a new mobile reader identifies the business and finds a relevant product; a salesperson uses one page to explain two options. Specific tasks clarify essential information. If several contexts matter, rank them and decide whether one adaptable version is enough or separate reading and presentation versions are needed.
Annotate the references
State whether a reference is useful for density, photography, type scale or colour, and identify what does not fit. Otherwise a designer may reproduce its mood when the business wanted clearer information. Compare like contexts rather than judging a technical sheet by an advertising film or a phone page by a desktop poster. References establish a shared vocabulary; they do not replace product facts or available assets.
Two or three relevant references are easier to discuss than dozens of unrelated styles. Note “consider image clarity, not the black background” or “consider heading proportions, not the brand graphic.” Add real copy and imagery so the team can judge comparable conditions. If the desired effect depends on photography, discuss that input before expecting a similar result.
Review against the agreed task
Evaluate the representative page using the original questions: discoverability, understanding, recognition and readability at actual size. Personal preferences can remain part of feedback, but explain which objective they affect. A change in audience or use is a change of direction, not simply a colour adjustment. That distinction makes the next round a defined task instead of another search for the right adjective.
Review at the intended size, without the designer’s explanation at first, and attempt the agreed task. Record practical difficulties before style preferences: an unreadable product name and a disliked colour have different implications. Both deserve discussion. If a new audience or channel emerges, record it explicitly rather than allowing the original brief to shift silently.
Write a checkable brief
Summarise reader, use, main message, existing assets and open questions in one paragraph. It need not be a long document, but should explain the design choice. If it tries to cover everyone and every context, prioritise the main use. Record additional uses explicitly so a focused task does not silently become a system rebuild.
The paragraph can cover audience, context, priority, evidence and elements to retain. Retained items may include the approved mark, product name and essential facts; evidence may include permitted cases, images or specifications. List unresolved points and their owners. Once both sides can describe the same task in their own words, a representative design has a shared basis for review.
