Examples of useful requests
The difference is context, not design jargon. These are illustrative examples you can adapt.
A website request
Too vague: “Make the homepage look better.”
Useful: “Our homepage does not make it clear that we serve commercial clients. We want facilities managers to request a consultation. Start with the hero and service overview. The approved copy and brand files are linked below. Keep the existing booking tool. Please show a desktop and mobile direction before implementation.”
Why it helps: the audience, desired action, scope, assets, and review stage are clear. We can assess a direction against the business goal.
A print request
Too vague: “Need a flyer ASAP.”
Useful: “Design a double-sided A5 flyer for our upcoming open house. Its job is to get local homeowners to register using the supplied URL. Final copy, photos, and the printer template are linked below. We need a production PDF and a digital JPG. The printer needs approved artwork by the date in the brief; our marketing lead will approve it.”
Why it helps: size, sides, audience, action, production requirements, formats, and the real deadline are known.
A brand request
Too vague: “Something modern, like this logo.”
Useful: “We need a logo that feels dependable and contemporary for an electrical contractor. It must stay readable on a van and at small website sizes. I like the reference’s simple geometry, not its color or exact symbol. Our business name, positioning, existing materials, and competitors are linked below.”
Why it helps: the reference communicates a quality to explore rather than a mark to copy. Real use cases can guide the design.
Feedback that moves work forward
Too vague: “Make it pop.”
Useful: “The service name is harder to spot than the photo caption. Customers need to identify the service first, then find the booking action. Can we adjust the hierarchy while keeping the current direction?”
Why it helps: the problem and priority are clear, while the design response remains open.