How would you then define what gitlab is doing. Namely a "minimal viable change". it just brings the same notion to features? So to go out with the smallest feature possible. Still good quality and good design, dadadada.. but only as much to test your assumption for its demand (aka desireabiltiy)? And if you see it actually is desirable you double down? I mean now that i wrote it it just sounds so obvious but tell that to people doing product who, in my experience, so often go down the waterfall route and only ship when its perfect, or in essence only shipping iteratio number x (where x > 1)... and by it totally leaving out their chances to not over engineer and not implement "waste" (aka stuff noone actually likes or wants).
Thanks Aakash for sharing great insights. Super helpful. I really loved how Jeff tested the hypothesis of selling books online without having whole lot of investment /infra ready.
Google Docs competing again MS Office is a great example to know how one can disrupt the market despite being a monopoly in the market.
Coincidentally I read most of the books in this list. Seems like I'm on the right track :') Thanks for sharing the list & great content (as always) Aakash.
How would you then define what gitlab is doing. Namely a "minimal viable change". it just brings the same notion to features? So to go out with the smallest feature possible. Still good quality and good design, dadadada.. but only as much to test your assumption for its demand (aka desireabiltiy)? And if you see it actually is desirable you double down? I mean now that i wrote it it just sounds so obvious but tell that to people doing product who, in my experience, so often go down the waterfall route and only ship when its perfect, or in essence only shipping iteratio number x (where x > 1)... and by it totally leaving out their chances to not over engineer and not implement "waste" (aka stuff noone actually likes or wants).
Very cool breakdown. Refreshing.
Thanks Zishan!
Thank you Aakash for your 'How Google Docs took on Microsoft Office' post.
These are great insights:
1. A reliable way to disrupt an incumbent is a cheaper product with less, but specific, performance.
2. Sticking to core differentiators creates an effective wedge
thanks
So happy to hear!
Thanks Aakash for sharing great insights. Super helpful. I really loved how Jeff tested the hypothesis of selling books online without having whole lot of investment /infra ready.
Google Docs competing again MS Office is a great example to know how one can disrupt the market despite being a monopoly in the market.
Super appreciate you reading!
Coincidentally I read most of the books in this list. Seems like I'm on the right track :') Thanks for sharing the list & great content (as always) Aakash.
Great minds read alike :)
The book list at the end is not to be overlooked, great curation
Appreciate that!
So happy to hear it!