Most stuck initiatives don't need a strategy off-site. They don't need a consulting engagement. They don't need a board memo or a new executive sponsor.
What they need is a structured 90-minute conversation that ends with a real decision — build, buy, or kill — and a person whose name is on it.
The reason this conversation doesn't happen in most companies isn't that the leadership team doesn't know how to make decisions. It's that the conversation gets routed through the wrong frame. The team treats it like a planning exercise, so it gets scheduled into a half-day workshop that gets postponed twice. Or it gets routed through the board, where it becomes a quarterly agenda item that nobody owns between meetings. Or it gets handed to the function leader closest to the initiative, who can't be objective about it.
A stuck initiative is a leadership decision. It needs ninety minutes, a small room, and a framework that forces clarity.
Here's the framework I use.
Before the conversation: prep the artifact
The biggest mistake teams make is showing up to this conversation cold. The leadership team walks into the room, someone says "okay, let's talk about Project X," and the next fifty minutes get burned re-establishing context that everyone has different versions of.
Before the meeting, one person — usually the function leader closest to the initiative, sometimes the chief of staff, often a Fractional CSO — prepares a one-page artifact with four sections.
- Current state, told honestly. What has actually been delivered. What's actually working. What's actually missing. What the metrics actually look like, not what the dashboards have been calibrated to show. This section is the hardest to write because it requires the closest person to the initiative to write something that doesn't read as a defense.
- Original strategic intent. What the company committed to when this initiative was launched. What problem it was supposed to solve. Why it was strategically important. Pulled from the original business case, the launch memo, the board materials — wherever the original commitment lives.
- What's changed. What's different now versus when the initiative was launched. New competitive dynamics, new technology options, new customer signals, new internal capacity. The world has moved since the launch. Name how.
- Three options on the table. Not "continue with adjustments." The actual options: build (continue, with named investment and timeline), buy (acquire, partner, or contract for the outcome), kill (stop the initiative and redeploy the people and capital). Each option named, with a sentence on what it commits the company to.
That artifact is the input to the conversation. It gets sent to the participants twenty-four hours in advance. No surprise reveals. No new data in the room.
The 90-minute structure
The conversation itself runs in five parts. A skilled facilitator — usually the founder, sometimes a Fractional CSO, occasionally the COO — keeps it moving and pulls the conversation back when it drifts.
Minutes 0-10: state the current commitment honestly.
The function leader closest to the initiative walks the room through current state and original intent. Three slides max. No deck theater. The point of this section is to get everyone on the same page about where things actually are, not to relitigate decisions made eighteen months ago.
The honest part is the work here. If the initiative is failing, the person presenting has to say that. If the team is exhausted, that has to be on the page. If the metrics aren't moving, that goes on the page in clean numbers without spin. The quality of the next eighty minutes is determined by the quality of these ten.
Minutes 10-30: reasons to continue.
The room generates reasons to continue with the initiative. Not the function leader's reasons — the whole room's. The frame is deliberately positive. What's working? What does this initiative still unlock that nothing else does? What would the company lose if it stopped? Where is the underlying thesis still alive?
Twenty minutes is more than enough. The reasons get captured on a whiteboard or a doc that's visible to everyone. The point is not to be exhaustive — it's to surface the strongest case for continuing.
Minutes 30-50: reasons to stop.
The room generates reasons to stop. The frame here is deliberately blunt. What's not working? What signals have been ignored? What other initiatives are being starved because this one is consuming people and capital? If you were starting today, would you start this?
This is the section where the conversation usually gets uncomfortable. That's the point. The discomfort is where the actual decision lives. A skilled facilitator notices when people are softening their objections and pushes back — "say that more directly" — because the polished version of a concern is the version that doesn't lead to a decision.
Minutes 50-70: score against strategic intent.
The room walks through three questions, each with the original strategic intent visible on the wall.
- Is the strategic intent still valid? The world may have shifted in a way that makes the original goal less important than it was. Be honest. Sometimes the answer is "we don't actually need this anymore."
- Is the current path the best path to the intent? Even if the intent is still valid, the company may be on the wrong vector to get there. A partnership or an acquisition might get there in nine months instead of the twenty-four the current build path will take.
- What does each of the three options actually commit the company to over the next twelve months? Real numbers. Real people. Real opportunity cost.
This section is where build/buy/kill gets evaluated as choices among choices, not as a referendum on the initiative in isolation.
Minutes 70-90: decide.
The decision gets made in the room. Not "we'll think about it." Not "let's reconvene next week." The decision is build, buy, or kill, and one person's name is on the next step.
If the decision is build: name the owner, the budget envelope, the next milestone, and the next decision date. The team that has been carrying this initiative now has the air cover to actually execute, with explicit support and explicit constraints.
If the decision is buy: name the owner of the buy process, the timeline to source options, and the budget envelope for the acquisition or partnership. Move the build team off the initiative and into the next-best assignment.
If the decision is kill: name the wind-down owner, the timeline to wind down, the redeployment of the team, and — critically — the conversation the founder or CEO is going to have with the team this week to honor the work and reframe the next assignment. The kill decision is not done until that conversation has happened.
The output of the ninety minutes is a one-page memo, written in the room, that captures the decision, the rationale, and the named next steps. The memo goes to the board, the leadership team, and the affected team within twenty-four hours.
The emotional traps
The framework only works if the leadership team is honest about the emotional traps that have been keeping the initiative alive past its point of usefulness.
Sunk cost. The initiative has consumed eighteen months and several million dollars. The team feels the weight of that investment, and every conversation about it gets framed as "we're so close." The honest test: if you were starting today, with the same resources, would you start this? If the answer is flatly no, the sunk cost is doing the deciding, not the strategy.
Identity of the team. A team has built itself around this initiative. People joined to work on it. Their LinkedIn profiles describe their work on it. Killing it threatens not just their roles but their sense of what they came here to do. The honest version of this trap is recognizing that the company is responsible for the talent, not the initiative. The team's job security and growth depend on being redeployed to something that compounds — not on continuing to fund something that isn't working.
Founder ego. This is the hardest trap to name in the room, because the person it applies to is usually the person running the conversation. The initiative was the founder's idea. The founder defended it to the board. Killing it feels like admitting the original call was wrong. It often wasn't — the call may have been correct for the world the company was in eighteen months ago, and the right call now is different because the world has changed. The founder who can name that out loud — "I committed to this because of X, and X has changed, so we're making a different call now" — gives the leadership team permission to make hard calls cleanly for the rest of the company's life.
Optimism bias. The team running the initiative has a sincere belief that breakthrough is six weeks away. They are not lying. They are honestly reporting their experience inside the work. But six-weeks-away has been six-weeks-away for nine months. The honest question: what specifically would have to change in the next six weeks for the breakthrough to actually arrive, and is there evidence that those specific changes are in motion? "We're so close" is not evidence. Named changes with named timelines are.
What to do this week
If you have an initiative that has been stuck for more than two quarters, don't schedule another off-site. Schedule ninety minutes.
Assign someone to prepare the one-page artifact. Walk the room through the framework. End with a decision and a name on it. Send the memo within twenty-four hours.
You'll either reaffirm the initiative with sharper terms, redirect it through a buy path, or kill it and redeploy the team. Any of those three is a better outcome than another quarter of drift.
If you have a stuck initiative and you'd like a sharper read on whether it's build, buy, or kill before you run the conversation internally, that's worth twenty minutes. Book a free alignment call and we'll work through it together. You leave with one specific strategic recommendation, regardless of whether we work together.