15Five

15Five exposes six main object types: users, check-ins, objectives, 1-on-1 meetings, performance reviews, and high fives. This integration covers four of them — check-ins, objectives, 1-on-1 meetings, and performance reviews — which together constitute the measurement surface of continuous performance management. High fives and raw pulse scores are excluded: recognition counts are driven by social dynamics rather than individual contribution, and self-reported engagement scores carry a Goodhart risk that makes them unsuitable as individual KPIs. Five KPIs were retained, selected against three criteria: ability to attribute to an owner, resistance to gaming, and balance between leading and lagging indicators.

Engagement and continuous feedback

Check-in Submission Rate measures the regularity with which each employee completes their weekly check-in. It is the earliest available signal in the 15Five data model: check-ins precede all other performance events by days or weeks, which makes a decline in submission rate the first observable symptom of disengagement. The KPI is attributed directly to the submitting user and is difficult to game at aggregate team level — an employee cannot consistently submit without actual participation.

What Check-in Submission Rate does not reveal is the quality of the content submitted. A high rate confirms behavioral regularity, not depth of reflection. For this reason, this KPI should be read alongside objective-level indicators: regularity in check-in submission combined with stagnant objective progress identifies the specific pattern of form without substance, where an employee maintains the ritual of engagement without advancing the underlying work.

Goal execution: reading objectives through paired indicators

Two KPIs cover the objectives object type, and they are intentionally paired to prevent a specific form of gaming.

Average Objective Progress tracks the real-time completion percentage across all active objectives for a given owner. It functions as a continuous health signal: an individual with several objectives consistently clustered at low progress as a quarter advances can be identified and supported before the deadline. Taken alone, however, this indicator invites inflation — progress percentages are often self-assessed, and an individual aware that the figure is tracked may update it upward without corresponding work.

Objective Completion Rate provides the lagging counterweight. At the end of a cycle, it measures whether objectives that were reported as progressing were actually closed as complete. A high Average Objective Progress combined with a low Objective Completion Rate is the signature of optimistic self-reporting: progress estimates were inflated during the period, but the objectives were not delivered. The combination of the two indicators makes this drift observable. Neither indicator is interpretable without the other.

Manager effectiveness

1-on-1 Completion Rate measures the proportion of scheduled manager-report meetings that are actually held. The KPI is attributed to the manager, whose responsibility is to initiate and maintain the cadence. Research consistently links regular 1-on-1 frequency to team retention and psychological safety; a sustained drop in this rate is a leading indicator of deteriorating team conditions, usually visible several weeks before it manifests in engagement surveys or attrition data.

Review Completion Rate measures process compliance at the individual level: what fraction of assigned performance reviews did a reviewer submit before the cycle closed. This is a lagging indicator because it is measured at the end of a review cycle, not during. Its relevance is twofold: incomplete reviews delay promotion and compensation decisions downstream, and a pattern of repeated non-completion signals disengagement from the feedback culture of the organization. The two KPIs together describe the manager's relationship to people development — one measures regular investment in their team, the other measures commitment to formal evaluation cycles.

Scope and limits of the integration

15Five records behavioral compliance — whether actions were taken — not the quality of what was produced. A submitted check-in may contain one sentence or a detailed reflection; the API does not distinguish. A completed 1-on-1 may have been substantive or perfunctory; the data does not know. An objective reported as complete may represent a delivered commitment or a definition revision that lowered the bar at the last moment. These distinctions require qualitative managerial judgment that no system can automate.

Additionally, Review Completion Rate and Objective Completion Rate depend on access permissions that are not guaranteed for every API key. Review cycle data requires the key holder to carry both company-admin and review-admin roles; an API key without those permissions will produce incomplete data for those two KPIs. The reliability of this integration depends directly on both the scope of the credentials provisioned and the discipline with which teams use 15Five — organizations where check-in culture is inconsistent or where objectives are set and forgotten will find the indicators noisy rather than informative.