Annual Planning: An 8-Week Process and Roadmap for Teams

11 min read ยท 2026-11-07

Annual planning turns your strategy into a small set of priorities for the year, and gives each one owners, milestones, people and budget. A department or a group of teams can do it in about 8 weeks. Review last year. Rank 3 to 5 priorities. Let each team draft its plan. Fit those drafts to the capacity and budget you really have. Agree the dependencies between teams. Then sign off and book the reviews that keep the plan alive.

This guide is for heads of department, project and PMO leads, chiefs of staff and new managers who have to bring several team plans together into one. Writing goals is the easy part. The hard part comes when the team plans together ask for more people, money and time than you have, and someone has to decide what gets cut. The roadmap below prepares for that moment from the first week. It ends with a quarterly view you can present to leadership.

The roadmap at a glance

Goal: A signed-off annual plan where every team's work links to a ranked priority, fits its capacity and budget, has its cross-team dependencies agreed, and has a review rhythm for the whole year. Duration: 8 weeks of planning, then four quarters of execution

  1. Review the Year Behind You (Week 1)

    Start from facts, so the new plan does not repeat last year's surprises.

    • List last year's goals and mark each one as hit, partly hit or missed, with one line on why.
    • Note where the time really went, including support, fixes and urgent requests that were never planned.
    • Collect the projects that slipped and say what blocked them: people, budget, a dependency or a late decision.
    • Write down what is still running and will carry into next year.

    Milestone: A one-page review of last year is shared with every team lead before any new goal is discussed.

  2. Frame Priorities and Planning Limits (Weeks 2 to 3)

    Give every team the same starting point before anyone writes a plan.

    • Rank 3 to 5 priorities in order, so teams know which one wins in a conflict.
    • Write a short "not this year" list of things you have decided not to do.
    • Set each team's budget and headcount limits: current headcount, approved hires with start dates, and a budget ceiling.
    • Share one planning template with the same fields and units for everyone, plus the calendar and the name of the process owner.

    Milestone: Every team lead has a kickoff pack with the ranked priorities, the "not this year" list, their budget and headcount limits, the template and the deadlines.

  3. Draft Team Plans (Weeks 3 to 4)

    Each team turns the priorities into its own plan and says what it needs.

    • List proposed initiatives and link each one to a ranked priority.
    • Estimate effort in person weeks, not in vague sizes.
    • List the ongoing work the team must keep doing anyway, such as support, maintenance and reporting.
    • List budget asks above the team's limits, with what each one would unlock.
    • Name every dependency on another team: what, from whom and by when.

    Milestone: All drafts arrive in the shared template by the deadline, with effort, asks and dependencies filled in.

  4. Trade Off Capacity and Budget (Weeks 5 to 6)

    Add up demand, compare it with supply and decide what is funded.

    • Add up each team's effort and compare it with its available capacity.
    • Add up budget asks and compare them with the total budget.
    • Sort initiatives by the priority they support and draw the funded line.
    • Apply the decision rules agreed in advance to everything close to the line.
    • Tell each team lead what moved above or below the line, and why.

    Milestone: One view shows every initiative as funded or not funded, and each team's funded work fits its capacity.

  5. Align Teams and Build the Quarterly Roadmap (Week 7)

    Make sure every promise one team relies on is also in the other team's plan, then lay the work out over time.

    • Build a dependency map: asking team, giving team, what is needed, needed by.
    • Confirm the giving team has funded capacity for each dependency.
    • Place funded initiatives and their milestones on a quarter by quarter timeline.
    • Hold one joint session to close the dependencies that are still open.

    Milestone: Every dependency is accepted with a date or removed, and the quarterly roadmap shows each initiative, its owner and its milestones.

  6. Sign Off and Communicate (Week 8)

    Lock the plan and make sure everyone knows what it means for them.

    • Leadership approves the plan and the "not funded" list in one meeting.
    • Publish team plans, the roadmap and the dependency map in one shared place.
    • Each team lead walks their team through what was funded, what was not, and why.
    • Write the change rule: who can add work, what must come out to make room, and who approves.

    Milestone: The plan is signed off and published, and every team has heard it from its own lead.

  7. Run the Year (Q1 to Q4)

    Keep the plan useful once the year starts.

    • Hold a short monthly review of milestones, risks and blocked dependencies.
    • Replan each quarter: confirm the next quarter, move or drop work, and check the "not funded" list.
    • Track hires against their planned start dates and adjust capacity when they move.
    • Hold a short retrospective at year end, which becomes Week 1 of next year's cycle.

    Milestone: Four quarterly replanning sessions are held, and each one ends with an updated roadmap.

What a Good Annual Plan Includes

An annual plan is not a long strategy document. It is the short list of what the organisation will deliver this year, who delivers it, and what it costs. Strategy says where you want to go. The plan says what you fund this year to get closer. Keeping the two apart stops the plan from turning into a wish list.

A plan people can actually use has these parts:

  • A review of last year: what was hit, what was missed and why.
  • 3 to 5 ranked priorities, plus a written list of what you are not doing.
  • Measurable goals for each priority, with an agreed meaning of success.
  • Initiatives and owners: one named person for each piece of work.
  • Milestones and dependencies laid out by quarter.
  • Headcount and budget tied to each initiative, not set separately.
  • A review rhythm and a change rule for the year.

When to Start Annual Planning and Who Is Involved

Many teams plan during the last quarter, so the plan is ready when the new year starts. Starting in Q4 gives Q1 a clean start. To set the date, count back 8 weeks from the day your budget year opens, then add a little margin. If finance closes budgets earlier, move the trade-off phase so it ends before their deadline. In a large group with many teams to bring together, you may need to start the review in Q3.

Keep the decision group small. Team leads propose, leadership decides. If everyone can veto, nothing gets cut.

  • Leadership: ranks priorities, sets budget and headcount limits, makes the final calls.
  • Process owner: runs the calendar, owns the template, brings the drafts together.
  • Team leads: write team plans, estimate effort, declare dependencies.
  • Finance: sets budget ceilings and checks asks against them.
  • People or HR: confirms headcount, open roles and realistic hiring dates.

Setting Goals and Agreeing What Success Means

Each priority needs a goal you can measure. OKRs, SMART goals or a few key metrics all work. Pick one format and use it in every team, otherwise you cannot compare the plans. "Improve onboarding" is a theme. "New customers reach their first result in under two weeks by Q3" is a goal.

Before the year starts, agree what counts as success. Is reaching 70 percent of an ambitious goal a good result, or does only 100 percent count? Teams that read the same goal in different ways end up fighting at review time. Write the rule down next to each goal, so the Q2 review is about progress and not about definitions.

Choosing Priorities and Saying What You Will Not Do

A frequent cause of failure in annual planning is having too many priorities. If ten things are "top priority," teams pick their own order, and leadership finds out at mid-year. Limit the year to 3 to 5 areas of focus and rank them, so any conflict has a clear answer.

The "not this year" list matters just as much. It tells teams which ideas were looked at and set aside, so they stop coming back every month. It also gives you a ready queue if capacity frees up during the year.

How to Check Capacity Without a Complex Model

You do not need special software to find out if a team plan fits. You need one simple sum per team, done the same way everywhere.

Here is an example. A team has 6 people. Take the working weeks each person really has in the year, after holidays and training. Say it is 44. That gives 264 person weeks. Then remove the ongoing work the team listed. If support and maintenance take about a third of the time, around 175 person weeks are left for new initiatives. If the draft asks for 260, the plan does not fit, and no amount of motivation will close that gap.

  • Count new hires from their start date, not from January. A role filled in summer gives half a year at most, and less while the new person learns the job.
  • Keep a buffer. Plan new work below the full remaining capacity, because urgent requests will come in during the year.

Decision Rules for When Plans Do Not Fit

Drafts often ask for more than you have. Agree the rules before the trade-off sessions, so decisions feel fair and do not depend on who argues best.

  • Two initiatives need the same people: the one tied to the higher ranked priority wins.
  • An initiative cannot be fully staffed: fund it fully or move it to the "not funded" list, never at half.
  • Ongoing work is squeezed by new projects: ongoing work is protected unless leadership decides to stop it.
  • A team asks for budget above its limit: it must say what it drops if the ask is refused.
  • An initiative depends on a team with no room: it waits until the giving team has funded capacity.

Turning the Annual Plan Into a Quarterly Roadmap

The plan decides what is funded. The roadmap shows when it happens. Put each funded initiative on a timeline by quarter, with its owner, its milestones and the dependencies it needs. Show both sides of a dependency on the same view, so a delivery date that falls after the need date stands out at once.

Plan the first quarter in detail, the second roughly, and keep the second half as larger blocks. Then refine each quarter at the replanning session. This keeps the roadmap honest without rebuilding it every month.

Annual Planning by Function

The process stays the same, but each function weighs different inputs:

  • Product: balance new features, technical debt and platform work, and protect time for discovery.
  • IT: list contract renewals, end of support dates and security work first, since their dates are fixed.
  • Marketing: plan around launch dates and seasonal peaks, and agree the campaign calendar with sales.
  • HR and people: build the hiring plan from the funded initiatives, and plan reviews and training cycles.
  • Operations: plan around peak periods and capacity limits, and flag the process changes other teams depend on.

Common mistakes to avoid

  • Letting teams plan before priorities are ranked, so every team says its work comes first; rank 3 to 5 priorities before any draft is written.
  • Accepting drafts in different formats, so the totals take weeks and nobody trusts them; require one template in person weeks.
  • Funding initiatives at half capacity, so several things move slowly and none finish; fund fully or move them to the "not funded" list.
  • Treating dependencies as notes, so they turn into mid-year delays; count a dependency only when the giving team has funded it.
  • Setting the budget apart from the plan, so funded work has no money; tie every budget line to an initiative.
  • Freezing the plan in January, so it is ignored by spring; hold monthly reviews and replan each quarter with a written change rule.

Frequently asked questions

What is annual planning?

Annual planning is the process of deciding what an organisation or team will deliver over the next year. It turns strategy into ranked priorities, measurable goals, owners, milestones, headcount and budget. The result is a plan everyone can follow and review during the year.

When should you start annual planning?

Many teams start in Q4 so the plan is signed off before the new year begins. Count back about 8 weeks from the start of your budget year and add some margin. If your company is large or finance sets early budget deadlines, start the review in Q3.

How do you prepare for annual planning?

Start with an honest review of last year: goals hit and missed, where time went, and what blocked work. Then confirm headcount, hiring dates and budget limits with finance and HR. Share one template and one calendar with every team before drafting begins.

Should annual planning be top-down or bottom-up?

Both, in that order. Leadership sets the ranked priorities and the budget and headcount limits first, then teams propose plans from the bottom up. The trade-off phase is where the two meet. Drafts written before priorities are set are hard to compare.

How do you keep an annual plan useful during the year?

Hold a short monthly review of milestones and risks, and a quarterly replanning session. Use a written change rule so new work replaces something instead of piling on. Check the "not funded" list each quarter in case capacity frees up.

Generate this roadmap with AI