Skip to content

sensor-web/sensorweb-plan

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

37 Commits
 
 
 
 
 
 

Repository files navigation

Lean Strategy for SensorWeb

We're focusing on validating end-user value and creating a minimum viable product(MVP) for them at this stage, not creating an open data platform for 3-rd party developers or makers.

SensorWeb is an open data platform for 3-rd party developers or makers in long term. And Project PM2.5 is about creating solutions(apps or hardware) with SensorWeb technology for end-users.

SensorWeb Concept

Q&A

  • What is SensorWeb?
    • Open Data Platform for IoT.
    • Community-based collaboration.
    • var SensorWeb = Community(OpenData, IoT);
  • Why we are NOT creating a data platform at this stage?
    • We don't have experiences about a successful data project, hence we don't know about key factors to support a successful platform for now. We might know after validated our end-user value.
  • Why SensorWeb platform's users at this stage are developers or makers, not end-users?
    • We should not and cannot build a platform or product for everyone. We should and need to focus.
    • Our data service is for helping developers or makers focus on developing their ideas. We provide back-end support, and they can make their products without re-building their own data back-end. It's more efficient.
    • Developers can re-use the open data to create solutions to fix new real world problems.
    • End-users cannot use our data service directly. They cannot write code.
    • End-users cannot build an IoT device for their needs.
    • As end-users, they just want to use products to improve their life.
  • What is the relationship between SensorWeb platform and end-users?
    • SensorWeb => Developers/Makers => End-users
    • SensorWeb platform help developers and makers build good products for end-users.
    • For example, our pilot project Project PM2.5 is for end-users.

How to Feedback

Please add a new issue, and let's discuss your ideas and questions on the Issues. Thanks for your feedback.

SensorWeb's Lean Framework

Value Hypothesis

  • Question to Answer
    • Is there already sufficient demand for consume PM2.5 data
  • Customers want to consume PM2.5 data to avoid exposure.

Growth Hypothesis

  • Question to Answer
    • Is the demand strong enough to generate viral effect?
  • Customers want to help us spread the word.

SensorWeb's Hypothesis for Schools

Value Hypothesis

  • Teachers in the schools with serious air pollution problem(e.g. Nearby Yunlin, Taiwan) want to have real-time PM2.5 data from nearby to help students live healthier in schools(e.g. PE class should be in the indoor when air quality is bad).

Growth Hypothesis

  • Teachers want to teach other (schools') teachers setup their own PM2.5 stations.

Why School(with Big Air Pollution Concerns)

  • Pros
    • We can do one time deployment to deliver our values to thousands students and teachers.
    • Whole society(government) really care about education environment. So it will help us to create the virus effects.
    • We already have some connections with several schools. (three schools with thousands people deploy our PM2.5 stations) Especilly, a teacher from Nanguo Elementary School(2500+ people) in Changhua, Taiwan is using SensorWeb as the class material in his class. He is also planning a semester science project with his students to improve their air pollution issues.
    • The air quality is really bad in center part of Taiwan because Formosa Plastics Corp's (FPC) sixth naphtha cracker complex is located there. And Nanguo Elementary School is also located in center part of Taiwan.
  • Cons
    • It would be difficult for schools to make purchases. (we can just give them our PM2.5 for free)
    • We don't know how people in schools cares about PM2.5. (same situation for most groups)
    • We might not have sufficient knowledge about actions they will take. (same situation for most groups)

MVP 1 (March 1 2016 - Now)

Assumption

  • People in schools want to know their PM2.5 concentration by going to our website.

Features

  • PM Sensor with basic visualization on SensorWeb website.

Metrics

  • Static link click through session count per day: 66/16 = 4.125
  • Widget link click through session count per day: 115/29 = 3.96
  • Widget click through conversion rate: 1.38%

User Actions

  • Teacher put static link on school website after a few days.
  • Teacher embedded widget on school website after 3 weeks.

Learning

  • The School is willing to add link to the Sensor Detail page.
  • The School want a widget to display real-time data.
  • Click through rate drops after a few days of installation.

Following Assumptions

  • People don't know what options they have when have bad readings. (by interview)
  • People don't trust the data. (by interview)
  • People think there's friction to get data (guessing from PV drop)
  • Website customers aren't necessarily people in school (guessing from PV drop)
  • Most people in schools don't know about the sensor (assumption 2 and guessing from PV drop)

TODOs

  • Interview with the school again to confirm our assumptions and options they have when air quality is bad.
  • Show them the benchmark of air quality sensors. Our sensor is accuracy enough for them to take actions. Sensors Benchmark

MVP 2 (Q3 2016)

Assumption

  • (PE class) teachers will take action(e.g. go to indoor for PE classes when air quality is bad) if we provide dedicated app for them.

Features

  • App for (PE class) teachers to display air quality of the class' location.
  • App prompt the teacher to tell us what action he took.

Metrics

  • (PE Class) teachers will take action(e.g. go to indoor for PE classes) when air quality is bad.

Learning

  • ...

TODOs

  • ...

Releases

No releases published

Packages

No packages published