Annual Plan Reality Check

Why this might help

A year-long plan feels solid when you write it. Then real life shows up. This room helps your team spot the hidden guesses baked into your annual plan — things like 'we'll have three people free in March' or 'that vendor will deliver on time.' An assumption calendar turns those guesses into visible checkpoints spread across the year. Instead of waiting for something to go wrong, your team checks in early, adjusts, and keeps moving. It's a simple habit that saves a lot of scrambling later.

Does this feel familiar?

Your team hits October and realizes a key assumption from January was never checked.
Someone says 'I thought we agreed on that' but nobody wrote down what the agreement was based on.
A plan falls apart mid-year and the post-mortem shows the warning signs were there in March.
Your team keeps revisiting the same debate because the original reasoning was never captured.

Try this together

List every 'we're assuming' statement hiding in your plan — things like budget holding, headcount staying stable, or a partner coming through on time.
Give each assumption a check-in date, not just a deadline. Ask: when would we know if this is going wrong?
Assign one person to own each assumption. Not a committee — one name, so it doesn't get lost.
When a check-in date arrives, spend ten minutes asking 'still true, partly true, or no longer true?' and write down what you find.
If an assumption breaks, update the plan right away. Don't wait for the next quarterly review to act on what you already know.

Assumption Calendar

Open a simple calendar — paper, digital, whatever your team already uses — and mark out the full year month by month.
Go through your annual plan and pull out every statement that starts with 'we expect,' 'assuming,' or 'as long as.' Write each one down as a plain sentence.
Place each assumption on the calendar at the earliest month you'd realistically know if it was going wrong — not when it matters most, but when you'd first see a signal.
Add the name of one person next to each assumption so there's a clear owner who'll raise a flag if something shifts.
At each check-in date, review the assumption together as a team, mark it as holding, shaky, or broken, and note any changes to the plan right there on the calendar.

Questions worth talking about

Which assumptions in our plan are we most nervous about — and have we actually scheduled a time to check them?

If one thing changed tomorrow and broke this plan, what would it most likely be?

Are we treating any assumption as a fact just because we've been saying it for a while?

A few common questions

How many assumptions should we actually track?

Start small. Five to ten assumptions is plenty for most annual plans. If you track too many, the calendar becomes noise and people stop checking it. Focus on the ones where being wrong would actually change what your team does. You can always add more as you get comfortable with the habit.

What if an assumption breaks halfway through the year — do we redo the whole plan?

Usually not. When an assumption breaks, you just update the parts of the plan that depended on it. Think of it like adjusting a recipe when you're out of one ingredient — you don't start over, you adapt. The goal is a living plan, not a perfect one written once and never touched.

Can Tindlo help us keep track of this across the team?

Yes, in a practical way. Tindlo lets your team place work items on a shared time axis in Day and Week views, so assumption check-ins can live alongside your actual work schedule. Everyone sees the same picture, which makes it easier to notice when a check-in date is coming up and act on it together.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?

Engineering Leadership ExchangeEngineering leaders Product Operations CircleProduct operations teams Project Managers' WorkshopProject managers