Getting started with Performance
Performance is where your company runs reviews: self-assessments and manager assessments, goals with KPIs, feedback between colleagues and skill endorsements. Score cards then combine the results into one score per person, and the talent grid shows who is rising, steady or slipping. This page is the map: how the pieces fit, who can do what, and which article to read for each task.
Where: Performance, in the KAMI sidebar
You need: nothing extra to see your own performance. Managing other people's needs the Reviewer or Admin right. See Performance user rights.
How Performance is laid out
Performance opens on My performance, your own dashboard. If you have the Reviewer right, a Team performance switch sits next to it.
| Area | Tabs |
|---|---|
| My performance | Dashboard, Assessments, Goals, Feedback, Skills |
| Team performance | Dashboard, Score Card, Assessments, Goals, Feedback, Skills, Kai AI (BETA) |
| Settings (top right of either dashboard) | Performance Settings: user rights, team, recurring cycles, categories, skills, feedback topics, automations and notifications |
There is also a Performance tab on each employee's profile, showing that person's history.
How the pieces fit
- Cycles run assessments and goals over a period, for a set of people with a reviewer each.
- Each person's part moves through Pending Employee, then Pending Manager, then Complete, so you can always see who you are waiting for.
- Scores come out of the cycles: assessment scores, goal progress and reviewer ratings, plus feedback ratings.
- A score card blends those four into one Overall score out of 100, using weights your admin sets.
- The talent grid in Kai AI (BETA) places people by their latest score card and the trend across score cards.
The one concept everything depends on is the score card weighting: it decides, in numbers, what your company means by performance. See Score cards: how the overall rating is built.
How to get started, by role
- Employees: read Performance for employees, then Tracking your performance.
- Managers: read Performance for managers, then The performance dashboard.
- Administrators: read Performance for administrators and follow its setup order.
Every Performance article
Overview and dashboards
- The performance dashboard
- Performance for employees
- Performance for managers
- Performance for administrators
- The Performance tab on an employee profile
Your own performance
- Tracking your performance
- Answering your self-assessment
- Updating progress on your goals
- Asking for feedback and endorsements
- Your Performance notification preferences
Assessments
- Creating an assessment cycle
- Assessment questions and categories
- Managing participants in an assessment cycle
- How assessment scores are calculated
- Reviewing team assessments
Goals
- Creating a goal cycle
- Managing participants in a goal cycle
- Adding and editing goals and KPIs
- Importing goals and KPIs into a goal cycle
- Goals and KPIs: how progress is calculated
- Reviewing and tracking team goals
- Rating a team member's goals
Feedback, skills and recommendations
- Giving and receiving feedback
- Reviewing team feedback
- Feedback topics
- Skills and endorsements
- The skills library
- Recommendations on a performance profile
Score cards and analysis
- Setting up a score card
- Score cards: how the overall rating is built
- The analysis view: talent grid, placements and gaps
- Performance scores and the talent grid
Settings
- Performance user rights
- Performance user rights reference
- The Performance Team page and reviewer roles
- Recurring cycles and automations
- Performance automations: probation feedback requests
- Performance notification settings
What Happens Next
- People added to a cycle see it on their dashboard and are notified, depending on your notification settings.
- Scores feed score cards, and dated score cards feed the talent grid.
- Nothing in KAMI acts on a score. What follows a review is a management decision.
Tips
- Design the questions and goals before you open a cycle. Changing them once people have answered changes what they are scored against.
- Run one small cycle first. A pilot with one team surfaces every design problem while it is still cheap to fix.
- Decide what the results are for, such as development, pay or promotion, and tell people. The design differs, and they will ask.
- Brief your reviewers on the scale. Consistency between reviewers matters more than any setting.