What is an Objective?
An objective is a clearly defined, qualitative goal that expresses what a team or company wants to accomplish. In the OKR framework, objectives provide direction while key results provide measurable milestones.
A well-written objective answers: "If we achieve this, what will be different?" It should be ambitious enough to stretch the team but realistic enough that success is possible.
Why Objectives Matter
Without clear objectives, teams optimize locally. Engineers ship features that are technically interesting. Designers polish pixels that do not matter. PMs chase metrics that do not align with company strategy. Objectives create shared purpose.
Objectives also enable autonomy. When a team knows the destination, they can choose the route. This is the difference between a team that executes tasks and a team that owns outcomes.
How to Set Good Objectives
Derive objectives from product strategy. If your strategy is to win the enterprise segment, an objective might be "Become the default tool for enterprise product teams." This gives the team direction without prescribing specific features.
Make objectives outcome-oriented, not output-oriented. "Launch redesigned onboarding" is an output. "Make new users successful in their first session" is an outcome. Outcomes give teams room to find the best solution.
Write in plain language. If the objective requires a glossary to understand, simplify it. The best objectives are ones the team can repeat from memory.
Set a time horizon. Quarterly objectives work for most teams. Annual objectives are too distant to create urgency. Monthly objectives are too short for meaningful work.
Objectives in Practice
Intel, where OKRs originated, used objectives like "Demonstrate that the 8086 processor is the best 16-bit processor family." This objective was ambitious, clear, and directly tied to the company's competitive position.
At Google, a team objective might read: "Make Google Docs the fastest way to collaborate on documents." This gives the team creative freedom while making the desired outcome unmistakable.
Common Pitfalls
- Objectives disguised as tasks. "Ship v2.0" is a project milestone, not an objective. Ask "why does v2.0 matter?" to find the real objective.
- Too many objectives. If everything is a priority, nothing is. Force rank and cut.
- No connection to strategy. Objectives should ladder up to company strategy. If a team's objective does not connect, it is either misaligned or the strategy is unclear.
- Playing it safe. Objectives that the team is certain to hit do not stretch performance. Set targets that require real effort.
Related Concepts
Objectives pair with key results in the OKR framework. They should align with the company's product vision and product strategy. For company-level direction, see north star framework.