Goals and objectives
A score needs something to be read against. Goals add the target, the stretch line, the team median and the personal objective, and the bot follows up on the last one for you.
Targets and bands
Each person has a target and a stretch efficiency, resolved from the most specific setting: a per-employee override, then the team, then the organisation, then the shipped default. Defaults are 70 and 90. A stretch below the target is ignored so the bands stay ordered.
goals.target_efficiency goals.stretch_efficiency goals.benchmark_weeks
| behind | below target |
|---|---|
| on track | at or above target |
| ahead | at or above stretch |
| no data | the window produced no score, for example a week on leave; never shown as 0% |
The benchmark
Beside the target is the team’s own median over recent weeks (four by default), read from the materialised weekly scores, one figure per colleague, excluding the person being viewed, and only across weeks scored under the same rubric. Right after a scoring change the benchmark is empty until the nightly rebuild refills it, and the card says so instead of inventing a number.
Who sees what
- Everyone can read their own goal. Being told what you are measured against is not privileged.
- Reading a colleague’s goal needs a manager or above; the Goals page lists everyone in scope, furthest behind first, with no-data rows at the bottom.
- Every goal payload carries provenance: the scope it came from, when it was set, and by whom. Default means nobody ever set it.
Personal objectives
A personal goal with a deadline, such as finishing a certification in three months. It is advisory and never enters the score. Four ways it gets set:
- On the due date the bot asks whether you completed it. Yes marks it completed, no marks it missed, anything else is recorded as a status note and the goal stays open. One check-in per person per day.
Goal check-in — did you complete it?
| self | from your own drawer |
|---|---|
| manager | from the same surface |
| admin | from the same surface |
| collection | the built-in prompt asks in chat for one goal for the next three months and files the reply |
Kudos
When a lead reacts to a standup with an applause, party or star emoji, a kudos event is recorded and adds a small, capped bonus to that week’s score. Self-kudos are ignored, reactions are deduplicated, and admins choose whether only leads count.
pulse.kudos_enabled pulse.kudos_per_event pulse.kudos_bonus_cap pulse.kudos_leads_only
Trend
The employee drawer and the monthly report draw a six-month efficiency bar graph coloured by band, with the current month emphasised and the delta against last month. The quarterly KPI appears only when the newest month closes a quarter.