Example · Device or platform developer
Which product claims can we substantiate before the next launch review?
A developer separates a wearable’s demonstrated purpose from broader commercial promises
The situation
A consumer neuro-wearable
You develop a non-invasive neuro-wearable with an app for personal feedback. A draft launch page promises better attention, mood and productivity; possible partners include schools and employers. You need to decide which claims and design questions to bring to the internal launch review
What this example starts with
- The hypothetical product
- The proposal includes repeated sensing, feedback and an account service; its claims extend beyond describing recorded signals or interactions
- The evidence gap
- Assume the supplied materials do not substantiate every proposed benefit, explain all inferred outputs or fully describe retention and secondary data uses
- The changing context
- An individual purchase, a school partnership and employer use would involve different people, expectations and choices, even if the hardware stayed identical
Working through the question
Break the promise into claims
You enter the intended use precisely and examine each proposed benefit separately. A working sensor, an understandable feedback display and an improvement in daily productivity would require different supporting material. In this example, you flag the broad draft language for an evidence review
Follow the information
You trace what the product records, what the app infers and where information could go. The absence of an implant does not answer these questions. You identify missing explanations about secondary uses and ask how the person would understand and control each relevant choice
Treat partnerships as changed uses
You consider how a school or employer offer could change participation. An individual consumer assessment would not transfer unchanged. Proposed youth marketing, mental-health implications and institutional reporting become separate scope and evidence questions for the teams responsible for those uses
An illustrative take-away
A launch-review evidence agenda
You pair proposed wording with evidence requirements and unresolved product decisions in a review note
- What evidence supports each attention, mood or productivity claim?
- Can a person understand the inferred outputs and proposed secondary data uses?
- Which proposed partnerships change the intended use enough to need a separate review?
Written for this example to show what the reader could take into their next conversation
The assessment does not approve product claims, determine compliance or authorize a launch
Try this with your own question
Your guide explains the steps, access requirements and limits for your role