Note 23 | Runway Is Not Only How Many Months Remain. It Is How Many Chances to Change Remain
These are Robin Shen’s original reading notes and commentary, written in his own words after reading Eric Ries’s The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. They are not the original book, excerpts from it, or an official publication. Methods and concepts from the book are attributed to Eric Ries; other sources are identified where stated. For reference only; not investment advice.
English translation of Robin’s Chinese reading notes and commentary. Passages are paraphrased, not verified verbatim quotations from the original English edition.

How long the cash on the books can last certainly matters. In Chapter 8, however, Eric Ries asks how many genuine changes the remaining time will let the company complete. He places another measure of runway on the remaining opportunities to pivot. This does not cancel cash management. It is a reminder that if you only cut the work needed for learning, you may extend life on the calendar without increasing the chance of finding a sustainable business.
Runway is commonly estimated by dividing the cash balance by monthly net spending, so cutting costs and raising funds become the intuitive answers. Ries warns that indiscriminate thrift can also slow the feedback of Build-Measure-Learn. By contrast, obtaining the same validated learning in less time or at lower cost can give the company one more adjustment before resources run out. Whether saving money helps has to be judged together with the feedback that is lost.
Why do most founders always wish they had pivoted earlier? Ries points to three sources of resistance. Vanity metrics make people think the present situation is fine and that there is no need to change. Assumptions that are too vague allow any result to be explained as still hopeful. And finally there is fear: worry that the vision will be rejected by a crude version before it has been fully presented. Together, the three push a genuine test to a time when more has been invested and it is harder to turn back.
Testing earlier is therefore not a rush to give up. It is a way of avoiding being forced to change only when there are no options left. When Ries discusses Path, he stresses that the team, facing criticism from the tech press, still went back to listen to actual users and identify who the target audience was. In the book this story is still at a starting stage, not proof of a successful ending. What it supports is the courage to receive feedback, not ignoring every criticism or praising every form of perseverance.
IMVU offers a lesson in delay after success. As Ries recounts, the company already had a substantial business, yet gradually treated overall growth in the numbers as a source of security, and did not adequately face the diminishing returns of tuning the engine. Ries has an interest in IMVU. The point of this retrospective is that success can also relax the check on fundamental premises. A single experiment may look like progress, yet over a longer period still be insufficient to support the next stage.
The key is that the customer group had changed. The incompleteness early adopters could accept is not necessarily suitable for mainstream users. When a company promotes itself to a broader market, it cannot treat early success as a permanent standard of quality. Ries points out that what was needed was a customer segment pivot. Experience investments postponed in order to avoid waste may, in front of another group of users, become necessary work. The method of one stage cannot be treated as an eternal article of faith.
The remedy is also not merely to announce that quality now matters. As Ries narrates, the team went back to understanding users, reworked the design, and used ongoing comparisons to observe new and old versions. A large redesign and an experimental mindset are not in contradiction. The question is not whether the project is large or small, but whether it is still organized around a clear hypothesis. The experience is a reminder that the ability to pivot is useful not only before success. After a company has grown, it may also have to learn again.
I think “how many more times can we try” is a more actionable question than “how long can we last,” but the cost and difficulty of each trial should not be treated as the same. This is a management extension of my own, not a precise formula Ries provides. The conclusion is that cash and the speed of learning should be managed together: cut the work that truly slows validation, and also keep the critical feedback. That is not using thrift to buy more time for hesitation.
Three suggestions
Examine the effect of each cost-cutting measure on cash and on the speed of feedback, and keep the ability to obtain key evidence. Do not treat a fall in overall spending as an automatic improvement in the quality of runway.
Pick a key behavior whose optimizations over several rounds have shown diminishing returns, check it against a longer trend and a change in customer group, and agree in advance when the fundamental direction will be discussed again.
Write down the vision you most fear being rejected, and the premises within it that can be tested separately. Run a smaller experiment first, and distinguish feedback from target users from the judgments of an audience that is not the target.
#TheLeanStartup | Source: Chapter 8, “Pivot (or Persevere)”
These are reading notes and reflections based on my personal understanding. I recommend reading them alongside the original book for the full context.
Comments
What do you think? Share your experience or questions.
Sign in to comment, reply or like. Sign in / Sign up
Loading comments…