OKR Management
Leemu Support
Last Update 7 months ago
Leemu OKR supports three hierarchical levels of objectives:
1. Company OKRsPurpose: Define organization-wide strategic priorities
Who Can Create: Company Admins
Characteristics:
- Align with strategic goals and company vision
- Typically set quarterly or annually
- Visible to entire organization
- Should be limited (3-5 per quarter recommended)
- High-level and aspirational
Example:
Objective: Become the market leader in customer satisfactionKey Results:
- Increase NPS score from 45 to 75 - Reduce churn rate to below 5% - Achieve 90% customer satisfaction rating 2. Team OKRs
Purpose: Define how teams contribute to company objectives
Who Can Create: Team Admins and Company Admins
Characteristics:
- Aligned with company OKRs
- Specific to team capabilities and responsibilities
- Team members can view and contribute
- Should support at least one company objective
- More tactical than company OKRs
Example:
Objective: Deliver exceptional customer support experience Key Results: - Reduce average response time to under 2 hours - Maintain 95% first-contact resolution rate - Train 100% of support team on new product features 3. Personal (Me) OKRsPurpose: Define individual contributions and growth
Who Can Create: All users (Members, Team Admins, Company Admins)
Characteristics:
- Aligned with team or company OKRs
- Personal development and contribution goals
- Individual accountability
- More specific and actionable
- Can include skill development
Example:
Objective: Master customer success best practices Key Results: - Complete 3 customer success certifications - Maintain customer satisfaction score above 4.5/5 - Handle 50+ support tickets per week with 95% resolution rate Creating an ObjectiveStep-by-Step: Creating Company OKRsNavigate to "Company OKRs" in the main menu
Click "Create Objective" or the "+" button
Fill in the objective form:
Objective Details:
Title (required): Clear, inspiring, qualitative goal
- Keep it concise (aim for 5-10 words)
- Make it memorable and motivating
- Avoid jargon or technical terms
Description (optional): Detailed context and rationale
- Explain why this objective matters
- Describe expected impact
- Include relevant background
Owner (required): Person accountable for this objective
- Typically a senior leader for company OKRs
- Choose someone with authority to drive results
Status (required): Current state
- Draft: Not yet started or under review
- Active: Currently being worked on
- Completed: Successfully achieved
- On Hold: Temporarily paused
- Cancelled: No longer being pursued
Start Date (required): When work begins
End Date (optional but recommended): Target completion date
Weight (default: 1.0): Relative importance
- Use to prioritize multiple objectives
- Higher weight = higher priority
- Scale: 0.5 (low) to 2.0 (critical)
Check-in Interval (default: 7 days): How often to update progress
- Weekly (7 days) - recommended for most OKRs
- Bi-weekly (14 days) - for longer-term objectives
- Monthly (30 days) - for strategic initiatives
Strategic Goal (optional): Link to overarching strategic goal
- Select from existing strategic goals
- Shows how this objective supports strategy
Parent Objective (optional): For alignment
- Leave blank for top-level company OKRs
- Used for cascading objectives
Click "Add Key Result" to add measurable outcomes (see next section)
Add at least 2-3 key results (maximum 5 recommended)
Review all information for accuracy
Click "Create Objective" or "Save as Draft"
Navigate to "Team OKRs" in the main menu
Click "Create Objective"
Fill in the objective form (same fields as company OKRs)
Additional Team-Specific Fields:
Team (required): Select which team this objective belongs to
- Only teams you manage appear in the dropdown
Parent Objective (recommended): Align with a company objective
- Shows dropdown of company OKRs
- Creates visual alignment in reports
Add key results specific to team capabilities
Click "Create Objective"
Alignment Best Practice: Always link team OKRs to company OKRs to show how your team contributes to organizational goals.
Step-by-Step: Creating Personal OKRsNavigate to "My OKRs" in the main menu
Click "Create Objective"
Fill in the objective form
Personal OKR Considerations:
- Owner: Automatically set to you
- Parent Objective (recommended): Link to your team's or company's OKR
- Choose from objectives you have visibility into
- Shows how your work contributes to larger goals
Add key results for personal goals
Click "Create Objective"
Tips for Personal OKRs:
- Mix professional skills with deliverables
- Include at least one learning/growth goal
- Ensure they're achievable within your role
- Align with your team's priorities
Key Results are the measurable outcomes that track objective progress.
Key Result FieldsWhen adding a key result, you'll configure:
Title (required)
- What you're measuring
- Action-oriented and specific
- Example: "Reduce customer churn rate"
Description (optional)
- Additional context
- How this will be measured
- Data sources
Unit Type (required)
- Number: Absolute count (e.g., customers, features, sales)
- Percentage: Progress from 0-100%
- Currency: Monetary value (e.g., revenue, cost savings)
- Boolean: Yes/No, Done/Not Done
Direction (required)
- Increase: Growing toward target (e.g., revenue, NPS)
- Decrease: Reducing toward target (e.g., churn, costs)
- Maintain: Keeping within range (e.g., uptime, quality)
Initial Value (required)
- Starting point or baseline
- Current state when objective begins
- Example: If NPS is currently 45, initial value = 45
Target Value (required)
- Goal to achieve
- Should be ambitious but achievable
- Example: Target NPS of 75
Current Value (auto-calculated)
- Updated through check-ins
- Starts at initial value
- Progresses toward target
Owner (required)
- Person responsible for this key result
- Can be different from objective owner
- Receives check-in reminders
Weight (default: 1.0)
- Relative importance among key results
- Affects objective progress calculation
- Higher weight = more impact on objective
Example 1: Number Type - Increase
Title: Acquire new enterprise customers Unit: Number Direction: Increase Initial Value: 10 Target Value: 25 Owner: Sales ManagerExample 2: Percentage Type - Increase
Title: Complete migration to cloud infrastructure Unit: Percentage Direction: Increase Initial Value: 0 Target Value: 100 Owner: DevOps LeadExample 3: Currency Type - Increase
Title: Increase monthly recurring revenue Unit: Currency Direction: Increase Initial Value: $50,000 Target Value: $100,000 Owner: Head of SalesExample 4: Number Type - Decrease
Title: Reduce support ticket resolution time Unit: Number (hours) Direction: Decrease Initial Value: 48 Target Value: 24 Owner: Support ManagerExample 5: Boolean Type
Title: Launch new mobile app Unit: Boolean Direction: Increase Initial Value: 0 (No) Target Value: 1 (Yes) Owner: Product Manager Adding Multiple Key ResultsTo add multiple key results to an objective:
- While creating/editing an objective
- Click "Add Key Result"
- Fill in the first key result details
- Click "Add Another Key Result"
- Repeat for each key result
- You can reorder key results by dragging (if available)
- Save the objective
Recommended: 2-5 key results per objective
- Too few (1): Not enough to fully measure success
- Too many (6+): Loses focus, hard to track
When you navigate to Company/Team/My OKRs, you see:
List Columns:
- Objective title
- Owner name and avatar
- Progress bar and percentage
- Status badge
- Due date
- Number of key results
- Team name (for team objectives)
Sorting Options:
- Progress (low to high or high to low)
- Due date (soonest or latest)
- Created date
- Title (A-Z)
- Status
Filtering Options:
- By status (Active, Draft, Completed, etc.)
- By owner
- By team
- By date range
- By strategic goal
Click any objective to see its detail page:
Top Section:
- Objective title
- Description
- Owner information
- Status badge
- Progress percentage
- Timeline (start and end dates)
- Alignment (parent objective, if any)
Key Results Section:
- List of all key results
- Individual progress for each
- Check-in history
- Quick check-in button
Alignment Section:
- Parent objective (if aligned)
- Child objectives (if any objectives align to this one)
- Strategic goal connection
- Visual alignment tree
Activity Section:
- Recent check-ins
- Comments and updates
- Progress changes
- Status changes
- Navigate to the objective (Company/Team/My OKRs)
- Click on the objective to open detail view
- Click "Edit" button
- Modify any fields:
- Title, description
- Dates, weight
- Status
- Key results (add, edit, remove)
- Click "Save Changes"
What You Can Edit:
- Title and description (anytime)
- Dates (best before objective is active)
- Status (progress from Draft → Active → Completed)
- Key results (add new ones, edit existing, archive old ones)
- Alignment (parent objective, strategic goal)
What You Should Avoid Changing:
- Objective owner mid-cycle
- Target values after significant progress
- Key result units or direction
Company Admins can edit any objective:
- Navigate to the objective
- Click "Edit"
- Make necessary changes
- Add a comment explaining the change
- Save
Best Practice: Communicate with objective owner before making changes.
Archiving vs. Deleting ObjectivesArchiving ObjectivesArchiving preserves the objective but removes it from active views:
When to Archive:
- Objective cycle has ended
- Want to keep historical data
- Objective completed or cancelled
- Need to reduce clutter
How to Archive:
- Open the objective
- Click "..." menu
- Select "Archive"
- Confirm action
What Happens:
- Objective no longer appears in default views
- Data is preserved
- Can be unarchived later
- Still appears in reports (if filtered)
Viewing Archived Objectives:
- Go to Company/Team/My OKRs
- Click "Filters"
- Enable "Show Archived"
Deleting permanently removes the objective:
When to Delete:
- Duplicate objectives
- Created by mistake
- Test objectives
- No longer needed and no historical value
How to Delete:
- Open the objective
- Click "..." menu
- Select "Delete"
- Confirm deletion (may require additional confirmation)
⚠️ Warning: Deletion is permanent and cannot be undone!
What Gets Deleted:
- The objective
- All key results
- All check-ins
- All alignment connections
- All historical data
Best Practice: Archive instead of delete unless absolutely certain.
OKR AlignmentAlignment creates a hierarchy showing how objectives support each other.
Why Alignment Matters- Shows how individual work contributes to company goals
- Creates accountability and transparency
- Helps identify gaps in strategy execution
- Motivates teams by showing impact
Method 1: During Objective Creation
- When creating an objective
- Look for "Parent Objective" field
- Select the higher-level objective this supports
- Save
Method 2: Editing Existing Objective
- Open the objective
- Click "Edit"
- Select parent objective
- Save changes
- Personal OKRs can align to Team or Company OKRs
- Team OKRs typically align to Company OKRs
- Company OKRs may align to Strategic Goals
- Cannot create circular alignments (A → B → A)
- One objective can have multiple children
- One objective can have only one parent
Alignment Tree View:
- Open any objective
- Look for "Alignment" section
- See visual tree showing:
- Parent objective (what this supports)
- Child objectives (what supports this)
- Sibling objectives (others aligned to same parent)
Company-Wide Alignment:
- Navigate to Reports
- Select "Alignment View" or "Cascade View"
- See entire OKR hierarchy
- Identify gaps or misalignments
Draft
- Objective is being planned
- Not yet active
- Can be freely edited
- Not counted in progress calculations
- Use for: Planning phase, getting feedback
Active
- Objective is currently being worked on
- Counted in progress metrics
- Check-ins should be regular
- Primary status during the cycle
- Use for: All in-progress work
Completed
- Objective has been achieved
- Key results at or near target
- No longer accepting check-ins
- Celebrated as achievement
- Use for: Successfully finished objectives
On Hold
- Temporarily paused
- Not currently being worked on
- May resume later
- Not counted in active metrics
- Use for: Deprioritized work, waiting on dependencies
Cancelled
- No longer being pursued
- Abandoned or deemed unnecessary
- Removed from active tracking
- Explains why work stopped
- Use for: Strategy changes, no longer relevant
- Open the objective
- Click "Edit" or status badge
- Select new status from dropdown
- Add a comment explaining the change (recommended)
- Save
Status Flow:
Draft → Active → Completed ↓ On Hold → Active ↓ Cancelled OKR Templates (If Available)Some organizations provide OKR templates:
Using Templates- When creating an objective
- Click "Use Template" or "Browse Templates"
- Browse available templates by:
- Department (Sales, Marketing, Engineering, etc.)
- Goal type (Growth, Efficiency, Quality, etc.)
- Strategic theme
- Click "Use This Template"
- Template populates with:
- Sample objective title
- Sample key results
- Suggested metrics
- Customize to your needs
- Save
Benefits of Templates:
- Faster objective creation
- Best practice examples
- Consistent formatting
- Proven key result metrics
✅ DO:
- Make them inspirational and memorable
- Focus on outcomes, not activities
- Keep them qualitative
- Make them time-bound
- Ensure they're ambitious
❌ DON'T:
- Write vague objectives ("Be better")
- Include metrics in objective title
- Create too many objectives
- Make them too easy to achieve
- Use technical jargon
✅ DO:
- Make them quantifiable and measurable
- Include starting and target values
- Use specific metrics
- Ensure they're verifiable
- Make them challenging (70% achievement is good)
❌ DON'T:
- Make them activities or tasks ("Launch feature")
- Use vague measures ("Increase slightly")
- Set impossible targets
- Have too many per objective
- Make them easy to game
Quarterly Cycle (Recommended):
- Week 1: Plan and create OKRs
- Weeks 2-11: Execute and check in weekly
- Week 12: Review and grade OKRs
- Week 13: Reflect and plan next quarter
Mid-Cycle Reviews:
- Week 6: Mid-quarter check-in
- Assess progress
- Adjust if needed (avoid frequent changes)
- Address blockers
- Too Many OKRs: Stick to 3-5 objectives
- Not Measuring: Always use metrics, not feelings
- Setting Easy Targets: OKRs should be ambitious
- Lack of Alignment: Connect to higher-level goals
- Ignoring Check-ins: Regular updates are critical
- No Ownership: Every OKR needs a clear owner
- Treating as Performance Review: OKRs are for stretch goals
