Frameworks

A framework is the heart of KManagement. It is the blueprint for how a person is scored: what you measure, how each measurement becomes a score, and how much each part counts toward the final result. You build one in the visual framework builder, found under Frameworks in the sidebar (Admins and Managers only).

The tree: groups and metrics

A framework is a tree. Every item in it is called a node, and there are two kinds:

• Groupshold other nodes and combine their scores into one. Use them to create sections — for example a “Productivity” group containing a couple of metrics. Groups can be nested inside groups.
• Metrics are the leaves of the tree — the actual things being measured, such as story points delivered or bugs found.

You build the tree by dragging groups and metrics into place. A common shape is one group per theme (Productivity, Quality, Behavior), each containing the metrics for that theme.

Weights

Each node has a weight that says how important it is compared to its siblings. You do not have to make weights add up to 100 — the app balances them automatically at calculation time and shows a live indicator of the resulting share. For example, three metrics with weights 2, 1, and 1 become 50%, 25%, and 25%.

Metric types

Each metric has a type that decides how its raw number turns into a score. Pick the one that matches what you are measuring:

• Target vs. actual — compares what was achieved against a target (for example 18 of 20 story points). You choose whether higher or lower is better.
• Ratio — a numerator over a denominator compared to a target ratio.
• Percentage — a percentage value, optionally against a target.
• Yes / no — a simple pass/fail that scores a configured value.
• Ordinal scale — named levels (for example Poor → Excellent) mapped to scores.
• Threshold band — the value falls into a band, and the band decides the score.
• Count — a raw count such as number of bugs or late tasks. Counts typically feed a penalty or bonus formula rather than scoring on their own.
• Formula — a safe math expression combining other metrics (for example starting at 100 and deducting points per bug).

How groups combine their children

Each group uses one of two strategies to roll up its children:

• Weighted average (the default) — blends the children by their weights.
• Formula— for penalty or bonus sections, for example “start at 100, subtract per bug and per violation.”

Missing values

For each metric you decide what happens if no value is entered for a cycle:

• Exclude — drop it and rebalance the other metrics.
• Score 0 — treat it as fully missed.
• Score 100 — treat it as fully met.
• Block — refuse to calculate until it is filled in, and list what is missing.

Preview before you publish

The builder includes a live preview: type in sample numbers and watch the scores roll up through the tree, all the way to the final percentage and grade. This lets you sanity-check the design before anyone is scored by it.

Drafts, publishing, and versions

A framework is edited as a draft. When it is ready you publish it, which runs a validation check and saves a numbered version. Each publish is a snapshot, so you can look back at earlier versions and see exactly what changed. A History tab records every edit with who made it and when.