Field Notes
The 90% Problem
Projects get to 90% done and stay there. Not because people are slow — because nobody owns the outcome, only the tasks.
February 27, 2026
When Everything Is a Priority
The planning document has seventeen initiatives.
A few were added this week. Nothing came off the list.
When someone asks which ones matter most, the answer is usually some version of "all of them."
This is how most B2B marketing teams operate now. Work doesn't arrive in cycles anymore. It arrives continuously.
A competitor launches something. Sales flags a missing asset. The board asks for an update. Each item shows up framed as urgent. Most show up without much context about what should move aside to make room. Because there's no shared agreement on what stays out, everything stays in.
The team responds the way capable teams do. They keep things moving. But direction becomes harder to hold. Activity is visible. What actually moved forward is harder to point to.
What Happens When Focus Fragments
Teams don't usually feel overwhelmed all at once. The shift is usually gradual.
Monday morning: brand refresh kickoff. Tuesday afternoon: lead generation campaign review. Wednesday: sales asks for deck updates. Thursday: website redesign meeting. Friday: product launch planning.
Each one matters. Each one has different stakeholders expecting progress. Each one pulls in a different direction. By the end of the week, the marketing lead has touched five initiatives. None have moved meaningfully forward.
This isn't a failure of focus. It's a consequence of how the work is structured. When everything runs in parallel, attention doesn't deepen. It spreads.
Over time, the switching itself becomes the work. Different goals. Different constraints. Different definitions of done. The adjustment costs more than most teams account for.
The Patterns That Follow
When execution spreads thin, certain things start showing up:
1. The 90% stall. Projects move close to completion, then pause. Not because they're blocked, but because something else became urgent. They sit at 90% for weeks. Sometimes months.
2. Meetings about delays. More time gets spent explaining why things aren't done than reviewing what shipped.
3. The quality ceiling. Work gets delivered often enough to maintain the appearance of momentum. But it rarely feels fully finished. There's always something that could have been tighter if there had been more time.
Nothing is visibly broken. Things just take longer. Decisions wait. Work sits.
Why Adding People Doesn't Fix It
When progress slows, the first instinct is often to add capacity. More people. Better tools. Tighter processes.
In practice, additional resources tend to expose the constraint rather than resolve it.
A new person joins the team. Now six people need to align instead of five. The approval that took three days now takes five. More Slack threads. More meetings to sync. More people waiting for the same input to move forward.
The bottleneck isn't effort. It's decision clarity.
Strategy comes before content. Content comes before activation. When decisions at the top stall, everything downstream waits. Adding people downstream doesn't change that.
The system gets busier. It doesn't get clearer.
Why Saying No Feels Risky
Reluctance to prioritize isn't usually about indecision. It's about risk.
In most organizations, declining a request carries social cost. Saying no can look like resistance. Or lack of ambition. Or not being a team player.
The request comes from sales. They need competitive content. It's urgent. It always is.
Or it comes from product. They're launching something. Marketing needs to support it.
Or it comes from the CEO. A prospect asked about something. Can we get that done?
Each request is reasonable on its own. Marketing doesn't have criteria to evaluate whether it fits. So they add it. The list grows. Nothing comes off. Focus redistributes in small increments. No single decision feels significant. The effect only becomes visible later, when the core initiatives that were supposed to drive the quarter are still stuck at 60%.
At that point, prioritization still happens. It just happens quietly, inside teams, without shared context. The work that doesn't get done is the work no one was explicitly protecting.
What Changes When Priorities Get Clear
Teams that execute consistently tend to have something in common. They've resolved what matters most before work starts.
Not in theory. In practice.
They know what the business needs to achieve this quarter. They've identified the two or three themes that drive that outcome. Everything else either supports those themes or waits.
When a new request arrives, it gets evaluated against those themes. If it fits, it might replace something currently active. If it doesn't fit, it goes to backlog.
This isn't ruthlessness. It's structure.
The first no is hard. After that, the pattern becomes recognizable. Stakeholders start to understand what qualifies and what doesn't. The team stops drowning in context switches.
Fewer things run at once. More things finish. Conversations shift from "Why isn't this done yet?" to "What did we learn from closing this?"
Urgency doesn't disappear. It just stops dictating everything else.
What a CMO Actually Controls
For a CMO, the work shifts over time.
Less energy goes into responding to requests. More goes into shaping the conditions under which requests get evaluated.
Clearer criteria. What qualifies as a priority before it enters the workflow. Not vague principles. Concrete criteria tied to outcomes.
Visible trade-offs. When something new comes in, what comes off? That conversation happens in the open, not buried in task lists.
Operational rhythm. Decisions happen on a cadence, not in response to whoever asked most recently. Weekly or biweekly. Scheduled. Protected.
As that rhythm settles, the planning document stops growing unchecked. The team gets better at finishing. Work that matters gets the attention it needs to actually work.
Where Friction Actually Lives
A Diagnostic Sprint reveals where priority conflicts actually sit.
Not in the planning document. In how decisions get made when someone's in the room asking for something urgent.
In whether the team has shared language for what "priority" means. In whether trade-offs get discussed or assumed. In whether marketing is reacting to requests or operating from a position of clarity.
The output isn't a new prioritization framework. It's visibility into where the current system creates friction and what needs to change for decisions to actually hold.
.jpg)
