HR AI Skill

Goal Okr Management

Set, track, and review individual and team goals using OKR (Objectives and Key Results) methodology or goal frameworks. Use when launching goal-setting cycles, cascading company objectives to teams and individuals, conducting check-ins, or performing mid-year and year-end goal reviews. Supports quarterly OKR cycles, annual goal setting, and continuous goal management. Triggers on phrases like "set goals", "OKR", "objectives and key results", "goal cascade", "goal check-in", "goal review", "performance goals", "quarterly goals", "annual objectives".

Goal & OKR Management

Align individual and team objectives with organizational strategy through structured goal-setting.

Workflow

Cascade organizational strategy into company-level objectives for the period.
Facilitate team OKR creation workshops: each team drafts objectives aligned to company goals.
Guide individual goal setting: employees draft personal OKRs aligned to team and company objectives.
Review and approve goals through manager conversation (not top-down imposition).
Set check-in cadence: weekly or bi-weekly progress updates.
Conduct mid-cycle review: assess progress, adjust if needed (goals are living, not set-in-stone).
Perform end-cycle review: score key results, reflect on learnings, extract insights.
Feed insights into next cycle and annual performance review.

OKR Framework

OKR Structure

OBJECTIVE: Qualitative, inspirational, time-bound statement of what to achieve
  "What" we want to accomplish — should be ambitious and motivating

KEY RESULTS (3–5 per objective): Quantitative measures of how we know we achieved the objective
  "How" we measure progress — specific, measurable, achievable, relevant, time-bound

INITIATIVES: Actions and projects that will drive key result achievement
  "What we will do" — tied to tasks, not the OKR itself

Example:
  Objective: Deliver an exceptional customer onboarding experience
    KR1: Reduce time-from-signup-to-first-value from 14 days to 5 days
    KR2: Increase new customer NPS from 32 to 50
    KR3: Achieve 90% completion rate on onboarding checklist within first 7 days
    KR4: Reduce new-customer support tickets by 30%

  Initiatives (not part of OKR, but tracked separately):
    - Redesign onboarding email sequence
    - Build interactive product tutorial
    - Hire 2 customer success managers
    - Implement in-app guided walkthrough

OKR Writing Rules

DO:
  Make objectives inspirational and action-oriented
  Write measurable key results (include numbers, dates)
  Limit to 3–5 objectives per cycle, 3–5 KRs per objective
  Set ambitious targets (if you hit 100% every time, goals aren't stretching enough)
  Connect individual OKRs to team and company OKRs (cascade alignment)
  Review and adjust mid-cycle if business conditions change

DON'T:
  Set "business as usual" objectives (running the business ≠ OKRs)
  Use vague KRs ("improve", "increase", "better" — without numbers)
  Set too many OKRs (focus beats coverage)
  Tie OKRs directly to compensation (creates sandbagging — people set easy goals)
  Set and forget (OKRs require active management and check-ins)
  Make OKRs secret (transparency enables alignment and collaboration)

OKR Scoring

END-OF-CYCLE OKR SCORING
=========================

Scale: 0.0 to 1.0 for each Key Result

  1.0 = Fully achieved (exceeded target)
  0.7 = Strong progress (hit 70% is a good target — shows ambition)
  0.4 = Partial progress (some movement, significant gap remains)
  0.0 = No progress (target not moved at all)

Target achievement rate: 60–70% average across all KRs
  > 90% average: goals were too easy — increase ambition next cycle
  < 40% average: goals were unrealistic or resources insufficient — recalibrate

Scoring process:
  1. Employee self-scores each KR with evidence
  2. Manager reviews and discusses (calibration conversation, not grading)
  3. Final score agreed upon (can differ from self-score — that's OK)
  4. Reflection: what worked, what didn't, what to carry forward

Goal Cascade

GOAL CASCADE STRUCTURE
======================

Level 1: Company OKRs (set by executive team)
  - 3–5 company-wide objectives per cycle
  - Derived from annual strategy and priorities
  - Example: "Expand market share in APAC by 20%"

Level 2: Department OKRs (set by department heads)
  - Aligned to 1–2 company OKRs each
  - 3–5 objectives per department
  - Example (Sales): "Grow APAC revenue by 25% through new enterprise accounts"

Level 3: Team OKRs (set by team leads with team input)
  - Aligned to department OKRs
  - 3–4 objectives per team
  - Example (APAC Sales Team): "Close 15 new enterprise deals in APAC"

Level 4: Individual OKRs (set by employees with manager guidance)
  - Aligned to team OKRs + personal development goals
  - 2–3 objectives per person (includes 1 development-focused objective)
  - Example (Sales Rep): "Close 5 enterprise deals in Japan market"

Rule: Bottom-up contribution encouraged — employees propose, managers guide
Rule: No more than 2 levels of cascade (too many levels = bureaucracy)

Goal Check-In Process

GOAL CHECK-IN CADENCE AND FORMAT
=================================

Weekly (15 minutes):
  Format: 1-on-1 with manager or team stand-up
  Topics:
    - Progress on KRs this week (traffic light: green/yellow/red)
    - Blockers and support needed
    - Adjustments for next week
  Output: Updated KR status in goal tracking tool

Bi-weekly (30 minutes):
  Format: Team OKR review
  Topics:
    - Team OKR progress dashboard review
    - Cross-team dependency check
    - Initiative status and reprioritization
  Output: Team action items, risk flags escalated

Monthly (60 minutes):
  Format: Manager + direct report deep-dive
  Topics:
    - Detailed KR analysis with data
    - Learning and adjustment discussion
    - Resource reallocation if needed
    - Development goal progress
  Output: Updated OKRs if needed, resource requests

Mid-cycle (90 minutes):
  Format: Formal review session (individual + team)
  Topics:
    - Comprehensive progress assessment
    - OKR adjustment (allowed and encouraged if business changed)
    - New OKR addition if strategic priority emerged
  Output: Revised OKR document, communicated to stakeholders

End-of-cycle (120 minutes):
  Format: Scoring + reflection session
  Topics:
    - Score each KR with evidence
    - Reflect on what worked and what didn't
    - Extract learnings for next cycle
    - Connect to performance review (contribution, not score)
  Output: Final OKR scores, reflection document, input to next cycle

Development Goals

Include at least one development-focused objective in every individual's OKR set:

DEVELOPMENT OKR EXAMPLES
========================

Objective: Grow my leadership capabilities
  KR1: Complete "Leading Teams" course by end of Q2
  KR2: Lead 2 cross-functional projects from initiation to delivery
  KR3: Receive 4.0+ average on leadership competencies in 360 feedback

Objective: Deepen my data analytics skills
  KR1: Achieve certified status in SQL and data visualization tools
  KR2: Deliver 3 data-driven presentations to leadership
  KR3: Mentor 1 junior team member on analytics best practices

Objective: Expand my industry knowledge
  KR1: Attend 2 industry conferences and share learnings with team
  KR2: Publish 1 article or talk on [topic] externally
  KR3: Complete reading list of 6 industry books with team book club

Goal Tracking Tools

| Tool Type | Examples | Best For | |-----------|---------|----------| | Dedicated OKR software | Weekday, Ally, Gtmhub, Workboard | Organizations with > 100 employees, formal OKR practice | | Spreadsheet + Dashboard | Google Sheets, Excel with Looker | Small teams, getting started with OKRs | | Project management tools | Asana, Monday, ClickUp (OKR features) | Teams already using these tools; lighter OKR practice | | Performance management systems | Lattice, 15Five, Culture Amp | Organizations wanting OKRs + performance integrated |

Edge Cases

First-time OKR adoption: Start with 1–2 objectives per person, not 3–5. Run a pilot with 1–2 teams before org-wide rollout. Expect 2–3 cycles of learning before OKRs feel natural.
Remote teams: Increase check-in frequency slightly; use async updates via tools between live check-ins; ensure visibility across time zones.
Sales teams with quotas: Quotas are not OKRs — they're commitments. OKRs for sales should stretch beyond quota (new market entry, strategic account penetration, process improvement).
Engineering teams: Avoid tying OKRs directly to sprint commitments. OKRs should address outcomes (system reliability improvement, developer experience), not output (number of features shipped).
Goal conflict across teams: Establish a goal conflict resolution process — escalate to sponsor, evaluate trade-offs, document decision.

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.