Professional Documents
Culture Documents
This year, Silicon Valley Product Group visited our Bandwidth office to
provide an in depth session on “How to Create Products Customers Will
Love”. There were a ton of valuable lessons that I learned in those 2 days
but the biggest take away for me was taking a step back, before building
the MVP, and instead iterating through a product discovery process.
During this phase, it is purely about validating that the problem we are
trying to solve, really is a pain point and that the solution we are thinking
about is one in which our customers would be willing to pay for.
Let’s talk through an example of how this would apply to a new idea in
the B2B world. The background is that employees in offices
communicate on their desk and mobile phones every day as part of their
daily job. They communicate internally with their co-workers, as well as
externally with customers. The product hypothesis is that those
employees want an easy way to have a conversation, no matter where
they are or which phone they are on. So how do I go about performing
product discovery for this?
Listen! Ok, so this one needed a big ‘ol exclamation point because it is so
true. Really pay attention to what they are saying during our discussion.
Do they seem to relate to the questions and wholeheartedly start telling
me, yes indeed, employees want a better way to communicate than just
talking on their desk phone? Do they start asking what my new app is
and how it will work? Do they get excited? If so, then Boom. Game on. If
not, then I have to start thinking of how to make the necessary pivots so
that I can get that kind of reaction.
So, I made it all the way through. I have pretty much successfully
validated that there really is a problem that my product can solve, and
that there is a market for it. Bingo. So am I poised for product stardom?
Maybe.
Seriously? Why not yes? Didn’t I just prove that my idea solves a
problem? Yes, but now I must prove that my view of the solution will be a
hit as well.
It is now time to move on to building the MVP, the minimal viable product.
It is the simplest form of my proven hypothesis and a version of the
solution. For me, it might be an app that simply allows me to add my desk
and mobile work phones and have a conversation start on one and end
on the other. I now have to prove that this simplified version of how to
solve the problem is going to be the beginnings of an awesome product
— the golden ticket to their happiness and one that they will love and
buy.
This blog is the first in a series of blogs that I will be writing around “How
to Launch a New Product.” In future blogs I will be talking about iterating
on an MVP, beta testing, creating the right product marketing materials,
educating and empowering internal teams, declaring official “product”,
and scaling & growth. In the meantime, I can’t wait to hear your thoughts
on product discovery. Cheers.