Written by DROPS.ST.
Build staff exercises from invented products, customer labels and order references. Include only what the decision needs, label the material clearly and use written cards unless a contained demonstration environment has been agreed.
DROPS gives cases a useful structure: products have prices, units and stock, while orders retain item and customer links. Model those relationships with fictional material instead of exposing customer histories during a walkthrough.
Start with the learning question
A pack-quantity exercise needs item references and clear units. A handoff exercise needs an unresolved task and a fictional receiving owner. Neither requires a copied customer conversation or personal history.
Write from a blank page. Replacing the name in an exported record leaves other details to assess and clean. ICO guidance also explains that synthetic datasets modeled from real information can reveal personal information; the label does not establish anonymity. ICO synthetic-data guidance.
For a small exercise, manually invented material avoids starting with a customer dataset.
Specify a small case set
Use labels such as TRAINING-CUSTOMER-A and TRAINING-ORDER-A, with separate fictional product references. This is a planning sheet, not an import template or authorization to create live records.
| Exercise field | Suggested value | Check |
|---|---|---|
| Customer label | TRAINING-CUSTOMER-A | No copied identity or contact details |
| Order reference | TRAINING-ORDER-A | No live order reference |
| Product reference | TRAINING-PACK-A | Separate from the live catalogue |
| Quantity and unit | Invented quantity with explicit pack meaning | Arithmetic agrees |
| Stock | Number selected for the exercise | Supports the intended decision |
| Order or payment state | Written fictional state | No transaction needed to create it |
| Message | Short invented question | No copied transcript or sensitive background |
| Expected step | Facilitator’s separate answer | Not disclosed before practice |
Leave unused fields out. More personal detail does not make a case more useful.
Remove external destinations from the exercise
Avoid plausible phone numbers, email addresses and payment destinations. They may correspond to real destinations. Use a label such as “contact route outside this exercise”; staff can draft a reply without sending it.
If interactive software requires contact data, the demonstration owner must establish containment first. A training label or example address is not proof that delivery cannot occur.
Represent payment states as written facts. Do not copy proofs, transaction identifiers, credentials or wallet details. Ask which evidence would be needed without generating a funded payment.
Check relationships, not just individual fields
Keep the customer, order and item references consistent. Define the pack behind the price and make quantities meaningful against the fictional stock. Mark deliberate contradictions as exercise features rather than leaving accidental errors.
Hold a short facilitator reference showing which records belong together. Use enough cases to teach the decision, not a large dataset nobody can inspect.
The approved product record guide helps distinguish units and pack information. Exercise values remain fictional.
Hypothetical example: packs versus individual items
A trainer creates TRAINING-PACK-A with an invented pack definition and an order for two packs. The case includes a stock number and a short customer question, but no personal contact, health narrative or payment record.
The facilitator keeps the expected calculation separately. The trainee explains the quantity meaning and identifies missing information before choosing a next step.
This is a hypothetical training specification, not an actual customer, product recommendation or DROPS record.
Release the material deliberately
Have another person check for copied details, ambiguous labels and accidental live-record links. They should follow the relationships using the facilitator reference.
For interactive practice, agree the environment and permitted actions. Establish how messages, calls, payments and other external effects are prevented. Use cards if containment cannot be verified.
Review trainer access too: DROPS catalogue editing includes customer-account edits and wallet adjustments. It is not an isolated training-editor role. The manager access checklist helps examine that scope.
Name the case-set owner and keep a version. Correct ambiguous cases before reuse and handle task-created copies through the agreed training process.
Practise the records your team will use
DROPS gives the team one catalogue and customer-linked order system to learn. Website and connected Telegram shopping use the same core records, making product identity, quantity and handoff relationships concrete.
See DROPS and explore demo shops. Bring one training question and identify the smallest fictional case that teaches it without making customer history the lesson material.