# Rolling Priorities: What to Do When Yesterday’s Plan Didn’t Finish

> Unfinished tasks don’t belong on today’s plan by default. Learn how to roll priorities with intention — so your team stops guessing and starts progressing.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-14
- Updated: 2026-10-14
- Source: https://aiadvisoryboard.me/blog/rolling-priorities-when-yesterdays-plan-didnt-finish

When a founder looks at the morning plan and sees half of yesterday’s tasks still open, the instinct is to either push harder or feel behind. Neither helps. Rolling priorities isn’t about catching up — it’s about resetting with clarity.

## TL;DR
- Review what’s truly done, not what was hoped for.
- Move only the essential unfinished items to today’s plan.
- Reset the rest with new estimates or drop them.

**Definition:** Rolling priorities — the practice of reviewing yesterday’s plan against actual outcomes, then deliberately deciding what carries forward, what gets re-estimated, and what is dropped or delegated.

**Definition:** Plan vs Fact — a daily comparison where ‘Plan’ is what was intended, ‘Fact’ is what was completed, and ‘Gap’ reveals blockers, overestimation, or shifting urgency.

How should you handle yesterday’s unfinished work when building today’s plan?
Start by separating completion from intention. Look at each item from yesterday’s plan: was it finished, partially done, or not started? Be honest — ‘almost done’ is not done. Only items that meet the definition of complete move to the ‘Fact’ column.

What do you do with the unfinished items?
For each incomplete task, ask: Is this still urgent? Does it still matter? If yes, estimate the remaining effort realistically — not what you hoped would be left, but what actually is. If no, either delegate it, drop it, or schedule it for a specific future date. Never just roll it over blindly.

How do you avoid turning rolling priorities into a guilt list?
Treat the plan as a forecast, not a promise. The goal isn’t to do everything listed — it’s to make visible progress on what matters. If a task keeps rolling for three days, it’s a signal: either it’s poorly defined, blocked by someone else, or not actually a priority. Use the pattern to improve future planning, not to self-punish.

## Manager Scan (2-minute digest example)
- Reviewed Plan vs Fact for dev team: 3 of 8 tasks complete.
- Two unfinished items: API auth (blocked on legal review) and dashboard updates (waiting on data).
- One item dropped: internal tool cleanup — low impact, no owner.
- API auth moved to today with a note: ‘awaiting legal feedback by 10 AM’.
- Dashboard updates rescheduled for Thursday after data pipeline fix.
- Team lead noted: ‘We overestimated capacity — next plan will limit to 5 high-confidence items.’

## Tool tip (AiAdvisoryBoard.me):
> The Plan → Fact → Gap review takes five minutes but prevents hours of rework and misalignment. When you see the same task rolling for days, it’s not a planning failure — it’s a visibility signal. Use it to adjust scope, unblock dependencies, or reset expectations before the day starts.

## Micro-case (what changes after 7–14 days)
A founder of a 40-person logistics company noticed their ops lead’s daily plan kept showing the same three items: update carrier contracts, review delay logs, and train new dispatchers. After tracking Plan vs Fact for two weeks, they saw the contracts were stuck waiting on legal, the logs were never opened because the team was firefighting, and the training kept getting pushed by shift changes. Instead of pushing harder, the founder blocked two hours each morning for contract work, delegated log review to a senior dispatcher, and made training a fixed Friday slot. Within ten days, the rolling items dropped off the list — not because they were done, but because the plan finally matched reality.

**Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ
**What if everything on yesterday’s plan is unfinished?**
Then your planning is too optimistic or your day is too reactive. Cut tomorrow’s plan in half and focus on unblocking — what’s stopping completion? Fix that first.

**Should I carry over partial progress as a new task?**
Only if the remaining work is clearly defined. ‘Almost done’ isn’t a task — it’s a feeling. Break it into what’s left: ‘awaiting feedback,’ ‘needs testing,’ etc.

**How is this different from just moving tasks to tomorrow?**
Blind rolling creates debt and confusion. Rolling priorities means reviewing, re-estimating, and making intentional choices — not just pushing work forward.

**Can this work for async teams?**
Yes. Async teams benefit more — they rely on written plans. A daily Plan vs Fact update in a shared doc keeps everyone aligned without meetings.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.
https://aiadvisoryboard.me/?lang=en

---

When citing, link to https://aiadvisoryboard.me/blog/rolling-priorities-when-yesterdays-plan-didnt-finish. More articles: https://aiadvisoryboard.me/blog