Judgment detail
One signal, fully reasoned: what goal it was meant to move, how good the work is on its own terms, and whether it was the highest-leverage use of capacity.
Weekly status sync (recurring)
60 min, 7 attendees, every week. Agenda: 'go around the room'. No decisions logged in the last 4 instances.
What the engine inferred
The three scores
never a single numberDimension breakdown
how output value was earnedMeeting happens reliably — but produces no decisions.
'Go around the room' agenda; 4 instances with zero logged decisions.
60 min × 7 people × weekly = ~7h/week of collective time for no recorded output.
Judgment trace
question → finding- 1
What goal was this meant to move?
None. It's a recurring status ritual, not a decision forum.
- 2
How good is the work on its own terms?
A meeting with no decisions in 4 instances is a candidate to make async.
- 3
Was this the highest-leverage use of capacity?
No — 7 person-hours weekly with no decisions is a structural drain on focus time.
Narrative
The weekly status sync is costing ~7 collective hours and producing no decisions across its last four runs. This is the meeting most worth converting to async — it would hand focus time back to the whole team, which the leverage data says is the scarce resource.
Action ladder
how far the engine will goConvert the weekly sync to an async written update; keep a 15-min decision-only slot. Reclaims ~6h/week across 7 people.
Proposal: replace the 60-min weekly sync with a Friday async thread (status in writing) + an optional 15-min decisions-only call. Last 4 syncs logged 0 decisions; this returns ~6 focus-hours/week to the team.