How do I write KRAs (Key Result Areas)?

Definition

Key Result Areas (KRAs) are the broad outcome categories a role is accountable for — typically 4–7 per role. KRAs are not tasks ("send weekly report") and not metrics ("95% accuracy"). They are the named buckets of value the role delivers. KPIs (Key Performance Indicators) sit underneath, measuring whether each KRA is achieved. KRAs answer "what does this role exist to achieve?" — KPIs answer "how do we measure it?".

How to write KRAs in practice

1. Start from role purpose — one sentence on why the role exists.
2. List major outcomes — value the role produces over a year.
3. Group into 4–7 buckets — collapse overlap, name each bucket clearly.
4. Verify completeness — together they should cover the role.
5. Assign weights — total 100%, weighted by business priority.
6. Add 1–3 KPIs per KRA — measurable indicators with targets.

When KRA-driven performance management is right

Use when	Don't use when	Common alternative
Stable roles with clear outputs	Highly fluid project teams	OKRs
Annual cycle with bonus link	Pure innovation work	Continuous feedback
Mid-sized organisations	Solo founders	Informal goals

In Myanmar context

Myanmar SMEs typically run 5 KRAs per role with 1–3 KPIs each, on an annual cycle that aligns with the year-end bonus. KRA writing is sometimes delegated to line managers without HR review, which leads to inconsistent quality. A simple HR template — role purpose, KRA list, KPI per KRA, weights — solves most of the issue. For factory and retail roles, KRAs around safety, attendance, and OT discipline are common alongside output KRAs. White-collar Yangon SMEs typically include a "compliance / process" KRA covering payroll, statutory filings, or quality standards.

Common misconceptions

• "KRAs are tasks." — they're outcomes; tasks live in the job description.
• "More KRAs is better." — 4–7 is the sweet spot; more dilutes focus.
• "KRAs and KPIs are the same." — KRAs are buckets; KPIs are measures.
• "KRAs only matter at year-end." — they should drive monthly check-ins.

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, OKR vs KPI, What is performance management.