How do I decide whether to continue, pause, or re-scope inherited work?
Quick answer
Before changing inherited work, write down what was agreed, what is known about its status, and what remains uncertain. Compare continuing, pausing, and re-scoping against the work’s purpose, deadlines, dependencies, and available capacity. Recommend an option, but distinguish your judgment from confirmed facts. Ask the appropriate decision-maker to resolve trade-offs, ownership, and any commitments you cannot change yourself.
The question, the details, the next step.
I’ve taken over several pieces of work, but I don’t know which ones to keep moving. How should I start without assuming the previous owner’s commitments were wrong?
Start with an inventory, not a verdict. For each item, capture its intended outcome, current state, next known milestone, people or work it depends on, and who appears to own the decision. Use records and handover notes where available, and mark anything you have not confirmed as an assumption or an open question.
Then ask: what problem was this work meant to solve, and is that purpose still understood by the people responsible for it? Avoid treating a missing detail as proof that the work is unnecessary. Your first goal is to make the decision visible, not to defend or discard the inherited plan.
What should I compare when I’m choosing between continuing, pausing, or re-scoping?
Use the same criteria for all three options so the comparison is fair:
- Purpose: Is the intended outcome still relevant and clear?
- Commitments: Is there a known deadline, promise, or expectation? Who confirmed it?
- Dependencies: Would stopping or changing this work affect another person or project?
- Capacity: What effort and attention would each option require, alongside other priorities?
- Reversibility: What would be difficult to restart or undo after a pause or change?
“Continue” means carry on with the current scope; “pause” means stop or defer for a stated reason and review point; “re-scope” means change the outcome, boundaries, or next deliverable. If you lack evidence to compare an item, show that gap rather than filling it with a guess.
How do I make a recommendation when I’m not the person authorized to change a commitment?
Separate your recommendation from the decision. State what you have observed, what you infer, and what needs confirmation. Name the decision-maker or group you believe should resolve it, and ask a specific question they can answer. Don’t present a pause or scope change as settled if you do not have authority to make it.
For example, assuming a project has a planned deliverable but its priority and deadline have not been confirmed, your brief could say:
“Work item: [name]. Intended outcome: [as recorded; confirmation needed]. Current state: [known progress]. Open points: [deadline and dependency]. Options: continue the current scope; pause until [specific information] is confirmed; or re-scope to [smaller outcome]. Recommendation: [option], because [reason]. Decision needed from: [role or person]. Please confirm [specific trade-off] by [date or review point]. If no decision is made by then, I will [only the next step within my authority].”
Replace placeholders with information you can support. If the deadline, dependency, or authority is unknown, label it as unknown.
What belongs in the final decision brief, and how can I make sure a pause doesn’t just disappear?
Keep the brief short enough to review, but complete enough to act on. Include the work item, intended outcome, status, relevant commitments and dependencies, uncertainties, options, your recommendation with reasons, and the decision requested. Record who made the decision and what they chose. For a pause, also propose a review date or a condition for reconsidering it, plus who will check whether that trigger has occurred.
A pause is not the same as cancellation: describe what will stop, what—if anything—continues, and what information would prompt a review. Confirm the resulting ownership and next step with the relevant people. This brief helps structure the conversation; it cannot establish the underlying facts or authorize a change on its own.
A practical checklist
List each inherited work item and its intended outcome, using confirmed information where possible.
Mark assumptions, missing details, deadlines, dependencies, and ownership questions explicitly.
Compare continue, pause, and re-scope using the same purpose, commitment, dependency, capacity, and reversibility criteria.
State your recommendation and reasoning separately from the decision requested.
For a pause, specify what stops, what could trigger review, and who will check in.
Record the decision-maker’s choice, owner, and next step after the discussion.
A few more useful answers
What if I can’t find a clear purpose or owner for an inherited item?
Mark both as unconfirmed and ask the people or group best placed to clarify them. Until then, avoid presenting a guessed purpose or owner as fact, and flag any time-sensitive decision separately.
Should I recommend pausing work if I don’t have enough information?
You can present a pause as an option and explain what information is missing, but distinguish that recommendation from an authorized decision. Identify who can decide and suggest a specific point or condition for review.
How can I keep re-scoping from becoming an undefined new project?
Describe the changed outcome and boundaries in concrete terms, including what is out of scope and what decision or confirmation is still needed. Ask the decision-maker to confirm the revised scope and ownership.