Outcome-Based Planning | OKRs & Measurable Goals
Shift from output to outcome planning. Define OKRs, measure business impact, and connect daily work to key results with GitScrum tracking.
9 min read
Outcomes drive impact. GitScrum helps teams shift from output-focused planning to outcome-oriented delivery, ensuring work creates real value.
Outputs vs Outcomes
Understanding the Difference
OUTPUTS VS OUTCOMES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ OUTPUTS (What you build): │
│ ────────────────────────── │
│ • Features shipped │
│ • Lines of code │
│ • Story points completed │
│ • Tasks done │
│ │
│ OUTCOMES (What changes): │
│ ───────────────────────── │
│ • User behavior changed │
│ • Revenue increased │
│ • Customer satisfaction improved │
│ • Time saved │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ EXAMPLE: │
│ │
│ OUTPUT-FOCUSED: │
│ "Build a new checkout page" │
│ ✓ Shipped page = success │
│ │
│ OUTCOME-FOCUSED: │
│ "Increase checkout completion rate from 45% to 60%" │
│ ✓ Rate increases = success │
│ (may or may not need new page) │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ THE TRAP: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ││
│ │ OUTPUT THINKING: ││
│ │ "We shipped 47 features this quarter! Great quarter!" ││
│ │ ││
│ │ REALITY: ││
│ │ Revenue: Flat ││
│ │ User engagement: Down ││
│ │ Customer satisfaction: Lower ││
│ │ ││
│ │ LOTS OF WORK, NO IMPACT ││
│ │ ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ OUTCOME THINKING: │
│ "We improved checkout completion by 15%" │
│ This required: 3 features, 5 bugs fixed, 2 experiments │
│ CLEAR IMPACT │
└─────────────────────────────────────────────────────────────┘
Defining Outcomes
Writing Good Outcomes
CRAFTING OUTCOMES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ OUTCOME FORMULA: │
│ ──────────────── │
│ │
│ [VERB] + [METRIC] + [FROM X] + [TO Y] │
│ │
│ EXAMPLES: │
│ ✅ "Increase daily active users from 10K to 15K" │
│ ✅ "Reduce customer support tickets by 30%" │
│ ✅ "Improve page load time from 3s to 1.5s" │
│ ✅ "Increase NPS from 32 to 45" │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ BAD OUTCOMES (Actually Outputs): │
│ ❌ "Launch mobile app" │
│ ❌ "Build dashboard feature" │
│ ❌ "Implement authentication" │
│ ❌ "Complete redesign" │
│ │
│ FIX: │
│ ❌ "Launch mobile app" │
│ ✅ "25% of users active on mobile app" │
│ │
│ ❌ "Build dashboard feature" │
│ ✅ "Reduce time to find key metrics from 5 min to 30 sec" │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ OUTCOME LEVELS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ BUSINESS OUTCOME: ││
│ │ "Increase quarterly revenue by 20%" ││
│ │ │ ││
│ │ ▼ ││
│ │ PRODUCT OUTCOME: ││
│ │ "Increase checkout completion by 15%" ││
│ │ │ ││
│ │ ▼ ││
│ │ USER OUTCOME: ││
│ │ "Users can checkout in under 60 seconds" ││
│ │ │ ││
│ │ ▼ ││
│ │ FEATURE/OUTPUT: ││
│ │ "One-click checkout button" ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ Start with business outcome, work down │
└─────────────────────────────────────────────────────────────┘
OKRs Framework
Objectives and Key Results
OKR STRUCTURE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ OBJECTIVE (Qualitative): │
│ ───────────────────────── │
│ • Aspirational, inspiring │
│ • Describes desired state │
│ • Time-bound (quarterly typically) │
│ │
│ KEY RESULTS (Quantitative): │
│ ─────────────────────────── │
│ • Measurable evidence of progress │
│ • 3-5 per objective │
│ • Specific metrics with targets │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ OKR EXAMPLE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ OBJECTIVE: ││
│ │ Make our checkout experience best-in-class ││
│ │ ││
│ │ KEY RESULTS: ││
│ │ KR1: Increase checkout completion from 45% to 60% ││
│ │ KR2: Reduce average checkout time from 3 min to 90 sec││
│ │ KR3: Decrease cart abandonment from 70% to 55% ││
│ │ KR4: Achieve checkout NPS of 50+ ││
│ │ ││
│ │ INITIATIVES (How we'll achieve): ││
│ │ • Implement one-click checkout ││
│ │ • Add saved payment methods ││
│ │ • Simplify form fields ││
│ │ • Mobile checkout optimization ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ KEY RESULTS ≠ TASKS │
│ Key Results = Evidence of outcome achieved │
│ Initiatives = Work that may produce the outcome │
│ │
│ GRADING: │
│ 0.7+ = Success (stretch goals) │
│ 0.3-0.7 = Progress │
│ <0.3 = Needs attention │
└─────────────────────────────────────────────────────────────┘
Planning with Outcomes
Roadmap Structure
OUTCOME-BASED ROADMAP:
┌─────────────────────────────────────────────────────────────┐
│ │
│ TRADITIONAL ROADMAP (Output-based): │
│ ─────────────────────────────────── │
│ Q1: Build feature A, B, C │
│ Q2: Build feature D, E │
│ Q3: Build feature F, G, H │
│ (What if features don't solve problems?) │
│ │
│ OUTCOME-BASED ROADMAP: │
│ ────────────────────── │
│ Q1: Outcome → Initiatives │
│ Q2: Outcome → Initiatives │
│ (Initiatives can change, outcomes stay) │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ EXAMPLE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Q1 2025 ROADMAP ││
│ │ ││
│ │ ┌─────────────────────────────────────────────────────┐││
│ │ │ OUTCOME: Improve checkout conversion +15% │││
│ │ │ │││
│ │ │ INITIATIVES: │││
│ │ │ ├── One-click checkout │││
│ │ │ ├── Guest checkout option │││
│ │ │ └── Simplified form │││
│ │ │ │││
│ │ │ CURRENT PROGRESS: +8% (on track) │││
│ │ └─────────────────────────────────────────────────────┘││
│ │ ││
│ │ ┌─────────────────────────────────────────────────────┐││
│ │ │ OUTCOME: Reduce support tickets 30% │││
│ │ │ │││
│ │ │ INITIATIVES: │││
│ │ │ ├── In-app help center │││
│ │ │ ├── Improved error messages │││
│ │ │ └── Self-service account management │││
│ │ │ │││
│ │ │ CURRENT PROGRESS: -12% (needs attention) │││
│ │ └─────────────────────────────────────────────────────┘││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ FLEXIBILITY: │
│ If initiative isn't working → Try different approach │
│ Outcome stays the same │
│ Pivot on HOW, not on WHAT matters │
└─────────────────────────────────────────────────────────────┘
Measuring Success
Tracking Outcomes
OUTCOME MEASUREMENT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ LEADING vs LAGGING INDICATORS: │
│ ────────────────────────────── │
│ │
│ LAGGING (Outcome happened): │
│ • Revenue increased │
│ • Users grew │
│ • Churn decreased │
│ Slow to change, hard to influence directly │
│ │
│ LEADING (Predicts outcome): │
│ • Feature adoption rate │
│ • User engagement │
│ • Time on task │
│ Changes faster, more actionable │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ MEASUREMENT PLAN: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ OUTCOME: Improve checkout conversion +15% ││
│ │ ││
│ │ METRICS TO TRACK: ││
│ │ ││
│ │ LAGGING (Target metric): ││
│ │ • Checkout completion rate ││
│ │ • Measured: Weekly ││
│ │ • Source: Analytics ││
│ │ ││
│ │ LEADING (Early signals): ││
│ │ • Time to checkout (faster = better) ││
│ │ • Form completion rate per step ││
│ │ • Error rate in checkout ││
│ │ • Payment method usage ││
│ │ • Measured: Daily ││
│ │ ││
│ │ QUALITATIVE: ││
│ │ • User feedback/surveys ││
│ │ • Session recordings ││
│ │ • Support tickets about checkout ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ REVIEW CADENCE: │
│ ─────────────── │
│ • Weekly: Leading indicators │
│ • Monthly: Lagging indicators + trends │
│ • Quarterly: Outcome achievement │
└─────────────────────────────────────────────────────────────┘
Team Alignment
Connecting Daily Work to Outcomes
ALIGNMENT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ FROM OUTCOME TO DAILY WORK: │
│ ─────────────────────────── │
│ │
│ OUTCOME │
│ │ │
│ ▼ │
│ KEY RESULTS │
│ │ │
│ ▼ │
│ INITIATIVES/PROJECTS │
│ │ │
│ ▼ │
│ EPICS │
│ │ │
│ ▼ │
│ STORIES │
│ │ │
│ ▼ │
│ DAILY TASKS │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ VISIBILITY: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ STORY: CHECKOUT-234 ││
│ │ "Add saved payment methods" ││
│ │ ││
│ │ CONTRIBUTES TO: ││
│ │ Epic: One-click checkout ││
│ │ Initiative: Simplify checkout ││
│ │ Key Result: Checkout time < 90 sec ││
│ │ Objective: Best-in-class checkout ││
│ │ ││
│ │ WHY THIS MATTERS: ││
│ │ Saved payment methods reduce checkout time by ~45 sec ││
│ │ Current avg: 3 min → Target: 90 sec ││
│ │ ││
│ │ SUCCESS METRIC: ││
│ │ 40% of users using saved payment method ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ DAILY STANDUP: │
│ ────────────── │
│ "Working on saved payment methods" │
│ "This helps us hit our 90-second checkout target" │
│ │
│ Everyone knows WHY their work matters │
└─────────────────────────────────────────────────────────────┘