The Planning Year

What to do this week

Find out when your strategy work is expected to finish, and when the goals it feeds are due. If the gap is less than a quarter, the cascade will eat the period it was meant to direct. No amount of discipline inside that quarter recovers it.

That single measurement tells you more about why a planning year is failing than any audit of the goals themselves.

The cycle length is a feedback question

Quarterly is the default, and almost nobody can say why. The reasoning exists, it is forty years old, and it is not about the calendar.

The argument is feedback latency. "For the feedback to be effective, it must be received very soon after the activity it is measuring occurs. Accordingly, an MBO system should set objectives for a relatively short period." Then the prescription, routinely quoted backwards. The time frame "should be at least as often as quarterly or perhaps even monthly" (Grove, 1983).

At least as often as quarterly. Quarterly is the floor, not the target. The practice inherited a ceiling from a sentence that set a minimum.

The test that follows is not what everyone else does. It is how long your organization can act on stale information without noticing. Work whose feedback arrives in weeks wants a shorter cycle than work whose feedback arrives in quarters. Both can live in the same company.

The two sequences anyone actually publishes

Most published planning calendars are generic diagrams. Two organizations have described a dated sequence, and they are the useful evidence because they disagree about almost everything except the timing.

Amazon. Its own filed account says the cycle "begins in the fall, and concludes early in the new year" (Amazon, 2009). The output is specific rather than thematic: "For 2010, we have 452 detailed goals with owners, deliverables, and targeted completion dates" (Amazon, 2009).

One honesty note. Former executives describe the process starting earlier, around June, with a top-down guidance step. That account is credible and widely repeated. It is not what the company filed, and the two should not be merged.

Sit with the tension in that number. Grove wrote that focus "can only happen if we keep the number of objectives small" (Grove, 1983). He gives no figure. Amazon tracks 452, and says these "are not the only goals our teams set for themselves" (Amazon, 2009). The tracked set and the working set are different things.

A manufacturing site running Hoshin Kanri. This is the Swedish arm of a Japanese-owned group, around 460 people, described through a single interview in a master's thesis. Small evidence, and the only published dated sequence besides Amazon's. Its cycle "is divided into two periods, December to March, 'the strategic part', and April to March, 'the operational part'" (Alic and Ideskog, 2016). The strategic part overlaps the tail of the previous cycle, so the two run in parallel for four months.

The handoff needs lead time, and only one sequence shows how much

The useful question is how much runway the handoff needs. Only one of these two answers it directly, and the other is often misread as agreeing.

In the Hoshin case, the negotiation between levels runs for four months and has to be finished before the year starts. By April "every level in the organization should have decided upon their Strategic pillars and Hoshins" (Alic and Ideskog, 2016).

Amazon is the case that gets misread, including by an earlier draft of this page. Its process "concludes early in the new year" (Amazon, 2009), and the goals it produces are for that same year. The cycle runs into the year it governs rather than finishing ahead of it.

So the two published sequences disagree about the handoff, and the disagreement is the finding. One finishes its negotiation before the year opens. The other is still concluding goals in the opening weeks of the year those goals govern.

What transfers is the scheduling question rather than a number. If the top of the house has not settled direction by the time teams must write goals, everything downstream is guesswork or delay. Four months of overlap is one documented answer. It is not a rule, because only one organization has published one.

A re-baseline worth considering

There is a second move worth considering, widely described by former Amazon executives and absent from anything the company has filed. It addresses a problem every organization has. Treat what follows as our recommendation rather than as a documented practice.

A plan gets written and approved before the year's largest uncertainty resolves, which for a retailer is the holiday quarter. Rather than planning blind or waiting until February, you revise against actuals early in the new year. That revision becomes the version you operate against.

This is not about retail. Every organization plans before something important is known. The choice is usually framed as plan early and be wrong, or plan late and lose the quarter. Splitting the lock is a third option. Approve the plan on schedule, then hold one short, scheduled revision once the thing you were waiting on is known.

The trap to avoid is letting that revision become continuous. A scheduled re-baseline is a decision point. An unscheduled one is a plan nobody trusts.

Frequent progress checks are the one evidenced mechanic

Everything above is convention. This is not.

A meta-analysis covered 138 studies and 19,951 people. Monitoring interventions raised how often people checked progress, and "promoted goal attainment" (Harkin et al., 2016).

Two design features strengthened it, and together they specify what a weekly check has to do. The effect was larger "when the outcomes were reported or made public, and when the information was physically recorded" (Harkin et al., 2016).

Frequently. Out loud, to someone else. Written down. That is the evidenced core, and it is the beat that gets cancelled first when the quarter gets busy.

Note what the evidence does not say. It supports more frequent monitoring against less frequent; it names no interval. Weekly is a convention, and a reasonable one, but it is our choice rather than the study's finding.

One caveat belongs in the open. That corpus is dominated by individual health behaviours rather than team goals at work. Carrying it into an organization is a reasonable inference and not a finding.

What the review ladder is for

Underneath the annual cycle, organizations run a ladder of reviews, and the useful distinction is what each one is allowed to decide.

A weekly operating review surfaces exceptions. It does not solve them. The versions described publicly keep strategic discussion out deliberately, which is what keeps the meeting short enough to hold weekly. Those are practitioner accounts rather than studies, and no one has tested the separation.

A monthly or quarterly business review compares progress against the plan and is the sanctioned place to propose changing it. Without that channel, teams carry goals they privately know are dead.

An annual review closes the year and feeds the next planning session. That is why it is scheduled against the start of the next cycle rather than the end of the last.

Hoshin Kanri adds a fourth that has no common Western equivalent. Its annual diagnosis audits how the planning process itself ran, including how the negotiation between levels went, rather than only whether the goals were met. It is the one mechanic in this survey aimed at stopping the cadence from rotting into ceremony, and it costs a single meeting a year.

The budget question

Most organizations bolt goals onto the budget calendar without asking whether that is right. There is a real argument that they should not, and it is worth stating accurately in both directions.

The case against is that the annual budget makes one number serve as target, forecast and resource allocation at once. The movement built on that argument puts it directly. Organise management processes "around business rhythms and events; not around the calendar year only" (Beyond Budgeting Institute, 2023). That source advocates the position it describes, which is worth knowing when weighing it.

The evidence does not support the stronger version of the claim. A two-country survey of 558 organizations found them "adapting their use ... rather than abandoning budgets altogether" (Libby and Lindsay, 2010).

The same survey measured the cost that the abandonment case rests on, and found it smaller than claimed. Median time for a business unit to complete the annual budget was 6.0 weeks in the Canadian sample and 10.0 in the US one, with an individual manager spending 3 to 4 weeks a year on it (Libby and Lindsay, 2010).

The defensible middle is the one most organizations already occupy. Keep the budget, and separate the target from the forecast from the resource allocation, so that one number stops doing three jobs.

What has no evidence at all

Said plainly, because the absence is useful.

The three-year plan. There is no evidence for that horizon, or for any particular number. Set the horizon by the lead time of the commitments being made, such as hiring, capital or platform work, rather than by a convention.

Most of Hoshin Kanri's specifics. A systematic review found the implementation data "often only conceptual and theoretical" (Pavlickova et al., 2022). The same review reports that smaller organizations struggled most with it, and credits success elsewhere to having permanent staff who own running the cycle. At small scale the binding constraint is usually not the calendar design but whether anyone owns it.

Every published cascade-duration statistic. The numbers in circulation about cascade duration, or about what share of goal programmes get abandoned, come from companies selling goal-setting software. None states a method. They are omitted here rather than repeated with a caveat.

Key Takeaways

• Quarterly is a floor, not a prescription. The original argument is about how fast feedback has to arrive to still be actionable, and it explicitly permits monthly.
• Give the handoff a full quarter. Both organizations with a published dated sequence finish strategy work well before the goals it feeds are due. One overlaps the prior cycle to manage it.
• Schedule one re-baseline after the year's largest uncertainty resolves, rather than planning blind or planning late.
• Protect the weekly beat above everything else. It is the only part of the rhythm with strong evidence, and the specification is frequent, said out loud to someone, and written down.
• Give each review a decision it is allowed to make. A weekly that solves problems becomes a monthly. A monthly that cannot change the plan becomes theatre.
• Audit the process once a year, not just the results. Nothing else in the calendar stops the calendar itself from rotting.
• Keep the budget if you have one, but stop making one number be target, forecast and allocation at once.

Sources

• Andrew S. Grove — High Output Management (Random House), verified against the full text, 1983. For the feedback to be effective, it must be received very soon after the activity it is measuring occurs. Accordingly, an MBO system should set objectives for a relatively short period. For example, if we plan on a yearly basis, the corresponding MBO system's time frame should be at least as often as quarterly or perhaps even monthly. View source · verified 2026-09-24 · primary
• Amazon (Jeff Bezos) — 2009 Letter to Shareholders, filed with the SEC as Exhibit 99.1, 2009. Our annual goal setting process begins in the fall, and concludes early in the new year after we've completed our peak holiday quarter. View source · verified 2026-09-24 · primary
• Amazon (Jeff Bezos) — 2009 Letter to Shareholders, filed with the SEC as Exhibit 99.1, 2009. For 2010, we have 452 detailed goals with owners, deliverables, and targeted completion dates. View source · verified 2026-09-24 · primary
• Andrew S. Grove — High Output Management (Random House), verified against the full text, 1983. The one thing an MBO system should provide par excellence is focus. This can only happen if we keep the number of objectives small. View source · verified 2026-09-24 · primary
• Alic and Ideskog — Hoshin Kanri implementation, master's thesis, Jonkoping International Business School, 2016. Company B's Hoshin Kanri process is divided into two periods, December to March, 'the strategic part', and April to March, 'the operational part'. View source · verified 2026-09-24 · primary
• Alic and Ideskog — Hoshin Kanri implementation, master's thesis, Jonkoping International Business School, 2016. When April comes every level in the organization should have decided upon their Strategic pillars and Hoshins so that they can start to implement them. View source · verified 2026-09-24 · primary
• Harkin, Webb, Chang, Prestwich, Conner, Kellar, Benn and Sheeran — Does Monitoring Goal Progress Promote Goal Attainment? A Meta-Analysis of the Experimental Evidence (Psychological Bulletin 142(2), 198-229), 2016. A random effects model revealed that, on average, interventions were successful at increasing the frequency of monitoring goal progress (d+ = 1.98, 95% CI [1.71, 2.24]) and promoted goal attainment (d+ = 0.40, 95% CI [0.32, 0.48]). View source · verified 2026-09-24 · primary
• Harkin, Webb, Chang, Prestwich, Conner, Kellar, Benn and Sheeran — Does Monitoring Goal Progress Promote Goal Attainment? A Meta-Analysis of the Experimental Evidence (Psychological Bulletin 142(2), 198-229), 2016. progress monitoring had larger effects on goal attainment when the outcomes were reported or made public, and when the information was physically recorded. View source · verified 2026-09-24 · primary
• Beyond Budgeting Institute — Beyond Budgeting at 25, white paper (dated 03.23 in the document; no bare year string appears in it), 2023. around business rhythms and events; not around the calendar year only. View source · verified 2026-09-24 · primary
• Libby and Lindsay — Beyond budgeting or budgeting reconsidered? A survey of North-American budgeting practice (Management Accounting Research 21), 2010. While problems exist with budgets, organizations are adapting their use to account for these problems rather than abandoning budgets altogether. View source · verified 2026-09-24 · primary
• Libby and Lindsay — Beyond budgeting or budgeting reconsidered? A survey of North-American budgeting practice (Management Accounting Research 21), Table 3, 2010. FIRM WEEKS Canadian sample (in weeks) 6.0 4.7 1 20 102 US sample (in weeks) 10.0 6.6 2 36 77 MANAGER TIME Canadian sample (in weeks) 3-4. View source · verified 2026-09-24 · primary
• Pavlickova, Mojzisova and Pocsova — Hoshin Kanri Process: A Review and Bibliometric Analysis (Processes 10, 1854), 2022. A few practical pieces of evidence exist on how to successfully introduce Hoshin Kanri, but the data are often only conceptual and theoretical. View source · verified 2026-09-24 · primary