Skip to content

2. Visão do produto \ Product's Vision

Jump to bottom
Luis Mizutani edited this page Nov 21, 2017 · 1 revision

Value proposition:

Below some core value propositions to guide product evolution:

  1. Free tool: CaronaBoard is about friendship and will be free. This means that it won't be used to make money or provide tools for people to make money.
  2. Connect people: the idea is simple, CaronaBoard has to allow people to easy communicate and get ride to each other.
  3. Communities: the product will evolve to the idea of communities, so people can create a community for its workplace, or a group of friends. This will ensure you do not risk to get/give ride to someone you do not know or someone that can offer risk, specially in the current world where there is a lot of violence, prejudice and sexism. The idea is that in the future group administrator could allow people to join group or ban other members.
  4. Collaboration: CaronaBoard idea is to be a collaborative project. Your ideas and contributions are welcome.

Product Evolution

MVP 1

The product started very simple with a board in the wall where people could give visibility to other people about their offer or need. The board was divided in 2 sections one with people advertising where they were going by car, and another section where people would advertise where they would like to go getting a ride.

At this version we wanted to validate:

  1. if there were really a good amount of people that could benefit from that
  2. if people would offer ride.

Both hypothesis were validated due to the high number of post its at the board a few weeks after its creation.

User's feedback: Four (4) people in total used, and the ones who not used stated that the information was too confusing and that it was not easy to know who was giving or taking rides.

MVP 2

We improve organisation of information on the same board by creating the concept of routes. We physically organised the board the offers and requests by line. Each lines stood for a given address or region (suburb) this way ride takers and donators could see each other physically grouped.

The hypothesis here were:

  1. The concept of route is intuitive to people
  2. Visual information can improve usage

We sort of validate that, because people said that now it was better to see, but the number of users did not increased drastically. However we got more people giving feedback and we could get valuable information.

User's feedback: Nine (9) people used the board, but other stated: "I simply forget to see the board."

MVP 3 - Current version

This was the first version available on the web and the user group is still limited number of people. This product is a very simple and raw mashup using HTML, CSS and a bunch of google forms that were edited to send mails and save data on google docs. You can have a better understanding of the information flow by accessing the section that explain the current working logic of the app: https://github.com/luismizutani/CaronaBoard/wiki/MVP3's---Information-workflow

This digital version was created to validate 2 assumptions:

  1. If people are reminded they will use more.
  2. Having to go and personally ask for a ride is a blocker, specially if you are shy or do not know the person prior to the ride.

So far we validated well this two assumptions. For example, before advertising the board I used to give ride to around 3 people that were usually the same, they were sit next to me, and that I was proactively offering the ride. After creating MVP3 I gave ride to more than 8 people, most of them sitting in the other side of the office, some of them I never know before!

#MVP 4 - Project just starting

Now that we validate the value proposition, usage, and got some feedback to guide product's evolution it is time to invest a little more on the product from a technology perspective. In order to achieve that CaronaBoard now has the collaboration of some experienced professionals.

  • @luismizutani (Founder & Product Manager)
  • @rogeriochaves (Co-founder & Developer)
  • @thiagorocha23 (Collaborator & UX/UI Designer)

PAST COLLABORATORS

  • @andressa (Developer)
  • @glauberramos (UX/UI Designer)
  • @jeffhsta (Developer)
  • @jonathanrz (Developer)
  • @othman853 (Developer)

We ran a first kick of meeting fi some of the team members, where we basically set the context (that gave birth to this post) and we listed the main goals and problems to be solved by MVP 4. You can find some core ideas of this discussion here.

Clone this wiki locally