Quarterly Goal Reset: Keep, Change, or Stop

Keep a quarterly goal when its result still matters and a credible plan fits the remaining capacity. Change it when the result matters but the scope, method, or timing no longer fits. Stop it when the reason for pursuing it has disappeared or the remaining cost no longer makes sense. Make the decision from evidence about the work ahead, not embarrassment about the work already invested.

Bring the original goal, its measures, actual results, remaining work, and available hours to one review. Separate a useful outcome from a favorite activity. Choose keep, change, or stop for each goal, assign a decision owner, and communicate the consequences. Leave with a dated next action and a review trigger. A reset should reduce uncertainty about what people will do next week.

Before rating progress, write the original intended benefit in one sentence. “Publish a weekly newsletter” describes an activity. “Help current customers find answers that reduce avoidable support requests” describes a possible reason for that activity. If the team no longer agrees about the reason, settle that disagreement before negotiating a new number of newsletters.

Retrieve the original target and date rather than quietly editing them to match current performance. Keep a short record of changes so the team can learn which assumptions were wrong. This is not an exercise in assigning blame. It prevents a moving target from obscuring whether the work created value.

Ask who would notice if the goal disappeared. A named customer, colleague, or operational dependency makes the benefit easier to examine. If nobody can identify a beneficiary or consequence, the goal may have become a habit rather than a current priority.

The first column is results: what happened for the intended beneficiary. The second is activity: what the team did. The third is explanation: what might account for the gap. Keeping them separate prevents “we worked hard” from substituting for a result and prevents a plausible story from being treated as established cause.

For example, a hypothetical team may have published eight help articles, observed unchanged support volume, and learned that customers rarely encountered those articles. The result does not prove that documentation is useless. It suggests a question about discovery, relevance, or measurement that the next decision should address. Record what is observed and what remains a hypothesis.

Use comparable periods and definitions. If a metric changed midway through the quarter, explain the change before comparing the numbers. Note data gaps directly rather than filling them with a confident estimate that nobody can reproduce.

The fourth row is a temporary state, not an escape route. Specify the missing fact and the time allowed to learn it. If the team cannot explain what evidence would change its decision, more research is unlikely to resolve the disagreement.

List the work still required and identify the people who must do it. Subtract existing commitments, routine operations, planned leave, and necessary support time from the available calendar. Do not allocate the same hours to several goals because each appears reasonable on its own.

Use ranges for uncertain tasks and identify the bottleneck. A project may require only a few hours of design work but depend on a specialist who is unavailable until next month. Moving the deadline on a slide does not create that capacity. Either change scope, obtain a real commitment, or choose a later delivery date.

Reserve space for inevitable coordination. A goal that fits only if every handoff is instantaneous and every attempt succeeds is a fragile plan. Ask what would be removed from the week if an urgent request arrived, and make that priority explicit now.

When choosing change, name the dimension: outcome, scope, method, owner, measure, or date. If all six change, treat the result as a new goal and close the old one transparently. That distinction keeps the record useful and helps people understand whether previous commitments still apply.

In the documentation example, the team might retain the desired customer benefit, reduce the publishing target, and test whether adding relevant article links to existing support replies improves discovery. That is a proposed experiment, not a guaranteed solution. Name the observation that would support continuing it and the result that would lead to another change.

Avoid changing a metric simply because it is easier to improve. A substitute measure should better represent the intended benefit, and the team should explain its limitations. More clicks may be useful evidence of discovery without proving that customers solved their problems.

Stopping an internal goal does not automatically cancel commitments to customers, staff, or partners. Identify those obligations and arrange a responsible handoff or closure. Preserve reusable research, explain where files live, and remove obsolete meetings and reminders so the stopped work does not continue invisibly.

Write a short closure note with the decision date, reason, remaining responsibilities, and person accountable for each. Avoid framing the decision as proof that the people involved failed. The review should distinguish a poor assumption, a changed environment, and a delivery problem, because each implies a different lesson.

Give the next action a cue and a concrete behavior. “When the Monday planning meeting ends, I will reserve the two agreed writing blocks” is easier to act on than “be more focused.” Research on implementation intentions studies this kind of if-then planning as a way to support follow-through, with effectiveness depending on context and how plans are formed. It does not establish that this quarterly worksheet guarantees better results. Research recommendations on planning interventions[1]

Ask the owner to restate the action in their own words. Then record the first review date and a trigger for earlier review, such as a dependency failing or a material change in demand. A useful review trigger tells the team when its current assumptions may no longer hold.

Send the goal records and evidence before the meeting. During the meeting, resolve one goal at a time: intended benefit, observed results, remaining cost, decision, owner, and next action. Park unrelated ideas in a separate list so they do not consume the capacity the review is trying to protect.

End by reading the decisions aloud and asking affected people what remains unclear. Update the shared plan immediately. A private agreement between managers is incomplete when the people doing the work still see last quarter's priorities in the task system.

Is stopping a goal the same as giving up?.

The useful question is whether the remaining work still deserves the resources. Stopping can be responsible when the benefit has changed; persistence can be responsible when a valuable goal has a credible path. Neither choice should be automatic.

What if progress is slow but learning is valuable?.

Name the learning objective and the decision it will support. Give that investigation a scope and end date. Otherwise “learning” can become an indefinite justification for continuing work that no longer has a clear purpose.

Where should I start if I have too many goals?.

Select the goals competing for the same scarce resource. Compare their remaining benefit and obligations, then choose what receives capacity first. Use the ResultsBreakthrough resource library to support the weekly routines that follow the reset.