Guide: Work Removal Before Work Addition Guide
Work Removal Before Work Addition Guide - Before adding more work: List new work; List old work; Stop something; Pause something; Shrink something; Protect the removal
Work Removal Before Work Addition Guide
A practical guide for managers who need to make room for new work without turning the team into a permanently overwatered plant.
Before adding new work, decide what stops, pauses, shrinks or moves.
What this guide helps with
This guide helps managers, team leads and operators create capacity before adding more work. It is useful for AI rollouts, reorganisations, new reporting requirements, transformation programmes, compliance changes and any “small ask” that somehow becomes permanent.
Why now
AI and transformation work often arrives on top of already crowded calendars. Teams are told to move faster, learn more, review outputs, adopt tools and keep the old system running. Without deliberate work removal, the new work does not land. It piles up.
The pattern
The pattern is that organisations treat capacity like optimism. They assume people will absorb the new thing because the new thing is important. But importance does not create hours. Work removal is how strategy becomes possible without quietly breaking people.
The check
Start by listing what is actually being added. Not “AI transformation,” but “review AI outputs, attend weekly pilot meeting, update adoption tracker, test prompts, train team members, rewrite process notes.” New work becomes easier to manage when it stops hiding inside inspiring labels.
Write down the meetings, reports, approvals, trackers, dashboards, manual checks and recurring tasks that already consume the team. Many teams cannot make room because the old work is treated as background noise. It is not noise. It is the current workload.
Some work needs a clean death. If a dashboard is no longer used, a meeting has no decision, or a report has no owner who acts on it, retire it. Stopping work is uncomfortable because it creates little political ghosts. That is why leadership matters.
Not everything can be killed. Some work can pause while a new priority lands. For example, pause a monthly improvement forum during an AI rollout pilot, or suspend a low-value report for one quarter while the team absorbs a new workflow. Pausing work is better than pretending time is infinite.
Some work still matters but can be smaller. Reduce meeting length, reduce report frequency, remove duplicated approvals or switch to exception-only updates. Shrinking work is often the easiest first pruning move because it reduces load without starting a political funeral.
If work remains necessary but no longer belongs with the same team, move it with context. Name the new owner, handover the reason, explain dependencies and set a review date. Moving work without context is just hiding the branch behind another plant.
Work has a way of coming back. Once something stops, document it. Tell affected people. Remove calendar invites. Archive templates. Update trackers. If you do not close the loop, the old work will return wearing a slightly different title.
Check whether the team actually gained time. If the removed work was replaced by informal chasing, hidden follow-ups or extra coordination, the pruning did not work. Capacity must be observed, not assumed.
Quick examples
| Situation | Better question |
|---|---|
| A new AI pilot starts | Which old meeting or tracker is paused while the team learns the tool? |
| A manager asks for faster reporting | Which existing report is retired, merged or moved to exception-only? |
| A team gets new compliance requirements | Which lower-value tasks stop so review work can happen properly? |
| A reorg creates new ownership | Which old approvals or handoffs disappear instead of following everyone into the new structure? |
The Satire
If everything is important, congratulations, you have invented a forest fire with nicer stationery.
Related Vieews paths
Chaos scenes spot the contradiction. Signals name it. Guides give you the next simple move.
Chaos
The Blue Blob and the Very Careful Gardener
The discovery scene that started this thread.
Signal
Leadership Is Also Deciding What Stops
The pattern behind this guide.
Playbook
AI Workload Waste Ledger
Use the heavier structure when needed.
Useful context
Use this guide when leaders are adding new work faster than the team can absorb it. The point is not to resist ambition. The point is to make room for it.
These are Vieews, not bibles. Use them as simple lenses, not legal advice, investment advice, HR advice or a replacement for doing your own investigation. If a line makes the spreadsheet uncomfortable, excellent. Ask one more question and tug on that thread.
