Getting risk findings understood by the people who pack, list and answer customers

A risk assessment that stays with the assessor cannot protect buyers. For bath bombs, the people who pack orders need to know that a bomb may crumble in transit and leave dye on towels, the person who writes listings needs to know what care wording to include, and the person who answers messages needs to know what to say when a customer reports staining. Each role needs a different slice of the same finding, in words they can use.

The most effective tool is often a one page summary, written for the team rather than for a file. It should state the finding in one sentence, list the actions for each role, and name the person to contact when a new problem appears. A long assessment file emailed to everyone will be opened by almost no one, while a short summary pinned where work happens will be read.

Plain language is not dumbing down; it is translation. A note that says a bomb exhibits friability and chromatic transfer will confuse a packer, while a note that says the bomb crumbles and its colour can stain towels gives the packer a clear action: wrap it separately and warn the buyer. The summary should be tested by asking a team member to explain it back, and rewritten if the explanation drifts.

Visual cues help too. A photo of a crumbled bomb, a photo of a stained towel, or a marked example of good wrapping can convey in seconds what paragraphs cannot. The summary should include such examples where they exist, labelled with the batch they came from, so the team does not generalise from one batch to all batches.

Illustration: a team of 30 people receives a summary and, in round illustration terms, 20 of them read it fully while the rest skim it. Those figures, as presented in Getting risk findings understood by the people who pack, list and answer customers, are invented, not measured. They illustrate why distribution is not communication: sending a document is not the same as ensuring it was understood, and a team that only tracks sending will overestimate how much was learned.

The remedy is a short check: ask each role what action they will take after reading the summary, and record the answers. If packers, listers, and customer service give different answers to the same finding, the summary needs rewriting, not resending.

Communication should run both ways. Packers notice crumbling first, customer service hears about staining first, and listers notice when a care instruction is unclear. The team should have a simple route for those observations to reach the assessor, such as a shared note, a weekly check in, or a message channel that is actually monitored.

• Write a one page summary with one finding sentence and role actions.
• Test the summary by asking team members to explain it back.
• Include labelled photos or examples where they clarify the finding.
• Provide a simple route for packers and customer service to report back.

Internal communication fails when it is treated as a one off announcement. A summary sent at launch and never updated becomes stale as ingredients, packaging, and batches change, and the team gradually stops trusting it. Summaries should carry a date and a version, and should be updated whenever the underlying finding changes, with the change highlighted.

Another failure is to share only good news. If a finding is worrying, the team may be tempted to soften it for morale, but a softened finding leads to softened actions: weaker wrapping, vaguer listings, and vaguer customer replies. Honest wording, delivered kindly, protects both the team and the buyer.

Close by naming a single owner for each summary, who keeps it current and who answers questions about it. Without an owner, summaries drift, questions go unanswered, and the team improvises, which is how inconsistent wrapping and inconsistent customer answers arise.

Finally, keep old summaries archived, not deleted, so a new team member can see how findings evolved. That history helps newcomers understand not only what to do now, but why the team does it that way.