Define the role once. Score it the same way every time.
A role is a weighted matrix of skills, each with a description of what good looks like. Everyone reviewed for that role is measured against the same yardstick.
- A matrix per role
- Guidance for every level
- Versioned as roles change
A yardstick for every role
List the skills that matter, say how much each one counts, and describe what each level looks like. Reviewers score against the description, not a feeling.
- Skills weighted by importance
- A description for every level
- Reused across every cycle
Roles change. Old reviews should not.
Edit a role as it evolves. Each change creates a new version, and every past review keeps the version it was scored against.
- See what changed and when
- Past results never shift under you
Skills feed everything else
The same matrix drives the review form, the result, the goals that follow and the skill history over time. Define it once.
- Strongest skill and focus area, in words
- Next-role gaps from the same matrix
The details that keep scores consistent
Weights you set
Decide how much each skill counts for this role.
Levels that mean something
Every level is described, so a 4 means the same for everyone.
Versioned by default
History stays put when the role changes.
Good questions, straight answers
Can two roles share skills?
Yes. A skill can appear in several roles with a different weight in each.
What happens to old reviews when I edit a role?
Nothing. Each edit creates a new version, and past reviews stay tied to the version they used.
How many skills should a role have?
Enough to cover what matters and few enough to review properly. Most teams start with four to six.