01
Objectives
Company, department and individual levels, each owned by a named person within a cycle.
Performance & skills · what people are working toward
An individual objective that cannot be traced to a company one is a wish. Flume aligns objectives into a tree, scores key results by weight, and shows you which branches are at risk while there is still a quarter left to fix them.
Weighted, not averaged
Every OKR tool shows a percentage. The question is what it does when one result is nearly done and another has not started. Drag any of these three and compare the weighted figure against the simple average sitting beside it.
Weights, targets and the at-risk band are set per key result in the product.
What ships
01
Company, department and individual levels, each owned by a named person within a cycle.
02
Measurable results with a start, target and current value, and a weight in the parent objective.
03
Progress recorded as dated check-ins, so a result has a history rather than only a latest number.
04
Child objectives link to the parent they serve, making the ladder from floor to strategy visible.
05
Key results falling outside their expected band are surfaced as at-risk rather than left to a quarter-end surprise.
06
Requests across peer, manager, upward and skip-level relationships, with rating and free-text questions.
07
Self-appraisal, peer feedback and manager category ratings inside one managed cycle.
08
A KPI framework with weighted categories producing a quarterly score per employee.
09
Score distribution and trend across a manager’s reporting chain, not just individual cards.
10
Skills held at a proficiency level, endorsed by colleagues or earned through a certification.
11
Job roles declare the skills they need, so the gap between a person and a role is computed rather than guessed.
How it actually works
An objective with one nearly-done result and one untouched result is not 50% done if the untouched one carries most of the weight. Progress is computed across key results with their weights and clamped to the range, so the number on the card cannot flatter the quarter.
OKR progress, at-risk counts and 360 completion are read from the performance service rather than recomputed for the dashboard. Two places calculating "progress" with slightly different rules is how a leadership review ends up arguing about which screen is right.
Skills carry proficiency levels and endorsements, and job roles declare required skills at required levels. That turns "who knows what" into an answerable question — who can cover this shift, who is one certification away from the role, where a single retirement takes a capability with it.
Book a demo
The fastest way to judge Flume is to run it against a period you already argued about. Send a month of punches and the payroll you produced from it, and we will show you the same month reconciled — including what the anomaly detectors flag.