Your Quarterly Plan Needs a Next Step for the Work That Didn't Get Done

Six · 6 min read · April 14, 2026

Your Quarterly Plan Needs a Next Step for the Work That Didn't Get Done

Say you run customer success at a software company. Last quarter's objective was to get one group of accounts ready to renew. The key result was their renewal rate, and the plan was to offer them an early-renewal discount.

The quarter is over and the objective is still open. Your team finished the account research, and it turned up something the plan didn't expect. Price isn't what's making these customers hesitate. Most of them never got their teams set up on the reporting they bought, so they aren't sure what they're paying for. And since their contracts don't come up until next quarter, the renewal rate hasn't been measured yet.

The planning meeting for the new quarter is on the calendar. The easiest move is to copy the objective across, keep the discount, and call it momentum.

That skips the decision. With what your team learned, there are really three options: keep going because the work still matters and the approach still holds, rescope because the original bet no longer fits, or stop because the company needs that attention somewhere else. Picking one is a leadership call, and it's a much easier call to make when last quarter's record is still intact.

Start with an honest record of the quarter

Before anyone writes next quarter's plan, write down what happened in this one. It doesn't need to be long. For the renewal objective, it might read like this:

The missing measurement goes in the record as missing. It doesn't mean renewals went to zero. Here it means the result needs more time to show up. On another team it might mean nobody set up a way to measure the work, or that the key result was the wrong measure in the first place. A tidy retrospective that scores the gap as zero would tell you the quarter failed, when what actually happened is that you learned why your customers hesitate.

That record isn't there to punish anyone for missing the plan. It's what you need to decide whether the work deserves a new commitment. Google's OKR playbook takes the same view of goals a team commits to deliver. One that misses its due date "requires a postmortem," and the playbook adds, "This is not intended to punish teams." If your renewal objective was a committed one, the postmortem already has its finding: the plan assumed price was the problem, and it wasn't.

Choose one of three paths

Put the record in front of the people who can change the objective's future, and pick one.

Choice When it fits What the next record needs
Continue The outcome still matters and the original approach is still credible. A next-quarter objective linked to the earlier one, with a current owner and a renewed success measure.
Rescope The outcome matters, but the target, audience, method or timing no longer fits what you learned. The exact change, why it changed, and which earlier assumptions and work still count.
Stop The opportunity, the evidence or the company's priorities no longer justify more work. The reason, the finished work worth keeping, and any obligation or risk that still needs an owner.

For the renewal objective, continuing as written would mean sending a discount the research says won't help, while the customers stay unsure what their reporting is for. Rescoping fits better. The outcome still matters, because these accounts still have to renew, but the method changes from a discount to getting each customer's team using the reporting they already pay for.

Stopping would also be a legitimate call if leadership decided the segment was too small to deserve another quarter. In that case you'd keep the research for the next time someone asks why those customers hesitate, and you'd still name someone to own the renewals coming due.

Google's playbook is stricter about stretch goals, which it calls aspirational OKRs. They "should remain on a team's OKR list until they are completed, carrying them forward from quarter to quarter as necessary." Dropping one "because of lack of progress is a mistake," since it hides persistent problems of prioritization, resources or understanding of the problem. Its only exit is a move to a team better placed to do it. We're less strict but keep the warning: slow progress isn't a reason to stop. A stop needs a reason about the opportunity, like leadership choosing to spend the time elsewhere. The renewal research undercut the method, not the need to renew these accounts, so it points to rescoping.

Carry the context forward without rewriting the past

If you rescope, the new objective should point back to the old one. Leave the original as it was: its quarter, its key result, the projects linked to it and what the evidence showed when the quarter closed. Then write the new commitment with its own quarter, owner and success measure.

That keeps two questions apart that tend to blur at planning time. What did we set out to do then? What are we choosing to do now?

If the old objective gets edited into the new one, the discount plan disappears from the record, and so does the reason you dropped it. A year from now someone proposes an early-renewal discount for the same customers, and nobody can say what the team already found out.

PeopleCues, an OKR tool, keeps the old version when you copy an objective into a new quarter. Its documentation says objectives and key results "are cloned, not moved, to ensure accurate reporting and auditability of completed work," and the copy's activity feed links back to the original. A spreadsheet can do the same: a new row for the new quarter, with a note saying where it came from.

Give the unfinished work a next assignment

"Carry forward" isn't an assignment. For the work you continue or rescope, write a new brief that answers five questions:

  1. What has to be true by the next review for this work to earn more attention?
  2. Which past work, sources and assumptions still hold, and which need checking again?
  3. What belongs inside the objective now, and what's explicitly out?
  4. Who accepts the result, changes the plan or stops it?
  5. When will the team decide again, so the next quarter doesn't silently inherit the same work?

For the renewal objective, the answers could be short. By the mid-quarter review, someone at every account in the segment has been trained on the reporting, and you know which accounts still aren't using it. The account research stands, and the idea that price drives the hesitation is out. Discounts are off the table this quarter. You own the result, and the team decides again at mid-quarter, before most of the renewals come due.

Where Supanova fits

Say last quarter's account research had been done by Supanova atoms. The rescoped objective doesn't have to start from nothing. You turn the brief above into a new project and attach last quarter's research to it, so your atoms can draw on what the team already learned. They might draft a reporting setup guide for each account and a plan for the onboarding calls your team will run, and the finished work comes back for your review. When you check it, you're asking what the brief asked: will this get someone at each account using the reporting before the mid-quarter review?

The brief comes after the decision, and the decision is still yours. You and whoever owns the renewals choose whether the objective continues, changes or ends, with last quarter's record in front of you.

Before your next planning meeting, pick one objective that didn't finish. Write down what happened, choose continue, rescope or stop, and give it a brief good enough to earn the next quarter. If it doesn't deserve one, stopping it on purpose is a better ending than letting it drift into another plan.

Explore Supanova at supanova.team.

Sources

LeadershipAI StrategyokrsQuarterly planning