A thread of 7 things you already know about discovering, testing, and shipping products
(but tend to forget at times)
👇🏾
(but tend to forget at times)
👇🏾
1/
Spending some time upstream to properly understand the problem & the domain will save you from spending a lot of time downstream wondering why people aren’t buying your product.
You can’t learn everything upfront, but you can learn many things upfront.
Spending some time upstream to properly understand the problem & the domain will save you from spending a lot of time downstream wondering why people aren’t buying your product.
You can’t learn everything upfront, but you can learn many things upfront.
2/
If you are talking to customers with a certain product idea already in your mind, you will usually manage to find great reasons why it makes sense to build that idea.
Starting with a blank slate keeps a product manager’s biggest enemy—confirmation bias—at bay.
If you are talking to customers with a certain product idea already in your mind, you will usually manage to find great reasons why it makes sense to build that idea.
Starting with a blank slate keeps a product manager’s biggest enemy—confirmation bias—at bay.
3/
When you are running an experiment, you need to specify your objectives, success/failure criteria, and decision tree upfront.
Without these things, it becomes a Validation, not an Experiment.
When you are running an experiment, you need to specify your objectives, success/failure criteria, and decision tree upfront.
Without these things, it becomes a Validation, not an Experiment.
4/
If you have just shipped a product, but don’t yet have a way of getting usage data for the product, you have not really shipped the product. You have just shipped functionality.
Shipping a product requires shipping a way to understand how people are using it.
If you have just shipped a product, but don’t yet have a way of getting usage data for the product, you have not really shipped the product. You have just shipped functionality.
Shipping a product requires shipping a way to understand how people are using it.
5/
For a self-respecting product person, very few feelings are as embarrassing as the feeling of having to tell a reasonable customer that the product does not yet support their perfectly reasonable need.
That’s why face-time with customers can be so motivating.
For a self-respecting product person, very few feelings are as embarrassing as the feeling of having to tell a reasonable customer that the product does not yet support their perfectly reasonable need.
That’s why face-time with customers can be so motivating.
6/
The best way to figure out what’s wrong with your product is to have the people working on the product use the product regularly. Try to get as close as possible to how your users use it.
No amount of user empathy can eclipse our self-empathy.
The best way to figure out what’s wrong with your product is to have the people working on the product use the product regularly. Try to get as close as possible to how your users use it.
No amount of user empathy can eclipse our self-empathy.
7/
Sometimes, despite rigorous strategy & relentless execution, our product will fail. The failure won’t define us & won’t matter in the long run. But what we choose to learn from it will define us & will matter in the long run.
Learn a lot, share a lot & you will succeed a lot
Sometimes, despite rigorous strategy & relentless execution, our product will fail. The failure won’t define us & won’t matter in the long run. But what we choose to learn from it will define us & will matter in the long run.
Learn a lot, share a lot & you will succeed a lot
Back to the top of this thread:
https://twitter.com/shreyas/status/1352860350719303681
• • •
Missing some Tweet in this thread? You can try to
force a refresh
