Research & Formulation

How to Run a Sample Review Meeting That Reaches a Decision

A sample review should produce a decision the development team can act on. Without a shared brief and a clear owner, the meeting can become a collection of preferences that cannot all be satisfied.

Anadoris editorial concept artwork; not a photograph of a facility or customer installation.
Anadoris editorial concept artwork; not a photograph of a facility or customer installation.

From Anadoris. This guide comes from the team behind Manufacturing & Development: formulation, packaging and production for other brands, from brief to finished batch. About the group.

Prepare the decision before the meeting

Send the current brief, sample codes and the specific question to be resolved. Explain whether the round is about texture, fragrance, packaging use or another defined issue. Make sure reviewers understand which parts are still exploratory and which qualities have already been accepted for the next stage.

Ask participants to record observations before the group conversation. Use the same prompts for everyone, such as dispensing, spreading, finish and fit with the intended occasion. A consistent structure allows different perspectives to be compared without forcing everybody to use the same adjectives or reach the same preference.

Separate observation, interpretation and choice

Begin by gathering what each person noticed. Then discuss possible explanations with the qualified specialists. Only after that should the owner decide the next step. Moving straight from a reaction to a requested formula change can skip the question of whether the issue belongs to packaging, use instructions or the brief itself.

When opinions conflict, return to the intended customer and setting. Do not average incompatible directions into a vague request for something in between. If the evidence is insufficient, define the smallest additional review that would help, with a clear question and a responsible owner.

End with a written instruction

Record the sample code, what should remain, what needs to change and why. State who owns the action and what the next round is expected to resolve. Confirm the meaning of approval so that a creative preference is not mistaken for technical release or readiness for commercial production.

Distribute the decision record to the people carrying out the work. At the next meeting, start by checking whether the requested change was delivered and whether it created a new trade-off. A concise review history makes progress visible and prevents the project from reopening settled choices without a clear reason.

Questions

Who should make the final decision?

An assigned owner should decide within defined authority, informed by the relevant specialists and the brief. Technical or safety approvals remain with qualified authorised reviewers.

What if the team cannot agree?

Identify the disputed requirement and the missing information. Decide what focused review would resolve it rather than asking for another sample with no clearer direction.

Your next chapter

Talk to the team behind this.

Manufacturing & Development: Formulation, packaging and production for other brands, from brief to finished batch.

Discuss manufacturing