Project Everest

Adopted Experiment

[Proposed Experiment]: Utility Test Health Amisen April 2019

by
Morgan Allan
Morgan Allan | 6 months ago | in ROA **TRAINING**

Lean Phase: Solution – Utility Test

 

Assumptions:

Customer segment places high value on the following functions:

  • ability to be able to easily access all their medical health data in one area and identify personal tendencies towards certain illnesses (susceptibility).

  • ability to be able to get personalised action plan that assists with treating illness via the pre-stored symptoms database.

  • ability to be able to get personalised action plan that assists with treating illness via the pre-stored symptoms database.

  • ability to be alerted quickly about contagious diseases spiking in geographical area and how to mitigate risk of infection.

  • ability to be quickly and thoroughly diagnosed when being seen by doctor.

 

Time Box:

3 hours

 

Success Metric

  • Scaled interest in solution value (1-7) - value of 5 or over is considered success.

  • Number of people who are identified as successful result.

  • Reach - number of people

  • Conversion rate = (no. of people considered successful interest)/(total reach)

 

Criteria:

Green Light- Proceed to channels

Success Point – Conversion rate 40%

Orange Light – Re-evaluate the functionalities and their values to the customer.

Failure Point – Conversion rate 20%

Red Light – Re-assess platform (mobile application) that utility tests are being based around.

 

MVP - Paper based demonstration of product outcomes.

Product Moonshot - phone/website application.

MVP details:

  • Personal data - ability to be able to easily access all their medical health data in one area and identify personal tendencies towards certain illnesses (susceptibility).

    • Demonstration: Patient receiving tailored medical advice taking into account diabetes and medical history.

  • Diagnosis -  ability to be able to get personalised action plan that assists with treating illness via the pre-stored symptoms database.

    • Patient puts in their symptoms, product diagnoses likely causes of symptoms.

  • Geographic Warnings - ability to be alerted quickly about contagious diseases spiking in geographical area and how to mitigate risk of infection.

    • Patient receiving “there is a large presence of the flu in your area. Recommended mitigations are here....”.

  • Health behaviours - ability to know common and high-risk diseases and mitigate risk of infection.

    • List of behaviours such as washing hands, eating properly listed with their respective risk mitigation outcomes.

  • Medical data - ability to be quickly and thoroughly diagnosed when being seen by doctor.

    • Medical summary of patient, pointing key times of medical episodes which would improve doctor’s speed to help.

 

Experiment Build:

  1. Engage with customer segment.

  2. Explain and walk through each of the functionality demonstrations.

  3. Ask for rating of satisfaction of each function on a scale from 1-7.

  4. Record and collate answers.

edited on 28th April 2019, 06:04 by Morgan Allan

Wade Tink 6 months ago

The purpose of a utility test is to ‘test’ the success of your product once it is in the users hands. What I can understand from this post is that you intend to go back to those who have placed a deposit and ask them what they want to see in the solution…?

This is the equivalent of Henry Ford asking consumers what they wanted, to which they would have replied “a faster horse!” What I suggest you do is make the product so that it solves the problem you have identified, and which covers the value proposition:
Time- it means that 70% of the time they don’t have to go to hospital/medical clinic
Money- they save the $$ they would have spent because they didn’t have to go
Greater productivity given kids are sick less or when they are it’s for a shorter time- …
Peace of mind from being in control of their kids health-…

Therefore what you have written here, to me, looks like the features which will solve these^^ problems. Which is great! This is your ‘black label solution post’.

You now need to look at these features and say “which is the absolute minimum which will achieve the value propositions”. Then make a product which only does that bare minimum at the minimum cost- for this you will need to cost it out and actually make it.

Consider here that your initial prototype which will get in the hands of your users won’t be your final- ie. You may want a super techy app but right now your prototype may be access via phone call… I don’t know.

Cost this solution out and then get it to your consumers (those who have paid a deposit) straight away.

Now they have the solution in hand wait a short while and then follow-up with them with this posted utility test which is qualitative. Sit down with them and ask them questions which cover technical features but also emotions they associate with the product that they have in hand- this is measuring the emotional delta.

As a bonus this also then links to your impact assessment because you are assessing all those elements which Lucy presented....

Reply 0

Wade Tink 6 months ago

Also, be conscious of providing 'manual' solutions instead of going down the path of 'automating' at this stage. Consider things like a concierge service...

Reply 0

Wade Tink 6 months ago

Status label added: Experiment adopted

Reply 0

Samantha Fisher 2 weeks ago

Human health is consider as top priority for doctors and scientist so they have introduced viagra kaufen österreich to solve all the problems of a man while having physical relation.

Reply 0