How to give useful feedback on a product sample

1. Establish what the sample is meant to show

Before reviewing a product sample, ask what question it is intended to answer. A formulation sample, a packaging component and a decorated mock-up may represent different stages of a project. Their details should not automatically be treated as final.

Record the sample identifier, version and the brief it relates to. Ask which characteristics are ready for feedback and which remain provisional. This gives your comments a defined scope and helps avoid misunderstandings in the next round.

• Sample name and version
• Purpose of the review
• Relevant brief or reference
• Details that remain provisional

2. Describe observations before requesting changes

A first impression can start a conversation, but it rarely gives enough direction on its own. Instead of writing that a sample feels wrong, describe the particular quality you noticed and the direction you would like to discuss.

Keep each observation focused on one area. Separate comments on flavour, texture, appearance, packaging and artwork so the team can identify the right next step. Include a reference where it makes your meaning clearer.

3. Consolidate feedback before sending it

When several people review a sample, collect their comments before sending revision requests. Different preferences may conflict, and forwarding each message separately can leave the development team unsure which direction to follow.

Agree a project owner who can bring the comments together. Keep unresolved differences visible and identify which points need a discussion. A coordinated response does not require everyone to have the same preference; it requires a clear decision about the next step.

Send one current feedback record linked to the correct sample version.

4. Set a focused objective for the next round

Use the feedback record to agree what the next sample should explore. Explain which qualities are being changed and which are intended to remain. If several alternatives are requested, give each one a distinct purpose.

Avoid silently changing the underlying product brief during sample review. If the target audience, market or packaging direction changes, update the brief as well. The next sample should answer the current project question rather than an outdated one.

• Identify the requested revision.
• Explain the reason and priority.
• Confirm the qualities to preserve.
• Record how the revised sample will be reviewed.

5. Make the outcome of each review explicit

At the end of a sample review, record the outcome: approved for the stated purpose, further revision requested or additional information needed. Include the exact sample version and the details covered by the decision.

Carry the confirmed direction into the product brief and keep other questions open until they are resolved. This makes the sample process a useful record of decisions rather than a collection of disconnected impressions.

Clear feedback helps the next conversation start from a shared understanding of the product.