Turn Strategy into a Few Team Goals with Measurable Key Results

## Decide Why the Goal System Is Used and How Often Goals Are Reviewed Establish why the organization is using a goal system before asking teams to write goals. The method may support strategic focus, cross-team alignment, learning, or resource decisions, but confusion follows when different groups assume different purposes. - State what the goal system will influence and what remains outside its scope. - Define the planning horizon, review cadence, ownership roles, and decision forums. - Explain how ambitious commitments differ from dependable delivery promises. - Give participants a shared vocabulary for outcomes, evidence, progress, and closure. ## Write Goals as Changes Worth Making, Not Lists of Tasks Describe the change worth creating rather than the work people expect to perform. A strong objective gives a team direction and a clear end state while leaving room to choose or revise the method as evidence develops. - Connect each objective to a customer, operational, strategic, or mission-level benefit. - Use concrete language that an independent reviewer can interpret consistently. - Focus the portfolio so attention and resources are not diluted across many priorities. - Replace maintenance phrases with the specific improvement or protected condition that matters. ## Give Each Goal Key Results with a Starting Point, Target, and Data Source Use key results to show whether the intended outcome is becoming real. Each measure should capture a consequential change, have a defined starting point and target, and rely on evidence that can be located and checked without relying on personal opinion. - Define the metric, population, calculation, data source, owner, and target date. - Measure effects and completed states rather than meetings, analysis, or participation. - Cover the conditions needed for the objective, including quality and risk where relevant. - Test whether reaching every key result would provide credible evidence that the objective advanced. ## Label Stretch Goals Apart from Goals Others Depend On Choose ambition deliberately. Exploratory goals can encourage discovery beyond routine plans, while committed goals protect outcomes that stakeholders depend on. Mixing the two without labels makes forecasts unreliable and turns missed experiments into apparent delivery failures. - Label the type of goal and define what success, partial progress, and failure mean for it. - Check that the goal creates value even if it is not fully achieved. - Compare expected benefit with capacity, uncertainty, dependencies, and downside risk. - Communicate confidence and assumptions whenever another team plans around the result. ## Link Team Goals to Higher Goals Without Copying the Same Words Create a traceable connection between organization, portfolio, team, and individual work without duplicating the same statement at every level. A team may support one strategic outcome deeply rather than mentioning every organization-wide priority. - Map each lower-level objective to the higher-level result it is expected to influence. - Combine leadership direction with evidence and proposals from people closest to the work. - Identify gaps, overlaps, conflicting incentives, and dependencies across teams. - Preserve local choice over methods while keeping shared outcomes and boundaries visible. ## Share Goals, Owners, and Status Where Everyone Can See Them Publish the goals, measures, owners, assumptions, and current status to the people who coordinate around them. Visibility supports rational trade-offs and early help, but it works only when updates are understandable, current, and safe for the intended audience. - Assign one accountable owner to each objective and one reporting owner to each measure. - Record dependencies and the people responsible for resolving them. - Use a consistent status vocabulary with evidence behind every material change. - Maintain an accessible source of truth and archive superseded versions for traceability. ## Keep Goal Results Separate from Judging Individual People Treat goal results as evidence about plans, assumptions, execution, and external conditions rather than as a complete judgment of a person. Directly tying every ambitious result to individual appraisal encourages conservative targets and distorted reporting. - Define which evidence may inform evaluation and which goal signals are diagnostic only. - Consider contribution, judgment, collaboration, constraints, and outcome quality together. - Review unusual results for context before drawing conclusions. - Protect honest reporting by rewarding early disclosure of risk and useful learning. ## Use Check-ins to Decide Whether to Continue, Change, or Stop Use scheduled check-ins to make decisions, not merely to collect status. Review the latest evidence, compare it with the expected path, surface changes in assumptions, and direct attention toward goals where intervention can still improve the outcome. - Confirm the current measure, trend, confidence, and evidence date. - Reassess dependencies, capacity, external changes, and emerging risks. - Decide whether to continue, adapt the method, add support, narrow scope, or stop. - Record the decision, rationale, owner, and next review point. ## Catch Weak Goals, Such as Task Lists or Easy Targets, Before Starting Review draft goals for structural problems before committing resources. Common failure patterns include activity lists presented as outcomes, measures that cover only part of the objective, low-value success, hidden dependencies, easy targets, and incompatible expectations. - Ask what would materially improve if the goal were fully achieved. - Check whether the evidence can be independently verified and discovered in time. - Compare the goal portfolio with the highest-value available work and real capacity. - Rewrite vague, incomplete, or gameable measures before they become reporting problems. ## Score Results at the End of the Period and Carry Lessons into the Next Plan At the end of the period, evaluate results consistently and turn the review into input for the next plan. A score without an explanation hides useful information, while an explanation without evidence makes comparisons and resource decisions unreliable. - Evaluate each key result from the agreed data and calculation. - Explain material differences between expected and observed outcomes. - Separate design flaws, execution choices, dependency failures, and external changes. - Keep, revise, retire, or replace each goal based on current value and evidence.