Metrics are the definition of “how we count it.” Every measurable Goal type — Key Result, Measure, AARRR/HEART metric, North Star input, and others — can carry a metric: what unit you use, which way is good, how numbers roll up, and what you’re aiming at.
A metric in Hamster is the quantitative shape attached to a measurable node in your framework. You set it once per goal (or inherited type) so Results have a clear place to land each period: targets, actuals, and status all read against the same definition.
Hamster supports:
sum, avg, last, max, min).Metrics inherit their measurable eligibility from the framework template — Key Results, OGSM Measures, AARRR/HEART Metrics, North Star and Input Metrics, and other types the template marks as measurable. You don’t attach a metric to a non-measurable goal type; the hierarchy enforces that for you.
Changing a metric’s definition is deliberate — historical results stay tied to the definition they were recorded against where versioning applies, so reviews stay comparable.
Initiatives link to goals; the metrics on those goals are what “moving the number” refers to in planning and in chat. When the AI assistant proposes work, it can reference the same metric language your team used when defining the goal.
Creating and editing metrics on goals follows the same goals.manage permission as frameworks and results. Roles & Permissions cover who holds it.