A few weeks ago we announced the launch of HealthBurger, our new product that sheds light on how small choices can have a huge impact on lifetime healthcare costs. Inspired by the Health 2.0 Dev Challenge, we decided to build something of our own ahead of the Health 2.0 Conference, but that left us with the question of deciding what to build.
We opted to document the process that we took to reaching final development, in hopes that some of this may be useful in your own work. Over the next few posts, we’ll tell you how we came up with the initial HealthBurger idea and then took that and refined it before going into our final implementation. If you have any questions about our process, let us know in the comments.
An Overview on the Health 2.0 Dev Challenge
The Birth of HealthBurger: The Pitch Party
When we decided to create something as a response to the Health 2.0 Dev Challenge, we were immediately presented with the problem of needing to decide on an idea that made us excited and what approach we wanted to take. Rather than keep that process to a handful of people, we opened up the ideation process to the entire company and hosted a “pitch party.”
We invited all of Substantial to gather over lunch and throw out some product ideas that would fit the scope of the challenge, presented in 2 minute pitches. The variety of ideas that came up were staggering, as was the variety in the ways those ideas were presented, with some having prepared slides and others just jumping up and speaking extemporaneously on their options.
Opening the process up had a number of positive results. First, it did the job of generating a dozen or so good ideas. While unfocused (as a good brainstorming session should be), having lots of ideas was a great way to “prime the pump” as we moved forward. These ideas ranged on a variety of axes (difficulty, playfulness, utility), forcing us to really consider what kind of app we wanted to build (a topic for the next post). By allowing input from everyone, it also created buy-in throughout the organization. Rather than what would become HealthBurger belonging only to a small group, it instead belonged to all of Substantial.
Here’s more about our pitch party process and what it meant for us.
In the next post of this series we’ll talk about how we took this plethora of ideas and reduced that to what would become HealthBurger.