Every review stage has a different job
An early concept review asks whether the direction can solve the brief. An execution review asks whether the chosen direction works across the required deliverables. A final review checks accuracy, consistency, and production readiness.
When a final review reopens the concept, rework expands. Name the stage before reviewers open the work.
Review in a useful order
Start with the brief, then move toward execution. A polished detail does not matter if the concept misses the audience or the asset has the wrong job.
- Objective: Does the work support the reason it exists?
- Audience and message: Will the intended person understand the right thing?
- Concept: Is the central idea strong enough to continue?
- Execution: Does the idea work across the actual deliverables?
- Production: Are specs, claims, source assets, and required details correct?
- Polish: What improves craft without reopening settled direction?
Turn reactions into decisions
“Make it pop” communicates a reaction and leaves the maker to diagnose the problem. “The headline blends into the product copy, so the new launch message is easy to miss” gives the team an observation connected to the brief.
Label the comment. If it is a required change, explain why. If it is a question, leave room for an answer. A preference should stay a preference.
Give the team one review
Collect feedback from required reviewers, resolve conflicts, and send one decision back to the team. A designer should not have to choose between three stakeholder comments that point in different directions.
One person should own the final call. That person can seek input without outsourcing the decision to the creative team.
Close the round
End each review with approved, revise, or stop. List the changes that belong in the next version, the owner of any open information, and the next decision date.
Use the brief as the shared context for the review. Keep proofing, comments, approvals, and version control in the review tools the team already uses.