How a 12-Person Team Rebuilt Their Quarterly Planning Process (Case Study)

This is a composite case study drawn from the planning patterns we have observed across multiple product and software teams. The company, team members, and specific metrics are illustrative, but the failure modes and remedies are real.

The Baseline: OKRs That Nobody Used

Volante Software (12-person B2B product team, two product managers, six engineers, two designers, and two growth marketers) had been running OKRs for three quarters by the time they decided something had to change.

The symptoms were familiar. Each quarter began with a two-hour planning meeting that produced a well-formatted OKR document. The document lived in Notion. It was referenced twice: at the planning meeting and at the end-of-quarter retrospective. In the eleven weeks between those two events, it was effectively ignored.

The team’s lead PM, Anika, described the dynamic accurately: “We would set five company OKRs and eight team OKRs and then spend the quarter doing whatever felt most urgent. At the retrospective we would score everything around 60% and tell ourselves the OKRs had been ambitious.”

The 60% score was technically within the acceptable OKR range (the conventional target is 70%). But when Anika examined what had been completed versus what the team had actually worked on, she found that execution had been disconnected from the OKRs almost entirely. The team had shipped meaningful product improvements that were not in the OKRs and had not meaningfully advanced two OKRs that were supposedly top priorities.

The OKRs were not failing because the goals were wrong. They were failing because there was no mechanism connecting the quarterly goals to weekly decisions.

Version 1: Adding a Weekly Review, Keeping the OKRs

Anika’s first intervention was minimal: add a 30-minute Monday team meeting specifically for weekly planning, using the OKRs as the explicit input.

The first two weeks went well. The meeting was energizing. People felt connected to the quarterly goals in a way they hadn’t before.

Week three, the meeting was cancelled because of a critical customer escalation that consumed the Monday morning. Week four, it was shortened to ten minutes because of a product launch. By week five, the meeting had been dropped from the calendar without a formal decision.

The failure revealed a structural problem beyond habit: Volante’s Monday mornings were structurally unavailable for planning. A recurring customer support escalation review, a standup with the CEO, and a product demo rotation collectively consumed most of the morning. The weekly planning meeting had been inserted into a full schedule and was the easiest thing to drop when something more urgent appeared.

The lesson was not that weekly reviews don’t work. It was that they need protected time, not borrowed time.

Version 2: Restructuring Around a Dedicated Planning Block

For the following quarter, Anika made two changes. She moved the weekly planning session to Wednesday afternoon—historically the team’s lowest-urgency time slot—and she reduced the OKR stack from 13 (five company plus eight team) to six (two company plus four team).

She also introduced a simple execution scorecard, borrowed from the 12 Week Year model: each team member committed to three planned actions at Wednesday’s meeting and self-reported completion at the following Wednesday before new actions were set.

The results were materially better. The Wednesday meeting survived the full quarter with one cancellation (a company offsite week) and one condensed session (25 minutes instead of 30). The execution scorecard showed an average weekly completion rate of 72%—below the 85% threshold Moran and Lennington identify as the high-performance zone, but dramatically better than the implicit zero of the prior quarters.

Two of the four team-level OKRs were fully achieved. One was 70% complete. One was substantially incomplete—but the team knew by week eight why it was falling short, and made an explicit decision to deprioritize it rather than discovering the gap at the final retrospective.

That last point was the most significant change. The quarterly plan had become a live document rather than a static one.

Version 3: Adding Narrative Planning at the Quarter Boundary

The quarter after Version 2 introduced one more element: a brief written narrative before the OKRs were finalized.

Anika had encountered Amazon’s narrative planning approach and adapted it to a one-page format. Before the quarterly planning meeting, each function (product, engineering, growth) submitted a one-page narrative covering: what happened last quarter and why, what the function believed were the highest-leverage priorities for the coming quarter, and what resources or decisions they needed.

The narratives were distributed 48 hours before the planning meeting. The meeting began with silent reading rather than a presentation.

The effects were immediate. Three priorities that had been assumed to be uncontroversial turned out to have significant disagreement within the team once the reasoning was written out. The growth team’s narrative revealed an assumption about sales cycle length that differed materially from the product team’s assumption—a misalignment that would have produced contradictory OKRs if it hadn’t been surfaced in the narrative.

The planning meeting became a discussion rather than a presentation. The OKRs that emerged were more genuinely owned by the team because the underlying reasoning had been examined, not just the goals.

The Stable State: What the Process Looks Like Now

By their fourth quarter running this combined approach, the Volante team had settled into a process that took approximately four hours of total team time per quarter:

• Week 12 of outgoing quarter: Individual one-page narratives submitted by function leads. (45 minutes per author)
• Thursday of week 13: Two-hour planning meeting: 30 minutes of silent reading, 90 minutes of discussion leading to agreed OKRs and initial weekly milestones for the first four weeks.
• Every Wednesday: 25-minute weekly review. Previous week’s scorecard. Current week’s planned actions for each team member. One blocking issue surfaced and assigned.
• Week 7: One-hour mid-quarter review. OKR status, explicit persist/adjust/deprioritize decisions for each objective.
• Week 13: 90-minute retrospective feeding into the following quarter’s narratives.

The process is not complicated. What makes it work is that it is consistent. The Wednesday meeting has survived 11 consecutive weeks in the current quarter. The OKR stack has stayed at six. The narratives have gotten better as the team has learned what the format reveals.

Anika’s summary of what changed: “We stopped using OKRs as a reporting format and started using them as an operating agreement. The difference is that everyone on the team can tell you what the two company OKRs are right now and what they personally did last week that connects to one of them.”

What This Team’s Journey Reveals

Three patterns emerge from this case that apply broadly.

The framework matters less than the consistency of execution reviews. Version 1 (OKRs with a weekly review) failed because the review didn’t survive. Version 2 (same OKRs, protected time for reviews) worked significantly better. The framework was identical; the execution infrastructure was different.

Narrative planning surfaces misalignments that structured templates hide. The one-page narrative at the quarter boundary added 45 minutes of work per function lead and prevented one significant planning error in its first use. That is a high-return investment.

Fewer objectives create more genuine ownership. The reduction from 13 OKRs to 6 did not reduce the team’s ambition—their actual output in the structured quarters exceeded the output of the OKR-heavy quarters. It reduced the dilution that made ownership feel abstract.

Beyond Time supports this kind of structured quarterly rhythm with built-in retrospective prompts, scorecard tracking, and weekly review templates—so the process infrastructure doesn’t have to be rebuilt from scratch each quarter.

The One Thing Most Teams Get Wrong

The most common error in quarterly planning is treating the framework as the solution. Teams read about OKRs, set up a Notion template, and expect the structure to produce alignment and execution automatically.

Frameworks are not self-executing. They are coordination protocols—agreements about how a team will make decisions together across a time period. A coordination protocol only works if the team actually uses it: references it in weekly decisions, updates it when reality diverges from the plan, and reviews it honestly at the end.

The Volante team’s success was not a function of which framework they used. It was a function of building the habits and structural protections that made the framework a live operating tool rather than a quarterly document.

This quarter, pick one element of your planning process that is currently inconsistent—the weekly review, the mid-quarter check-in, or the retrospective—and make it explicitly protected time before anything else.

Related:

• The Complete Guide to Quarterly Planning Frameworks
• Why Quarterly Planning Drifts by Week 4
• A Quarterly Planning Framework That Actually Holds Together
• Beyond Time Quarterly Walkthrough

Tags: quarterly planning, case study, OKRs, execution, team planning