A founder we work with sent us a list of 14 things she wanted to launch in Q2: a lead magnet, a webinar series, a new service line, a partnership program, a brand refresh, a newsletter relaunch, a content calendar, a hiring plan, a team retreat. The list went on. She wanted to know which three she should prioritize.
We told her none of them.
The problem wasn’t that she had too few good ideas. The problem was that her team was already running about 30 active initiatives, of which maybe three were getting real attention, and adding more wasn’t going to help. The fix was the opposite. Cut the list to five. Finish them. Then talk about Q3.
This conversation isn’t unusual. It’s the most common one we have. And the diagnostic move it requires, asking what to stop doing rather than what to start doing, is the move most growing companies are structurally unable to make on their own.
The Add-By-Default Reflex
Every growing company defaults to adding. There’s a structural reason for it. Adding feels like progress. New initiative launches generate energy.
They give the team something to rally around. They give the founder something to talk about in the next investor update or board meeting. They make the company look ambitious.
Subtracting feels like the opposite. Killing a project means admitting the project didn’t work. It means having a conversation with the person who championed it. It means explaining to the board why a previously announced strategic priority is no longer one. It means reckoning with the resources that were spent on something that won’t ship. None of those conversations is fun, and most companies don’t have a structured process for having any of them.
So things accumulate. Every quarter brings new priorities. Old priorities don’t get retired; they just get quieter. The team’s attention gets thinner. The number of active initiatives keeps growing while the percentage of them actually shipping keeps shrinking. We call this scattered execution, and it’s the single most common pattern we see across engagements.
The cost of the add-by-default reflex shows up in the team. Microsoft’s 2025 Work Trend Index report found that one in three employees now say the pace of work over the past five years makes it impossible to keep up. The pace problem isn’t usually about volume of effort. It’s about the volume of priorities. A team that’s trying to do 30 things at once can’t keep up with any of them, no matter how hard it works.
The Anatomy of an Unfinished Pile
Scattered execution doesn’t look like chaos from the inside. It looks like productivity. People are working on things. Meetings are happening. Documents are being created. Slack channels are active. The visible signal is motion.
What’s missing isn’t motion. It’s completion.
A typical pile we audit looks something like this: twenty to forty named initiatives across the company, maybe a quarter of them with a clear owner, maybe half of those actually being worked on this month. Of the ones being worked on, most are stuck on a decision someone hasn’t made or a dependency on a team that doesn’t know it’s been depended on. The ones moving forward are usually doing so because one person is heroically dragging them through the system.
Underneath the pile, three patterns repeat.
The first is zombie projects that no one’s actively moving but no one’s also retired. They consume calendar space, slide-deck space, and mental space without producing anything. They survive because killing them requires a coordination conversation that no one has time to have.
The second is the priority that has no owner. Every leadership team can list its top five initiatives. Most of those leadership teams cannot tell you who’s accountable for any of them. The initiative is “ours,” which in practice means it’s no one’s, which means it doesn’t move.
The third is the project that’s been redefined three times since it launched. The original goal was X. Then the team realized X was harder than expected, so the goal became Y. Then market conditions shifted, so it became Z. Each redefinition was reasonable in isolation. The cumulative effect is that the project has now been “in progress” for nine months without producing anything anyone can point to.
Why Killing Things Is So Hard
The reason scattered execution is so persistent isn’t that founders don’t see it. Most founders see it clearly when it’s described to them. The reason it persists is that the act of subtracting requires authority, structure, and a forum, and most growing companies don’t have any of the three.
It requires authority, because killing a project means saying no to the person who proposed it. In a small or mid-sized company, that person is usually still in the room. Saying no to them costs political capital. Saying no to them repeatedly, across many initiatives, costs more political capital than most leaders have.
It requires structure, because there has to be a recurring moment when the question gets asked. Not “what should we add this quarter,” which everyone asks, but “what should we retire this quarter,” which almost no one asks. Without a structured retirement process, the default is accumulation.
It requires a forum, because the conversation is uncomfortable. It works best when it happens in a setting designed for it, with an agreed-upon framework for the decision, and with everyone in the room understanding that retirement is a normal part of the operating rhythm, not a personal indictment. Without a forum, the conversation either doesn’t happen, or happens informally between two people who then have to socialize the decision to everyone else, which is slower and more expensive than just doing it together in the first place.
Most growing companies have a launch process. Almost none have a retirement process. That asymmetry is the structural reason the pile keeps growing.
What Happens When You Subtract
The first thing that happens when a team retires half its initiatives is that the team panics, briefly. The visible signal of productivity drops. Calendars empty out. Slack quiets down. People who were used to being in three meetings about three different things are now in one meeting about one thing. It feels, for a beat, like the wheels have come off.
Then the second thing happens: The remaining initiatives start moving. Faster than expected. Cleaner than expected. Not because the team is working harder, but because the cognitive overhead of holding twenty things in mind has been replaced with the focus of holding five. Decisions get made in the same week they get raised. Handoffs land cleanly. People can answer the question “what are you working on this week?” without a long pause.
The third thing is harder to see but more important. The team starts to trust the process. They’ve experienced a quarter where decisions actually got made and projects actually shipped. The pattern starts to feel possible rather than aspirational. The next time the founder is tempted to add a fourteenth initiative to a working list of five, someone in the room is now equipped to ask, “what are we removing first?”
That question is the diagnosis. It doesn’t sound like much. It is the difference between a company that compounds and a company that spins.
The Diagnostic Question
When we walk into a fractional growth and operations engagement at Lúcida, the first question we ask isn’t what the company should do next. It’s what the company should stop doing now.
The answer is almost never zero. There’s almost always a list of initiatives that have outlived their usefulness, priorities that no one’s actually moving, and meetings that exist because they used to. Surfacing the list is the first hour of work. Building the structure to retire things on a regular cadence, and making retirement a normal, low-emotional-stakes part of how the company runs, is the rest of the engagement.
You don’t need more ideas. You probably have more ideas than your team has the capacity to absorb. What you need is the discipline of finishing, the structure of retiring, and the operating rhythm that makes both of those things normal rather than heroic.
That’s the work most companies skip. It’s also the work that, more than any new tool or hire or initiative, separates the companies that grow from the companies that just get busier.