Before the mood board, write the briefCreava Editorial · Topic discussion
Project planning / @creava.editorial
Before the mood board, write the brief
A collection of references can create momentum before the project has a shared purpose. One person sees the color, another sees the casting, and someone else assumes the production scale is part of the proposal. Begin with the audience, the setting in which they will encounter the work, and the change the work is meant to support. A reference becomes more useful when that context is already clear.
Specific questions, practical answers, and the next detail to check. Prepared by Creava Editorial.
Q
Question 01
A workshop announcement must serve first-time visitors and returning members, but only one poster is funded. How should the brief decide what receives the largest space?
A
Creava Editorial · Answer
Start with the information both groups need to act: what is happening, where, when and how to respond. Identify the extra explanation a newcomer needs, then see whether a short supporting line can provide it. Choose the hierarchy around the primary viewing situation, and document which secondary questions the poster will direct elsewhere.
↳
Follow-up question
What if the organizer insists that every workshop technique must appear, because experienced visitors use that list to decide?
A
Creava Editorial · Clarification
Ask which techniques materially change the decision and which are supporting detail. Test a concise selection with a clearly named destination for the full list. If the full list must remain on the poster, acknowledge the resulting space requirement instead of quietly shrinking essential information.
Q
Question 02
A team approves a reference board, then changes the target audience before production begins. Which parts of the brief should be reopened without automatically discarding all previous work?
A
Creava Editorial · Answer
Recheck the audience task, required evidence and viewing context first. Mark the previous decisions that depend on those assumptions, and retain independent choices only where their purpose still holds. Prepare a short comparison showing what remains usable, what needs testing and what cannot be carried forward without a new decision.
↳
Follow-up question
Should the existing colour direction stay while the message changes, or does keeping it risk carrying the old brief forward?
A
Creava Editorial · Clarification
Treat the colour direction as a hypothesis with a reason, not as protected work or an automatic mistake. Test it against a representative output for the new audience. Keep it if it supports the revised task, and record that rationale beside the updated approval.
YOUR SIDE OF THE DISCUSSION
Add your perspective.
Your own notes stay private on this device. They are not sent to other members.
Background discussion & source notes
CREAVA EDITORIAL / DISCUSSION DESK
Let’s take the question further.
Practical follow-ups, open questions and considered answers from the Creava editorial desk.
5 official discussion notes
Creava Editorial@creava.editorial · Note 01
Which audience gets the first sentence?
When a launch brief names customers, retail partners and potential collaborators as one audience, ask what each group must do next. A customer may need to understand a product difference; a retailer needs usable assortment information. Those are separate reading tasks. For a small assignment, choose one primary task and list secondary material elsewhere. A useful exercise is to write the first sentence for each audience, then compare the required evidence. If the sentences demand different facts, the brief probably needs separate outputs rather than a more expansive mood board.
Creava Editorial@creava.editorial · Note 02
A brief should leave some choices open
Specificity does not mean deciding every visual detail before exploration. Separate acceptance conditions from creative hypotheses. A launch image may need readable packaging and room for translated copy, while the exact background remains an experiment. Write the conditions as tests and the hypotheses as questions. This avoids two opposite problems: a vague assignment that cannot be reviewed and a rigid document that quietly dictates an untested solution. At kickoff, ask which decision would be expensive to reverse. Resolve that dependency early and leave lower-risk choices available for study.
Creava Editorial@creava.editorial · Note 03
Case analysis: one bottle, three destinations
Consider a reusable bottle introduction needed for a product page, a retailer sheet and a vertical social story. A single attractive photograph cannot automatically satisfy all three. The product page needs detail and scale, the sheet needs space for specifications, and the story needs a legible opening at phone size. Build three deliverable rows with their information priorities before designing the shoot. Then identify shared capture requirements, such as a clean side view and a fastening detail. Sharing production becomes a deliberate efficiency, rather than an assumption that every destination accepts the same crop.
Creava Editorial@creava.editorial · Note 04
Tradeoff: approve the question before polishing the answer
A polished reference deck can make an unresolved strategy feel settled. If the team cannot agree whether a story should explain durability or celebrate appearance, make two rough communication outlines instead. Each outline should state its promise, the evidence it requires and what it leaves out. Review those outlines without detailed styling so the decision concerns the communication task. Only develop the preferred route once an owner chooses. This spends a small amount on clarification while avoiding a larger investment in beautifully presented work that answers the wrong question.
Creava Editorial@creava.editorial · Note 05
After the kickoff: test independent interpretation
Send the agreed brief without your presentation notes to someone who did not attend the kickoff. Ask them to list the deliverables, the first production action and the unresolved decisions. Compare their answer with yours rather than asking whether the document looks clear. If they infer a video where you intended a still image, revise the output description. If they cannot identify approval ownership, revise the process section. Keep a dated change summary so collaborators can see what changed. The test is shared understanding, not the length or formality of the document.
CREAVA / WORKING GUIDE
Keep a discussion attached to its decision.
The editorial rooms connect complete guides with useful follow-ups; personal notes here remain on this device.
01
Read the thread in context
Start with the guide’s central question, then read the follow-ups about examples, limitations and practical decisions. A good continuation changes or clarifies an action rather than simply agreeing with the title.
Use a particular paragraph or question as the starting point for your own notes. Record what applies to your current project and what remains uncertain.
02
Keep private information out of public material
Remove personal contact details, client secrets and restricted source files from anything you intend to publish. A useful discussion can usually describe the decision without disclosing the entire project.
Ask permission before turning another person’s feedback into a quote or testimonial. Public editorial notes and actual member messages are different kinds of content.
03
Take the result back into the work
Close a reading session by writing the next action, the evidence needed and the person who owns the decision. Keep a separate list of unresolved questions so they are not forgotten after an interesting discussion.
If a conversation needs to be delivered to another person, use a confirmed communication channel. A note saved in this browser does not send a message or notify a collaborator.