Understanding OKR and OGSM: How to Set Effective Objectives and Key Results
This article explains the purpose of OKR, how it addresses focus, transparency, measurement, and motivation, outlines the iterative top‑down and bottom‑up process for creating OKRs, discusses when to include launch dates, and compares OKR with the OGSM framework for strategic planning.
Many teams spend a lot of time writing OKRs, and the understanding of OKR varies widely; some write them merely to fulfill a requirement.
This article discusses what problems OKR solves for an organization, how to generate OKRs, whether to include launch dates, and the relationship between OKR and OGSM.
OKR is a goal‑management tool that helps organizations set, track, and achieve objectives.
It addresses four main issues: (1) focus and prioritization, helping limited resources concentrate on the most important tasks; (2) transparency and alignment, allowing teams to see each other's goals and work toward a common direction; (3) measurement and tracking, providing a mechanism to regularly check key results and adjust strategies; and (4) employee engagement and motivation, using challenging goals to inspire and give a sense of achievement. It also enhances execution capability.
For technical team managers, creating OKRs is an iterative process that moves from top‑down to bottom‑up.
Top‑down: leaders define the organization’s vision and strategic objectives for the year or quarter, drafting the first version of OKRs to give clear direction.
Bottom‑up: managers and team members evaluate those objectives based on their roles and business knowledge, providing feedback that fosters ownership and ensures goals are realistic.
Multiple discussions and adjustments between leadership and teams create shared ownership and commitment, resulting in challenging yet feasible goals and broader organizational participation.
A common dilemma is whether to include a product’s launch date in an OKR; the decision depends on relevance, measurability, and controllability.
If the launch date is tightly linked to the objective, serves as a key metric, and the team can control it, it can be a Key Result; otherwise it is better treated as a milestone rather than a KR.
When the launch date carries strategic significance, it can be reframed as an OKR, e.g., Objective: launch a new product to increase market share; Key Result: achieve 100,000 users within three months after launch.
If market timing is critical, an objective like “capture market opportunity quickly” can have a KR such as “complete product launch before [date] to meet seasonal demand.”
The article then introduces OGSM, another strategic planning framework that predates OKR.
OGSM stands for Objectives, Goals, Strategies, and Measures.
Each component is defined: Objectives are the overarching vision; Goals are quantitative targets; Strategies describe how to achieve the goals; Measures are the metrics (including dashboards and plans) used to track progress.
Compared with OKR’s rapid iteration, OGSM is typically used for annual planning and provides a longer‑term perspective.
Key points for writing OGSM include: setting a clear Objective, aligning Goals with the Objective and following SMART criteria, ensuring Strategies support the Goals, linking Measures to Strategies, creating dashboards that truly measure execution, and avoiding confusion between dashboards and plans.
The flow can be summarized as O → G → S → M, where each strategy has corresponding measures and supporting plans.
OGSM’s strength lies in its structured, hierarchical approach that not only sets goals but also outlines how to achieve them and how to measure success.
By using OGSM, organizations ensure that strategic planning includes concrete action plans and metrics, keeping teams focused and adaptable to changing market conditions.
Both OKR and OGSM require understanding the underlying logic and aligning the tools with the organization’s culture, workflows, and collaborative practices.
Architecture and Beyond
Focused on AIGC SaaS technical architecture and tech team management, sharing insights on architecture, development efficiency, team leadership, startup technology choices, large‑scale website design, and high‑performance, highly‑available, scalable solutions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.