Quarterly Priorities: Choosing a Few and Keeping Them in View

An annual plan sets direction, but a year is too long to steer by. Weekly to-do lists are too short to carry strategy. The quarter sits in between: long enough to finish something meaningful, short enough that you cannot pretend there is plenty of time.

The hard part is not writing quarterly priorities. It is choosing few enough of them, writing them so everyone knows when they are done, and keeping them in front of the team when customers, problems and email crowd in.

This guide covers each of those steps for a small business.

Why the quarter works as a planning unit

Google's re:Work guide to objectives and key results describes Google setting both annual and quarterly goals and meeting company-wide each quarter to review results and set new goals. You do not need OKRs to use the same rhythm. A quarter gives you about thirteen weeks: enough for a project like launching a new service or fixing a billing process, and short enough that slipping by a month is obvious.

Quarterly priorities should come from the annual plan. For each annual priority, ask: what must be true by the end of this quarter for us to be on track? Some annual priorities will need work every quarter; others may sit out a quarter while something more urgent finishes.

How many priorities

Fewer than you think. The re:Work guide recommends "just three to five objectives," noting that more "can lead to over-extended teams and a diffusion of effort." When teams list their own priorities, the same guide suggests checking, among other things, "Are there more than three priorities?"

For a small business, a workable pattern is three company priorities for the quarter, with no person owning more than one or two. If you have ten candidates, rank them and park the rest on a visible "next quarter" list so the ideas are not lost.

Remember that priorities are not the whole job. The re:Work guide says plainly that OKRs "are not a shared to-do list." The same applies here: your quarterly priorities are the few things that would change the business, sitting on top of the routine work that keeps it running.

Write each priority so done is obvious

A useful priority has a clear finish line. The re:Work guide advises using "tangible, objective, and unambiguous terms" so that "it should be obvious to an observer whether or not an objective has been achieved." It also warns against expressions that do not push for new achievement, such as "keep hiring," "maintain market position" or "continue doing X."

A simple format works well:

• Priority: what will be different at the end of the quarter.
• Why it matters: the link to an annual priority, in one line.
• Done means: one to three measurable signs of completion.
• Owner: one person, even if several people help.
• Milestones: two or three checkpoints, roughly one per month.

For example, imagine a five-person accounting practice. "Improve onboarding" is vague. "New clients complete onboarding in two weeks or less, measured on every client who signs in March" is a priority someone can own and check.

Limit how many start at once

It is tempting to start every priority in the first week and then finish none of them. The Kanban Guide (May 2025) defines work in progress as "work items started but not finished" and says teams should explicitly control how much of it they carry, starting new work only "when there is a clear signal that there is capacity to do so."

Apply that to strategic projects. If two priorities depend on the same person, sequence them: finish the first, then start the second. A priority that is done in week eight is worth more than two that are each half done in week thirteen.

Make priorities hard to ignore

Out of sight is out of mind. The re:Work guide stresses that OKRs should be public within an organization "so that every employee knows the organizational objectives and metrics for success." The Lean Enterprise Institute defines visual management as placing tools, activities and performance indicators "in plain view" so that the status of the system "can be understood at a glance by everyone involved."

Practical ways to do this in a small business:

• A single board or shared page listing the quarter's priorities, owners, measures and a simple status: on track, at risk or off track.
• A ten-minute standing item at the start of each weekly team meeting: each owner gives the status and names anything blocking progress.
• The priority list at the top of the monthly numbers report, so financial results and strategic progress are read together.

Keep the format the same all quarter. Changing the tracking tool mid-quarter is a common way to lose momentum.

When daily work collides with priorities

It will. A big order, a sick employee or a broken system will eat the time you set aside. Decide in advance how you will handle it. Some owners protect a fixed block each week for priority work; others agree that a priority owner can say no to new requests unless the owner of the business overrides it.

It also helps to be clear about what kind of goal each priority is. The OKR site What Matters distinguishes committed goals, which are expected to earn a passing grade at the end of the cycle, from aspirational goals, sometimes called stretch goals or moonshots. Most small-business quarterly priorities should be committed, with at most one stretch goal labeled as such.

Check midway and close out cleanly

The re:Work guide suggests a mid-quarter check-in before final grading and notes that revisiting goals can give everyone the chance to "abandon objectives that are clearly not going to happen." Dropping a priority on purpose is better than letting it fade. At quarter end, record what was finished, what was not and why, and carry lessons into next quarter's choices. Our guide A Strategy Review Cadence: Monthly Check-Ins and Quarterly Resets describes how to run those sessions.

Key takeaways

• Derive quarterly priorities from the annual plan by asking what must be true by quarter end.
• Keep the list to three to five, and give each priority a single owner.
• Write priorities so an observer could tell whether they were achieved.
• Limit how many priorities are in progress at once; finishing beats starting.
• Make status visible every week, and drop priorities deliberately rather than letting them fade.

Sources

• Google re:Work, Set goals with OKRs (originally published 2016)
• What Matters, What is an OKR? OKR Meaning, Definition & Examples
• John Coleman and Daniel Vacanti, The Kanban Guide (May 2025)
• Lean Enterprise Institute, Lexicon: Visual Management