The 90% Problem

There is a pattern that shows up in almost every B2B marketing team I work with. A campaign, a launch, a cross-team initiative — it gets to about 90% done, and then it stays there. For weeks. Sometimes longer.

Nobody dropped the ball. Everyone did their part. The content was written. The assets were designed. The brief was approved. Sales gave their input. Product signed off on the messaging. By every individual measure, the work was done.

But the thing itself never shipped.

‍

The last 10% is a different kind of work

Getting a project to 90% is execution. People do their tasks, hit their deadlines, move things forward within their function. That part usually works.

The last 10% is different. It is integration work — pulling the pieces together across functions, resolving the small decisions that do not belong to any single role, getting final sign-off from someone who was never explicitly asked to give it.

This is where projects stall. Not because anyone is slow or incompetent, but because the system was designed to divide work, not to reunite it. The tasks were assigned. The ownership of the outcome was not.

A content lead owns the copy. A designer owns the visuals. A demand gen manager owns the distribution plan. But who owns the moment where all of that becomes a launched campaign? In most teams, the answer is vague. "Marketing ops." "The project lead." "Whoever is driving it." Which, in practice, often means nobody.

‍

What this looks like in daily work

You can recognise the 90% problem without running an audit. It has a few reliable tells.

The first is recurring status meetings that exist primarily to ask "where are we on this?" If the answer is consistently some version of "almost there," you are likely looking at an ownership gap, not a speed problem.

The second is the campaign that went through three rounds of review but still has not launched. Not because the feedback was wrong, but because nobody closed the loop between receiving feedback and making a final decision. The brief sits in a shared folder, technically approved, practically unfinished.

The third is the quarterly review where the team presents what shipped — and the list is shorter than anyone expected. Not because people were idle. Because a meaningful percentage of the work got stuck in the space between functions.

‍

Why adding process does not fix it

The instinct when projects stall is to add structure. A new project management tool. A more detailed briefing template. A weekly sync to track progress. Another column in the spreadsheet.

These interventions address symptoms, not the cause. The cause is that ownership was defined at the task level but not at the outcome level. No amount of tracking will fix a project where five people each own a piece and nobody owns the whole.

In fact, adding process to a system with an ownership gap often makes things worse. It adds overhead to every function without addressing the structural issue. People spend more time updating status and less time resolving the gaps that caused the stall in the first place.

‍

The cost compounds quietly

One project stuck at 90% is frustrating. Multiple projects stuck at 90% is a systemic drain.

Every initiative that stalls pushes the next one back. Timelines compress. Teams start the next project before the last one shipped, carrying the cognitive load of unfinished work. Over a quarter, you lose weeks — not to bad work, but to good work that could not cross the finish line.

The cost is also emotional. Teams that consistently produce 90%-done work lose confidence in the system. They stop trusting that what they start will actually ship. Senior people spend more energy navigating the friction than doing the work they were hired to do. Eventually, the best people leave — not because the strategy was bad, but because the operating structure made it impossible to execute.

‍

The question that changes things

When a project stalls at 90%, the natural question is "who dropped the ball?" That question almost always leads to blame, which leads to defensiveness, which leads to more process layered on top of the same structural gap.

A better question: "Who owns the outcome, not just the tasks?"

If the answer is clear, you have an accountability conversation. If the answer is vague — "the team," "marketing," "whoever is driving it" — you have a structural problem. And structural problems do not resolve through harder work or better tools. They resolve through redesigning how ownership works.

That distinction — between a people problem and a structural one — changes more than you might expect. It shifts the conversation from blame to design. And it usually surfaces the two or three changes that would have the largest impact on how work actually moves.

‍

The patterns behind this? They're not random.

Read the full breakdown of why B2B marketing execution breaks down →

‍

‍