Most founders I’ve worked with can generate ideas faster than they can execute them. The constraint is never the ability to start something new. It’s the ability to stop doing something that once mattered, or that still generates revenue, or that someone on the team built their role around. I’ve watched this play out hundreds of times, and the decision to stop is almost never clean or obvious.
The friction doesn’t come from lack of data. Founders usually know which initiatives are underperforming. They can see the metrics. They understand the opportunity cost. What they struggle with is the gap between knowing something should stop and actually stopping it. That gap is where most of the real work happens.
I’ve noticed that the founders who navigate this well don’t rely on a single decision-making framework. They tend to layer different kinds of thinking depending on what they’re evaluating. A product line that’s profitable but stagnant gets assessed differently than an internal process that’s become a bottleneck. The stakes are different. The reversibility is different. The emotional attachment is different.
When Revenue Obscures the Real Problem
One pattern I see repeatedly: a founder keeps a revenue stream alive because it funds other work, even though it consumes disproportionate energy. A SaaS founder might have a legacy product tier that generates 8% of revenue but requires 30% of support load. The math is clear. But the founder hesitates because that 8% pays for one engineer’s salary, and cutting it means restructuring headcount or finding revenue elsewhere.
The decision doesn’t happen in a spreadsheet. It happens when the founder recognizes that the energy cost has become a constraint on what’s possible. Sometimes that recognition takes months. Sometimes it takes a key person threatening to leave because they’re tired of maintaining legacy code. The data was always there, but the motivation to act wasn’t.
I’ve also seen the reverse: founders who kill something profitable too quickly because they’re bored with it or because a new opportunity feels more exciting. That’s rarer, but it happens. Usually it’s a founder who has strong pattern-recognition skills but weaker patience for the grinding work of optimization. They see the new thing as more interesting, and they underestimate how much the old thing still matters to the business.
The Team Attachment Problem
Stopping something often means someone’s role changes or disappears. That person might be excellent at their job. They might have been with the company for years. The decision becomes less about business logic and more about how to handle that conversation, and what comes next for that person. I’ve seen founders delay stopping things for months because they were genuinely uncertain how to restructure the team without creating resentment or losing someone they valued.
The best founders I’ve worked with tend to separate those two decisions. First, they decide whether the thing should stop based on business logic. Second, they decide what happens to the person. Those are different questions with different answers. But many founders try to solve both at once, which often leads to keeping the thing alive as a way to avoid the harder conversation.
There’s also a version where the team member is the one who should stop doing something, but they’re not ready to. A founder might realize that a particular person is spending 60% of their time on a task that could be automated or outsourced, but that person has built their identity around that work. The founder knows the person is capable of more interesting work, but the person isn’t convinced. Stopping the old thing means the founder has to push the team member into something unfamiliar, and that creates friction.
Timing and the Threshold Question
I’ve noticed that founders don’t stop things when they’re at their worst. They stop them when they’re stable enough that stopping feels safe, or when something new is urgent enough that the old thing becomes obviously expendable. It’s rarely a decision made in crisis. It’s usually made during a period of relative stability when the founder has enough breathing room to think strategically.
The threshold question is often: “What would need to be true for me to stop this?” For some initiatives, the answer is straightforward. For others, it’s murky. A founder might realize they’re waiting for permission that will never come, or for conditions that won’t materialize. At that point, the decision becomes less about the initiative itself and more about the founder’s willingness to act despite uncertainty.
I’ve also observed that founders tend to have a personal stopping threshold that’s different from what the business logic suggests. Some founders are naturally conservative and need more evidence before they kill something. Others are quick to cut. Neither is objectively better, but it shapes which initiatives survive and which don’t. A conservative founder might keep an underperforming product alive longer than optimal, but they also avoid cutting things that could have been turned around with more time. A quick-cutting founder moves faster, but they sometimes abandon things too early.
The Reversibility Calculus
Founders who are skilled at this tend to think carefully about reversibility. Some decisions to stop are genuinely irreversible. You can’t easily restart a product you’ve shut down if you’ve let the team disperse and the codebase atrophy. Other decisions are more reversible. You can pause a marketing channel and restart it in a few weeks. You can reduce investment in something without fully eliminating it.
The reversibility of a decision often determines how much evidence a founder needs before acting. If stopping something is easily reversible, the bar for stopping is lower. If it’s hard to restart, the bar is higher. I’ve seen founders use this thinking to move faster on reversible decisions and be more cautious on irreversible ones. That’s usually a sound instinct.
What’s interesting is that founders often misjudge reversibility. They think something is irreversible when it’s actually not, or vice versa. A product shutdown feels permanent, but if the market changes, you can rebuild it. A team restructuring feels like it should be permanent, but people can be rehired or moved back into roles. Overestimating irreversibility leads to unnecessary caution. Underestimating it leads to reckless cuts.
The Emotional and Narrative Layers
There’s always a story attached to the thing a founder is considering stopping. Maybe it was the first product they built. Maybe it represents a pivot they made years ago. Maybe it’s something they’re proud of, even if it’s not working. The narrative weight of that thing often matters more than the metrics.
I’ve watched founders keep things alive partly because they can’t bear to admit that the original bet didn’t work out. That’s not irrational. It’s human. The decision to stop is also a decision to accept that something you invested in didn’t pan out. Some founders process that quickly. Others need time.
The skilled founders I’ve observed tend to separate the narrative from the decision. They acknowledge the thing that was built, they recognize the effort that went into it, and then they make a clear-eyed call about whether it should continue. They don’t need to pretend the old thing is still working to justify having tried it in the first place.
What I’ve seen less often, but what seems to work well when it happens, is a founder who can articulate why they’re stopping something in a way that doesn’t require the original bet to have been wrong. Sometimes you stop something because the market moved, not because you built it poorly. Sometimes you stop something because the company’s priorities shifted, not because the initiative failed. That framing makes the decision feel less like a failure and more like a natural evolution.
The founders who struggle most with stopping tend to be the ones who treat every decision as permanent and final. They see stopping something as a verdict on their judgment. The ones who move more easily tend to see stopping as a temporary state, a response to current conditions, something that could theoretically change if conditions change. That mindset seems to make the actual decision easier to execute.
