Connected Devices/Projects/Project Cue: Difference between revisions

Connected Devices/Projects/Project Cue (view source)

Revision as of 23:27, 27 July 2016

3,947 bytes added , 27 July 2016

Updated with MVP2 data and results of MVP1

Juliemccracken

670

edits

@@ Line 16: / Line 16: @@
   | content7 = TBD  <!-- Project Website -->
 }}
-'''Project Cue''' makes use of an always-on voice-enabled smart screen device to keep track of activities, events, and to-do lists of the family members. The initial focus of the project will be on reminders and will enable any family member to set reminders for his/her own to do's, activities, and events or for any other family member and to receive notifications for these reminders.
+'''Project Cue''' makes use of an always-on voice-enabled smart screen device to set reminders and manage and keep track of activities, events, and to-do lists of family members.
 == Project Overview ==
-*Busy families have to manage and remember many to do’s, scheduled events, and activities related to the management of their households. Often, disorganized or ad hoc methods or tools are used to manage these, including post-its, reminders stuck on the refrigerator, various digital apps, or overloaded memories. This leads to stress and chaos, and it’s time consuming and cumbersome.
+*Busy families have to manage and remember many to do’s, scheduled events, and activities related to the management of their households. Often, disorganized or ad hoc methods or tools are used to manage these, including post-its, reminders stuck on the refrigerator, various digital apps, or overloaded memories. This leads to stress and chaos, and it’s time consuming and cumbersome. Project Cue would save time and bring peace of mind to the entire family with its simple and intuitive solution to turn the daily coordination chaos across the family members to organized control.
-*Project Cue saves time and brings peace of mind to the entire family with its simple and intuitive solution to turn the daily coordination chaos across the family members to organized control.
+*Envisioned as a Family Organizer, Cue will:
-*Envisioned as a Family Organizer, Cue will enable family members to easily manage their activities, events, and to do's.
+**Enable family members to easily manage their activities, events, and to do's
-*The initial focus for Project Cue will be a prototype for Reminders only.  Voice will be tested as a friction free way to request and use reminders.
+**Provide voice enabled reminder functionality that improves upon existing methods by relieving the need to carry to do's, events, or upcoming activities in your memory or write or type them up
-*Project Cue wants to offer a better, easier way than having to carry all those to do's, events, or upcoming activities in your memory or having to write or type up reminders.
+**Provide automated functionality to organize events and activities quickly and easily by coordinating the schedules of family members and friends
 ==Early Exploration==
 '''Initial Experimentation'''
-*Project Cue grew out of the study and research conducted by the Project Link team. Initially, the team looked at a hub that would manage smart devices in the home. They evaluated what was desirable from a hub angle, if it was going to be viable from a Mozilla perspective, and desirable for customer.  The team used the "Design Thinking" innovation approach by IDEO, where the philosophy of Product Innovation is at the center of technology (feasibility), person (desirability) & business (viability). After prototyping certain fundamental elements like first time user experience, device discovery, interoperability, and a rules engine, and evaluating the market and competitor landscape, including whether or not a digital assistant using voice would be a good way to differentiate, the team concluded that a hub was not where we should be.
+*Project Cue grew out of the study and research conducted by the Project Link team. Initially, the team looked at a hub that would manage smart devices in the home. They evaluated what was desirable from a hub angle, if it was going to be viable from a Mozilla perspective, and desirable for customer.
+*The team used the "Design Thinking" innovation approach by IDEO, where the philosophy of Product Innovation is at the center of technology (feasibility), person (desirability) & business (viability).
+*After prototyping certain fundamental elements like first time user experience, device discovery, interoperability, and a rules engine, and evaluating the market and competitor landscape, including whether or not a digital assistant using voice would be a good way to differentiate, the team concluded that a hub was not where we should be.
 '''Project Study'''
@@ Line 38: / Line 40: @@
 *The team chose "busy families" as the target market segment for its study. User research was conducted by the team via interviews with 18 busy families in North American and Europe to gather data on how they were managing their busy lives and what kinds of help they envisioned needing.
-'''Hypotheses Tested in the Study'''
+'''Hypotheses Tested in the Initial Study'''
 We believe that there are..
@@ Line 94: / Line 96: @@
 ==Concept Validation==
-'''Hypothesis'''
+'''Original Hypothesis'''
-The initial focus on Reminders would test the following hypothesis:
+The hypothesis we initially developed for the entire Cue project was:
 *We believe that there are:
 **Families in NA/EU with 2 or more kids in elementary schools (PS-5), all living together in the same household, and both of the parents are working full time from 9am to 5pm and are between 30 & 40 yrs old, well educated, and in a medium to high income bracket
@@ Line 103: / Line 106: @@
 **by building a friction-free simple way to organize and keep track of the daily activities that are needed for the management of the household
 **we will provide them with more peace of mind and a sense of being more in control of their household and on top of their needs.
-'''Prototype'''
-*A prototype is being developed within a month-long time frame to test how the use of a voice interface for reminders might provide a friction free, easy and better way to help busy family members manage the activities and events related to their household management, and provide them with more peace of mind and a sense of control.
-* Specifically, the Project Cue team will build and test with the target market a web app prototype that provides the ability to:
-**Use voice (3rd party) to create reminders for one’s self and his/her family members and display on an always-on tablet
-**Receive reminders whether at home or away
-**Receive notifications via voice and in-app notifications at the time of the reminder
-**View your agenda for the day on either a tablet or smartphone
-With the Project Cue prototype, team team wants to test:
+==Reminders (MVP1)==
-*how different speech patterns can be detected
-*if voice is truly a friction fee way to interact with reminders
+We narrowed the focus of our experimentation to Reminders and used the same design thinking referenced above, and Lean StartUp methodology.
-*if we can differentiate the reminders functionality by making it available for the entire family
+'''Assumptions (Leap of Faith)'''
+*We believe that busy families are looking for an alternative solution other than what they currently use (memory, post-its, black boards, calendar apps etc.) to manage & organize their schedule
+*We believe that VOICE is a friction free way to create reminders, lists, coordinate schedules.
+*We believe that busy families would require an alternative way to create & manage reminders, lists & schedules using a SMART DISPLAY that would further simplify their management.
+'''Hypotheses'''
+*Creating a voice enabled solution to create reminders, lists, coordinate schedules, we will reduce the time taken to perform these tasks by 20%.
+*Offering a solution that provides an alternative way to create and manage reminders, lists & schedules using a smart display, families would be able to accomplish their tasks 20% more times than before.
+'''BUILD'''
+*A prototype was developed over four weeks to test how the use of a voice interface for reminders might provide a friction free, easy and better way to help busy family members manage the activities and events related to their household management, and provide them with more peace of mind and a sense of control.
+*Leverage Google’s Speech API to build a speech enabled interaction to create reminders
+*Webapp to display the reminders created
+*Provide both voice & visual feedback for each reminder created
+*Notifications to multiple devices
+*Remote access to retrieve/create reminders
+'''LEARN'''
+*Gather feedback on a voice enabled solution to create reminders
+*Get a deeper insight on what types of reminders, lists, schedules people are looking to manage
+*Get an understanding of the speech patterns:
+*Determine 2-3 speech patterns (different ways of instructing the robot) to set reminders, to-do lists, schedule events both within the family & outside the families
+*Gather ideas on how people foresee interacting with this device
+'''MEASURE'''
+*Compare the time taken to create reminders via existing methods & by leveraging our proposed solution
+'''RESULTS'''
+*Interviewed 5 participants to validate or invalidate our hypothesis
+*The product even in its current primitive state ignited a fair amount of enthusiasm in the participants.
+*Hypothesis 1 has been validated: All participants agreed that voice is a friction free way to interact. This product at its prototype stage has reduced the time taken to create reminders by an average of 77% (peak savings of 91%)
+*Hypothesis 2 could not be validated as we could not yet give away a product for independent use; we will revisit this hypothesis at a later time.
+'''RECOMMENDATIONS FOR NEXT STEPS'''
+*Build the first phase of the product with just reminders & lists functionality and give it to customers for independent use.
-'''Assumptions and Risks'''
+==Coordination of Small Events (MVP2)==
+The team moved forward with additional assumptions resulting from the results of the completed studies.
+'''Hypothesis''' (to be tested over 2 weeks)
+*Creating a product that leverages voice interaction & chatbot to coordinate small gatherings
+* will result in these families seeing
+**50% reduction in the time required to coordinate such events using traditional methods of email, sms, phone calls
+**25% quicker response rates from recipients
+*Creating a targeted Facebook campaign that is supported by a polished landing page & video clearly articulating the vision for Cue will result in at least 50 users signing up for updates
+'''BUILD'''
+*Create a video that explains the entire product
+*Create a landing page to explain the entire product & host the video
+*Launch a Facebook campaign
+*Wizard of Oz / Concierge MVP style to determine interest & areas that demand a solution for coordinating smaller gatherings (3-4 families)
+'''MEASURE'''
+*# of clicks on facebook ads
+*# of views on the video
+*# of lead gens on the Landing page
+*Bounce rate?
+'''LEARN'''
+*Gauge customer interest in the product even before it is completely built
+*Vested group of customers to engage with for future product iterations
+*Validate customer appetite in automating coordination through chatbot
+==Assumptions and Risks==
 {| class="wikitable"
 ! style="text-align: center;" | Assumptions
@@ Line 134: / Line 194: @@
 |-
 |}
-'''Concept Validation Status'''
+==Concept Validation Status==
 {| class="wikitable"
@@ Line 143: / Line 203: @@
 ! style="background:#00B2FF;" | Done
 |-
-| MVP approved || June 30, 2016
+| MVP1 approved || June 30, 2016
-! style="background:#FF2800;" | Late
+! style="background:#00B2FF;" | Done
 |-
 | Submit lite version of pitch deck for Gate 0 to reflect pilot || July 5, 2016
 ! style="background:#00B2FF;" | Done
 |-
-| Initial end-to-end demo of prototype ready || July 8, 2016
+| Initial demo of prototype ready || July 8, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Present demo at Cue sync up with CD leadership || July 12, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Project Cue leadership attends Lean Startup Training || July 13-14, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Ready to test prototype within Cue team || July 15, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Testing within Cue team completed|| July 22, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Busy Family testers identified and scheduled|| July 21, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Testing of busy family members completed|| July 25, 2016
+! style="background:#00B2FF;" | Done
+|-
+| Results of MVP1 presented to CD leadership|| July 27, 2016
+! style="background:#00EC00;" | On Target
+|-
+| Update presented to PIB|| August 10, 2016
+! style="background:#00EC00;" | On Target
+|-
+| Devices ready for MVP1 testing with study participants|| August 19, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Present demo at Cue sync up with CD leadership || July 12, 2016
+| MVP1 testing with devices completed|| September 2, 2016
+! style="background:#00EC00;" | On Target
+|-
+| Facebook Campaign created|| August 1, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Project Cue leadership attends Lean Startup Training || July 13-14, 2016
+| Cue public landing page created|| August 1, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Ready to test prototype within Cue team || July 15, 2016
+| MVP2 study started|| August 1, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Testing within Cue team completed|| July 22, 2016
+| Cue video created|| August 8, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Busy Family testers identified and scheduled|| July 22, 2016
+| Update presented to PIB|| August 10, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Testing by busy family members completed|| August 5, 2016
+| MVP2 study completed|| August 12, 2016
 ! style="background:#00EC00;" | On Target
 |-
-| Results presented to PIB|| August 5, 2016
+| MVP1 testing with devices completed|| September 2, 2016
 ! style="background:#00EC00;" | On Target
 |}