The Startup Industry Has Forgotten How to Wait

9 min read

The Startup Industry Has Forgotten How to Wait

Iniobong Uyah

August 29, 2026

9 min read

Industry Insights

Share this article

In the race to move fast, founders may be losing the patience, resilience and persistence required to build something that lasts

For years, startup culture has celebrated speed. Launch quickly. Test quickly. Fail quickly. Iterate quickly. Raise capital quickly. Scale quickly. The language is so familiar that it's easy to forget speed was never supposed to be the destination. It was supposed to be a tool.

There's a good reason startups value speed. Young companies operate with limited information and limited resources. A founder who can test an assumption in days instead of months learns faster and avoids wasting time. Rapid experimentation can expose a weak product before the company commits too much money to it.

But a useful principle becomes a harmful one when it's applied without judgment. Speed can help a company learn. It can also encourage a company to move before it understands what it's doing. Some of the world's most durable products weren't created by founders in a hurry.

When Speed Became a Measure of Success

Somewhere along the way, speed stopped being merely a method and became a measure of entrepreneurial virtue. Founders are encouraged to show how quickly they can launch, acquire users, raise funding, expand into new markets and increase revenue. Investors naturally care about growth because venture investing depends on a relatively small number of companies producing very large outcomes. Research on blitzscaling describes an approach that prioritizes extremely fast growth over efficiency under uncertainty.

There's nothing inherently wrong with that strategy. For some companies and markets, moving quickly can be decisive. But when speed becomes the dominant objective, founders can begin to mistake activity for progress. A company can launch several products in a year and still have no product customers truly need. It can double its headcount and become less productive. It can raise millions and still have no durable business model.

Growth is valuable. Speed is valuable. Neither is a substitute for building something that works.

The Founder Traits We May Be Undervaluing

Older stories about entrepreneurship often celebrated a different set of qualities: persistence, patience, craftsmanship, resilience, and the willingness to remain with a difficult problem long enough to understand it. These qualities are less glamorous than a rapid funding announcement. They don't always produce impressive monthly metrics, and they're difficult to put on a pitch deck.

But they matter precisely because entrepreneurship is full of periods when results don't arrive on schedule. Customers may not understand the product immediately. A technology may require years of development. A distribution channel may take time to build. A founder may need to hear no repeatedly before finding the right partner or market.

Harvard Business School professor Tom Eisenmann's widely cited research on why startups fail found that failure rarely traces to a single cause. His analysis of hundreds of founders and investors identified recurring, overlapping patterns, including weak support from investors and partners, and skipping the customer research that lean methodology assumes founders do. In other words, speed alone doesn't determine outcomes, and neither does persistence alone. What matters is understanding the actual conditions that produce failure.

Then There Was James Dyson

Consider the story of James Dyson. In 1978, Dyson became frustrated with the declining performance of his vacuum cleaner. He discovered the bag was clogging with dust and reducing suction. He had encountered cyclone technology in an industrial setting and wondered whether the same principle could be applied to a vacuum cleaner.

That sounds like the beginning of a familiar startup story: identify a problem, find an unusual solution, build a prototype. But then came the part that modern startup culture can find difficult to celebrate. Dyson kept working on it.

By Dyson's own account, and confirmed on the company's official history, it took 5,127 prototypes and three years of development to reach a working design, followed by another two years spent trying to find a company willing to license the technology. European manufacturers rejected the idea, fearing it would undercut their profits from replacement bags, so Dyson launched the G-Force in Japan in 1983 before eventually building his own manufacturing operation and releasing the DC01 in the UK a decade later, in 1993.

The number 5,127 isn't impressive because it's large. It matters because each prototype represented another attempt to solve a technical problem that hadn't yet been solved to Dyson's satisfaction.

What If Dyson Had Been Obsessed With Speed?

Imagine applying today's startup vocabulary to Dyson's early work. The first prototype works. Launch the minimum viable product. Raise capital. Acquire customers. Scale. Move on.

That approach might have produced a company sooner. It might also have produced a much worse product.

Dyson's story demonstrates something the phrase "fail fast" can obscure: not every failure is evidence an idea should be abandoned. Sometimes failure is simply information about how the current version of the idea needs to change. Dyson didn't repeat the same attempt thousands of times. He changed the design, learned from what didn't work, and kept moving toward a defined technical objective. His persistence was useful because it was paired with iteration.

The Problem With "Fail Fast"

Few startup phrases are more widely repeated than "fail fast." It contains a valuable idea: founders shouldn't spend years defending an assumption that evidence has already disproved. But taken literally, the phrase can become an excuse for impatience.

Some ideas deserve to be abandoned quickly. Others deserve to be developed slowly. The challenge is knowing which is which. A founder should be willing to kill a product when customers repeatedly demonstrate they don't want it. But a founder should also recognize that some products fail because the execution is weak, the technology is immature, or the market hasn't yet been reached correctly.

The better principle isn't simply to fail fast. It's to learn quickly and persist intelligently: knowing the difference between evidence that a problem isn't worth solving and evidence that the current solution isn't good enough.

Speed and patience aren't opposites. A founder can move quickly while remaining patient about the ultimate outcome, responding to customer feedback within a day while understanding that building customer trust may take years. The problem begins when a short feedback cycle is mistaken for a short development cycle. Some things can be tested in a week. Some things can't. Speed is useful when the objective is learning. Patience is necessary when the objective is mastery.

The Venture Capital Clock

The startup ecosystem also operates under a financial clock. Once venture capital enters the picture, founders aren't simply building a product. They're operating within a system of investment rounds, growth expectations, competitive pressure and eventual investor returns.

That creates understandable pressure to grow quickly. Research on digital entrepreneurship has found that investors can push portfolio companies toward rapid growth because venture investing depends heavily on a relatively small number of successful outcomes. Blitzscaling takes this logic further by deliberately prioritizing rapid growth over efficiency when the opportunity is large and the market is uncertain, and separate research identifies organizational growing pains when companies expand faster than their internal systems can develop.

The problem isn't venture capital, and it isn't growth. The problem occurs when the investor's clock becomes more important than the customer's clock. A company may need years to develop a difficult technology. If the business is forced to behave as though everything important must happen within months, the founder may end up optimizing for milestones rather than substance.

The Valley Where Nothing Seems to Happen

Every serious venture eventually encounters a period when the outside world sees very little progress. The product isn't ready. Revenue is modest. The market is uncertain. The founder has already invested years. There's no major funding announcement to make and no impressive growth chart to share. There's simply work.

This is where resilience becomes valuable. Resilience doesn't mean refusing to change. It means being able to absorb setbacks without allowing them to destroy your judgment. A resilient founder can hear no without assuming the idea is worthless, encounter a failed experiment without treating it as a personal failure, and change direction without abandoning the underlying mission at the first sign of difficulty.

Stanford's Graduate School of Business has built entire programs around this idea, teaching that psychological safety, a climate where people feel comfortable failing, speaking up and taking risks without fear of judgment, is what actually enables teams to learn from setbacks rather than avoid them. The point isn't to glorify failure. It's to understand that learning from setbacks is part of developing something new.

The Danger of Building for the Pitch Deck

There's another consequence of the obsession with speed: founders can begin building for the story they'll tell about the company rather than for the company itself. Growth looks good on a slide. Funding looks good in a headline. A rapidly expanding team looks impressive. A new market launch sounds exciting.

Quality is harder to demonstrate. So is customer trust, operational discipline, and a product that quietly gets better for five years. This can produce dangerous substitutions:

• Growth instead of retention

• Users instead of useful users

• Funding instead of validation

• Valuation instead of value

• Launches instead of product quality

• Headcount instead of productivity

A company can become very good at looking like a startup while becoming less good at becoming a durable business.

What Dyson Teaches Modern Founders

1. Persistence Needs a Reason

Dyson wasn't stubborn for the sake of being stubborn. He was trying to solve a clearly defined problem: how to maintain suction without relying on a conventional vacuum bag.

2. Iteration Is Not the Same as Failure

A prototype that doesn't work can still be valuable if it reveals something about the problem.

3. Quality Sometimes Takes Time

There are technical problems that can't be solved simply by moving faster between meetings.

4. Rejection Isn't Necessarily a Verdict on the Idea

Dyson's licensing attempts were rejected across Europe before the product eventually found a route to market in Japan.

5. Persistence Is Most Powerful When Combined With Learning

The lesson isn't to keep doing the same thing until something magically works. It's to keep improving the approach while remaining committed to a problem worth solving.

The Founder Playbook for a Faster World

None of this means founders should become slow. The better approach is to become deliberate about what deserves speed and what deserves time.

Move quickly when:

• You're testing an assumption

• A customer has given you clear feedback

• An experiment can cheaply reduce uncertainty

Slow down when:

• The issue is product quality

• The technology is genuinely difficult

• You're making a decision that will shape the company for years

• You're tempted to expand before the organization can support it

Most importantly, learn to distinguish urgency from impatience. Urgency comes from the problem. Impatience often comes from the founder's fear of falling behind.

The Competitive Advantage of Staying Power

Perhaps the most important question for a founder isn't "How quickly can I build this?" It's "How long am I prepared to work intelligently on this if it takes longer than I expected?"

That's a very different question. It forces the founder to think about resources, conviction, evidence, and the difference between persistence and stubbornness. It also forces an uncomfortable recognition: some of the most valuable work in a company may happen during periods when almost nobody outside the company is paying attention.

Dyson's customers ultimately saw the finished machine. They didn't see the thousands of prototypes that preceded it. Investors see the company that eventually succeeds. They rarely see every rejection that came before it. Markets see the breakthrough. They rarely see the years of refinement underneath it.

Conclusion: Know When to Move and When to Stay

The startup industry doesn't need less ambition, less experimentation, or founders who move less quickly. It needs a better understanding of what speed is for.

Speed should help a founder discover the truth faster. It shouldn't pressure the founder to manufacture progress before the underlying work is ready.

The founders who build enduring companies will still need to move quickly. But they'll also need something less fashionable: the patience to let difficult problems take the time they require, the resilience to survive periods of uncertainty, and the persistence to keep improving when the world has stopped paying attention.

James Dyson's story is powerful for exactly that reason. The memorable number is 5,127 prototypes. But the deeper lesson is what happened between the first prototype and the last one. He kept learning. That may be the quality modern startup culture most needs to recover: not the ability to move fast at all costs, but the judgment to know when speed creates progress, when patience creates quality, and when persistence is the difference between an interesting idea and something that lasts.