Set the purpose before showing the work
An early concept is a proposal for discussion, not a finished design awaiting approval. Say that at the start of the meeting. Identify the decision you need now: perhaps whether a visual direction fits the audience, whether the central idea is clear, or whether a proposed format suits the project. This gives clients a useful role without asking them to judge details that have not been developed yet.
Revisit the parts of the brief that matter to that decision. For example: “We need a visual identity that feels welcoming to first-time visitors while remaining easy to use across signs and social posts.” Then explain which parts of the concept are exploratory. A client can respond more confidently when they know that the broad direction is under review but the exact typography and image choices can still change. If you need feedback from several people, name who will collect and consolidate their responses.
Show enough context to make the idea understandable
Start with a short explanation of the problem the concept addresses, followed by the idea behind it and one or two representative examples. A name, sketch, sample layout or rough image treatment may be enough. Label work-in-progress material so its level of finish is unmistakable. A polished mockup can make an unresolved idea look final; an unlabelled sketch can make a considered direction look careless.
Connect each example to a purpose rather than describing only its appearance. Instead of “We chose bright colours,” try “The contrasting colours help different workshop topics feel distinct within one system.” Show the concept in a setting where it would actually be used, such as a small event poster or a mobile page. If something is placeholder content, say so. The aim is to help the client assess the idea, not guess which details are intentional.
Ask questions that reveal the reason behind a reaction
“What do you think?” invites broad opinions that can be difficult to act on. Ask questions tied to the brief: “Would a first-time visitor understand what this event offers?” or “Which part feels least aligned with the tone we agreed on?” You can also ask what information seems missing, what might be difficult for their team to maintain, and whether the examples reflect real uses of the work.
When someone says a direction feels “too playful” or asks for a different colour, resist the urge to defend or revise it on the spot. Ask what prompted the reaction and where they expect a problem. They may be concerned about legibility, a particular audience or an internal expectation. Those are different problems, and each calls for a different response. Capture the concern in their words before proposing a solution.
Make room for feedback without losing the brief
Give clients a simple way to sort their comments. One useful distinction is between what supports the direction, what raises a concern, and what needs further testing. You might also ask them to separate essential requirements from preferences. This is particularly helpful when several stakeholders are involved: conflicting preferences become easier to discuss when everyone can see the shared project goal.
Treat unexpected feedback as information, not automatically as a change request. If a client asks for a feature outside the agreed scope, record it and ask what need it would meet. It may point to a gap in the concept, or it may belong to a later phase. Equally, do not use the brief to dismiss a legitimate concern. Explain the trade-off between options and agree on what matters most before deciding what to revise.
Close with a decision and a clear next step
End by summarising what you heard: the direction that seems promising, the concerns to address, any open questions and the person responsible for resolving them. Confirm whether the client is choosing a direction, requesting a focused revision or asking to see another possibility. Avoid leaving the meeting with only a collection of disconnected comments.
A brief written recap makes the next round easier for everyone. For example: “We will keep the welcoming tone and flexible layout, test a calmer colour approach, and check that the event details remain clear at small sizes.” That statement turns feedback into work you can evaluate. When you present the revision, show how it responds to the agreed concerns. The goal of an early presentation is not to win immediate approval; it is to create enough shared understanding to make the next decision well.
