3 ms·
I already have a copy and actually have it right by my laptop as I type this into the wee morning. The book is fantastic so far and I haven't been able to put i
by 9oliYQjP 15y ago
I already have a copy and actually have it right by my laptop as I type this into the wee morning. The book is fantastic so far and I haven't been able to put it down. I'm not reading it in a linear fashion but treating it like a reference book. It's literally a tool I've been able to put into action immediately. The book has a level of rigour to it that I really appreciate.
For instance, we're all familiar with the concept of runway on Hacker News right? How many of us think it's the amount of time that we have left or money left in the bank? Ries writes this on the subject:
"The true measure of runway is how many pivots a startup has left: the number of opportunities it has to make a fundamental change to its business strategy. Measuring runway through the lens of pivots rather than that of time suggests another way to extend that runway: get to each pivot faster."
How many entrepreneurs feel like they're barrelling down the runway and just crossing their fingers that something's going to change? "Apple will feature my iPhone app and I'll get a thousand users, I can just feel it!" Or, "I'm sure we can just get some angel funding, it's a hot market right now."
With Ries' view of the runway, you can literally rely on Pivotal Tracker to show you whether you're extending your runway or shortening it, and that's damn more effective than praying/crossing fingers/refreshing Google Analytics every half hour to see if your product has gone viral, etc.
EDIT: The book of course goes into when you should/shouldn't cut costs to extend runway and when you should pivot faster. It also explains what it means to pivot faster (e.g., validate your assumptions more quickly, not necessarily code features faster). I just wanted to clarify that given my PT remark above.