Explore how a proposed feature, audience, claim, or business model could affect your product’s obligations. Give product, design, and engineering teams regulatory questions they can resolve while the roadmap is still flexible.
Product managers and founders can investigate regulatory questions while options are still open. Explore how a feature, audience, claim, or business model may change the product’s obligations.
Compare proposed approaches using a defined market and use case. Ask which regulatory assumptions differ, what evidence each option needs, and where specialist input could change the decision.
Turn research into a draft product brief that engineering, design, legal, and operations can discuss. Include a specification or user-flow document in the analysis.
Investigate whether a capability introduces a new product category, regulated activity, or duty. Consider the intended use and real user experience before translating the answer into a requirement.
Research questions involving children, patients, consumers, employees, or professional users. Explore how the target audience changes expectations for safety, information, accessibility, or data handling.
Examine what an intended claim implies about the product and the evidence behind it. Prepare a joint discussion with marketing, technical, and regulatory colleagues before launch messaging is finalized.
Research the proposed destination and compare it with the product’s existing market assumptions. Outline differences in labeling, roles, permissions, or supporting documentation for further assessment.
Draft a view of regulatory dependencies, evidence needs, and unresolved decisions. Use that research to inform sequencing and ownership alongside customer value, cost, and technical feasibility.
Explore how updates, complaints, repairs, recalls, or end-of-life arrangements affect the product. Identify the operational questions that should be addressed before the roadmap moves on.
