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.
Break the experience into moments
Observe dispensing, initial contact, spreading, the finish and fragrance impression as separate parts of the experience. A product can be easy to spread but difficult to dispense from a chosen pack. Combining those impressions into a single score hides the distinction and may send the team toward the wrong adjustment.
Use descriptive sentences before asking for a solution. “I need several pump presses to obtain the amount I expect” describes an experience. “Make the formula thinner” proposes a technical intervention. The formulation and packaging teams should determine whether the cause belongs to the formula, dispenser or expectation.
Control the review conversation
Ask reviewers to record their observations independently before a group discussion. This reduces the chance that the first confident opinion becomes everybody’s vocabulary. Capture disagreements honestly. A texture that feels ideal for a slow evening routine may feel less convenient for somebody preparing to leave home.
Connect feedback to the original brief. If the product was designed for a quick daily routine, that use should guide the decision even when a reviewer personally prefers a richer experience. Feedback becomes useful when the team can distinguish a brief mismatch from an individual preference outside the intended audience.
Write a change request the team can evaluate
Summarise the most important observation, its use context and the desired direction. Keep the approved qualities visible so that an improvement in one area does not accidentally discard what already works. Ask the technical team to explain likely trade-offs before issuing several simultaneous changes.
At the next round, compare the new sample with the prior version using the same observation structure. Record whether the specific issue improved, stayed the same or changed into another problem. This makes the development history easier to understand and prevents the project from circling endlessly around subjective adjectives.
