Currently, one of the things I am trying to do on our new MedTech venture is to build a roadmap of experiments to run before we get to the MVP itself.
Why am I doing that, you may want to ask?
Because I think it is super important to do whatever it takes to make sure that we can deliver some sort of tangible value from day 1 with our MVP. Nonetheless so because we’re in MedTech and because we’re dealing with a serious medical issue. We simply need to get it right.
But also because I think it makes overall sense as an approach. In fact I think it might even make better sense than to work on a more regular product roadmap at this stage.
Simply because at the stage we’re currently at there are so many unknowns and associated assumptions about where we might take this that the most robust roadmap, we can have, is the one articulating what we don’t know and thus need to find out more about.
But does that make it easier to do a roadmap of experiments than a more normal product roadmap?
After all there are a ton of different experiments, you can run at any given point in time, and the trick is to figure out – or at the very least have an idea – which ones are going to give you most bang for the buck at any given moment in time. And where you take it from there – depending on how the experiment goes.
It’s a super interesting exercise in doing a blueprint for your activities while trying to make sure that you get to that ultimate goal of the experiment series; feeling pretty confident – on a data based basis – what should go into the MVP and hopefully set you off on a good trajectory for startup success.