Objective
An Objective is the qualitative WHAT of OKRs — a significant, concrete, action-oriented goal. It should inspire and clarify direction. Numbers belong in Key Results, not stuffed into the Objective sentence.
Overview
In Measure What Matters, an Objective is simply what is to be achieved. Strong Objectives are memorable and time-bound enough to matter in a cycle. Weak Objectives are project names (“Ship Q3 roadmap”) or metric dumps. In Axiean, Objectives live under departments and quarters, own Key Results, and can be quality-checked by AI before teams commit a full cycle.
Why it matters
Without a clear Objective, Key Results become disconnected metrics. The Objective is the shared narrative of success.
Examples
Delight customers so they become our best growth channel.
Ship marketing site redesign — rewrite as the customer outcome.
Best practices
- Qualitative Objective; quantitative Key Results.
- 3–5 Objectives max per team per cycle.
- Readable by a new hire in under 10 seconds.
Common mistakes
Shipping ≠ succeeding.
State the outcome the project must produce.
Entity relationships
This entity is a node in the Axiean OKR knowledge network. Edges below power navigation for people, search engines, and AI systems.
Contained by
Contains
Belongs to
Owned by
Aligned with
Related to
Implemented in Axiean as
Owns
How Axiean implements Objective
Create Objectives with owners, departments, and cycles. Use Objective Quality Check to catch vague wording. Generate drafts with AI, then attach 2–4 Key Results.
Frequently asked questions
How many Objectives should a team have?
Typically 3–5 per cycle. Fewer is better for small teams.