Show the reference. Name the reason. Request the decision.
Give references a job to do.
Original practical guidance by Super. The sharing mechanics below are grounded in current Figma and Miro documentation checked October 5, 2026; the creative method is editorial advice, not a measured performance claim.
A useful team handoff contains: a concise campaign intention, selected references with explicit annotations, a few constraints, and a review question with an owner. Separate the creative direction from the platform used to share it. A folder full of images leaves the interpretation to each person.
Explain the visual choice
Name the specific property: lighting, crop, hierarchy, texture, pace or composition. State what the team should transfer to this campaign and what is only incidental to the reference. Use references you have the right to share.
Annotation example: “Keep the generous negative space; do not reproduce this product styling.” This is a sample instruction, not a rule for every campaign.
Choose the review surface
Figma documents prototype presentation links and comments in presentation view. Its sharing guide cautions that Starter-plan viewers may still open the source file from that view. Review access rather than assuming a presentation link hides everything.
Miro frames organize board content for navigation and presentation. The official guide documents arranging frames and exporting them. It notes that sidebar frame reordering is unavailable on mobile and touch devices; plan sequencing where the controls are available.
Share decisions about the look, not just a collection of images.
A campaign's visual direction explains what the audience should experience and the choices that create that experience. References help make those choices visible, but the team still needs to know what to borrow, what to avoid and which constraints cannot change. A folder of attractive pictures leaves every maker to infer a different campaign. Pair each important reference with a reason and a practical consequence.
Three audiences use the direction differently. Decision-makers need to understand the intended relationship between the creative idea and the campaign objective. Makers need rules they can apply to actual assets. Production partners need information about what must be sourced, staged, built or captured. One shared direction can serve all three when its overview, examples and production notes remain connected. It need not force everyone through the same presentation each time they have a question.
A deck can be useful for the first conversation. The problem is treating its exported copy as the only working source while production changes elsewhere. A shared board, design file or maintained document can preserve references and current decisions; a presentation can summarize them. Choose the container that helps the team navigate and maintain the material. A board is not automatically superior if no one owns it.
Direction often deteriorates through four routes: unexplained references; instructions that different people interpret differently; production decisions that alter the idea without discussion; and outdated copies whose status is unclear. Solve those problems with reasons, concrete examples, constraints and ownership. Software can hold the records, but it cannot decide whether a new execution serves the original creative purpose.
Build a seven-part visual direction package.
The idea in one line: State the audience experience and its relationship to the campaign. Avoid relying on adjectives such as premium, warm or bold. Explain what the audience should notice or feel and which choice makes that happen. The line should guide production decisions without pretending every visual detail has already been resolved.
Annotated references: Select images because they demonstrate a choice. Identify composition, lighting, texture, gesture, scale or framing. Explain which feature to borrow and which is irrelevant. Retain provenance and rights status. A reference can support discussion without granting permission to reuse the image publicly or reproduce a protected design.
Palette and typography: Distinguish actual brand constraints from campaign proposals. Specify usable colors, contrast expectations and type roles with examples at relevant sizes. A color swatch without an application rule leaves the team guessing. Check the combination in the real channel, including small text, captions and overlay treatments.
Do and avoid pairs: Show an acceptable execution beside a misleading one and explain the difference. For example, a natural product interaction can be preferred over a staged arrangement that implies a different audience. The pair should reveal the rule, not merely communicate that the director likes one image more.
Casting, styling and location: Translate the direction into production requirements. Identify representation, wardrobe, props, settings, access and practical constraints relevant to the idea. Record what is established, proposed or unresolved. An inspirational location photo does not prove the team can shoot there.
Key frames or storyboard: Show important moments, focal relationships and sequence. Separate a composition proposal from a final captured shot. Give makers enough information to understand intent while preserving room for production expertise. Do not turn an early sketch into an accidental promise of technical feasibility.
Channel adaptations: Explain how the direction survives different aspect ratios, placements and viewing conditions. Identify safe areas, text placement, crops, captions and the relationship between still and moving assets. A landscape reference does not establish that a vertical crop retains the focal subject or message.
Move from brief to production in eight steps.
Agree the brief and idea. Clarify audience, purpose, required deliverables and decision owner. Write the one-line creative intent in language the team can apply.
Choose a maintained container. Establish where the current source lives, how makers navigate it and how presentation or export copies relate to it.
Curate and explain references. Retain provenance and annotate the feature each reference demonstrates. Remove images that add atmosphere without a useful decision.
Write practical rules. Define palette, type, composition and do/avoid examples. Check them against actual brand requirements rather than inventing new permanent rules for a temporary campaign.
Add production context. Connect casting, styling, props, locations, shot needs and constraints to the intended look. Assign unresolved feasibility questions to owners.
Adapt by channel. Test representative crops and layouts. Carry the same idea into the required formats without assuming identical treatment is always appropriate.
Run a decision-focused kickoff. Explain the idea, walk through examples and let makers test their understanding against likely production choices.
Maintain checkpoints and change records. Review actual work against the current direction, identify drift and record approved changes with their consequences.
Run a kickoff that makes the handoff understandable.
Invite the people who approve the idea, the makers who interpret it and the production contributors whose decisions affect feasibility. Others can receive the resulting record without every person attending every discussion. The useful criterion is whether the necessary decisions can be made and their consequences understood.
Begin with the brief and one-line idea. Show why the references belong together, then explain a few important rules through do/avoid pairs. Walk through key frames and a representative channel adaptation. Bring unresolved access, cost or production questions into the conversation rather than hiding them behind the moodboard. Label a proposed treatment as proposed until the owner can decide.
Ask concrete questions. What would a maker do differently after seeing this direction? Which reference could be interpreted in conflicting ways? Where does the production plan make the look difficult? What would count as a successful adaptation in a narrow format? Which parts are fixed and which can change? A meeting where everyone says the board looks good may still leave those questions unanswered.
After the kickoff, send the current source link, the approved version or state, decisions made, open questions, responsible owners and next checkpoint. Include the exact export when someone needs a portable copy, and explain its relationship to the maintained source. Do not describe an unresolved question as an approval simply because the meeting ended.
Remote teams need an access check and a route for people who cannot attend live. A readable summary and recorded decisions can be more useful than asking everyone to replay a long presentation. If you record a walkthrough, verify permissions, playback and whether it still describes the current direction after changes. No recording capability is assumed merely because a tool supports presentations.
Keep the direction current and classify drift.
Name one owner for the current direction and identify where its authoritative version lives. Individual makers can create drafts, but a new draft should not silently redefine the campaign's rules. Record a significant change with its reason, approver and affected deliverables. A maintained source can still retain useful earlier versions without leaving people unsure which to use.
Three checkpoints can help: an early representative execution; a meaningful production or rough-cut review; and a final cross-channel release check. They are points for decisions, not an inflexible meeting quota. Choose timing that exposes a misunderstanding while the team can still change the work. Looking at only a finished asset can make correction unnecessarily expensive.
Classify drift before responding. Interpretation drift happens when someone understood the instruction differently; improve the example or explanation. Constraint drift happens when access, budget, equipment or timing changes the feasible treatment; decide which creative priority to preserve. Intentional creative development proposes a better execution; review it against the purpose rather than rejecting it because it differs from the sketch. Accidental inconsistency often comes from outdated source or missing rules; correct the record and affected assets.
Review beside the relevant references and rules. A note such as make it warmer is incomplete if it could mean color temperature, human interaction or a less formal composition. State the observable issue and intended result. When feedback conflicts, the decision owner should reconcile it before asking a maker to execute both instructions.
A fictional spring campaign for a ceramics studio.
Consider a fictional ceramics studio preparing a campaign for an everyday tableware collection. The idea is that the pieces belong in ordinary shared moments rather than a display cabinet. The campaign needs a short moving asset, a landscape website image, vertical social variants and a small set of product details. This is an illustrative scenario, not a report of measured campaign results.
The creative director writes the intent: show the collection through relaxed interaction and tactile detail, with the object useful rather than isolated as a luxury ornament. The direction package separates the studio's existing logo and type constraints from proposed campaign colors. It uses references for hand-to-object scale, changing daylight and table texture. Each annotation states what matters; an example's particular furniture is not automatically a required purchase.
A do/avoid pair contrasts a naturally used table with a symmetrical arrangement in which no person appears to interact with the objects. The rule is about lived use and focal relationships, not a blanket ban on symmetry. A second pair shows readable copy placed beside the action versus a crop that pushes text across a hand and obscures the product. These examples help the designer and photographer make related choices.
The production layer names the required setting, props, casting considerations, access and unresolved materials. The team needs a place where daylight can be controlled and where close-ups can be captured safely. A source photo of a kitchen establishes a desired spatial quality, not confirmed access. The producer checks the real location and notes which shots may need another arrangement.
At kickoff, the photographer proposes using a different table surface that is locally available. The director compares it with the tactile intent and approves a test, rather than requiring literal reproduction of the reference. The designer asks how the visual idea translates to a vertical asset. The team sketches a crop that keeps the hand, product and copy region intact. Those decisions become part of the current package.
At the early execution checkpoint, the team discovers that the props dominate the object. This is interpretation drift: the reference's surrounding texture had been treated as the subject. The director clarifies the focal hierarchy and annotates the example more precisely. At a later checkpoint, a location access change reduces the possible camera distance. This is constraint drift. The team chooses a tighter interaction shot that retains the idea and adjusts the website composition deliberately.
Before release, the director and designer compare the landscape and vertical variants side by side. They check object recognition, copy legibility, type usage and the relationship to the campaign intent. Approval identifies the actual versions. The maintained source records why the framing changed, so a later adaptation does not reintroduce the discarded composition.
Compare seven tools by the decisions they carry.
Use one direction package, one reviewer invitation and one production change as the common test. The following roles are documented or practical workflow choices rather than a universal ranking. No hands-on vendor speed measurement or numerical trust score is claimed.
Tool
Useful direction workflow
What to verify
Storyflow
Assemble planning context and visual direction on a shared board.
Current source handling, permissions and access route; a visual plan does not establish approval, production feasibility or publication.
Figma
Maintain precise visual layouts, variants and linked design context.
Actual viewer and prototype permissions on your plan. A presentation link is not a blanket guarantee that other source material is inaccessible.
Miro
Organize a spatial direction board and facilitate a review or workshop.
Frames, navigation, export choices and mobile access; a board's presentation order and its production source need to remain understandable.
Frontify
Govern brand guidelines and an asset library across contributors.
The scope of asset sharing, protection, licenses and ongoing access. A brand system and a campaign-specific direction solve different tasks.
Canva
Create visual treatments and reusable channel designs.
Design approval roles, current export fidelity and asset licensing; clarify where production notes and change decisions live.
Pitch
Present an agreed direction and distribute a slide narrative.
Link access, export behavior and the relationship between a slide copy and the maintained production source.
Milanote
Curate references and connect creative context on a visual board.
Reviewer access, source provenance, ongoing maintenance and the handoff into production files.
Figma's sharing guidance distinguishes files and prototypes; test the actual permission route rather than promising source privacy from the appearance of a link. Miro's Frames guidance explains organization and presentation or export uses. Frontify's sharing documentation describes different internal and external sharing routes. Those documented controls do not independently establish that your particular campaign references are licensed.
Choose a design environment when exact layouts and variants are the difficult part. Choose a spatial planning board when source context and relationships are hard to navigate. Choose brand governance when many people need a maintained asset and guideline system. A presentation tool can be useful for the kickoff while another environment owns production decisions. The combination works when responsibilities are explicit.
Read costs and access in the context of the team.
A solo director may need a familiar source container and a creation tool. A five-person team may need a few editing seats, occasional reviewers, exports and a specialist asset service. Viewer, guest, comment and editor roles vary by vendor and plan; five participants do not always imply five equivalent paid seats. Test the needed roles and current billing terms before buying.
Include recurring seats, premium assets, storage, AI allowances, brand controls, export requirements and the time spent maintaining duplicate copies. A sophisticated library can be worthwhile for a long-lived multi-team brand operation while adding unnecessary work to a small temporary campaign. Conversely, a cheap board may be insufficient when licenses, access restrictions or a large asset archive need governance.
Storyflow's current pricing FAQ should guide obtainable access. Paid early access, invited collaboration and a future standalone free plan are different routes. Do not infer current free creator access from a broad marketing statement. Confirm what happens to source, links and exports when a subscription changes or collaborators leave.
Scale the workflow by decision complexity rather than an arbitrary headcount. A small remote team with several production partners can need careful source control. A larger team using an established brand library may only need a compact campaign-specific package. The useful stack makes the current decisions easy to locate and the necessary people able to act on them.
Avoid eight failures and reuse a direction template.
The first failure is direction expressed only through adjectives. The second is references without reasons. The third is treating an exported deck as the only current copy. The fourth is omitting do/avoid examples, which leaves boundaries implicit. The fifth is forgetting the production layer. The sixth is ignoring the required channel set. The seventh is reviewing work without the rules or references beside it. The eighth is treating every change as the same kind of drift.
A reusable direction record can contain these fields:
Campaign title, version and decision owner.
Audience, campaign purpose and one-line creative intent.
Approved constraints and open questions.
Annotated references with provenance and use boundaries.
Palette, typography and composition application rules.
Do/avoid pairs with an explanation of the difference.
Casting, styling, props, location and production dependencies.
Key frames or storyboard with status and purpose.
Channel variants, crops, copy regions and accessibility needs.
Review questions, checkpoint owners and decision evidence.
Change record and affected deliverables.
Current source link and relationship to portable exports.
Before kickoff, check that the idea is clear, references have reasons, the production constraints are visible, representative channel treatments exist and attendees can open the material. Identify what requires a decision during the meeting. Do not present an annotated research reference as an approved licensed production asset.
Practical questions about visual direction.
How should a creative director share it?
Give the team a maintained source containing the idea, explained references, usable rules, production context and channel adaptations. Use a kickoff to resolve interpretation and assign decisions.
How is it different from a moodboard?
A moodboard can suggest a visual territory. Direction explains what the team should do with it, where the boundaries lie and how the idea survives actual production and release.
What belongs in a direction deck?
The idea, annotated examples, constraints and representative execution. Link it to the maintained source and production notes when the deck is a presentation copy.
How many references are enough?
Enough to explain the relevant choices without repeating the same mood. There is no universal image quota. Remove images that add no actionable distinction.
What should happen at kickoff?
Review intent, examples, production questions and adaptations. Test what makers understand, reconcile open decisions and send the current source with owners and checkpoints.
What if execution drifts?
Identify whether the issue is interpretation, constraint, intentional development or outdated source. Choose the correction that preserves the purpose and record the resulting decision.
Should the client see the board?
Share the appropriate current material with a tested permission route. Separate internal deliberation from approved presentation content and agree what decision the client is being asked to make.
Figma or Miro?
Compare precise design variants with spatial planning and workshop needs. Test the actual file, comment, export and viewer permissions for the intended contributors.
Does Frontify replace a moodboard?
A brand library and guideline system can supply approved rules and assets. Campaign direction may still need a distinct idea, annotated research and production decisions.
Can Canva hold the direction?
It can support treatments and designed examples. Establish where contextual rules, production notes, approvals and changes are maintained, then test actual reviewer roles.
Can AI generate references?
Where supported, it can propose images or organize a draft. People must assess relevance, brand fit, source handling and permitted use. Generated imagery does not prove feasibility or permission for every downstream use.
Creative director or art director?
Responsibilities vary by team. Explicitly identify who owns the overarching creative intent, who develops its visual execution and who approves a change; avoid relying on job titles alone.
Is Storyflow free?
Verify current standalone and invited access in the pricing FAQ. An upcoming free plan is not currently obtainable access.
How do remote teams keep aligned?
Maintain a navigable source, tested permissions, clear decision records and representative checkpoints. Supply a readable summary for asynchronous contributors rather than relying only on a live call.
What does this annotation board do?
Fabric provides real editable image and annotation objects, while jsPDF exports a board and review notes. PNG gives a portable image and JSON restores the editable source. The board does not host collaboration, infer design quality, verify rights or approve production. Inspect the exported file before sharing; its PDF text font supports the tested Latin and extended-Latin material rather than every writing system.
Choose the specialist route when the handoff needs it
A direction package can be shared in several ways, but a common board does not complete every adjacent job. Choose the review, presentation and production route around the actual decision the recipient must make. Current official documentation supports the following distinctions; test access and the relevant plan rather than assuming all sharing features are equivalent.
A recorded walkthrough is different from a decision record
When colleagues cannot attend kickoff, a narrated walkthrough can explain the relationship between references, rules and intended execution. Miro's Talktrack guide describes recording a walkthrough of a board or other screen content, with platform and role requirements. Transcript and summary capabilities are plan-dependent.
Use a short tour to explain the important choices, then retain an accessible written summary and the current source link. Test actual playback and permission from the recipient's route. Identify which source version the tour explains; a recording can become stale as the board changes. A recording is a presentation aid, while the decision log records what was accepted and why. Neither should be mistaken for the other.
Asset proofing requires more than a board comment
If reviewers must mark an exact image area, video frame or document page and make a formal decision on a named version, evaluate a dedicated proofing route. Filestage and Ziflow describe creative review and approval workflows. Compare the actual file type, reviewer identity, decision permissions, revised-version behavior and retained evidence on the plan you would buy.
Keep the creative direction linked to the proof, but use the appropriate asset review record to identify what was accepted. A comment resolved on a reference board does not establish that the final cut or layout has been approved. Test one revision and export before promising a formal audit record to a client.
Presentation engagement is a separate question
If the director needs to know how a presentation link is used, Pitch's analytics guide describes engagement analytics for analytics links. Check current plan access, configuration and the information actually recorded. Link access and engagement tracking are different features.
Do not infer agreement from a visit or time spent on a slide. A forwarded link or shared device can also complicate identity. Ask the authorized reviewer for an explicit decision on the version and scope; use engagement information only for the purpose it actually supports.
Preserve production setups and rejected alternatives
Add a setup-oriented shot list when the direction will be produced through a shoot. Useful fields include setup or location, shot identifier, intended subject and action, framing, lighting rule, deliverable or channel, priority, required resources and unresolved dependency. Grouping by setup helps the producer inspect feasibility without losing the creative purpose of each shot. A key-frame sketch expresses an important moment; it is not the complete production sequence.
Also keep a small rejected-alternatives record: proposed direction, reason it was set aside, relevant evidence, decision owner, date and any condition that would justify reconsideration. This prevents a later contributor from reintroducing an attractive idea without knowing why it failed the brief. It should explain the decision rather than merely label an option bad.
Before kickoff, verify that these records are linked from the maintained direction, the producer has inspected the practical constraints, recipients can open the intended source, and the review dates have actual owners. The goal is a handoff someone can use, not a longer deck.
Put the instruction on the reference.
Upload a PNG, JPEG or WebP, add editable highlights and labels, and export an annotated board with a team review note. Actual Fabric.js canvas editing and jsPDF export; no AI judgment, remote collaboration or automatic approval.
Tap or click an object to select it. Drag to move; use corner handles to resize. Double-click a label to edit it. Keyboard controls below move selected objects precisely, including on mobile. Imported images are fitted inside the 1000 × 600 board, then remain editable. Overlapping objects are intentional layers.
Load the illustrative demo or add your own local images.
Empty board · no approval recorded
The local JSON includes embedded image data and your notes. The PDF contains a board page and text notes; the PNG contains only the visible board. These are exported files, not a hosted team review link. Nothing is automatically saved. Inputs and images stay in this browser; the tool does not contact an image or AI service. Browser memory and image size determine practical capacity.
Only this tool's validated JSON schema and allowed local image objects can be restored. External image URLs are rejected. Export only references you may distribute and inspect the files before sharing. The canvas contains manual annotations; it cannot verify brand fit, image rights or campaign approval.
Give the team a defined question and a decision owner. A useful response identifies the part of the reference, the reason for concern and the change requested.
Separate requirements from exploration
Mark what is fixed: brand constraints, deliverable format or a necessary message. Label explorations as options. A reference can inspire one property without requiring every part of it.
Ask for specific feedback
Ask whether the direction communicates the intended idea, where it conflicts with a stated constraint, and what the team needs to test. Opinions are easier to act on when attached to a particular feature and reason.
Record the decision elsewhere
This local board does not collect approvals or comments. Share the exported artifact through your team's chosen system, preserve the version being reviewed and record the final decision with its owner.
Update the reference and the reason together
When the visual changes, update the annotation that explains it. An old note on a new image can create an avoidable ambiguity. Review the exported board and notes together before sharing.
It can show a visual territory, but an explicit intention and annotations help the team understand which properties to use. This is editorial guidance rather than a claim that one workflow guarantees better results.
Can the board collect team feedback?
No. It is a local editor and exporter. Use a reviewed sharing surface such as your existing team board or prototype, with appropriate access, to collect feedback.
Can I use it on a phone?
The board scales to the viewport. Tap to select and use the position controls for precise changes. PNG, PDF and restorable JSON exports remain available; larger images may require more browser memory.
What is in the illustrative demo?
Locally drawn synthetic color and composition shapes with example annotations. They are not a real campaign, client approval or customer reference.