HireFly Blog

How to Set Clear Performance Goals and Key Result Areas

Performance goals translate a role into a small set of results and standards for a defined period. Key Result Areas describe important areas of accountability; goals specify what progress or outcome is expected within them.

Start with role contribution

Identify the work the employee controls or materially influences. Connect it to team priorities, customers and required operations. Do not copy a senior manager’s revenue target onto an HR coordinator who has no authority over revenue.

Balance outcome and quality

A recruiter goal based only on positions filled can encourage weak screening. Pair volume or speed with job-relevant quality, candidate communication or process accuracy. A payroll goal should not reward fast release if corrections rise.

Write measurable without forcing a number

Some goals use quantities, dates or service levels. Others require milestone and quality evidence. “Implement onboarding improvements by September, including manager checklist, joiner schedule and a tested escalation route” can be reviewed even without an invented percentage.

Define the evidence

State the source, frequency and owner of the data. If the measure depends on another team, clarify that dependency. Avoid a metric that employees cannot see until the final rating.

Account for shared work

Record individual contribution and team outcomes separately. For a cross-functional HRMS launch, one person may own data validation, another training and another configuration. Giving everyone the same broad “successful launch” goal hides accountability.

Include behavioural expectations carefully

Use observable work behaviour: escalates payroll risk before cut-off, documents decisions, or gives direct reports monthly feedback. Avoid personality labels such as “be positive” or “show executive presence” unless translated into relevant actions.

Review and adjust

Discuss goals when priorities, staffing or assumptions change. Preserve the original, reason, approval and revised expectation. Quietly adding a year-end requirement is unfair; refusing to adjust a goal after authorised work changes makes the measure meaningless.

Example KRA and goals

KRA: recruitment operations. Goals could include maintaining complete requisition records, issuing candidate updates within the agreed service level and providing a weekly ageing view with named blockers. Each has an evidence source and supports a different part of the work.

Final quality check

  • Can the employee influence the result?
  • Are trade-offs and quality visible?
  • Is evidence available during the period?
  • Are dependencies named?
  • Will the goal still make sense if one unusual case occurs?

Good goals guide decisions during the year. If they are useful only when calculating a final score, they arrived too late.

Handle changing targets

A target can become inappropriate when demand, territory, system availability or headcount changes. Review the underlying assumption and revise through the approved process. Do not compensate by quietly lowering the quality standard or asking employees to absorb impossible work.

Avoid common metric traps

Percentage measures can swing with a small denominator. Average completion time can hide overdue cases. Satisfaction can reward easy decisions. Pair a measure with context and a quality check. Use a small number of goals so priorities remain visible.

Manager-employee alignment

Ask the employee to explain the goal back: expected result, evidence, dependencies and first action. Different interpretations found in January are useful; the same difference discovered during appraisal feels like a changed standard.

Written by

Hariprasad Chandramangalath