brief-creative

Brief creative work

Turn a marketing decision into a production brief that a designer, developer, photographer, or video creator can execute without guessing.

Define the communication job

Establish:

• target audience and viewing context;
• action or belief the asset must create;
• one message hierarchy;
• product mechanism and proof to make visible;
• destination and campaign promise;
• format, placement, dimensions, duration, language, and accessibility constraints;
• available source assets and factual restrictions.

Ask only when a missing decision would materially change the concept. Label reasonable assumptions.

Choose one concept

Express the concept as a concrete relationship between message, product evidence, and form. A concept is not a mood-board adjective. Explain why the chosen form makes the claim easier to understand or believe.

Prefer:

• product behavior, demonstration, comparison, or artifact as evidence;
• one dominant idea and deliberate hierarchy;
• native composition for the destination;
• readable type, useful contrast, captions, and reduced-motion alternatives;
• modular production that supports the required variants.

Reject arbitrary gradients, stock symbolism, decorative dashboards, fake UI, fabricated metrics, and visual novelty disconnected from the message.

Specify the production

Deliver:

1. communication job and audience moment;
2. single concept and why it works;
3. frame, section, shot, or scene sequence;
4. exact copy hierarchy and required product evidence;
5. art direction: composition, imagery, typography behavior, color roles, and motion;
6. asset inventory, source-of-truth files, and production constraints;
7. variant matrix for formats that genuinely need different composition;
8. accessibility and localization requirements;
9. acceptance criteria and rejection conditions.

For a landing page, specify scan order, sections, proof placement, objection handling, and responsive behavior. For video, specify hook, beat timing, visual proof, captions, audio role, CTA, and end state. For product previews, distinguish representative mockups from shipped functionality.