Love this, Kenny. One thing I might add to this is learning to test your hypothesis as quickly as possible. It’s going to hurt a lot more if you spend weeks or months working on something before you put it out in the world and test it. Having led product at early stage startups for the last decade, something my team and I always ask is “what’s the simplest thing we can do to see if this idea has legs?”
I realized this morning I forgot to add this very important point. Thanks for bringing it up.
You add more of your hopes and dreams the more you spend on an idea. I think it makes sense, you don’t want your efforts to go to waste!
Now, I’m curious, even with this question, how was it to get you and your team to scope down the idea and make sure you were not tackling something too complex at first?
Your post is 🎯 . Building through experimentation liberates you and enables progress.
I learned the power of experimentation while working at Amazon. All teams are encouraged to take experimentation goals with clear hypothesis.
At any given time, multiple experiments are running. Data is gathered. Experiments showing showing positive signs turn into products. The ones that fail are useful learnings.
I experiment with features in my apps. I don’t completely automate any new features unless I see traction. For example I introduced subscription plans in my app early last month.
And I waited to a month to see if the plans were being adopted. This month I finally see traction and I will automate subscription handling.
I commend you for that! I see so many people reaching out to automate processes that haven’t been used once before. I’m always reticent to tackle those because the potential to be a waste of time for me and them is too high.
Love this, Kenny. One thing I might add to this is learning to test your hypothesis as quickly as possible. It’s going to hurt a lot more if you spend weeks or months working on something before you put it out in the world and test it. Having led product at early stage startups for the last decade, something my team and I always ask is “what’s the simplest thing we can do to see if this idea has legs?”
I realized this morning I forgot to add this very important point. Thanks for bringing it up.
You add more of your hopes and dreams the more you spend on an idea. I think it makes sense, you don’t want your efforts to go to waste!
Now, I’m curious, even with this question, how was it to get you and your team to scope down the idea and make sure you were not tackling something too complex at first?
Your post is 🎯 . Building through experimentation liberates you and enables progress.
I learned the power of experimentation while working at Amazon. All teams are encouraged to take experimentation goals with clear hypothesis.
At any given time, multiple experiments are running. Data is gathered. Experiments showing showing positive signs turn into products. The ones that fail are useful learnings.
Thanks, Kunal! That must've been a cool experience.
How are you using this approach in your project nowadays?
I experiment with features in my apps. I don’t completely automate any new features unless I see traction. For example I introduced subscription plans in my app early last month.
And I waited to a month to see if the plans were being adopted. This month I finally see traction and I will automate subscription handling.
I commend you for that! I see so many people reaching out to automate processes that haven’t been used once before. I’m always reticent to tackle those because the potential to be a waste of time for me and them is too high.