Process Documentation and Campaign Defense

Process Documentation and Campaign Defense

The final stage of your capstone campaign is also the most professional: you must clearly explain what you made, why you made it that way, and how you got there. Employers and clients routinely ask designers to defend their choices, and this lesson prepares you to do exactly that.

Writing Your Process Document

A process document is not a list of steps you followed. It is a written argument that connects your creative decisions to your campaign goals. Using the instructor-supplied outline, your document must reach at least 800 words and include four required sections.

Design rationale explains why each deliverable looks the way it does. Discuss typeface selection, color palette, grid structure, and imagery choices in terms of the audience and message — not personal preference. For example, "I chose a high-contrast sans-serif headline because the target audience reads on mobile devices at small sizes" is stronger than "I liked the look."

Software workflow decisions describe the tools and techniques you used inside Adobe applications. Name specific features: paragraph styles in InDesign, Smart Objects in Photoshop, component states in Illustrator, export presets, and so on. Explain why a particular workflow saved time or protected print quality.

Revision cycles are documented proof that your work improved through feedback. You must include at least two complete cycles, each showing a before screenshot, a summary of the feedback received, and an after screenshot with a brief explanation of what changed and why. Label screenshots clearly with filenames and dates.

Self-assessment is a closing paragraph in which you honestly evaluate your own strengths, weaknesses, and what you would do differently with more time. Reviewers value candor here; it demonstrates professional maturity.

After drafting, exchange documents with a peer who uses the provided checklist to verify that every section is present and clear before you submit.

Packaging Your Deliverable Files

A campaign is only useful if another designer or print vendor can open every file without broken links or missing fonts. InDesign's Package function collects all linked graphics and fonts into one folder automatically — use it for every InDesign document in your project.

Organize your submission inside a single root folder named with your last name, first name, and project title (for example, `Rodriguez_Ana_BrandCampaign`). Inside that root folder, create four sub-folders:

• Fonts — copies of all typeface files used across the project
• Links — all placed images, logos, and vector assets
• Exports — press-ready PDFs, web-optimized JPEGs or PNGs, and any other final output files
• Working Files — native InDesign, Photoshop, and Illustrator source files

Run a final preflight check in InDesign before you close the files. Zero errors is the target. Resolve any missing-link or overset-text warnings before packaging.

Compress the entire root folder into a single ZIP archive and upload it to the course LMS. Also upload a plain-text file named `file_manifest.txt` that lists every asset, its file format, and its intended use — one asset per line. This manifest allows an instructor or future employer to audit your package quickly.

Presenting and Defending Your Work

Your formal defense runs 10 to 15 minutes before a review panel. Prepare a slide deck of no more than 10 slides. A logical structure is: one title/overview slide, one slide per major deliverable (usually four to six), and one lessons-learned slide.

For each deliverable slide, show the final piece and speak to three points: the strategic goal it served, the key design decisions you made, and what changed between your first draft and the final version. Use precise software terminology — say "applied a drop shadow via Photoshop's Layer Style dialog" rather than "added an effect."

Panelists will ask at least one spontaneous question. Common questions include: "Why did you choose that typeface over a different option?", "How would you adjust this layout for a different screen size?", or "What would you change if the client's brand color changed?" Pause, think, and answer directly. It is acceptable to say "I would need to test that" as long as you explain how you would test it.

Mock Defense Rehearsal

Before the formal panel, present your full deck to a partner. Your partner uses the panel rubric to time your presentation, note unclear explanations, flag incorrect software terminology, and ask one spontaneous question. Record the written feedback on the feedback sheet, and both of you sign it. This signed sheet is a gate requirement: you cannot proceed to the formal defense without it. Use the feedback to revise any weak slides or talking points.

Safety and Professional Responsibility

Digital media work carries intellectual-property obligations. Every image, font, and audio asset in your package must be either your original work, properly licensed, or cleared under a Creative Commons license that permits commercial use. Include license documentation in your manifest file for any third-party asset. Submitting unlicensed work in a professional deliverable can expose you and a future employer to legal liability — treat copyright compliance the same way a tradesperson treats a safety checklist.