A packaging designer needs a decision to work toward. A folder of attractive references can help set a mood, but it does not explain the audience, the communication problem or the files required at the end. A useful brief connects those pieces. It gives the designer room to propose an answer while keeping the project specific enough to review.
For an adult gum-category identity study, the brief can stay focused on visual communication and presentation. The task might be to compare two packaging formats, develop a wordmark system or prepare a professional introduction kit. The practical outcome of this guide is a short brief that a designer can estimate, question and use, followed by a clear plan for reviewing the work.
Name the project and the audience
Begin with a plain description of the project in one or two sentences. Say who is commissioning it, which adult audience the materials are intended for and where the design will appear. Avoid opening with a string of adjectives such as premium, modern and distinctive. Those words become useful only when the brief explains the situation in which the design needs to work.
For example, a founder might need an identity presentation for professional collaborators. The first materials could be a title slide, a simple overview page and a packaging-format study. That is a concrete setting. It tells the designer that the work must hold together across a screen presentation and a physical mockup, with enough clarity to support a professional conversation.
Write down the reader's task. Is the collaborator comparing visual directions, reviewing information hierarchy or considering a design engagement? Each task suggests a different presentation. A comparison needs consistent scales and labels. An introduction needs a clear sequence. Naming the task keeps the design discussion attached to the intended use of the materials.
Describe the communication problem
The brief should explain what is difficult today. Perhaps the project has several wordmark sketches with no common spacing system. Perhaps the packaging references use inconsistent proportions. Perhaps the overview page contains too much text at the same level. A specific problem gives the designer something to solve and gives the review meeting a useful starting point.
Include the content that must appear. Supply the exact name, approved short description, required contact link and any other fixed text. Label provisional copy separately. A designer should not have to guess which wording can change and which wording has already been approved. That distinction also prevents a visual review from quietly becoming a debate about an unfinished message.
If the project has a category address such as CBDGum.com, show how the full address will be used alongside any shorter wordmark treatment. A website address, an email signature and a presentation cover have different space constraints. The brief can ask the designer to demonstrate the same identity in those actual settings, so the final choice is based on useful applications.
Choose a small reference set
Select a few references and explain what each one contributes. One might demonstrate a calm reading surface, another a compact wordmark and another a restrained material palette. The explanation matters more than the number of images. A designer can use a specific observation; an unlabeled board requires them to infer what the client likes about every object.
Also say what should not carry into the work. A reference may have an interesting type scale but an unsuitable illustration style. A material image may be useful for color while its lettering is irrelevant. Clear notes help the designer borrow the right principle and create an identity that belongs to the project, rather than imitate the surface of a reference.
Use only material the team is entitled to share for the intended purpose, and keep a source note beside each item. The working folder should preserve the original filename or a descriptive replacement. When a reference changes during the project, record which version is current. That small habit can prevent a review from comparing work against two different boards.
Specify the first deliverable
A manageable first round might request two visual directions shown on the same three applications. Define the applications and their viewing scale in advance. Both directions could appear on a title slide, a website header and a neutral packaging mockup. Equal conditions make the comparison more useful than one polished scene beside a rough sketch.
For a worked example, the project could explore a forest-green and mint identity. The first direction might use a large serif wordmark with a compact symbol; the second might use a restrained sans-serif treatment. The brief would ask each direction to demonstrate hierarchy, small-size legibility and the same approved content. The review can then discuss how each solution serves the stated task.
List the files needed at the end of this round. A review PDF may be enough for the first discussion, with editable artwork reserved for the selected direction. Ask the designer to explain the status of fonts, photographs and other dependencies. A clear deliverable list makes it easier to understand what is ready for use and what remains part of the development process.
Plan the review before the work arrives
Choose one person to consolidate feedback. Contributors can have different responsibilities, but the designer needs a coherent response. A useful feedback note identifies the application, the observation and the requested next step. “Increase the subtitle at the actual mobile size” is more actionable than “make it feel stronger.” The first can be inspected in the next proof.
Separate decisions from experiments. The team might approve the palette while asking for another test of wordmark scale. Record both in a decision log so a later round does not reopen everything. That log can be short: date, decision, reason and owner. It gives the designer a stable set of choices to build on.
Review the digital version with accessibility in mind. The W3C image decision tree can help the team consider the purpose and description of each image. For text and controls, the W3C explanation of minimum contrast is a useful original reference. Include those checks in the handoff rather than leaving them as a final cosmetic review.
Close the brief with a handoff plan
The last part of the brief should explain how the selected direction will be packaged for the next contributor. Name the expected folder structure, approved file formats and person responsible for the final review. Include a short usage sheet showing the wordmark, spacing and palette. A future contributor should be able to find the current assets without reopening the entire project conversation.
Before sending the brief, read it as if you were estimating the work. Can you identify the audience, the communication problem, the fixed content, the first deliverable and the decision maker? If one is missing, add the answer in plain language. A strong brief is useful because it turns a broad visual ambition into a sequence of decisions a designer and founder can make together.