Brand Presentation, Critique, and Packaging Final Deliverables

Why the Final Presentation Matters

A finished brand system has no value until a client or employer can see it, understand it, and act on it. The panel presentation is not a formality — it is the moment you prove that every design decision connects back to a strategic purpose. Reviewers in professional practice ask hard questions, and your ability to respond calmly and precisely using correct design vocabulary is just as important as the quality of the work on screen.

This lesson walks you through three phases: rehearsing and refining your verbal defense, performing under panel critique, and packaging every file so the work can be handed off without errors.

Phase 1: Rehearsal with a Peer Partner

Eight minutes is not much time. Rehearsal lets you discover which sections run long and which transitions feel weak before the panel sees them. Deliver your full run-through out loud — silent review is not the same as speaking in front of an audience.

Your peer partner uses a structured feedback form with three focus areas:

• Strategy connection — Can the reviewer trace each design choice back to a stated brand value or brief criterion?
• System coverage — Have you shown every required component: logo suite, color palette, typography system, usage rules, and at least one application example?
• Design vocabulary — Are you using precise terms (primary logotype, secondary palette, clear space, visual hierarchy) rather than informal descriptions?

After rehearsal, identify at least two specific feedback points and revise your script or slides before the panel. This is not optional; acting on feedback demonstrates professional responsiveness.

Phase 2: Panel Presentation and Critique

The two-person panel includes your instructor and a guest reviewer or advanced student acting in that role. Expect at least three critique questions. These questions are not meant to catch you out — they are meant to test whether you understand your own work deeply enough to defend it.

Common critique question types include:

• Why did you choose this typeface over alternatives?
• How does this color palette address the target audience identified in the brief?
• What would you change if the client needed a one-color version?

When answering, do three things: reference the original brief criteria, use correct terminology, and be honest if a decision was exploratory. Saying "I tested two approaches and chose this one because the x-height at small sizes read more clearly" is stronger than a vague answer.

Avoid defensive body language. Write down each question before answering so you respond to what was actually asked. If a question reveals a genuine gap in the system, acknowledge it briefly and describe how you would address it in revision.

Phase 3: File Packaging and Final Submission

After any required revisions, you will organize and package all project files into a standardized folder hierarchy. Professional studios use consistent naming conventions so any team member — or a print vendor — can open the job without hunting for missing assets.

Required folder structure:

```

LastName_BrandProject_Final/

├── Fonts/

├── Links/

├── Packaged_AI_Files/

├── Exports/

└── Guidelines_PDF/

```

For every Adobe Illustrator print file, run File > Package from within Illustrator. This function copies all linked images and the document fonts into a self-contained folder alongside the native `.ai` file. It does not embed fonts into the file itself; it gathers the font files so a recipient with the proper license can open the job correctly. Verify that the package report shows zero missing links and zero missing fonts before closing.

For any InDesign guidelines document, run the equivalent File > Package process in InDesign, then move the resulting folder into your Packaged_AI_Files directory or a separate InDesign_Package subfolder depending on your instructor's checklist.

Complete the instructor-provided file delivery checklist line by line. Common failure points include:

• Exported PDFs saved at screen resolution instead of print resolution (300 ppi minimum for raster elements)
• Font folders that are empty because a font was activated through a cloud service rather than installed locally
• Files named with spaces or special characters that cause errors on some operating systems — use underscores instead

Compress the entire top-level folder into a single `.zip` archive before submitting via USB drive or shared cloud folder. Label the archive with your last name, project name, and the submission date in YYYY-MM-DD format.

File and Equipment Safety

Before the presentation session, back up your working files to a second location — a cloud folder or a separate drive. Hardware failure during a final critique is rare but not unheard of. Confirm that the presentation display is powered and the correct input is selected before your session begins; do not assume a previous student left the setup correct for you.

When connecting personal USB drives to school equipment, scan for malware first using whatever utility is available on the workstation. Never submit a drive that has been connected to an unknown network environment without scanning it.

Passing Criteria

The panel rubric divides the presentation score equally across four areas: strategy articulation, design vocabulary use, response to critique, and completeness of the system — 25% each. You must earn 75% overall to pass the presentation component.

The file-packaging component is pass/fail: every item on the delivery checklist must be present and correctly named. One missing or misnamed file is enough to require resubmission, so work through the checklist methodically rather than skimming it.