A four-state objective tree whose parents are the weighted rollup of their children, with sibling weights that do not sum to 1 either normalised out loud or drawn at the scale they actually describe.
Preview in your theme
Loading preview…
This component is part of Pro
The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.
status="ready" · 3 objectives, 9 key results, and a sub-objective nested under the third. The middle objective was split in half between two key results and then given a third, so its weights read 0.5, 0.5 and 0.4 — a group summing to 1.40. The default policy divides by 1.40 and names the group underneath rather than rescaling in silence. Under the tree, the three objectives’ shares of the progress actually earned print 59 / 32 / 9 — apportioned by largest remainder, so a breakdown of everything adds up to 100 rather than to 99. Click any row, or walk it with the arrow keys, to re-point the headline.
Objectives · Platform group
Snapshot taken 18 Aug · weights set at kick-off
Weighted rollup of 3 objectives54%Q3 rolluppace 53% · due Sep 30
on track43 days left
Q3 rollupweight 100%progress 54%on track
Make onboarding self-serveweight 50%progress 64%ahead
Median time to first value under 10 minutesweight 40%progress 62%on track
Docs deflect 30% of setup ticketsweight 25%progress 90%ahead
Cut support load per accountweight 30%progress 57%on track
First response under 2 hoursweight 36%progress 85%ahead
Self-serve refunds shippedweight 36% · due Sep 4progress 30%off track
Ticket backlog under 40weight 28%progress 55%on track
Ship the shared workspaceweight 20%progress 26%off track
Design-partner betaweight 60%progress 33%at risk
Realtime presence generally availableweight 40%progress 15%off track
Where the 54% under “Q3 rollup” comes from — each child’s share of what has been earned:
Make onboarding self-serve59%Cut support load per account32%Ship the shared workspace9%
Weights under “Cut support load per account” sum to 1.40, not 1 — each child was divided by 1.40 before rolling up.
Objective rollup: Objectives · Platform group. The tree holds 13 nodes, 9 of them key results, across 3 top-level entries. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 54% against a pace of 53%, which is on track, with 43 days left in the cycle. The headline currently reads Q3 rollup at 54%. 1 note about weighting or stated figures, listed after the table.
Objectives · Platform group: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
54%
n/a
on track, against a pace of 53%
Sep 30
43 days left
Make onboarding self-serve
2
Hannah Hodkiewicz Sr.
50%
64%
59%
ahead, against a pace of 53%
Sep 30
43 days left
Median time to first value under 10 minutes
3
unassigned
40%
62%
39%
on track, against a pace of 53%
Sep 30
43 days left
Setup completion 45% → 70%
3
unassigned
35%
48%
26%
on track, against a pace of 53%
Sep 30
43 days left
Docs deflect 30% of setup tickets
3
unassigned
25%
90%
35%
ahead, against a pace of 53%
Sep 30
43 days left
Cut support load per account
2
Kristin Wilderman-Howe
30%
57%
32%
on track, against a pace of 53%
Sep 30
43 days left
First response under 2 hours
3
unassigned
36%
85%
53%
ahead, against a pace of 53%
Sep 30
43 days left
Self-serve refunds shipped
3
unassigned
36%
30%
19%
off track, against a pace of 74%
Sep 4
17 days left
Ticket backlog under 40
3
unassigned
28%
55%
28%
on track, against a pace of 53%
Sep 30
43 days left
Ship the shared workspace
2
Melyssa Murazik
20%
26%
9%
off track, against a pace of 53%
Sep 30
43 days left
Design-partner beta
3
unassigned
60%
33%
76%
at risk, against a pace of 53%
Sep 30
43 days left
20 design partners in the beta
4
unassigned
50%
45%
69%
on track, against a pace of 53%
Sep 30
43 days left
Weekly active in beta at 60%
4
unassigned
50%
20%
31%
off track, against a pace of 53%
Sep 30
43 days left
Realtime presence generally available
3
unassigned
40%
15%
24%
off track, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
status="empty" · a valid payload with a cycle but no objectives — told apart from "loading" and from "failed to fetch".
Objectives · Platform group
Snapshot taken 18 Aug · weights set at kick-off
No objectives in this cycle
A rollup needs at least one objective with one measurable key result under it.
status="loading" · a headline block and five stepped rows, aria-hidden plus an sr-only role=status. No timers involved, and the pulse stops under reduced motion.
Objectives · Platform group
Snapshot taken 18 Aug · weights set at kick-off
Loading the objective rollup
status="error" · the fetch failed. "Try again" appears only when onRetry is passed, and pressing it switches this card to ready.
Objectives · Platform group
Snapshot taken 18 Aug · weights set at kick-off
Couldn’t load this chart
The data source didn’t respond.
weightMode="strict" on exactly the same board, opened one level deeper with defaultExpandedDepth=3. Nothing is divided, so the over-allocated objective is reported on the scale its weights actually describe: the whole cycle reads 61% here against 54% under the default policy. Select the over-allocated objective and its own bar carries a hairline where 100% falls.
Objectives · Platform group
Snapshot taken 18 Aug · weights set at kick-off
Weighted rollup of 3 objectives61%Q3 rolluppace 53% · due Sep 30
on track43 days left
Q3 rollupweight 100%progress 61%on track
Make onboarding self-serveweight 50%progress 64%ahead
Median time to first value under 10 minutesweight 40%progress 62%on track
Docs deflect 30% of setup ticketsweight 25%progress 90%ahead
Cut support load per accountweight 30%progress 80%ahead
First response under 2 hoursweight 50%progress 85%ahead
Self-serve refunds shippedweight 50% · due Sep 4progress 30%off track
Ticket backlog under 40weight 40%progress 55%on track
Ship the shared workspaceweight 20%progress 26%off track
Design-partner betaweight 60%progress 33%at risk
20 design partners in the betaweight 50%progress 45%on track
Weekly active in beta at 60%weight 50%progress 20%off track
Realtime presence generally availableweight 40%progress 15%off track
Where the 61% under “Q3 rollup” comes from — each child’s share of what has been earned:
Make onboarding self-serve53%Cut support load per account39%Ship the shared workspace8%
Weights under “Cut support load per account” sum to 1.40 and are used as given, so its bar runs to 1.40 and 100% arrives before every child is done.
Objective rollup: Objectives · Platform group. The tree holds 13 nodes, 9 of them key results, across 3 top-level entries. Sibling weights are used exactly as given, so a group can run past 100% or leave an unallocated remainder. Q3 rollup rolls up to 61% against a pace of 53%, which is on track, with 43 days left in the cycle. The headline currently reads Q3 rollup at 61%. 1 note about weighting or stated figures, listed after the table.
Objectives · Platform group: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
61%
n/a
on track, against a pace of 53%
Sep 30
43 days left
Make onboarding self-serve
2
Hannah Hodkiewicz Sr.
50%
64%
53%
ahead, against a pace of 53%
Sep 30
43 days left
Median time to first value under 10 minutes
3
unassigned
40%
62%
39%
on track, against a pace of 53%
Sep 30
43 days left
Setup completion 45% → 70%
3
unassigned
35%
48%
26%
on track, against a pace of 53%
Sep 30
43 days left
Docs deflect 30% of setup tickets
3
unassigned
25%
90%
35%
ahead, against a pace of 53%
Sep 30
43 days left
Cut support load per account
2
Kristin Wilderman-Howe
30%
80%
39%
ahead, against a pace of 53%
Sep 30
43 days left
First response under 2 hours
3
unassigned
50%
85%
53%
ahead, against a pace of 53%
Sep 30
43 days left
Self-serve refunds shipped
3
unassigned
50%
30%
19%
off track, against a pace of 74%
Sep 4
17 days left
Ticket backlog under 40
3
unassigned
40%
55%
28%
on track, against a pace of 53%
Sep 30
43 days left
Ship the shared workspace
2
Melyssa Murazik
20%
26%
8%
off track, against a pace of 53%
Sep 30
43 days left
Design-partner beta
3
unassigned
60%
33%
76%
at risk, against a pace of 53%
Sep 30
43 days left
20 design partners in the beta
4
unassigned
50%
45%
69%
on track, against a pace of 53%
Sep 30
43 days left
Weekly active in beta at 60%
4
unassigned
50%
20%
31%
off track, against a pace of 53%
Sep 30
43 days left
Realtime presence generally available
3
unassigned
40%
15%
24%
off track, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are used as given: the hairline marks where 100% falls when a group is over-allocated, and the hatched slice is weight nobody claimed.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
The other half of strict mode, opened on the objective with defaultSelectedId: three key results weighted 0.3, 0.3 and 0.2 claim 80% of it, and the 20% nobody allocated is the hatched slice on the right of the headline bar rather than something quietly shared out. The rollup can never reach 100% and the note says so.
Objectives · Reliability
Weights signed off before the fourth key result was dropped
Weighted rollup of 3 key results51%Earn back reliability trustpace 53% · due Sep 30 · owner SRE guild
on track43 days left
Q3 rollupweight 100%progress 51%on track
Earn back reliability trustweight 100%progress 51%on track
Monthly uptime 99.95%weight 30%progress 72%ahead
Median time to recovery under 20 minutesweight 30%progress 40%at risk
Every Sev-1 has a postmortem inside a weekweight 20%progress 85%ahead
Where the 51% under “Earn back reliability trust” comes from — each child’s share of what has been earned:
Monthly uptime 99.95%43%Median time to recovery under 20 minutes24%Every Sev-1 has a postmortem inside a week33%
Weights under “Earn back reliability trust” sum to 0.80 and are used as given, so 20% of its bar is unallocated and the rollup can never reach 100%.
Objective rollup: Objectives · Reliability. The tree holds 4 nodes, 3 of them key results, across 1 top-level entry. Sibling weights are used exactly as given, so a group can run past 100% or leave an unallocated remainder. Q3 rollup rolls up to 51% against a pace of 53%, which is on track, with 43 days left in the cycle. The headline currently reads Earn back reliability trust at 51%. 1 note about weighting or stated figures, listed after the table.
Objectives · Reliability: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
51%
n/a
on track, against a pace of 53%
Sep 30
43 days left
Earn back reliability trust
2
SRE guild
100%
51%
100%
on track, against a pace of 53%
Sep 30
43 days left
Monthly uptime 99.95%
3
unassigned
30%
72%
43%
ahead, against a pace of 53%
Sep 30
43 days left
Median time to recovery under 20 minutes
3
unassigned
30%
40%
24%
at risk, against a pace of 53%
Sep 30
43 days left
Every Sev-1 has a postmortem inside a week
3
unassigned
20%
85%
33%
ahead, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are used as given: the hairline marks where 100% falls when a group is over-allocated, and the hatched slice is weight nobody claimed.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
Degenerate weights: every key result under the objective is weighted 0. Weighting by zeros would pin the objective at 0% for the rest of the quarter, so the group is split equally — stated out loud, never assumed.
Objectives · Growth
Weighting enabled mid-cycle, nothing filled in
Weighted rollup of 1 objective57%Q3 rolluppace 53% · due Sep 30
Where the 57% under “Q3 rollup” comes from — each child’s share of what has been earned:
Grow qualified pipeline100%
Every weight under “Grow qualified pipeline” is 0, so there is nothing to weight by — its 3 children were split equally instead.
Objective rollup: Objectives · Growth. The tree holds 4 nodes, 3 of them key results, across 1 top-level entry. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 57% against a pace of 53%, which is on track, with 43 days left in the cycle. The headline currently reads Q3 rollup at 57%. 1 note about weighting or stated figures, listed after the table.
Objectives · Growth: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
57%
n/a
on track, against a pace of 53%
Sep 30
43 days left
Grow qualified pipeline
2
Growth pod
100%
57%
100%
on track, against a pace of 53%
Sep 30
43 days left
Trial signups 900 → 1,400
3
unassigned
34%
55%
32%
on track, against a pace of 53%
Sep 30
43 days left
Sales-qualified leads 120 → 200
3
unassigned
33%
35%
21%
at risk, against a pace of 53%
Sep 30
43 days left
Blended CAC down 15%
3
unassigned
33%
80%
47%
ahead, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
The objective carries a progress figure of its own — someone typed 70% into it while its key results roll up to 39%. The rollup is what is drawn, the typed figure is kept beside the headline, and the gap is named rather than hidden.
Objectives · Mobile
Objective progress typed in by hand, key results measured
Weighted rollup of 3 key results39%Make the mobile app a first-class clientpace 53% · due Sep 30 · owner Mobile team
at risk43 days leftstated 70%
Q3 rollupweight 100%progress 39%at risk
Make the mobile app a first-class clientweight 100%progress 39%at risk
Feature parity on the top 12 flowsweight 50%progress 50%on track
Store rating 3.8 → 4.4weight 20%progress 25%off track
Where the 39% under “Make the mobile app a first-class client” comes from — each child’s share of what has been earned:
Feature parity on the top 12 flows64%Crash-free sessions above 99.5%23%Store rating 3.8 → 4.413%
“Make the mobile app a first-class client” states 70% but its children roll up to 39%. The rollup is what is drawn.
Objective rollup: Objectives · Mobile. The tree holds 4 nodes, 3 of them key results, across 1 top-level entry. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 39% against a pace of 53%, which is at risk, with 43 days left in the cycle. The headline currently reads Make the mobile app a first-class client at 39%. 1 note about weighting or stated figures, listed after the table.
Objectives · Mobile: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
39%
n/a
at risk, against a pace of 53%
Sep 30
43 days left
Make the mobile app a first-class client
2
Mobile team
100%
39% (stated 70%)
100%
at risk, against a pace of 53%
Sep 30
43 days left
Feature parity on the top 12 flows
3
unassigned
50%
50%
64%
on track, against a pace of 53%
Sep 30
43 days left
Crash-free sessions above 99.5%
3
unassigned
30%
30%
23%
at risk, against a pace of 53%
Sep 30
43 days left
Store rating 3.8 → 4.4
3
unassigned
20%
25%
13%
off track, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
Single-element tree: one objective, one key result, one weight. Every denominator in the rollup still has something in it — the weight sum is 1, the contribution split is 100%, and the key result carries its own deadline ahead of the cycle end.
Objectives · Data platform
One objective, one key result
Weighted rollup of 1 objective55%Q3 rolluppace 53% · due Sep 30
on track43 days left
Q3 rollupweight 100%progress 55%on track
Finish the Postgres 17 migrationweight 100%progress 55%on track
All 9 services cut overweight 100% · due Sep 12progress 55%at risk
Where the 55% under “Q3 rollup” comes from — each child’s share of what has been earned:
Finish the Postgres 17 migration100%
Objective rollup: Objectives · Data platform. The tree holds 2 nodes, 1 of them key results, across 1 top-level entry. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 55% against a pace of 53%, which is on track, with 43 days left in the cycle. The headline currently reads Q3 rollup at 55%. Every sibling group's weights already sum to 1.
Objectives · Data platform: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
55%
n/a
on track, against a pace of 53%
Sep 30
43 days left
Finish the Postgres 17 migration
2
Data platform
100%
55%
100%
on track, against a pace of 53%
Sep 30
43 days left
All 9 services cut over
3
unassigned
100%
55%
100%
at risk, against a pace of 66%
Sep 12
25 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
All-identical values: three key results at exactly 40% under weights of 0.7, 0.2 and 0.1. A weighted mean of identical values is that value whatever the weights are, so the objective reads 40% — and the contribution split falls back to the weights, 70 / 20 / 10.
Objectives · Quality
Three key results, all at 40%, weights 0.7 / 0.2 / 0.1
Weighted rollup of 3 key results40%Hold the quality barpace 53% · due Sep 30 · owner Quality guild
at risk43 days left
Q3 rollupweight 100%progress 40%at risk
Hold the quality barweight 100%progress 40%at risk
Escaped defects under 5 per releaseweight 70%progress 40%at risk
Flaky test rate under 1%weight 10%progress 40%at risk
Where the 40% under “Hold the quality bar” comes from — each child’s share of what has been earned:
Escaped defects under 5 per release70%Critical-path coverage above 80%20%Flaky test rate under 1%10%
Objective rollup: Objectives · Quality. The tree holds 4 nodes, 3 of them key results, across 1 top-level entry. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 40% against a pace of 53%, which is at risk, with 43 days left in the cycle. The headline currently reads Hold the quality bar at 40%. Every sibling group's weights already sum to 1.
Objectives · Quality: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
40%
n/a
at risk, against a pace of 53%
Sep 30
43 days left
Hold the quality bar
2
Quality guild
100%
40%
100%
at risk, against a pace of 53%
Sep 30
43 days left
Escaped defects under 5 per release
3
unassigned
70%
40%
70%
at risk, against a pace of 53%
Sep 30
43 days left
Critical-path coverage above 80%
3
unassigned
20%
40%
20%
at risk, against a pace of 53%
Sep 30
43 days left
Flaky test rate under 1%
3
unassigned
10%
40%
10%
at risk, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
Over-achievement: attainment is not clipped on the way in, so a key result at 130% keeps saying 130%. A bar cannot be longer than itself, so those bars stop at the cap and carry a truncation mark, and the objective lands above 100%.
Objectives · Revenue
Two key results past target
Weighted rollup of 3 key results104%Beat the expansion planpace 53% · due Sep 30 · owner Revenue
ahead43 days left
Q3 rollupweight 100%progress 104%ahead
Beat the expansion planweight 100%progress 104%ahead
Where the 104% under “Beat the expansion plan” comes from — each child’s share of what has been earned:
Expansion ARR $1.2M63%12 net-new enterprise logos30%Gross churn under 4%7%
3 nodes are past 100%; those bars stop at the cap and carry a truncation mark, while the printed number keeps the real value.
Objective rollup: Objectives · Revenue. The tree holds 4 nodes, 3 of them key results, across 1 top-level entry. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 104% against a pace of 53%, which is ahead, with 43 days left in the cycle. The headline currently reads Beat the expansion plan at 104%. 1 note about weighting or stated figures, listed after the table.
Objectives · Revenue: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
104%
n/a
ahead, against a pace of 53%
Sep 30
43 days left
Beat the expansion plan
2
Revenue
100%
104%
100%
ahead, against a pace of 53%
Sep 30
43 days left
Expansion ARR $1.2M
3
unassigned
50%
130%
63%
ahead, against a pace of 53%
Sep 30
43 days left
12 net-new enterprise logos
3
unassigned
30%
105%
30%
ahead, against a pace of 53%
Sep 30
43 days left
Gross churn under 4%
3
unassigned
20%
35%
7%
at risk, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
A flat board: five key results tracked straight at the top level with no objectives above them. The synthetic root is then the only branch there is, and the headline is the weighted mean of five leaves.
Objectives · Squad Kestrel
A flat board: five key results, no objectives above them
Weighted rollup of 5 key results66%Team scorecardpace 53% · due Sep 30
ahead43 days left
Team scorecardweight 100%progress 66%ahead
Weekly active accounts 4,200weight 30%progress 62%on track
Activation rate 38%weight 25%progress 74%ahead
Support CSAT 4.6weight 20%progress 67%ahead
Page p75 under 1.8 sweight 15%progress 88%ahead
Two case studies publishedweight 10%progress 26%off track
Where the 66% under “Team scorecard” comes from — each child’s share of what has been earned:
Weekly active accounts 4,20028%Activation rate 38%28%Support CSAT 4.620%Page p75 under 1.8 s20%Two case studies published4%
Objective rollup: Objectives · Squad Kestrel. The tree holds 5 nodes, 5 of them key results, across 5 top-level entries. Every sibling group is normalised to one unit before rolling up. Team scorecard rolls up to 66% against a pace of 53%, which is ahead, with 43 days left in the cycle. The headline currently reads Team scorecard at 66%. Every sibling group's weights already sum to 1.
Objectives · Squad Kestrel: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Team scorecard
1
unassigned
whole cycle
66%
n/a
ahead, against a pace of 53%
Sep 30
43 days left
Weekly active accounts 4,200
2
unassigned
30%
62%
28%
on track, against a pace of 53%
Sep 30
43 days left
Activation rate 38%
2
unassigned
25%
74%
28%
ahead, against a pace of 53%
Sep 30
43 days left
Support CSAT 4.6
2
unassigned
20%
67%
20%
ahead, against a pace of 53%
Sep 30
43 days left
Page p75 under 1.8 s
2
unassigned
15%
88%
20%
ahead, against a pace of 53%
Sep 30
43 days left
Two case studies published
2
unassigned
10%
26%
4%
off track, against a pace of 53%
Sep 30
43 days left
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
The snapshot is dated five days after the cycle closed. Elapsed time is clamped, so pace reads 100%, the deadline line reads "5 days over" instead of a negative count, and anything unfinished is measured against a window that has run out.
Objectives · Quarter close
Reviewed on 5 Oct, five days after the cycle closed
Weighted rollup of 1 objective77%Q3 rolluppace 100% · due Sep 30
at risk5 days over
Q3 rollupweight 100%progress 77%at risk
Close out the quarterweight 100%progress 77%at risk
All 14 objectives reviewedweight 50%progress 93%on track
Carry-over agreed with every ownerweight 50%progress 60%off track
Where the 77% under “Q3 rollup” comes from — each child’s share of what has been earned:
Close out the quarter100%
Objective rollup: Objectives · Quarter close. The tree holds 3 nodes, 2 of them key results, across 1 top-level entry. Every sibling group is normalised to one unit before rolling up. Q3 rollup rolls up to 77% against a pace of 100%, which is at risk, with 5 days over in the cycle. The headline currently reads Q3 rollup at 77%. Every sibling group's weights already sum to 1.
Objectives · Quarter close: every objective and key result with its weight in its own group, its progress, its share of what its parent has earned, its deadline and how it sits against pace.
Node
Level
Owner
Weight in group
Progress
Share of parent’s earned progress
Pace
Due
Days left
Q3 rollup
1
unassigned
whole cycle
77%
n/a
at risk, against a pace of 100%
Sep 30
5 days over
Close out the quarter
2
Chief of staff
100%
77%
100%
at risk, against a pace of 100%
Sep 30
5 days over
All 14 objectives reviewed
3
unassigned
50%
93%
61%
on track, against a pace of 100%
Sep 30
5 days over
Carry-over agreed with every owner
3
unassigned
50%
60%
39%
off track, against a pace of 100%
Sep 30
5 days over
A parent is the weighted mean of its children, so a key result’s pull on the number above is the product of its weight and every weight on the way up. Sibling weights are normalised to one unit, and any group that needed it is named below.
Click a row to re-point the number above; with a row focused ↑ and ↓ walk the tree, → and ← open and close a branch, Enter folds it, and Home / End jump to the ends.
Contract refusal: an import re-parented an objective under its own key result. A rollup walks from the leaves upwards, so a loop has no leaf to start from — better to refuse and name the node than to recurse until the stack gives out.
Objectives · Billing
An import re-parented an objective under its own key result
This tree can’t be rolled up
"Re-platform billing" is its own ancestor. A rollup walks from the leaves upwards, so a loop has no leaf to start from and no root to finish at.
Contract refusal: a key result was never wired up to a metric. A leaf is the only place a measurement enters the tree, so treating the hole as a zero would quietly drag every objective above it down.
Objectives · Security
One key result was never wired up to a metric
This tree can’t be rolled up
"Pen-test findings closed" has no children and no progress. A leaf is the only place a measurement enters the tree, so an unmeasured one would make every objective above it a guess.
Zyeon UI