Skip Annual Planning: A Quarterly Rolling Goals Approach for Small Teams

Why Annual Planning Always Fails in Small Companies

Every January, many small teams spend a day or two locked in a room crafting annual plans: revenue targets, product roadmaps, hiring plans. Then March arrives. The market shifts, customer feedback changes, competitors launch new features. Most assumptions become obsolete. But the team is already executing against that plan, either stubbornly pushing forward or constantly pivoting without direction.

I've been through this cycle myself. Early in my product career, I'd set a long list of feature priorities for the year. Two months later, users told us what they really wanted wasn't on the list. We spent more time maintaining the plan than responding to real needs.

Planning isn't the problem—the planning cycle length is. Small companies face much higher uncertainty than large ones. Information updates weekly or even daily. An annual plan, built on limited information at the start of the year, is essentially a bet that nothing will change for 12 months. That's unreasonable.

Quarterly Rolling Goals: A More Realistic Compromise

I later switched to quarterly rolling goals. Simply put, at the start of each quarter, set the key results you want to achieve in the next three months. Check progress weekly. At the end of the quarter, review and adjust the next quarter's goals. This way, you maintain direction while retaining flexibility.

This idea is not original—it's derived from OKR, but stripped of the complex evaluation and cross-team alignment mechanisms. For small teams (5-20 people), we only need three core elements:

1. Quarterly Goals (No More Than 3)

Choose no more than three most important goals each quarter. Each goal should have 1-2 key results that are measurable. For example:

• Goal: Improve new user conversion rate
• Key Result: Increase registration-to-payment conversion from 5% to 8%

Why no more than three? Because small teams have limited attention. Pushing too many goals means none will be done well. You must dare to drop the "important but not urgent" items and focus only on the highest leverage point.

2. Weekly Plan Breakdown

Every Monday, break down the 3-5 most important things to do this week from the quarterly goals. These should be specific, actionable tasks, like "Finalize A/B test design and launch." The weekly plan doesn't need to cover everything, but each item must directly serve the quarterly goal.

3. Quarterly Review and Adjustment

In the last week of each quarter, hold a formal review. Answer three questions:

• What did we achieve? What didn't we? Why?
• Which external assumptions have changed?
• What should we do next quarter? What should we stop doing?

Especially the "stop doing" part—many teams ignore it. Quarterly rolling gives you a natural opportunity to cut tasks that are obsolete or no longer important, rather than letting them pile up.

A Hypothetical Case: AI Writing Product's Quarterly Goal Evolution

Suppose a small team builds an AI writing tool. Their annual plan was "grow user base by 200%." Under quarterly rolling, they might go like this:

Q1 Goal: Improve user retention (because past retention was poor). Key Result: 7-day retention from 30% to 45%. Execution: Optimize onboarding, add writing templates.

Q1 Review: Retention reached 40%, but improvement came mainly from templates. The team realized users really need richer templates, but developing content in-house is slow.

Q2 Goal: Explore content partnership model (partner with professional writers to quickly expand template library). Key Result: 100 partnership templates, driving retention to 50%.

In this example, Q2's goal is completely different from Q1's, but it's a reasonable adjustment based on Q1 data. If they stuck to the annual plan, they'd still be optimizing onboarding, missing the more effective lever of content partnerships.

The Key to Quarterly Rolling: Dare to Drop

Many teams do quarterly rolling, but when they review and find targets unmet, they just carry them over to the next quarter. That defeats the purpose. A core principle: at the end of each quarter, re-evaluate all goals. Don't default to continuation.

If a goal becomes clearly invalid mid-quarter (e.g., market shift requires a product pivot), drop it and set a new goal. Don't wait until the quarter ends. The advantage of small teams is flexibility; don't let the quarterly cycle box you in.

Relationship with Annual Planning

Quarterly rolling doesn't mean abandoning long-term thinking entirely. I still recommend an annual strategic discussion, but that discussion should only set a "direction," not specific numbers. For example, "This year we want to go deep into the education sector" instead of "Revenue of $5 million this year." Quarterly goals are the concrete milestones along that direction.

Implementation Tips

1. Involve the whole team: When setting quarterly goals, let everyone participate and ensure shared understanding and buy-in.
2. Make it visible: Post quarterly goals and weekly plans somewhere public—a wall or shared doc—to increase transparency.
3. Weekly sync: Every Friday afternoon, spend 15 minutes: each person says one sentence about progress, next week's plan, and blockers.
4. Don't aim for perfection: The first quarter rolling may be rough, key results may be inaccurate. That's fine. Iterate continuously. It's better than your previous management method.

Summary

Small companies don't need annual planning. Quarterly rolling goals are a more fitting management method: they acknowledge uncertainty, emphasize quick response, and keep the team aligned. If you're tired of annual plans becoming empty paperwork, try shortening the cycle to three months.

PaxLee