Least disruptive isn’t least motion. It’s least context lost.
When a team is doing too much and something has to give, the reflex is to count tasks. List everything in flight, find the pieces you can drop or move, hand off the ones that look most self-contained. Fewer boxes on the team’s plate, problem solved.
That’s the wrong thing to count.
I went through this in July with one of my teams. Five tracks running at once: our plugin platform, a batch of integration migrations, a forms rebuild, an agentic connector, and an enterprise customer integration. Every one in progress, none finished. The team was stretched past sustainable and everyone felt it. We had to give work away.
The obvious move was to hand off the platform. It was the biggest, most demanding track, and there was a central team that could plausibly take it. Cut the largest thing, free up the most room. On a task count it’s the clear winner.
It’s also the worst option, and it took reframing the question to see why.
The platform is the track my team built from nothing. They hold more context on it than anyone in the company. Give it to another team and that team spends months climbing a ramp mine is already standing on top of. The work doesn’t get faster by moving, it gets slower, because you’ve relocated it away from the people who understand it. The context doesn’t ride along with the ticket. It stays in the heads of the people you just took off the work.
Ask what’s cheapest to lose
So I stopped asking what’s biggest and started asking what’s cheapest to lose. Not which track takes the most effort, but which one throws away the least understanding when it changes hands.
That flips the answer. The right things to hand off were the enterprise integration and a separate feature we’d been carrying. The team held shallow context on both, and neither was core to where we’re headed. More boxes changed hands than in the give-away-the-platform plan. Far less knowledge left the building. The team kept the work where its context runs deepest and shed the work where its context was thinnest.
Least disruptive isn’t least motion. It’s least context lost. Those two pull in opposite directions more often than you’d expect. The cleanest-looking descope on a slide, the one where a single big item moves in one piece, is often the one that destroys the most, because items get big precisely when someone has spent a long time building the knowledge to run them.
What kept it honest
Two things stopped this from being a nice theory I talked myself into.
The team reached the same place from the bottom up, before I brought them any options. In their retro they named it directly: too many repos, reviews dragging because half the code was unfamiliar, keep-the-lights-on work crowding out the thing they wanted to build. Every one of those is a context problem. Shedding the low-context tracks was the fix they were already reaching for.
It also matched where the business is betting. The platform is the strategic play, not the individual plugins. Keeping the team on it protected their context and moved in the direction leadership had already chosen. When the context argument and the strategy argument land on the same track, you can stop deliberating.
One caveat, because this is where the framing goes soft if you let it. Handing work off only works if someone catches it. I could name what to shed. I could not, by myself, promise the receiving teams had room to take it. That’s the real decision and it lives one level up. A handover with no confirmed receiver is a slide, not a plan. If you use this lens, carry that question to whoever owns capacity across teams and make them answer it. Otherwise you’ve just drawn a picture of where you wish the work would go.
This is the same reason the best call a team makes often leaves no visible artifact: protecting deep context looks like nothing happened, while the flashy reorg that moved a big box looks decisive and quietly destroys the most.
When your team is underwater, don’t open with what’s easiest to remove. Find where your team’s context is deepest, protect it, and give away the work that costs the least understanding to lose. The task count will sometimes go up. Your team’s capacity to do its best work goes up with it.