The Work Kept Slipping. So I Joined the Flow.
Turning an important-but-stuck backlog into work the team could actually move
A representative story from embedded B2B marketing work: start with the symptoms, make the priorities visible, then stay close enough to help ship what matters.
Story summary
The Challenge
The team was capable and busy. Important work kept losing to the day-to-day because ownership sat between marketing, sales, product, and external suppliers.
The Solution
I started with discovery to map the work and decisions, then joined the team one day a week to own the backlog, build across functions, and keep the context in one place.
The symptom was capacity
The team had no shortage of ideas. The backlog was full of work everyone agreed mattered: a website section that needed rebuilding, CRM changes nobody wanted to touch, reporting that took too long, and campaign work waiting on decisions from three different people.
Nothing was officially blocked.
It just kept moving to next quarter.
That is usually the point where someone asks for an extra set of hands. But adding capacity before deciding what the work actually needs can make the backlog bigger, not smaller.
Discovery made the work visible
I started by following the work rather than the org chart.
Where did requests begin? Who had the context? Which decisions were waiting? Which systems were involved? What had already been tried?
The picture showed that the problem was not one missing campaign or one broken tool. Ownership disappeared whenever the work crossed from marketing into sales, product, or an external supplier.
Once everyone could see that, the priorities became much easier to set.
We left discovery with a short backlog, named decisions, and a clear view of what could move without creating another dependency.
Then I stayed close enough to move it
The next phase needed ongoing ownership, so I joined the team one day a week.
Some weeks I built. Some weeks I worked through a decision with the people involved. Some weeks I fixed the system behind the symptom so the same problem did not return a month later.
Because I already had the context from discovery, the work could shift without a new brief every time. The backlog changed on Tuesday. I changed with it.
That is the useful part of being embedded. The team does not have to translate the situation for a new supplier each time something moves.
What changed
Important work stopped living between people.
The team had one shared view of the backlog, one owner for moving it, and a working rhythm that made room for both decisions and execution. Website, CRM, paid media, and reporting no longer had to pretend they were separate projects.
The output was not a dramatic transformation reveal. It was better: work that had been stuck was now live, understood, and maintainable.
Want to bring a backlog like this into focus? Start with discovery.
Key Outcomes
- A shared view of what mattered now and what could wait
- Clear ownership for work that previously sat between teams
- Long-stalled website, CRM, and reporting work moved into production
- Decisions and documentation stayed with the team
Parts of the work
Bring me what is stuck
You do not need a clean brief. We can start with the symptoms and work out what the situation needs.
Start with a conversation