Creative Design and Media Production

01Purpose and scope

• This manual supports the course Creative Design and Media Production. It describes how practitioners move a creative brief through concept, production, review and delivery for print, screen, audio and social channels, and it is written as a working reference for people who make these pieces and the colleagues who approve them.
• The scope covers graphic design, illustration, layout, photo and video editing, motion graphics, podcast and audio editing, and the packaging of files for distribution. It does not cover advertising law, broadcast licensing, or the clinical, financial or legal claims that a piece may make. Where a project touches those areas, the work should go to a qualified reviewer, and the manual does not replace that judgment.
• Practice varies with the setting. A freelance designer working alone makes most decisions directly, while a production team at a media company splits them across writers, art directors, editors, sound engineers and legal reviewers. The steps below assume a small or mid-sized team and note where a larger organization would add gates or sign-offs.

02Core principles

• The brief is the working contract. A useful brief states the audience, the single main message, the channel, the required formats, the deadline, the approved assets and the decision maker. When a brief is vague, most later revisions trace back to that vagueness, so the first job is to make the brief specific enough that two people would produce roughly the same plan from it.
• Constraints shape good work. File size limits, color gamut of a target screen, safe margins for print trim, caption length for a short video, and the reading level of a public notice all narrow the options. Treat these as design inputs rather than obstacles, and record them early so they are not discovered during final review.
• Accessibility is part of the product. Text contrast, alternative text for images, captions and transcripts for video and audio, and logical reading order in documents are standard expectations. The Web Content Accessibility Guidelines (WCAG) 2.2, published by the W3C, are the most widely referenced standard for digital content, and they are a sensible baseline even for print files that will also be posted online.
• Rights and consent come before publication. Every font, photograph, music track, stock asset and recognizable person in a piece needs a documented license or release. Copyright and privacy rules differ by country and sometimes by state, so the authoritative source is the relevant national or regional law and the licensor's terms, and a qualified rights professional should confirm anything unusual.

03Planning and preparation

• Start with a scope document that lists deliverables by name, size and format. A campaign might include a 1080 by 1350 pixel social post, a 16 by 9 video cut, a 30 second audio spot and a printed poster at a fixed trim size. Listing each item prevents the common situation where the team finishes the hero image and discovers that nobody planned the vertical version.
• Build a schedule backward from the publication date. Allow time for concept approval, asset capture or sourcing, production, at least two review rounds, technical checks and delivery. Production schedules often slip most at review, so it helps to set a fixed number of review rounds and to state that additional rounds will be scheduled as change requests.
• Confirm roles before work begins. A typical set includes a project owner who approves scope and budget, a creative lead who makes visual decisions, production staff who build the files, a reviewer who checks accuracy and brand use, and a technical checker who verifies file specifications. One person can hold several roles on a small project, but the roles should still be named.
• Choose tools by the output, not by habit. Vector illustration software suits logos and icons that must scale. Raster editors handle photo retouching. A nonlinear video editor and a digital audio workstation cover most moving image and sound work. Tool choice also determines which file formats the team can hand off, so check what the printer, platform or client accepts before building the file.
• Set up a project folder structure, naming convention and asset log at the start. Keep source files, exports, licenses and client feedback in separate locations. This small step saves hours when a version from three weeks earlier needs to be recovered.

04Recommended workflow

1. 1
   : Write the brief with the audience, message, channel, formats, constraints, deadline and approver named. Get the approver to sign off on the brief itself before any concepts are made, because that sign-off becomes the reference point for later disagreements.
2. 2
   : Develop two or three concepts at low fidelity. Use thumbnails, rough layouts, storyboards or a short audio sketch. Low fidelity keeps the discussion on structure and message rather than on color or typeface preferences.
3. 3
   : Select one direction and produce a refined prototype. For a video, this may be a rough cut with temporary music and placeholder graphics. For print, it may be a layout with real type and image placement at actual size. Test the prototype against the brief before spending production time on it.
4. 4
   : Capture or source the assets and log their licenses. Photographs, footage, illustrations, fonts and music each need a record with the source, license type, permitted uses and expiration if any. Replace placeholders with final assets as early as possible, because mismatched sizes and resolutions are expensive to correct late.
5. 5
   : Produce the full set of deliverables from the master files. Build each format from a single source so that a text change propagates correctly. Export to the required formats, such as a press PDF with embedded fonts and a CMYK profile for print, an H.264 or H.265 export for video, and a WAV or MP3 at the specified bitrate for audio, following the platform or client specification.
6. 6
   : Run the review cycle with clear instructions. Ask reviewers to comment on the brief, not on personal taste. Collect feedback in one place, sort it into required changes and optional suggestions, and record decisions that close each comment.
7. 7
   : Perform technical checks, then deliver and archive. Check fonts, links, color, captions, loudness, trim and safe margins against the specification. Deliver the files with a short readme that lists formats, dimensions, durations and any known limits, and archive the master project with its asset log.

05Quality checks, risk controls and compliance

• Quality checks work best as a list tied to the specification rather than to memory. For print, check trim, bleed, safe zones, image resolution at final size, ink coverage, overprint settings and whether text converted to outlines has been reviewed for errors. For video, check frame rate, aspect ratio, title safe area, caption timing and file integrity by playing the full export on the target device.
• Audio requires loudness measurement rather than only listening. Many platforms and broadcasters specify integrated loudness and true peak limits measured under ITU-R BS.1770, and the target differs by destination. Confirm the target with the receiving platform, since a podcast host, a streaming service and a broadcaster may each set different values.
• Risk controls cover factual accuracy, brand misuse, sensitive imagery and claims. A reviewer with subject knowledge should check any statistic, health or safety instruction, financial figure or legal statement before release. Where a piece makes a claim that could affect someone's money, health or legal position, the guidance here does not replace qualified professional judgment, approved procedures or any required authorization.
• Compliance depends on jurisdiction and sector. Advertising disclosures, data protection rules for collecting audience information, election or political content rules, and accessibility requirements for public bodies all vary by location. Point the team to the current authoritative source in the relevant country or region, and have the organization's legal or compliance function confirm the final version when the rules are uncertain.
• Recording approvals is part of compliance. Keep a dated approval log in the project record showing who approved each stage and which version was approved. This is a practical record, and it also protects the team if a question about a published piece arises later.

06Collaboration and documentation

• Keep one owner for the feedback loop. Multiple stakeholders sending comments by email, chat and in person produce conflicting instructions. A shared review tool with a single comment thread per deliverable, or a document with numbered comments, lets the creative lead see what has been asked and what has been resolved.
• Hand off with documentation, not only with files. A handoff note should state which version is final, what fonts and assets are required, what was changed from the previous round, and what open questions remain. Designers who inherit a project with no notes often spend the first day reconstructing decisions that were already made.
• Respect the creative role of reviewers without giving them control of every choice. Reviewers are best placed to judge accuracy, brand consistency and audience fit. Creative choices such as composition, pacing and typeface selection are usually better made by the lead, who is accountable for the look. Define this split in the planning stage so disputes do not arise mid-project.
• Document the master source files and their dependencies. Linked images, missing fonts and external plug-ins are the most common causes of files that open correctly on one machine and fail on another. Embed or package fonts and media where the tool allows, and store a copy of the project with its linked assets.

07Measures and continuous improvement

• Measure delivery and quality with simple indicators. Useful ones include on-time delivery rate against the agreed schedule, number of review rounds needed to reach approval, count of technical defects found at final check, accessibility checks passed before release, and rework hours as a share of total production time. Track these per project so patterns become visible.
• Audience response can inform later work, but treat it with care. Engagement numbers, completion rates for videos and downloads of a poster depend on the channel, the audience and factors outside the design. Use them as prompts for investigation rather than as proof that a design choice worked, and record the context alongside the numbers.
• Review each project after delivery with a short retrospective. Ask what the brief missed, which constraint surprised the team, which tool or file format caused trouble and which review step added the most value. Turn the answers into updates to the brief template, the checklist and the asset log.
• Trade-offs are unavoidable. Faster delivery often means fewer concept rounds or fewer test passes. Richer media, such as high resolution video or interactive elements, increases file size and load time for some audiences and may limit access on older devices. Name these trade-offs in the planning stage so the approver chooses them knowingly.

08Common mistakes and how to prevent them

• Starting production before the brief is approved is the most frequent error. The team builds polished work against assumptions that the approver never shared, and the revision cost lands at the worst point in the schedule. Prevent it by making brief approval a gate that production cannot begin without.
• Designing only for the screen where the piece is first viewed causes problems later. A poster that reads well on a monitor may lose fine type at print size, and a video with critical text near the edges may be cropped on a phone. Preview each deliverable at its real size and on its real device before final approval.
• Using unlicensed or unclear assets is a serious and avoidable risk. A font included with a computer may not cover commercial embedding, and a stock image may forbid use in merchandise. Log each asset's license when it is added, not when the piece is about to publish.
• Skipping the technical check because the piece looks right is another common mistake. Missing bleed, incorrect color profiles, low audio loudness and absent captions all pass a casual look. Use the checklist for every deliverable, including small resizes that are easy to overlook.
• Letting review comments pile up in several places leads to missed changes. Consolidate feedback into one list, assign each item an owner, and confirm closure with the reviewer before the next export.

09Practical checklist

• Confirm the brief is written and approved by the named decision maker before concept work starts.
• List every deliverable with its dimensions, duration, file format and destination.
• Build a schedule backward from the publication date with a fixed number of review rounds.
• Log the source and license of every font, image, clip, music track and release.
• Build all formats from a single master file and keep linked assets packaged with it.
• Check print files for trim, bleed, safe zones, color profile and image resolution at final size.
• Check video for frame rate, aspect ratio, caption timing and playback on the target device.
• Measure audio loudness and true peak against the receiving platform's stated target.
• Route factual, health, financial and legal content to a qualified reviewer before release.
• Record each approval with the version approved, the approver and the date held in the project file.
• Hold a short retrospective after delivery and update the brief template and checklist from it.

★Learning sources

• Micro Degree: Creative Design and Media Production
• Micro Degree: Leadership and Team Management
• Micro Degree: Business Intelligence Management
• Micro Degree: ESG Advisory Services