What is OKR and how does it differ from KPI?

Definition

OKR (Objectives and Key Results) is a goal-setting framework popularised by Intel and Google. Each Objective is a qualitative, aspirational statement of what you want to achieve. Underneath sit 3–5 Key Results — measurable indicators of whether the Objective was reached. KPI (Key Performance Indicator) is a continuous operational metric. The simplest distinction: OKRs are about change and ambition; KPIs are about steady-state operational health.

How OKRs work in practice

1. Set quarterly Objective — qualitative, ambitious, time-bound.
2. Define 3–5 Key Results — measurable, aim for 70% completion as success.
3. Cascade across teams — company → department → team → individual.
4. Weekly check-ins on progress.
5. Quarterly score — typical scoring 0.0–1.0 per Key Result.
6. Reset for next quarter.

When OKRs and KPIs are each appropriate

Use OKRs when	Use KPIs when	Use both when
High-growth scaleup	Stable operations	Mid-sized companies
Strategy in motion	Operational excellence	Quarterly OKRs + continuous KPIs
Need cross-team alignment	Single-team performance tracking	Cascading goals + measures

In Myanmar context

OKRs are still the exception in Myanmar SMEs. KPIs dominate because they fit annual review cycles, the year-end "13th-month" bonus tradition, and the more hierarchical local management style. Where OKRs do appear, it's typically in tech scaleups and BPO companies that have adopted Silicon Valley playbooks. The hybrid pattern — OKRs for strategy at director-and-above, KPIs for operations at manager-and-below — works well for local mid-market companies. Translation matters: "ambitious stretch goals at 70% success" can read as failure-tolerant in cultures that expect 100% achievement, so coaching matters during rollout.

Common misconceptions

• "OKRs replace KPIs." — they coexist; OKRs drive change, KPIs hold operations steady.
• "OKRs are just renamed KPIs." — OKRs are deliberately ambitious with explicit cascading.
• "100% achievement on OKRs is success." — 70% is the typical target for stretch OKRs.
• "OKRs work in any culture." — they need coaching to land in hierarchical environments.

Maturity model and practical adoption path in Myanmar

Concepts in HR rarely arrive fully formed. Most Myanmar SMEs adopt them in stages, learning what works through one or two cycles before refining. The maturity model below is a working pattern observed across local employers in factories, retail, hospitality, BPO, and SaaS — useful for benchmarking where a company is and what to invest in next.

Stages of maturity

1. Stage 1 — Ad hoc: the practice exists informally; nothing documented; founder or HR lead handles case by case.
2. Stage 2 — Templated: the practice has a one-page template, applied inconsistently; some managers use it, some skip it.
3. Stage 3 — Standardised: HR enforces consistency across the company; templates are reviewed annually; manager training in place.
4. Stage 4 — Data-driven: the practice is measured, reported, and connected to other HR data — performance, attrition, payroll cost.
5. Stage 5 — Strategic: outcomes feed leadership decisions on workforce planning, total rewards, and business strategy.

Where most Myanmar employers actually are

Sector	Typical stage	Common gap
Locally-owned office SME (under 30 staff)	Stage 1–2	Templates exist on paper, not in workflow
BPO and tech SME	Stage 2–3	Manager calibration and follow-through
Hospitality / retail mid-market	Stage 2–3	Multi-site consistency
Factory / FDI manufacturing	Stage 3–4	Linking outputs to leadership decisions
FDI subsidiary of multinational	Stage 3–5	Local relevance vs global template

Practical first moves for a Myanmar HR team

• Document the current practice — even a one-page note locks in baseline.
• Pilot in one team rather than rolling out company-wide on day one.
• Use Burmese-language materials for shop-floor and front-line staff.
• Tie to existing payroll cycle so HR effort compounds rather than duplicates.
• Measure one metric before / after — attrition, time-to-hire, review completion.
• Refresh annually with feedback from managers and employees.

Adoption is rarely linear. Companies frequently slip back a stage during periods of growth or leadership change. The discipline lies in noticing the slip early and re-engaging managers — not in chasing global best-practice frameworks that don't fit local realities.

Signals that the practice is mature in your company

• It survives leadership change — the practice is documented and continues even when a key champion leaves.
• It is taught, not improvised — new managers receive structured guidance rather than figuring it out alone.
• It produces measurable outputs — completion rates, scores, or development plans that feed downstream HR decisions.
• It is reviewed annually — HR refreshes templates, manager training, and metrics every cycle.
• Employees can describe it — when asked, the workforce understands what to expect and when.

Why Myanmar context still matters at maturity

Even at higher stages of maturity, Myanmar context shapes how a global HR concept actually lands. Cultural norms around face-saving and indirect feedback influence how reviews and 360-degree input are designed. Burmese-language materials remain essential for shop-floor adoption, no matter how sophisticated the framework. Statutory anchors — PIT, SSB, the Leave & Holidays Act, the Factories Act — keep payroll, leave, and OT obligations grounded in local rules, not regional templates. The companies that build mature HR practice in Myanmar are the ones that adapt rather than copy: they take the global concept, strip it down to its essential mechanics, and rebuild the surface in a way that fits local managers and employees.

Related: How to write KPIs, How to write KRAs, What is performance management.