The 10 guiding principles of real OKRs.

Principle 1. High-performing OKR teams need Psychological Safety and must overcome the Five Dysfunctions of a Team: build trust, embrace healthy conflict, commit despite disagreement, hold peers accountable, and focus on collective results.

In practice: debate vigorously but stay united on goals, address conflict openly, escalate problems quickly, and prioritize business success over individual accolades.

A 60-person company we worked with had 23 "priorities". We cut to four company OKRs. Two quarters later, every team could name all four unprompted, and progress tripled.

Principle 2. Everyone must read, understand, and be able to recall the Strategy, vision, priorities, and success metrics, because aligned autonomous decisions depend on it.

This comprehension is what makes Aligned Not Cascaded possible: teams that deeply understand strategy don't need approval chains to set good OKRs. Every OKR narrative should explain its connection to strategy.

The test we run in workshops: ask five people, separately, why this quarter’s OKRs exist. Five matching answers means aligned. Five different answers means you have goals, not strategy.

Principle 3. Raise the bar on critical thinking: assess ideas rationally and back them with evidence rather than gut feel. Use the Levels of Confidence scale to grade evidence, and actively counter Cognitive Biases.

Applied when proposing OKRs (OKRs as Bets), writing Key Result Narratives, and running OKR Risk Assessment.

The best question a leadership team can ask of a draft Key Result: "what evidence says this target is achievable, and what would have to be true for it to move?" Silence is your answer.

Principle 4. Be explicit about strategic metrics and levers: build Metric Trees that make cause-and-effect relationships visible, distinguish Input and Output Metrics, articulate hypotheses for each relationship, and refine the model continually.

Shared models create common language, better prioritization, and better Key Result selection. The goal is useful, not perfect.

A retention OKR went nowhere for two quarters until the metric tree showed the lever was onboarding completion, not support response time. Same effort, different lever, 14-point lift.

Principle 5. Limit OKRs to the wildly important. Attention and resources are finite; the more goals pursued at once, the less each gets. If everything is important, nothing is.

Fewer OKRs → more focus, better resource allocation, better execution, higher achievement, clearer communication. Practically: one (max two) active OKRs per team, worked in serial. See OKRs as Bets.

One team, one OKR. When a team insists it needs three, it usually means nobody has made the hard call yet. Making it is the moment the quarter starts working.

Principle 6. Focus on the meaningful changes you want to create, not the actions you plan to take: start with measurable value (observable benefits) and work backwards through behavior (how people change) to action (what we do).

Pitfalls it protects against: the Activity Trap, Solution Bias, and the Measurement Mirage. It's the reasoning behind avoiding Task-Based Key Results.

"Launch the new pricing page" became "Increase trial-to-paid conversion from 8% to 12%". Same work, but now the team kept iterating after launch, because launching was never the point.

Principle 7. OKRs represent the most critical objectives, so resource them for success: cross-functional Single-Threaded Teams with autonomy, de-risked collaboration (charters/SLAs), governance for conflicts, and invested leadership.

Includes "push & pull" management: managers proactively push their skills into OKR work and are pulled into BAU only where needed. See OKR Team Forming for the playbook.

Leadership sets the destination; the team that does the work writes the Key Results. Teams hit targets they set themselves and quietly sandbag targets they were handed.

Principle 8. OKRs define outcomes, not methods, so teams must articulate and continually discuss how they'll achieve them. Separate outcomes from Initiatives, Process Commitments and Experiments, make plans the focus of weekly OKR Check-ins, and update beliefs as evidence arrives.

Benefits: engagement, faster issue resolution, confidence, adaptability, and accountability.

A one-page narrative per OKR: what we believe, what would have to be true, what we’re not doing. New joiners understand the quarter in ten minutes instead of ten meetings.

Principle 9. OKRs drive transformative change; Business-as-Usual needs its own optimization approach, a metrics model, a KPI Scorecard, team-health monitoring, and root-cause fixes. Misunderstanding this distinction causes many failed OKR implementations.

Reserve OKRs for breakthrough goals (Operational Excellence OKRs at team level); let scorecards run the day-to-day.

The sales quota stays on the KPI scorecard with its own logic. The sales OKR rebuilds the engine: win rate, ramp time, segment mix. Mixing the two corrupts both.

Principle 10. Cascading OKRs level-by-level is slow, bureaucratic, and kills autonomy. Instead, alignment comes from three elements: strategy comprehension and recall (Strategy Alignment), outcome-focused execution capability, and clear impact narratives explaining why each OKR matters now.

Teams seek input but don't wait for approval; trust and strategic clarity replace approval processes.

Choices cascade; goals align. Teams read the company OKRs and answer "what is the biggest contribution we can make?" rather than receiving fragments of a target sheet.