(This will start a 2-Week Free Trial - No Credit Card Needed)
This is the fifth part of our Illustrated Guide to Product Development series.
Throughout this series we have extended a product idea into a business concept, the beginning of a Go-to-Market Plan and developed personas to correspond to all of these parts. We have also warned repeatedly that the biggest risk a company, new product or service has is making something nobody wants.
In this article we are going to dissect a few assumptions we have made, how they impact our work, and how we can test them. Many of the aspects of our business plan require the previous assumption to be true, but if all of a sudden the previous assumption is false, large parts of future work can and should be skipped.
For this, just getting started you may want to review The “Elevator Pitch” as we discuss our solution for Social Local Mobile Food Alerts, affectionately called SoLoMoFoo.
Let’s go back to a few key scenes from our very storyboard about SoLoMoFoo. In this storyboard we see Baking Bridget happily bringing in cupcakes to work, alerting her co-workers, and Hangry Henry enjoying a snack. To make it even clearer, I have relabeled the storyboard with the assumptions.
By coincidence the magnitude of the assumptions are in order, but it is typical that each cell in the narrative relies on a previous assumption.
People will make food and want to give it away for free at work.
In order for SoLoMoFoo to be useful, it has to provide a healthy frequency of alerts of free food and enough free food with each alert that users are left finding a snack if they want one, and not one of hundreds of people showing up for cupcake remnants. Engaging our crack team of analysts, we can determine an optimal ratio of frequency : food : users : happiness.
Now that we have a nice complicated formula for return on cupcakes baked, we can send a survey to 100 average office workers and ask them:
With this data and our formula we can have a sense if there are truly enough Baking Bridgets and Bobs.
The best scenario is your quick test says you are 100% correct. This is rare and unusual on your first try, so you may want to double check!
On the other hand, you should be thrilled if the survey says your assumptions are wrong! At this point we have invested the time to make a storyboard, think about our storyboard, talk about our storyboard, and the time to make and send a survey. If we find out our idea doesn’t work, we still have time to change our idea before we run out of time and money!
Think of how expensive it would have been to build this entire platform, only to find out the supply side doesn’t work!
After taking a few deep breaths to collect ourselves, it is now time to start thinking of another scenario where the product could still work. We have noticed in our own office that while Baking Bridget may appear once a quarter, twice a week there is a catered lunch meeting, and Lunch Meeting Larry always orders a few extra meals to cover dietary preferences and restrictions. Truth be told, I may be spilling some leftovers on my keyboard as I write this…
This storyboard shows the first three assumptions listed, an empirical test to validate or reject the hypothesis, and a potential change to our storyboard if we need to iterate.
Throughout our storyboards we intentionally littered our examples with lots of unproven hypotheses, since we believe in our business and in yours we are constantly making big assertions and assumptions that we will need to test and iterate on.
Other Big Assumptions We Made
There is even a desire for this product over just leaving free food in the kitchen which seems to work well enough …
HR would be the target customer to actually pay for this
IT would be willing with security concerns to actually deploy the application and then have the time to do this
Management wants employees spending more time eating cupcakes and less time making TPS reports
What other big assumptions did you see here?
Identifying, testing, and iterating over your product assumptions is one of the most important parts of product development. Very few business ideas or assumptions are correct, and it is only be methodically testing, learning and improving will you be able to create world class products.
My absolute favorite book on this subject is Lean Startup by Eric Ries , which I re-read regularly. He has taken this concept of incredibly tight feedback and testing loops and paired them with the solution of making a Minimum Viable Product (MVP). An MVP is the cheapest simplest possible solution/prototype to see how real customers react to your ideas, and it enables powerful learnings at a fraction of the cost.
After years of my own product development experiences I found the philosophies of MVPs and Agile Development echoed by what I had seen again and again, but didn’t have the terminology, or a 10,000 foot viewpoint to explain. When I, Aaron Sherman, created Storyboard That, my goal from day one was to empower product developers to
Be able to sit down and express their product ideas in a more natural, storytelling way
Make it simple to share ideas (think of how simple and clear the examples have been)
Get real feedback from stakeholders and potential customers
This is the MVP.
Pairing this with all of the exercises we have done, we now have the tools and knowledge to think like a customer, create simple prototypes, and get feedback to make sure you are not part of the 90% of startups that fail, 42% from building a product no one wanted (Forbes).
Now that you have created a large portfolio of storyboards, customer journey maps, personas, and all your other assets, take some time to look for your big assumptions. Think about what you would need to prove to know if your assumptions are true, and what you can do to test them.
After you have begun to compile a list, use the template below to document your findings and then go about the fun process of proving and disproving your hypotheses. I strongly encourage you to take at least an hour and write your thoughts down; it makes it much easier over time to verify you are truly learning and prevent revisionist assumption making!
Aaron Sherman (@AaronBenSherman) is the CEO and Creator of Storyboard That (www.storyboardthat.com) – the award-winning, world leader in digital storytelling technology. Aaron founded Storyboard That in 2012 after 10 years working the full gamut of product development roles (Developer, Project Manager, Product Owner, and Long Term Strategist) across three continents (North America, Europe and Australia) to fundamentally improve how products were internally prototyped and discussed.
Aaron has spoken as a guest Lecturer to MBA students at Northeastern, and with General Assembly leading workshops on Product Development.