Lesson 5 of 7 in Create Work That Fits the Strategy
- 1Move from a plan task to Create
- 2Start a New Asset Run and understand the cost boundary
- 3Review concepts before rendering visuals
- 4Use brand voice, typography, logos, and reusable assets
- 5Review, vote, reject, and explain a creative direction
- 6Refine in the design editor
- 7Save, keep the content-task connection, and ship
Why this matters
Your judgment is an input to the system. Every image you like or pass, and every reason you give, steers what later runs treat as good for this brand, with recent passes counting most. It is a small version of the Learn step working inside Execute. Votes publish nothing, and human judgment still decides what ships. But careless or missing votes teach the wrong lesson, and the next run pays for it in more drafts to reject.
When to use it
Once images have rendered: on the finished run's page, or in the "Review" tab in Create, which gathers generated content still waiting for a decision. Vote while the run is fresh rather than saving it all for the end.
Before you start
- Rendered images from a run you checked at the concept stage (Review concepts before rendering visuals).
- The plan task and the Brand Kit in mind, so each vote is a judgment against the brief and the brand, not personal taste.
Do this
- 1Open the run from "Recent Asset Runs" (or "View Asset Run" when a run completes), or open the "Review" tab, where the same decision is labelled "Approve" and "Reject".
- 2Read what the system checked before you vote. An image may show a vision review score (0 to 10) and flags such as "Below the bar", "Check headline", or "Logo not applied". Treat them as prompts to look closely, not as verdicts.
- 3Vote with the thumbs: up marks the image "Liked", down marks it "Passed". Anything you leave alone stays "Not rated". A carousel is voted on as one set.
- 4When you pass, the "Not this one" dialog asks for a reason: "Off brand", "Weak composition", "Wrong colours", "Text problem", or "Something else". Add a note under "What would make it right?" when the reason alone does not say enough; the next run reads it.
- 5Before passing a single image, check its "Alternates" if any are listed. "Use this" swaps in another candidate from the same render and re-adds your headline and logo.
- 6Leave "Not rated" on anything you are unsure about rather than voting blind. Uncertain votes only add noise.
What you should see
"Liked" or "Passed" on each image you voted on, with the pass reason (and your note) shown under passed images. The "Review" tab thins out as you decide; when nothing is left it shows "All caught up".
How to judge it
Over the next few runs, fewer images need passing for the reasons you named. The pass dialog notes that recent passes count most and older ones fade, so judge the trend across several runs, not one.
What it does not mean
- A like is not approval to publish. Nothing ships from a vote; shipping is covered in Save, keep the content-task connection, and ship.
- "Passed" is not a permanent ban. It means not this time, and older passes fade.
- A vision review score is the system's check of the render, not a prediction of performance.
Try it in Signal & Science
Open Create, open your latest run from Recent Asset Runs, and vote on each rendered image.
Open in Signal & Science