Product Development
Part of Creator brand product development
Testing prototypes with intended customers
Plan a prototype task, observe intended customers using the sample, record failures and retest revisions without overstating the results.
Give intended customers a realistic task with an identified prototype; observe what they do, then ask about their experience. Use important failures to decide what to change and retest.
A favourable reaction from the creator or followers does not show how the item works for every intended user.
Testing prototypes with intended customers: key steps
- Define the taskGive intended customers a realistic task with the prototype to observe real-world use.
- Observe actionsWatch how users interact with the prototype—note pauses, help-seeking, or unexpected methods.
- Collect feedbackAsk about their experience after the task, focusing on expectations, changes they’d make, and relevance to normal use.
- Analyse failuresUse observed issues to identify design or instruction flaws; separate actions from explanations.
- Retest revisionsImplement changes based on key findings and retest with new participants using the updated version.
Prototype testing vs. internal feedback
- Internal feedback (e.g., friends, followers)May be positive but not representative of broader user behaviour; can miss usability issues.
- Intended customer testingReveals real-world challenges; identifies confusion, safety risks, and functional gaps.
Choose a question the prototype can answer
List the uncertainty first. Can someone recognise how to use the item? Does a component fit what it is meant to hold? Is handling awkward?
Build a version able to answer the chosen question. A cardboard form may reveal shape and reach; it cannot establish the durability of a final material.
Record what the sample includes, what is simulated and what is missing. Note which version each participant handles. If a creator demonstrates an earlier sample, keep that demonstration separate from claims about the saleable item.
Benefits and limitations of using cardboard prototypes
- ProsQuick, low-cost way to test shape, size, reach, and basic function; helps identify early design flaws.
- ConsCannot assess durability, material performance, or long-term usability; may give false confidence in final product quality.
Recruit for the intended use
Invite people who face the task the product is meant to support. Include people outside the creator’s following if the intended market extends beyond it.
Record how each person was recruited and their relevant experience. Enthusiastic fans can reveal defects, but their reactions should not be reported as representative customer results.
Present the same task, starting conditions and prototype version where practical. Let the participant try before explaining a confusing step.
Note where they pause, seek help, use an unexpected method or abandon the task. If the prototype could present a hazard, assess that risk before inviting use and stop the exercise if a safety concern appears.
Separate actions from explanations
Keep a short record of the task, version, relevant participant context, observed action, participant’s explanation and any safety concern. “Turned the component upside down” is an observation. “The label caused confusion” is a possible explanation to check.
After the attempt, ask what the person expected, what they would change and whether the task resembles their normal use. If they misunderstood the intended use, examine the product, instructions and recruitment criteria before deciding why.
| Observation | Next decision |
|---|---|
| A participant cannot complete an important task without help | Check the cause, revise the design or instructions, and retest. |
| A plausible hazardous use appears | Stop that use and obtain a qualified safety assessment before relying on a design change. |
| The task succeeds but a feature is disliked | Compare the objection with the product requirements and trade-offs. |
| The prototype is praised | Record the reaction while checking observed use separately. |
These are proposed responses, not results from a performed test. A serious failure can matter even when other participants respond positively.
Key insights from prototype testing
- Observation: Task failed without help
- Check cause, revise design or instructions, and retest
- Observation: Hazardous use identified
- Stop that use and obtain a qualified safety assessment before proceeding
- Observation: Task succeeded but feature disliked
- Compare objection to product requirements and trade-offs
- Observation: Prototype praised
- Record reaction but validate against observed usage—positive feedback doesn’t override failure
Retest the change that matters
For each revision, record the observation behind it and the requirement it aims to meet. Give the affected task to intended users again with the new version.
If materials, size, contents or instructions change, earlier observations may no longer apply.
Australian Government guidance recommends letting potential customers try a prototype, watching how they use it and improving the item from feedback.
That exercise does not replace the safety, labelling and quality checks applicable to the finished product. Keep the findings tied to the version tested rather than describing the saleable item as approved.
![Turn complaints into clear product needs: Collect recurring feedback from customers, followers and users.; Use the formula: For [user] in [situation], must [action], checked by [measure].; Verify requirements with observation, not just suggestions or preferences. Turning audience problems into product requirements](/covers/turning-audience-problems-into-product-requirements-640.webp?v=090fb2da)
