Skip to content

Goals

What the role owns, written once.

A key result area belongs to the role, so the next person to hold it inherits the job instead of negotiating it from a blank page.

The screen

Goals

Goals, results and the measures under them.

Sample workspace: Northwind Ops

What you get

Everything below ships today.

  • On the roleKRAs sit on the role definition. Move a person into the role and the result areas come with the seat.
  • WeightedEach KRA carries a weight, so a composite score reflects what the role is actually for.
  • Linked to a KPIA KRA names the KPI that measures it, which is how a reading becomes evidence rather than an opinion.
  • Owns its SOPsThe processes that serve a result area hang off it, so the question of who runs this has one answer.
  • Read by reviewsA review cycle opens on the subject's KRAs, with the self rating and the manager rating against each one.
  • BoundariesA role definition also records what it escalates and to whom, which is the half of a job description everyone skips.

It reads the rest.

  • KPIsTrack, weight and score, tied to performance.
  • ReviewsCycles with weighted scoring.
  • PeopleOrg chart, roles and history.

Questions

Straight answers.

Why on the role and not on the person?

Because roles change less often than people do. A new hire steps into a seat that already knows what it owns.

Can a KRA be edited during a cycle?

Yes. The cycle in flight keeps the set it opened with, and the next one picks up the new set.

Do KRAs move by themselves when work is done?

A KRA moves with the KPI reading behind it, and a reading is recorded by whoever owns it. Completing a task does not write a reading today.

Open it on your own work.