A Quarterly Planning Framework That Actually Holds Together

Every planning framework we have encountered in practice breaks in one of two ways. Some are too aspirational—they generate inspiring objectives that never connect to Tuesday’s work. Others are too operational—they produce detailed task lists that lose sight of why any of it matters.

The framework we lay out here was built to avoid both failure modes. We call it the Four Corners Framework. It synthesizes the strongest elements of OKRs, the 12 Week Year, and Amazon’s narrative planning practice into a single coherent system that a team of two to eight people can run without a dedicated planning coordinator.

The Underlying Problem: The Gap Between Intention and Execution

Planning frameworks fail at a predictable point. The quarterly plan is set with genuine enthusiasm. The first two weeks feel aligned. Then a product fire, an unexpected customer demand, or a leadership distraction pulls attention sideways. By week four, the plan exists as a document rather than a living operating guide.

Brian Moran and Michael Lennington documented this pattern in The 12 Week Year and traced it to the absence of execution tracking. Most quarterly plans measure outcomes (did we hit the metric?) rather than execution (did we do the work we said we would?). Outcomes lag by weeks or months. By the time the metric shows a problem, it is too late to course-correct within the quarter.

The Four Corners Framework addresses this by separating what you want to achieve (the objective layer) from what you need to do each week to achieve it (the execution layer), and treating both as mandatory inputs to the weekly review.

The Four Corners: What They Are

The framework is organized around four interdependent elements, arranged as the corners of a single planning document.

Corner 1: The Destination Statement A three-to-five sentence narrative description of the state you want to be in at the end of the quarter. Written in present tense as if the quarter has just ended. “We have closed six enterprise contracts. Our gross margin has improved to 68%. The new engineering hire is fully onboarded and has shipped their first independent feature.”

This is borrowed from Amazon’s narrative planning tradition. The act of writing the destination in prose—rather than bullets—forces a more honest reckoning with what the team is actually capable of. Bullet points allow vague commitments; sentences expose them.

Corner 2: The Objectives Stack Two to four objectives that are the primary levers for reaching the destination state. Each objective is paired with one to three Key Results (measurable outcomes that confirm the objective was achieved).

The objectives are not task lists. They are outcomes. Each one should answer the question: “What would have to be true for us to say this quarter was a success?”

Corner 3: The Capacity Budget A realistic accounting of available hours per week for planned work, after accounting for meetings, administration, and unexpected issues. For most knowledge workers, available deep work hours per week are considerably lower than nominal work hours suggest—typically 15–20 hours per week when meetings, email, and reactive work are accounted for.

The capacity budget forces prioritization. If the two to four objectives would require 40 hours of deep work per week and the team has 20 available, something must come out of the plan before it begins rather than falling out of it mid-quarter.

This corner is absent from most frameworks and is the reason most plans are structurally impossible at the moment they are approved.

Corner 4: The Weekly Execution Scorecard A simple tracker: for each week, list the three to five planned actions that would advance the objectives. At the end of the week, score completion as a percentage. Moran and Lennington’s research suggests 85% weekly execution rate is the threshold for consistent quarterly goal achievement.

The scorecard is reviewed every Monday morning in a 15-minute session. No narrative required—just the percentage and one sentence on the biggest blocker from last week.

How to Build Your Four Corners Document

Set the Destination First

Before naming any objectives, write the destination statement. Allow 20 minutes for this. Resist the temptation to jump to objectives immediately—the destination statement is what prevents you from selecting the wrong ones.

A useful forcing question: “If I had to explain to a skeptical board member or investor exactly what we accomplished this quarter, what would I want to be able to say?”

Write it. Then read it back. If it does not feel ambitious enough to be worth a quarter of effort, or realistic enough to be achievable with the team and resources you have, adjust before moving on.

Select the Objectives

From the destination statement, identify the two to four initiatives that are most direct paths to that described state. For each, ask: “Is this the highest-leverage thing we could work on, or are we including it because we feel we should?”

This question will eliminate roughly a third of the candidates that initially feel important. That elimination is the planning process working correctly.

Write each objective as an outcome, not a project:

• Not: “Work on the new onboarding flow”
• Yes: “Reduce onboarding drop-off from 45% to 25%”

Then add one to three Key Results that would confirm the objective was achieved. These should be measurable by the end of the quarter without ambiguity.

Build the Capacity Budget

For each team member involved in the quarterly plan, estimate:

• Hours per week in recurring meetings
• Hours per week in reactive communication (email, Slack, support)
• Hours per week available for planned work

Total the planned work hours and compare to what the objectives actually require. If there is a gap—and there usually is—decide explicitly whether to reduce scope, add resources, or accept a higher risk of partial completion.

This is uncomfortable. It is also the most valuable 20 minutes of the planning session.

Map the Execution Scorecard Template

Create a 13-row table, one row per week. For week one, fill in the three to five planned actions that would visibly advance at least one objective. Leave weeks two through thirteen blank for now—you will fill each week in the Monday review.

This is the difference between a planning document and an operating tool. The planning document tells you where you are going. The execution scorecard tells you whether you are actually moving.

Three Examples of the Framework in Practice

A product team at a 40-person company. Their destination statement for the quarter: “We have shipped the redesigned onboarding experience, reduced drop-off to below 30%, and collected structured feedback from 50 enterprise users.” Their objectives: reduce onboarding drop-off, ship the API documentation update, and run 50 structured user interviews. Their capacity budget revealed they had 25 available deep work hours per week across three people—enough for two objectives confidently, three at risk. They deprioritized the API documentation to a stretch objective. Mid-quarter, they hit the onboarding target at week eight and pulled the API work back into active status for weeks nine through twelve.

A freelance consultant. Her destination: “I have signed two new retainer clients and delivered the strategic audit for the healthcare engagement.” Her capacity budget showed that client delivery, administration, and prospecting together consumed 38 of her 45 working hours per week, leaving 7 hours for business development. Her objectives were adjusted to reflect that constraint. The execution scorecard revealed in week two that she was spending 4 of those 7 hours on low-priority prospecting channels. She reallocated before the pattern solidified.

A two-person founding team. Their destination: “We have ten paying customers and a clear hypothesis about which segment converts fastest.” Because they were pre-revenue, their objectives were predominantly learn-based rather than scale-based: run 30 discovery calls, close first three paying customers, test two different pricing structures. The capacity budget conversation revealed a misalignment—one founder assumed the other would lead customer calls. Making that explicit in week one prevented a coordination gap that would otherwise have surfaced at week five.

Using AI to Populate Each Corner

Each corner of the framework has a natural AI-assist point.

For the destination statement, feed the AI your last quarter’s results and your company’s annual goals, and ask it to draft a destination statement for review and editing. The draft will rarely be exactly right—but it will be faster and more concrete than starting from a blank page.

For objective selection, describe your top six to eight candidate objectives and ask the AI to identify which three are most directly tied to the destination statement and which can be deferred. Use the output as a pressure test, not a final decision.

For the capacity budget, paste your calendar from a representative week and ask for an analysis of planned vs. unplanned time. The output will inform your available-hours estimate without requiring a full time audit.

Beyond Time integrates this kind of AI-assisted quarterly review into a structured workflow—from retrospective prompts to milestone mapping—so the Four Corners setup can be completed in a single focused session.

What to Do When the Plan Breaks

Plans break. The question is not whether a quarterly plan will encounter unexpected obstacles but whether the team has a protocol for addressing them.

At the mid-quarter review (week six or seven), evaluate each objective against three options:

Persist — The objective is still the right priority and the team is on track or close to it. Continue as planned.

Adjust — The objective is still right but the scope, timeline, or approach needs revision based on what was learned in the first half. Rewrite the Key Results to reflect the adjusted target.

Deprioritize — The objective is no longer the highest-leverage use of the team’s remaining capacity. Move it explicitly to the backlog for next quarter. This is a legitimate planning decision, not a failure.

The mid-quarter review is not a morale event. It is a resource allocation decision. Treat it accordingly.

This week, write one destination statement for next quarter—three to five sentences in present tense as if the quarter just ended. That single document is the most valuable planning artifact you can produce.

Related:

• The Complete Guide to Quarterly Planning Frameworks
• How to Do Quarterly Planning
• Team Runs Quarterly Planning: A Case Study
• Long-Term vs. Short-Term Goals

Tags: quarterly planning framework, OKRs, 12 week year, goal setting, execution