Connected Devices Weekly Update/2016-07-26: Difference between revisions

Jump to navigation Jump to search

Connected Devices Weekly Update/2016-07-26 (view source)

Revision as of 15:59, 26 July 2016

506 bytes removed ,  26 July 2016
update Haiku
No edit summary
(update Haiku)
Line 64: Line 64:
! style="background:#00EC00;" | On Target
! style="background:#00EC00;" | On Target
|  
|  
* Last week we were taking some time to design our next experiment using some of the tools we learned in Lean Startup training last week.
We have been working on 2 ideas for a wearable device that lights up/buzzes when people I care about are available.
* We have been working on the [https://docs.google.com/spreadsheets/d/1_C8njNIUu5DohL0ZywxyDEvK88Da_I7oFGmXKSIw_Vo/edit?usp=sharing assumptions] about the Idea '''"A wearable that lights up/buzzes when people I care about are available"''' to identify the ones that could be leap-of-faith assumptions to create experiments about them. We identified 4 LOFs
* Idea 1 is a device that lets me set/unset my status for my friends to see.
** "We believe people have a limited set of “statuses” that they want to communicate and know to priority people/things" -> '''Limited status auto replies''' experiment
* Idea 2 is a device that lets me request the current status of my friends - my friends can then send back an auto-reply that means "Busy now, txt you later."
** "We believe that people want to provide status" -> '''Desire to provide status''' experiment
 
** "We believe people will find value in the device even if one (or all) of the priority group don't set their status" -> '''Find Value''' experiment
Priority assumptions to test - [https://drive.google.com/open?id=1_C8njNIUu5DohL0ZywxyDEvK88Da_I7oFGmXKSIw_Vo see here for all].
** "We believe people want a wearable device that tells them about the status/avail of people/things they care about" -> '''Product is desirable''' experiment
* We believe people have 5-6 priority people/things that they care about at a time (both ideas).
* We are going to start to create experiments for the first one '''Limited status auto replies''' experiment to know more about:
* We believe that the number of desired auto-replies is small (idea 2).
** The auto-replies I want to send - design implication
 
** Do people adjust their priority people/things based on some context (geography, time, work, etc)?
Our next experiment is a survey to learn about the following. Launching this week.
** Who are the people/things people mark as priority? Also to confirm our idea that 5-6 is the number.
* For both ideas, how many people are considered "priority people"? This has design implications for the hardware and software.
** Experiments to validate this assumption:
* For Idea 2, what are the types of auto-replies people would need to make this device valuable to them? This also has design implications.
*** Desk research
 
*** Survey girls out of Silicon Valley
Also working on visualizations of the device interaction. We plan to use these in future experiments prior to building the actual device.
* Another goal was to get more concrete/tangible about what the device really is, based on what we know right now. We started to describe interactions with the device to make it easier to understand. ([https://docs.google.com/document/d/1dCmr76uBciy4NFHC2mbyw33ZElRigiVzZxvCOsa2SqU/edit?usp=sharing Idea 1 - Requirements + Visualizations]
* [https://docs.google.com/document/d/1dCmr76uBciy4NFHC2mbyw33ZElRigiVzZxvCOsa2SqU/edit#heading=h.8dr1wpopimgk Example for Idea 1]
* [https://irccloud.mozilla.com/file/G6v3eVgr/example-client-hand-screenshot.png Screenshot from interactive HTMl client]
 
 
|-
|-
| [[Sensor_Web|Project Sensor Web]]
| [[Sensor_Web|Project Sensor Web]]
Ezoehunt
Confirmed users
195

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1141295"

Navigation menu