The Projects You Won’t Kill Are Running Your Company

Picture a Monday leadership meeting. The team reviews a new market expansion that has been underway for nine months. There are encouraging conversations. A revised deck. A potential partner who apparently loves the concept but hasn’t committed to anything. Someone asks whether it still deserves the investment. The founder says, “We’ve come too far to stop now.” Everyone nods, and the project survives another quarter. That sentence sounds like determination. Sometimes it’s just an expensive way to avoid admitting that the original bet hasn’t worked.

Founders get rewarded for starting things. We spot an opening, rally people, and make something happen before anyone else believes it can. That instinct builds companies. It also fills them with projects nobody knows how to end. The unfinished product extension. The partnership that never produces business. The expansion into a market where the economics still don’t work. Each one has a reasonable explanation for why it needs another month. Together, they consume the capacity your best opportunities need.

The cost isn’t only the money on the budget. It’s your operations lead spending Thursday untangling a side initiative instead of fixing delivery. It’s the engineering team maintaining something a handful of customers use. It’s the leadership meeting where twenty minutes disappear into the same update, again. You can see salaries and vendor invoices. It’s much harder to see the progress you never made because your strongest people were occupied protecting yesterday’s decisions.

After more than 25 years building, scaling, and exiting companies, I don’t believe persistence and good judgment are the same thing. You need both, but they do different jobs. Persistence helps you work through a difficult problem. Judgment tells you whether that problem still deserves solving. A tough quarter isn’t automatically a reason to quit. Neither is a year of effort automatically a reason to continue. The question is what you know now, and whether you would make the same investment today.

Start there. Take one stalled initiative and ask: If this project didn’t already exist, would we launch it this morning with the information we have? Not with the information we hoped to have. Not because someone important proposed it. Not because a competitor announced something similar. If the answer is no, the next question should be why you’re still funding it. There may be a legitimate contractual obligation or strategic dependency. Name it. Embarrassment is not a strategic dependency.

Then separate activity from evidence. Meetings, proposals, demos, and positive feedback can tell you that work is happening. They don’t necessarily tell you the underlying bet is sound. Suppose you’re testing a new customer segment. Evidence might mean three paid customers buying at a workable price, through a buying process you can repeat. If every sale requires custom development and founder heroics, you haven’t validated the expansion you planned. You may have discovered a different business, but that deserves a different decision.

Every meaningful experiment should begin with a short written agreement: what we believe, what would support that belief, what would weaken it, how much we’ll spend, and when we’ll decide. Give it an owner. Put the review date on the calendar before the kickoff. Match the timeline to the actual buying cycle or development cycle. An enterprise market test won’t produce meaningful answers in two weeks. But “enterprise takes time” cannot become permission to operate indefinitely without milestones.

At the review, make a real decision: continue, change, or stop. Continuing means the evidence supports another defined investment. Changing means you can explain what you learned and what you’ll test differently. Stopping means resources come off the project. “Let’s keep an eye on it” isn’t a fourth option if people are still working on it. And changing the plan should not mean moving the goalposts every time the original target gets uncomfortable. Record the new hypothesis and give it a boundary.

Be careful not to turn this into a quarterly purge of anything that hasn’t produced immediate revenue. Security improvements, leadership development, core infrastructure, and other necessary investments need different measures. Some work protects the business. Some creates options that take time to mature. The point is not that everything must pay back quickly. The point is that you should know why you’re doing it, what progress looks like, and what conditions would cause you to reconsider.

The people side matters just as much. If stopping a project damages the owner’s reputation, your team will learn to hide bad news and manufacture encouraging updates. Make it safe to tell the truth early. Thank people for useful learning. Separate the quality of their work from whether the original hypothesis proved correct. Then close the loop properly: handle customer commitments, document what’s reusable, end unnecessary spending, and give affected employees a clear next assignment. Don’t leave them maintaining a project you supposedly killed.

Founders have to go first. If your pet initiative is exempt from scrutiny, nobody will believe the process is real. Put your own bet on the table. Explain what you expected, what happened, and why the next dollar belongs elsewhere. You don’t lose credibility by updating a decision when the evidence changes. You lose credibility when everyone can see the problem and has to pretend they can’t because your name is attached to it.

This week, choose one project that keeps returning to the agenda without moving the business forward. Don’t ask for another status update. Ask for a decision, supported by evidence. If you stop it, name exactly where the released time and money will go. Otherwise, the empty space will fill itself. Your company doesn’t need to preserve every idea you once believed in. It needs you to put today’s resources behind the opportunities that deserve them now.