Start by separating the request from the goal
“Can you make this look more professional?” sounds like a design request, but it does not yet explain what the design needs to accomplish. Before opening a template or choosing a font, ask what the finished piece is for. A presentation meant to help an audience follow a complex idea needs different choices from a printable planner meant to be written on every day.
Write down the request in the requester’s own words, then translate it into a working goal. For example, “Make these slides more polished” might become “Help new team members understand a five-step process during a short presentation.” That goal gives you something to evaluate. Larger headings, fewer ideas per slide and a consistent diagram style may serve it better than decorative details.
If the goal still feels broad, ask what the audience should know, feel or do after seeing the design. The answer does not need to sound formal. “Find the next step without asking for help” is a useful goal for a planner page; “remember the three main points” is useful for a presentation. A clear outcome narrows the design decisions that follow.
Ask questions that reveal useful constraints
A long questionnaire can be as unhelpful as no questions at all. Start with the decisions that would change the layout: Who will use this? Where will they see it? What information must it include? What must remain editable? When does a first version need to be reviewed? These answers shape the format before you spend time refining details.
Ask about existing materials, too. A brand palette, logo, previous presentation or sample page can show what should stay consistent. Treat examples as clues rather than instructions to copy. If someone shares a design they like, ask which part appeals to them: the open spacing, the restrained colors, the image treatment or the way information is grouped.
Make constraints concrete. “It needs to work for print” should lead to questions about page size, orientation and whether people will write on it. “It’s for social media” should lead to the intended format, amount of text and whether the graphic needs to work as part of a series. Record any unknowns instead of quietly making assumptions; an unresolved question is easier to handle when it is visible.
Turn descriptive words into design decisions
Words such as “clean,” “bold” and “friendly” can mean different things to different people. Do not discard them, but ask what they should look like in this project. “Clean” might mean generous spacing and a limited number of text styles. “Bold” might mean stronger headings, not brighter colors everywhere. “Friendly” might mean straightforward language and approachable illustrations rather than a playful font.
Choose two or three priorities and describe how they affect the work. For instance: “Readers should scan the page quickly, so each section will have a clear heading and short supporting text.” This connects a preference to a purpose. It also gives you a way to explain design choices during review without relying only on personal taste.
When priorities compete, decide which one wins. A slide packed with required detail cannot also be effortless to scan from a distance without changing how the information is presented. The brief might specify that essential points stay on the slide while supporting detail moves to speaker notes. Naming that trade-off early prevents the first draft from becoming an attempt to satisfy incompatible expectations.
Write a brief someone can actually use
A useful creative brief does not need to be long. Give it a short project summary, the primary audience, the desired outcome, the required content and the planned deliverables. Add the intended size or format, any existing visual guidelines, the top design priorities and known constraints. If there are several pieces, list each one separately rather than hiding them under a phrase like “a set of graphics.”
For a printable weekly planner, a brief might say: “Create a letter-size, portrait page for people planning work and personal tasks. Include a seven-day overview, space for three priorities and a notes area. Keep it legible when printed without color, and leave enough open space for handwriting.” This is more actionable than “make a simple planner.” It identifies both what must appear and how the page will be used.
Keep assumptions distinct from confirmed requirements. You might note, “Assumption: this will be printed at home,” followed by a question about paper size. That small distinction protects the workflow: you can begin exploring an approach without mistaking a guess for approval.
Confirm the brief before refining the design
Send the brief back in plain language and invite corrections. Ask the requester to confirm the goal, required content and deliverables before you refine typography, color or imagery. If they cannot answer every question yet, agree on which unknowns matter now and which can wait. A brief is a working agreement, not a promise that nothing will change.
Set a review point that matches the risk. For a layout-heavy presentation, reviewing a few representative slides can reveal problems before the full deck is built. For a planner, an early page structure can confirm whether the writing spaces are useful. Ask for feedback against the stated goal: Is anything missing? Is the order clear? Will the intended audience be able to use it?
When the request changes, update the brief rather than relying on memory. A new audience, added content or different format may affect the layout throughout the project. Keeping those decisions in one place makes revisions easier to understand and helps everyone judge the finished design by what it was meant to do.
