Skip to main content

From Idea to reality - The progress of an Idea

 I have been thinking of writing a simple app for locating trash cans at Chennai.

The first thing anyone would do was to see if the idea has been already implemented. Sure enough, it has been. This is the app - Check it out. http://trashithere.herokuapp.com/

When I tried using the app, I found out that there were only few trash cans. This was a crowd sourced application. I guess this app was not used much.

The Spark


This led me to questioning myself - What problem led me to this application. I yearned to live in a place that was clean. My assumption was that if people found places to throw thrash, they would not litter.

Going ahead with your idea



The path forward 

I started questioning these assumptions:
  • Would people stop littering if they can find trash cans?
  • What if the trash cans were full? Would people walk to the next trash can? What if that trash can was full too?
  • Would it be helpful if there was an indicator on which trash cans are full?
  • Would it also be helpful to show what time the trash cans get cleared?
Extending this exercise, who are going to be the users of the application for me to be able to solve the problem.
  • The obvious answer is the regular city citizens
  • The not-so-obvious corporation workers that clear the cans
  • The corporation planning team that dispatches the clearing crews
It is now time to question the problem statement.
  • Do we just want people to see where the trash cans are?
  • Do we want people to stop littering?
  • Do we want the corporation to clear the trash cans on time?
  • Do we want to just track the amount of trash and create awareness?
Next we can map the problem statement with our users to come up with a feature map.
We need the application to do the following:
  • Show location and status of trash cans to the citizens
  • Allow users to mark locations and update status of trash cans
  • Alert corporation workers on filling trash cans with location
  • Provide reports on trash collection & clearing patterns for corporation to plan its operations.
We can build various features around the high level feature map and then try it out.
The key to the success of the application and hence the original goal is not functional. We need some support.
  • Make sure that users can submit data without friction
  • Get buy-in from corporation for them to use data
  • Get some support to spread the application and get more crowd-sourced data
  • Have a way of getting automated data inputs and confirm with user's inputs.

Summary

While the idea taken is pretty simple, let us generalise the path:
  • Question the assumptions
  • List of all users
  • Question the problem statement
  • Come up with the feature map and functionalities
  • List any hep needed to succeed in the effort
There are a few things that we have ignored in the attempt:
  • Try the most common functionality first
  • If a functionality fails, try another functionality for the same purpose.
  • Aim for traction
  • We did not discuss how this transforms into a business model.

Comments

Popular posts from this blog

The right business model for your product

How would you decide what is the best business model for your product? Deciding on the right business model is very important for the product. It does not necessarily mean what is the price of your product. There could be no price for your product - though that is a myth. For example, we think google or Facebook is free. However, we are never the customers for Google or Facebook. It is the advertisers that are its customers. What we need to figure out when we decide on a business model are as follows: Who is my target audience? Who is my customer What is the price. How is the support model going to work Who are my partners While we do not absolutely need to price a product, we need to understand how we would make money. For example Open ERP does not price its product. However, its product is not the ERP software but really the hosting, service and training that it offers. While pricing is an important part, what is more important is in realising who is you...

Finding your target audience

The biggest task of the product manager is to find your target audience. Typically it is a very tight rope walk. You define it too narrowly and you would struggle to generalize the product later. You define it too broad and you would struggle to satisfy a lot of people and the product might not take off at all. There is this awesome post by Dave Mcclure on why Niche target segment works. Blog link here . What he says is mostly right and that is what we did as well. We did it mostly by accident. We had to define our niche because we could only talk to those kind of retailers and get data from them to start developing the data. It did have its upside. We were very clear on what we wanted to develop and we are slowly talking to retailers and adding more scenarios. As we are doing this, we are also talking to a slightly different set of retailers. This helps us incrementally build our product while also generalizing the existing features. In our case, we did not fin...

Constructing the Product Roadmap

When I started out in the team, I was tasked out with coming out with a plan so that we can demonstrate the product with real data. The idea was to demonstrate it to our prospect with their own data and win them over. However, when I started working, I found out that what we lacked was not a plan but a vision. I quickly put together a one day workshop with our team and our product owner. When we started talking, we talked about several things and figured out that we needed a plan of various proportions. We needed a plan that could help us one the following: Provide a focus for the long term with near term focus on just one thing Help us talk to prospects on what we are going to do Help us decide on when we would need to focus shift on which function - Engineering , sales etc We also did a quick “Product in a box” exercise so that all of us in a team can practice and imbibe the elevator pitch. We needed this since we had to do this pitch at several levels - Inter...