Preparing people to give useful feedback is part of preparing the work for review.
That responsibility belongs to whoever introduces the work. It might be the person standing in front of a room, speaking on a video call, or writing the email that accompanies a deck. In each case, someone needs to consider what reviewers will see and what they need to know.
Preparation includes the explanation, the materials, their order, and the equipment used to present them. A team can spend days refining a concept and leave those decisions until the last few minutes before the review. By then, the presentation may depend on context the reviewers do not have or on equipment nobody has checked.
Establish what the review needs to resolve
Imagine a team preparing a deck for a campaign concept review. The idea is developed enough to discuss, but the execution is still open. Reference images suggest the intended scale and tone. A short sequence shows how the proposed campaign would work. The team needs agreement on whether the concept communicates the message before developing a full treatment.
The people making the deck understand which decisions remain open. They know why each image was chosen and which questions remain unanswered. A reviewer seeing it for the first time may reasonably assume that everything on the page represents a proposal.
A photograph intended to suggest the relationship between a person and a large space also contains a particular location, wardrobe, and style of lighting. Without an explanation, any of those qualities might attract attention. One reviewer begins discussing the location. Another thinks the casting is wrong. A third imagines a different setting that would require a different approach to the concept.
The discussion can generate several assignments before anyone has addressed the question the team needed to resolve. People leave believing that progress has been made because there are notes to act on. Yet the next stage may still depend on a decision nobody made.
A short introduction can help establish the purpose of the review: the team is asking whether the idea communicates the intended message; the imagery illustrates scale and tone; casting and locations will be developed after the concept is agreed. That gives reviewers a way to interpret the material and identifies the decision they are being asked to make.
The request also needs to match the work. If the team needs a concept decision, the presentation must contain enough information to make one. Asking for approval while leaving a central part of the idea unexplained is likely to produce either hesitation or an agreement based on assumptions.
Make the materials support the explanation
An explanation may not be enough when the image suggests something else.
In the hypothetical deck, suppose the reference photograph is visually striking because of its location. A small caption explaining that it is only a reference for scale may not overcome the impression created by the image. The team needs to consider whether a different reference, a crop, or a simple drawing would communicate its intention more accurately.
A reference asks reviewers to imagine something the team has not made yet. Explain which parts represent the intended result. If every image needs a different qualification, reviewers may struggle to remember what they are supposed to retain and what they should ignore.
The level of finish matters too. A polished layout can make a provisional idea look settled. An unnecessarily rough presentation can make a developed choice look unresolved. Creative and production need to agree on how much development the review requires, then allow time to prepare it.
That may mean resolving one detail because the concept depends on it, while leaving others visibly open. If a performance style is essential to the idea, reviewers need a useful way to understand it. Calling it a later execution decision would leave them approving a concept whose effect they cannot yet judge.
Be prepared to revise the explanation or materials. If reviewers consistently need an explanation the team did not expect to give, that may reveal a weakness in the presentation or the concept. Their reaction provides information about what the materials actually communicate.
Prepare for live presentation or independent reading
A deck presented live can rely on a speaker. The presenter can explain a reference before showing it, pause at a decision, and answer a question before it becomes a misunderstanding. A page with very little text may work well because the spoken explanation supplies what is missing.
That same page can be ambiguous in an email attachment. The reader may open it halfway through, move quickly between options, or return to it after forgetting the accompanying message. If it is forwarded, the next person may receive only the file.
The version intended to circulate may therefore need a short opening explanation, captions beside references, and a clear statement of the decision being requested. Put an essential explanation beside the image or statement it concerns. If it appears only in the email, someone who receives the forwarded file may never see it.
Adding that context can make the circulated version more useful while making the live version cumbersome. A presenter does not necessarily need to read paragraphs that everyone can already see. The same work may need two presentations with different amounts of explanation.
The team still needs to keep the proposal consistent between them. Preparing an emailed version is a chance to make the reasoning explicit, and any substantive change needs to be understood by the people who presented the original. Otherwise, the person forwarding it may unknowingly be introducing a different recommendation.
When someone else will present, that person needs preparation too. Discuss the proposal, the open questions, and likely points of confusion with them. They can explain the work in their own words and recognize when a question needs to come back to its authors.
Check the conditions of the review
Even a clear presentation depends on people being able to see, hear, and follow it.
Text that is comfortable on a designer’s monitor may be unreadable from the back of a room or inside a shared screen on a laptop. A reference clip may rely on movement that becomes difficult to judge when playback stutters. Check that the playback method allows reviewers to see or hear the detail they need to judge.
Checking the actual file, links, and playback method is part of preparing the review. So is understanding how much time the reviewers have. A sequence designed for a half-hour discussion may need reconsideration if the decision maker can attend only the first ten minutes. Show the essential material early enough for that person to understand and discuss it.
The order of information deserves the same attention. A reviewer may need to understand the intended audience before a creative choice makes sense. Two options may be easier to compare if each is shown with equivalent context. An explanation that seems repetitive to the team may be necessary for someone joining the project at this stage.
Production can check the review arrangements while creative identifies what people need to see or hear to assess the idea. That exchange should happen early enough to affect the presentation. Discovering a limitation during the review leaves fewer useful choices.
Some conditions will remain outside the team’s control. People get interrupted. Files are viewed on unexpected devices. A carefully prepared deck may arrive without its introduction. Anticipating those possibilities helps the team decide which context must remain visible within the materials and where a follow-up conversation may be necessary.
Consider concerns beyond the planned question
Preparing a review does not guarantee agreement. People can understand the work fully and still find it unconvincing. They may also notice a problem outside the intended focus that affects whether the idea should proceed.
The presenter needs to hear that distinction. A concern about a temporary location might be deferred. A concern that the entire concept depends on an inaccessible setting may need attention now. Redirecting every unexpected comment would prevent the review from doing useful work.
The introduction should help people understand the proposal and what remains undecided. Allow questions that affect whether the idea should proceed. That is easier when reviewers understand both the decision needed today and what they will have another opportunity to review later.
Before sending the campaign deck, the team can read it without supplying the presentation from memory. Does it explain the concept? Can a new reader tell why the references are there? Is the requested decision clear? Before the live review, the team can make the same assessment of the complete experience, including the spoken introduction and the way the material will be shown.
The two versions may look different. Each should explain the idea, identify the purpose of its references, and make the requested decision clear.