Start with the request, but do not treat it as the brief
“Make it feel more modern” can sound like a design direction, but it leaves important decisions unresolved. Modern to whom? Which part of the experience feels dated? What should people understand or do differently? If a team moves straight from that phrase to visual concepts, each person may solve a different problem. Treat the request as an opening observation: it tells you what the client has noticed, not necessarily what the project needs to answer.
Write down the request in the client’s own words before interpreting it. Then separate what you know from what you assume. You might know that the client wants to update a website; you might only assume that its colours are the problem. This distinction gives you a useful starting point for a conversation. It also makes it easier to explain later why the agreed project question differs from the client’s first description.
Find the change behind the requested change
Ask what prompted the request and what would be different if the work succeeded. Useful prompts include: Who is having difficulty now? Where does that difficulty appear? What do people misunderstand, overlook or struggle to complete? Why does it matter at this point in the project? Ask for a specific example, such as a recent client conversation or a page the team hesitates to share. Examples make broad adjectives easier to discuss without pretending they are precise requirements.
Listen for a distinction between symptoms and goals. A client may say their presentation looks inconsistent because different team members keep rebuilding slides. The inconsistency is visible, but the project may need to address how people create and reuse materials. That does not rule out visual design. It shows why the design work might need a simple template and guidance, rather than a collection of polished sample slides.
Write a question that gives the work direction
A workable project question names an audience, a situation and a useful change, while leaving room to explore the answer. A simple pattern is: How might we help a specific group understand or do something in a specific context? “How might we make the brand more exciting?” is hard to test because excitement can mean almost anything. “How might we help first-time visitors understand what this studio offers before they contact us?” gives the team something clearer to investigate.
For example, imagine a small studio asks for “a stronger website.” During the conversation, it becomes clear that prospective clients often ask whether the studio handles production as well as concept development. A project question could be: “How might we show prospective clients the full path from concept to production on the studio website?” That question suggests possible work on page structure, project descriptions and imagery. It does not decide in advance that a new homepage or visual identity is required.
Check whether the question fits the project
A clear question can still be too large. Check it against the time, access and decisions available. Can the team speak with the intended audience, review existing material or examine a few relevant interactions? Which parts can the client approve or change? If the question is about an entire customer experience but the project covers only a brochure, narrow the question to what the brochure can reasonably influence.
Try a short working exercise with the client. Write one proposed question, then ask each participant to name one possible answer and one piece of information they would need before choosing it. If the answers are all minor variations of the same execution, the question may already contain a solution. If they range across unrelated problems, it may be too broad. Revise until it supports several plausible approaches within the agreed scope.
Confirm the question and keep it visible
Put the agreed question in a brief note alongside the audience, the known constraints and what the team will produce. Add a few signs that would indicate progress, such as whether a reader can explain the studio’s services after viewing a draft page. These signs need not be formal metrics. Their purpose is to give the client and creative team a shared way to discuss the work beyond personal preference.
Return to the question when reviewing concepts. Instead of asking only which option looks better, ask what each option helps the intended audience understand or do. If new information changes the problem, update the question openly and check whether the scope must change with it. A project question is not a promise that the first interpretation was perfect. It is a practical tool for keeping exploration, decisions and feedback connected to the same purpose.
