Would this product create enough value for users in a way that benefits my business?
~ everyone who wants to validate a new product idea
But this questions is quite hard to answer and can cost quite some resources.
Let's break down this journey a little bit 👇
When starting out with a new idea, you might want to test for desirability.
Your hypothesis looks something like this:
I believe the customers are interested in my idea. I know that's true when the conversion rate on my landing page is > 1,5 %.
The problem with quantitative tests: You need to know what conversion rate you can expect and a lot of steps can go wrong:
• You can't acquire enough visitors
• You can't acquire the right visitors
• The copy of your landing page isn't convincing
You can't expect to nail everything in the first step.
This would be nuts.
If you were able to do that, you wouldn't need an experiment mindset.
So it's totally normal, that you'll need to learn first.
To capture your findings you need a traction model.
Disclaimer: Don't start with a quantitative experiment like a landing page test.
Always start with interviews to learn about the goals of the users.
• Do they care?
• How do they evaluate solutions?
This will improve the copy of your landingpage and doesn't cost any $.
So what's a traction model?
Traction is quantitative evidence of customer demand.
That sounds nerdy.
It just means, that you have to model the customer journeys in funnels and loops with numbers.
If you haven't done that before start with the Pirate Metrics.
The Pirate Metrics are named after their initial letters:
• Acquisition: #visitors
• Activation: # of users who experience value
• Revenue: # of paying customers
• Retention: # of customers who stay
• Referral: # of referred customers
AARRR like a pirate.
The next step is to guess the # of customers in each step.
• Model it to be viable.
• How many paying customers do you need?
That doesn't have to be exact. Why? Because your next step is to learn.
If you have no clue, conduct your first experiment and collect a baseline.
Most likely your baseline won't be viable yet.
Your customer acquisition costs are most likely too high.
So the next step is to learn which step of the journey could be improved.
You have 2 options:
• Trial & Error
• Conducting more interviews
Only then you conduct the experiment everybody knows:
I believe changing the value proposition on my landingpage will increase the conversion rate from 0,9% to >1,5%.
But still you aren't invalidating your idea.
You still examine ONE TWEAK to make your traction model viable.
Different levels of experiments:
Model
• Learn about the users goals
• Learn about the customer journey
• Find opportunities on this journey
• Find a bottleneck in your product
Optimize
• Evaluate if you created more value for users in a way that benefits your business?
That's a wrap!
If you enjoyed this thread:
1. Follow me @FrediVosberg for more about how to get started developing products in a data informed way 2. RT the tweet below to share this thread with other product people
Unexperienced founders and PMs affirm this question most of the time.
More experienced PMs know it's a significant risk.
After over 30 start-ups I have a method on hand to point new PMs and first-time-founders in the right direction.
The whole approach is about testing your business idea, which means testing hypotheses.
They are about assumptions that must be true for your product to succeed.
But most assumptions are too big, which leads to overconfidence and costly experiments.
The 4 biggest hypotheses for your product are:
• People want it (Desirability).
• People understand how to use it (Usability)
• You'll be able to develop it (Feasibility).
• It pays off (Viability).
They are confident about that. Otherwise, they wouldn't want to pursue it.
"Our management doesn't get agile! They want us to ship this list of features!"
I've talked to over 50 product managers who tried to convince management. They wanted to be empowered and trusted to achieve outcomes.
But management doesn't listen cause they don't talk business 👇
Management and PM are talking past each other.
Management cares about business and doesn't know how to manage by outcomes. So they communicate the features they think will achieve the business outcomes.
PMs yell at them: That's not agile! You can't define that in advance.
PMs on the other hand want to be empowered!
They know from books like Inspired by @cagan, that the best PMs don't implement features, but achieve impact through outcomes. You have to test first the riskiest assumptions.
Books like Inspired or Escaping the Build Trap picture how product management can be.
The reality of the vast majority looks different.
It's a target condition and we need to be patient.
But there are small steps PMs can do to move the way we work from output to outcomes 👇
The different things you could do can be sorted into two buckets:
1) Through Results
There are small things you just can do without asking for permission.
2) Through Convince
Bigger change happens, when you convince management. Your first results help with that.
1) Convince Through Results
• model for each feature in your backlog on which business metric it pays
• search for supporting/contradicting data
• start weekly customer interviews
• start the search for a leading indicator to measure the impact of your team