Objectives & Key Results (OKR)

The OKR module connects individual and team effort to organisational strategy through transparent, measurable objectives. It gives every employee visibility into how their work contributes to the bigger picture — and gives leadership a real-time pulse on progress across the entire organisation.

41
API Endpoints
3
Hierarchy Tiers (Org / Team / Personal)
4
BSC Perspectives
◆
Immutable Check-in Log (MGOALTRACK)

Business Value

Research consistently shows that employees who understand how their work connects to company goals are more engaged and more productive. OKRs make this connection explicit: a personal goal to "reduce client onboarding time from 10 days to 5" directly contributes to a team objective of "improve client satisfaction NPS" which in turn contributes to an org objective of "become the highest-rated HRMS in the region".

The check-in cadence — ideally weekly — creates a rhythm of accountability without the overhead of formal reviews. Confidence levels (High/Medium/Low) give managers an early warning signal when a goal is at risk, allowing intervention before the cycle ends.

Unlike spreadsheet-based goal tracking, every check-in in MGOALTRACK is permanent and append-only — building a complete, tamper-proof history of progress that supports performance conversations, appraisal evidence, and audit trails.

Who Can Do What

FeatureOKR Champion / HRManagerEmployeeExecutive
Create OKR CyclesYes———
Create Org-level ObjectivesYes——Can author
Create Team ObjectivesYesYes——
Create Personal Objectives & Goals——Yes—
Submit Check-ins—For team goalsYes—
View Team ProgressYesOwn teamOwn onlyAll
Close OKR CycleYes———
View Org Dashboard / CascadeYesTeam viewOwn onlyYes

Stakeholder Roles

🌟 OKR Champion / HR

Sets up the system: creates cycles, defines BSC perspectives, authors or facilitates org-level objectives, monitors cycle health, and closes cycles. Runs the OKR programme across the organisation.

👤 Manager / Team Lead

Creates team-tier objectives aligned to org objectives. Monitors team goal progress and confidence levels. Reviews direct reports' personal OKRs. Uses check-in notes as agenda for 1:1 discussions. Flags at-risk goals early.

👥 Employee

Creates personal objectives (aligned to team objectives where possible). Defines their own goals (key results) with measurable targets. Submits regular check-ins with current value, confidence, and notes. Views own OKR dashboard.

📊 Executive / Leadership

Reads the org-level cascade dashboard — completion % by tier, BSC balanced scorecard view, top objectives by progress, at-risk goals. Cycle-over-cycle trend from OKRTrendBLL for strategic review meetings.

Core Concepts

TermPlain EnglishExample
OKRObjectives + Key Results — the goal-setting frameworkObjective: Become the best-reviewed HRMS. Key Result: Achieve NPS of 65 by Q4.
ObjectiveThe "What" — a qualitative, aspirational statement of direction"Deliver exceptional client onboarding"
Goal / Key ResultThe "How much" — a specific, measurable outcome that proves the objective was achieved"Reduce onboarding time from 12 days to 5 days"
OKR CycleThe time period for a round of OKRs — has a start, end, and lock dateQ3 FY2026 (1 Jul – 30 Sep), Lock date: 5 Oct
TierLevel in the hierarchy — Org, Team, or PersonalOrg → Team → Personal cascade chain
AlignmentLinking a child objective to its parent — creates the cascadeMy personal objective aligned to team objective "Scale client base"
BSC PerspectiveThe strategic lens: Financial, Customer, Internal Process, Learning & GrowthAn objective "Reduce server costs by 20%" sits in Financial
Check-inA progress update submitted by the goal owner — records current value, confidence, notesWeekly update: "Current: 7 days → Target: 5 days. Confidence: High"
Confidence LevelTeam's self-assessment of likelihood to hit target: High / Medium / LowLow = early warning signal for manager to intervene
MGOALTRACKThe immutable check-in log — every check-in is a new INSERT, never an UPDATE5 weekly check-ins = 5 rows; history is permanent and complete
Progress %Auto-calculated from current value: (Current − Start) ÷ (Target − Start) × 100Start=12, Target=5, Current=8 → Progress = (12−8)÷(12−5) × 100 = 57%
Cycle LockAfter Lock Date, no more check-ins can be submitted — final scores are calculatedPrevents retroactive updates after cycle scoring

OKR Hierarchy & BSC Perspectives

3-Tier Hierarchy

Org Objectives
Team Objectives (aligned to Org)
Personal Objectives (aligned to Team)

The cascade works top-down in setup but bottom-up in execution: employees work on personal goals → team goals aggregate up → org objectives are fulfilled. Every tier of the pyramid contributes to the one above it.

Alignment is optional but strongly recommended. An unaligned personal objective still tracks progress but doesn't contribute to the cascade completion view. Encourage employees to align at least one personal objective to a team objective each cycle.

BSC Perspectives

Each objective is tagged to one of four Balanced Scorecard perspectives. This ensures strategy is balanced across all dimensions — not just financial targets.

📈 Financial

Revenue, profitability, cost reduction, ROI. What financial outcomes must we achieve?

👥 Customer

Satisfaction, retention, NPS, acquisition. How do customers see us?

⚙ Internal Process

Efficiency, quality, cycle time, compliance. What must we do well internally?

📚 Learning & Growth

Skills, culture, innovation, talent. How do we build capability for the future?

A healthy OKR cycle has objectives distributed across all four perspectives. An executive BSC view shows completion % per perspective — making it easy to see if you're over-invested in one area.

Cycle Setup Guide — OKR Champion / HR

Complete Step 1 and 2 once (one-time master data). Repeat Steps 3–5 for each new cycle.

  1. Create BSC Perspectives — set up the four perspectives (or customise labels for your organisation). This is one-time setup. Example: rename "Internal Process" to "Operational Excellence" if that resonates better with your culture.
  2. Create Objective Categories (optional) — e.g. Product, Sales, Operations, People. Categories help filter and group objectives in dashboards. Skip if your org prefers BSC perspectives alone for categorisation.
  3. Create an OKR Cycle — fields: Name (e.g. "Q3 FY2026"), Start Date, End Date, Lock Date. The Lock Date should be 5–10 days after End Date to give employees time for final check-ins.
    ⚠ Setting Lock Date equal to End Date is a common mistake — employees who are on leave during the last week miss their final check-in. Give a 5-day grace window.
  4. Create Org-level Objectives — ideally in a leadership offsite before the cycle opens. Each objective needs: Title, BSC Perspective, Owner, and Cycle reference.
  5. Communicate to teams — share the org objectives widely. Teams create their objectives in response. Give teams a 1-week window to set their objectives after org objectives are published.

Creating Objectives

Fields Explained

FieldRequiredGuidance
TitleYesAspirational, qualitative statement. Not a task. Example: "Transform our support experience" not "Respond to tickets faster".
DescriptionOptionalExplain the why — what changes if this objective is achieved? Who benefits?
OwnerYesThe person or team accountable for this objective's achievement
TierYesOrg / Team / Personal — determines where it appears in dashboards
BSC PerspectiveYesPick the primary strategic lens for this objective
CycleYesLink to the active OKR Cycle
Parent ObjectiveOptionalAligns this objective to a higher-tier objective. Creates the cascade chain.

Writing Good Objectives

❌ Weak Objective

"Improve our product" — too vague, not inspiring, no clear success state

✓ Strong Objective

"Become the fastest-to-deploy HRMS in our market segment" — aspirational, time-bound implicitly, clear direction

❌ Weak Objective

"Complete Q3 roadmap items" — a task list, not a goal; completion doesn't signal meaningful achievement

✓ Strong Objective

"Make every new client successful in their first 60 days" — outcome focused, customer-centred, inspiring

Creating Goals (Key Results)

Goals are the measurable outcomes that prove an objective was achieved. Each objective should have 3–5 goals. More than 5 signals the objective is too broad.

Quantitative Goals

For outcomes that can be measured numerically. Set a Start Value, Target Value, and Unit of Measure. Progress % is auto-calculated at each check-in based on the current value entered.

Progress % = (Current Value − Start Value) ÷ (Target Value − Start Value) × 100

Example: NPS Start=28, Target=50, Current=38
         Progress = (38−28) ÷ (50−28) × 100 = 45.5%

Qualitative Goals

For outcomes that cannot be reduced to a number — e.g. "Establish a weekly cross-functional sync". Progress % is entered manually at each check-in based on the owner's judgement. Use qualitative goals sparingly — they are harder to evaluate fairly.

Common Units of Measure

% (percentage) Count (#) Days (time) Hours Revenue (₹ / $) NPS Score CSAT Score Ratio Rating (1–5)
ⓘ Give each goal a weight within its parent objective. All goal weights under an objective must sum to 100%. This allows objective progress to roll up correctly from weighted goal progress.

Check-in Guide

A check-in is a progress update on a single goal. It records the current value, your confidence in hitting the target, and any notes. Check-ins are the heartbeat of the OKR system — frequency matters more than length.

How to Submit a Check-in

  1. Go to My OKRs → find the goal you want to update. Goals overdue for a check-in are highlighted.
  2. Click Check-in on the goal.
  3. Enter the current value (for quantitative goals) or manually enter your % progress (for qualitative goals). The system calculates progress % automatically for quantitative goals.
  4. Set your Confidence level:
      High — on track, no blockers
      Medium — at risk, manageable
      Low — off track, needs intervention
  5. Add notes — what happened since the last check-in? What is the blocker? What is the next step? Even 2 sentences is valuable.
  6. Submit. The check-in is permanently recorded in MGOALTRACK. You cannot edit or delete it — this ensures honest, consistent tracking.
⚠ MGOALTRACK is INSERT-ONLY. Every check-in creates a new permanent record — no updates, no deletes. This is by design: it prevents retroactive manipulation of progress history and gives managers a trusted audit trail for performance conversations.

Check-in Cadence Guidance

Cycle DurationRecommended CadenceExpected Check-ins
Quarterly (13 weeks)Weekly~12 per goal
Half-year (26 weeks)Bi-weekly~12 per goal
Annual (52 weeks)Monthly~12 per goal

My OKRs — Employee Self-Service

The My OKRs dashboard gives every employee a personalised view of their objectives and goals for the current cycle. It is the employee's command centre for goal management and check-ins.

What You See

Objectives Owned

All objectives you own in the current cycle, with overall completion % and parent alignment chain visible.

Goals Summary

All goals under your objectives. Progress bar, current value, confidence dot, and last check-in date for each.

Pending Check-ins

Goals overdue for a check-in, highlighted in amber. Quick check-in button for each — no need to navigate away.

Check-in History

Full MGOALTRACK timeline for each goal — see how progress moved from week to week, including your past notes.

Career Alignment View

Each personal objective shows its cascade chain: Personal Objective → Team Objective → Org Objective. Employees can see exactly how their work contributes to the organisation's strategic goals — a powerful motivator and useful context for conversations with managers.

OKR Dashboard — Manager & Executive View

Manager / Team View

Executive / Org View

Closing the OKR Cycle

Lock Date Approaching
→
Reminder to Employees
→
Final Check-ins
→
HR Closes Cycle
→
Scores Calculated
→
Trend Generated
  1. 3 days before Lock Date: send reminder to all employees to submit final check-ins. Employees cannot check in after lock.
  2. After Lock Date: HR Champion closes the cycle via Cycle Management → Close Cycle.
  3. System calculates final scores: each goal's final progress % is taken from the last MGOALTRACK entry. Objective scores roll up from weighted goal scores. Cycle aggregate calculated.
  4. OKRTrendBLL generates trend data: delta from previous cycle (improvement or regression), rolling averages, and cycle comparison charts are all available immediately after close.
  5. Run a debrief: within 2 weeks of cycle close, hold team and org-level retrospectives. Celebrate what was achieved. Understand why targets were missed — system data (check-in history, confidence trends) supports these conversations.
ⓘ Closed cycles remain permanently readable. All objectives, goals, and check-in history are retained for historical reference, trend reporting, and appraisal evidence.

OKR Best Practices

📺 Right Number of OKRs

3–5 objectives maximum. 3–5 goals per objective. More than this dilutes focus — a common failure mode in OKR adoption.

🎯 Stretch, Don't Sandbag

70% completion of a stretch goal is better than 100% of an easy one. OKRs are tools for alignment and growth, not performance rating (that's PERM's job).

👁 Make OKRs Transparent

All OKRs should be visible across the org. Transparency drives alignment — employees copy patterns they see in peers, and managers coach more effectively when they can see the full picture.

💬 Check-in = Conversation

The best managers use OKR check-in notes as the opening agenda for 1:1 meetings. "You rated confidence Low last week — what's blocking you?" is a coach's question.

⚠ Outcomes, Not Activities

"Run 3 training sessions" is an activity. "Increase team CSAT from 3.8 to 4.5" is an outcome. OKRs should always measure results, not effort.

🔄 Separate OKR from Appraisal

Don't tie OKR score directly to salary — it kills the willingness to set stretch goals. Use OKR scores as an input (context) in appraisal conversations, not as the appraisal itself.

Integration Map

▲ OKR
Objective & Goal tracking engine
★ PERM
OKR cycle final score optionally weighted into appraisal scoring
♥ FBCK
Check-in notes and confidence trends as context in 1:1 notes
👤 ESS
My OKRs self-service: personal objectives, goals, check-ins, history
📊 Dashboard
Cascade view, BSC balance, at-risk objectives, trend charts

Cycle Setup Checklist

ItemOwnerNotes
BSC Perspectives defined (one-time)OKR ChampionUse standard 4 or customise labels
Objective Categories created (optional)OKR ChampionOnly if needed beyond BSC perspectives
OKR Cycle created with correct Lock DateOKR ChampionLock Date = End Date + 5 days minimum
Org-level objectives authored by leadershipLeadership + OKR ChampionDone before teams create their objectives
Teams given 1-week window to create objectivesOKR ChampionCommunicate deadline clearly
Employees briefed on personal OKR creationManagersCover alignment to team objectives
Check-in cadence agreed and communicatedOKR ChampionWeekly for quarterly cycles
Dashboard access granted to executivesIT / HR AdminExecutive users need Org Dashboard permission
Cycle-close procedure documented for ChampionOKR ChampionLock date, close steps, debrief schedule

Frequently Asked Questions

1. What is the difference between an OKR Cycle and an Objective?
A Cycle is the time period (e.g. Q3 FY2026). An Objective is a goal within that period. Multiple objectives — across all tiers — exist within a single cycle. When the cycle closes, all objectives within it are scored.
2. Can one personal objective align to multiple team objectives?
The primary alignment is to one parent objective. However, an objective can be tagged to multiple BSC perspectives if it genuinely serves multiple strategic dimensions. Cross-tier alignment (one personal to multiple teams) is not supported in the primary cascade model.
3. What happens to check-ins after the cycle is locked?
Check-ins after the Lock Date are blocked — the submission form closes. All existing MGOALTRACK records remain permanently readable. The last check-in before lock is used as the final value for scoring.
4. Why is MGOALTRACK insert-only — can we never correct a check-in error?
The immutability is intentional: it prevents retroactive manipulation of progress history. If a check-in had an error in the value, the correction is simply the next check-in — which shows the corrected value and a note explaining the adjustment. The history shows both entries, which is more honest than a silent edit.
5. Should all 4 BSC perspectives be used every cycle?
Ideally yes, but it depends on strategic priorities. An early-stage company may legitimately focus 60% on Financial and Customer perspectives. The BSC dashboard makes imbalances visible — use it as a prompt for conversation, not a mandatory constraint.
6. Can an objective have zero goals?
An objective can be created without goals, but it cannot be tracked — there is nothing to check in against. An objective without goals shows 0% progress forever. Always add at least one goal per objective.
7. What does "Confidence = Low" mean and what should a manager do?
Confidence = Low means the employee believes the goal will not be achieved by cycle end. It is an early warning signal — not a failure. The manager should initiate a 1:1 conversation: understand the blocker, consider reallocating resources, adjusting the target (rare but sometimes justified), or accepting the likely shortfall and learning from it in the debrief.
8. Can we run Annual and Quarterly cycles simultaneously?
Yes. Multiple cycles can run concurrently. For example, an Annual Org-level OKR cycle running alongside four Quarterly cycles for teams and individuals. Employees can have objectives in multiple active cycles.
9. How does OKR score feed into the performance appraisal?
When configured in PERM, the OKR cycle's final aggregate score is available as an input to the appraisal weighted score. HR sets what % of the appraisal score the OKR contribution represents (e.g. 20%). This linkage is optional — many organisations prefer to keep OKR and appraisal scores fully separate.
10. What if an employee leaves mid-cycle — what happens to their OKRs?
Their objectives remain in the cycle as historical records. Check-in history is preserved. If another employee takes over the work, a new goal can be created for the new owner — the old goal is not transferred. The cycle close will calculate a score based on the last check-in before the employee's departure.