• Define detailed user personas and their needs
  • Map out user journeys and needs along the journey along with assumptions along the way → identify which tests happen for each stage
• Define list of assumptions about those personas
  • Use literature reviews to answer possible assumptions
• Define questions to test with those personas
  • Use interviews and focus groups to answer those questions
  • Document and translate those interviews
• Define features that answer those questions
  • Follow an agile development approach and communicate results of tests and learnings across teams at all times.
  • Teams developing a feature should be composed of different skillsets and focus on a set aspect of the product and work alongside each-other from assumption definition to final test.
• Define tests that can evaluate the efficacy of those features
  • Start with in house small pilot studies, measureable tests and trials under IRB
    • Test user engagement, clinical outcomes and validity of the experience
    • Involve clinicians in the review and evaluation of the product in its earliest stages
    • Base testing on real life scenarios and replicate real world settings as much as possible, provide just enough context for the scenario to be realistic
  • A/B tests for smaller feature changes → shouldn’t be necessary until major decisions have been made
  • Beta testing with select users before a wider release
  • Accesibility and implementation testing → ensuring all populations can use the tool easily
• Set up specific RCTs that look to prove the efficacy of well tested product at scale internally or with external customer institutions
• Clearly define and identify the feature they are developing
• Establish the list of assumptions regarding this feature or product
• Conduct a comprehensive literature review
• Establish clear and measurable end points that they will measure along the development and testing
• Test and validate findings with VR1 assessments surveys and focus groups
  • Use standardized repeatable 7 point likert assessments (see Alex or Vic for advice)
  • Use physiological data measures when possible using empatica
• Synthesize the collected data into product updates to improve tests and features
• Establish user experience outcomes and repeat above process until pilots with customers

If a pilot is not used for the below parts and internal research is performed use the bellow procedures:

• Set up VR2 feasibility study tests to further validate and improve the product
• Continuously synthesize updates based on feedback and findings
• Establish clinical outcomes
• Set up V3 RCT to validate clinical outcomes