The Weekly Slippage Reconciler: Turn Last Week's Plan vs Actual Into This Week's Realistic Priorities
Why this prompt matters
Carrying forward 100% of unfinished work without diagnosing why it slipped just rebuilds the same overcommitted list — so the same items stall again, trust in your own estimates erodes, and the backlog of almost-done work keeps growing instead of shrinking. Naming the actual slippage pattern (sequencing, dependency, underestimate, interrupt, overcommitment) is the only way to stop repeating it.
What we use it for
You are a product manager (or any individual contributor juggling multiple workstreams) who ends most Fridays with 2-3 planned priorities still undone, and every Monday you face the same choice: silently carry everything forward, or sit down and actually figure out what happened before deciding what is realistic this week.
Prompt
Role: Act as a ruthless but constructive chief-of-staff who specializes in diagnosing why plans don't survive contact with the week. Context: - My role/function: [YOUR ROLE OR JOB] - Last week's planned priorities: [PASTE THE LIST YOU COMMITTED TO LAST WEEK] - What actually happened: [PASTE A ROUGH LOG — WHAT GOT DONE, WHAT GOT BUMPED, WHAT UNEXPECTED THINGS ATE YOUR TIME] - This week's fixed calendar load: [HOURS ALREADY COMMITTED TO MEETINGS / FIXED OBLIGATIONS] - This week's candidate priorities: [PASTE YOUR ROUGH, UNORDERED LIST FOR THIS WEEK] Task: Step 1 — Diagnose: For each item from last week that slipped, identify the TRUE root cause, choosing from: underestimated effort, dependency on someone else, a higher-priority interrupt, poor sequencing, or simply committing to too many items. Name the single most common cause across all slipped items. Step 2 — Reconcile: For each slipped item, decide whether it still genuinely matters this week or whether its relevance has decayed and it should be formally dropped — not silently carried forward and not silently forgotten. Step 3 — Replan: Build this week's priority list using available hours (total working hours minus the fixed calendar load from Context), sequenced by dependency and cost of delay, not just by who asked most recently. Constraints: - Do not carry over 100% of unfinished items by default — that is denial, not reconciliation. - Cap the final list at no more than [MAX NUMBER OF PRIORITIES, e.g. 5] items. - If the available-hours math does not support even the capped list, say so explicitly rather than quietly padding a list that will slip again. - Name capacity delusion directly when you see it (e.g., "this plan assumes zero interrupts, which contradicts what happened last week"). Output Format: 1. Root Cause Summary (2-3 sentences, naming the dominant slippage pattern) 2. Dropped Items table: Item | Why It No Longer Matters 3. This Week's Priorities table: Priority | Why It's In | Estimated Hours | Dependency Risk 4. One direct, blunt paragraph starting with: "If you only change one thing this week, it's..."
Result
**Root Cause Summary** Three of your four slipped items shared the same root cause: poor sequencing, not lack of effort. You started the vendor contract review and the Q4 roadmap draft in parallel on Monday, both stalled waiting on the same finance input, and neither finished. The onboarding doc rewrite wasn't a sequencing problem — it was a straightforward underestimate; you scoped it at 2 hours and it needed 6.
**Dropped Items** | Item | Why It No Longer Matters | |---|---| | Competitor pricing audit | Sales already pulled this data for Thursday's QBR independently — duplicate effort | | Slack channel reorg | Nice-to-have that nobody has asked about since you proposed it three weeks ago |
**This Week's Priorities** (capacity: 24 available hours after 16 hours of fixed meetings) | Priority | Why It's In | Est. Hours | Dependency Risk | |---|---|---|---| | Finance input for vendor contract + roadmap | Unblocks two stalled items at once; single conversation fixes both | 3 | Low — finance confirmed availability Tuesday | | Finish vendor contract review | Legal needs this by Friday for the renewal deadline | 5 | Medium — depends on finance input above | | Onboarding doc rewrite (properly scoped this time) | Already 60% done; finishing has a low marginal cost | 6 | Low | | Q4 roadmap draft v1 | Leadership review is in 9 days; a rough draft now beats a rushed one later | 8 | Medium — depends on finance input |
Total: 22 of 24 available hours. Two hours of buffer intentionally left unallocated, because last week had zero buffer and that is exactly why the interrupt from the client escalation blew up your whole Wednesday.
**If you only change one thing this week, it's this:** stop starting two finance-dependent items in parallel — book the 30-minute finance conversation first thing Monday morning, because last week proved that running both tracks simultaneously without that input just produces two half-finished things instead of one finished thing.
Most "weekly planning" prompts just take a wish list and reorder it. They skip the part that actually matters: figuring out why last week's plan didn't survive contact with reality, so you don't rebuild the same unrealistic list this week.
This prompt forces a three-step sequence — diagnose, reconcile, replan — before it lets you touch this week's priorities. The diagnosis step matters most. "I didn't get to it" is not a root cause; underestimated effort, a blocking dependency, an interrupt, bad sequencing, or simple overcommitment are. Naming the actual pattern is what stops next week from looking like last week.
The reconcile step is the part most planning tools skip entirely. Unfinished items don't automatically deserve a spot on this week's list — some have simply decayed in relevance since you wrote them down. The prompt makes you say that out loud, with a reason, instead of letting a to-do silently calcify into permanent backlog.
The replan step is deliberately capacity-constrained. You give the model your actual available hours — total hours minus whatever is already locked into meetings — and it has to fit priorities into that real number, not an imaginary 40-hour week where nothing else happens. If the math doesn't work even after capping the list, the prompt is instructed to say so directly rather than quietly overpromising again.
Who this is for: anyone who ends most weeks with a chunk of their plan undone and starts the next week by just copying the leftovers onto a new list, without asking whether that's actually the right move.
How to adapt it: the "what actually happened" input doesn't need to be polished — a rough, honest log of what got done, bumped, or blown up works better than a cleaned-up version, since the diagnosis step relies on the real mess to find the real pattern.