Operational Risk Engine
Risk is computed from your actual task data — not from individual judgment. Two signals drive the score: how many tasks are open (Quantity) and how fast tasks move through to done (Velocity). When both signals are elevated, tech debt compounds faster than it can be paid.
Loading data…
Quantity — Backlog Pressure
Count of active (open + in-progress + blocked) tasks.
More unresolved work = higher debt carrying cost.
More unresolved work = higher debt carrying cost.
—
open tasks
0 – 15 tasks
Low
Healthy backlog. Team capacity matches demand.
16 – 35 tasks
Medium
Backlog growing. Monitor for stalling.
36 – 60 tasks
High
Backlog pressure is significant. Prioritize ruthlessly.
61+ tasks
Critical
Debt likely unserviceable at current pace.
Velocity — Speed to Done
Average age of active tasks (days from created to now).
Slow throughput means debt stays on the books longer.
Slow throughput means debt stays on the books longer.
—
avg days open
0 – 5 days
Low
Team is moving fast. Healthy throughput.
6 – 10 days
Medium
Slowing down. Review blockers and priorities.
11 – 20 days
High
Tasks aging significantly. Velocity at risk.
21+ days
Critical
Work is stalling. Structural intervention required.
Key Signals
—
Open Tasks
—
Blocked Tasks
—
Overdue (Past Due Date)
—
Oldest Active Task (days)
Backlog by Owner
Loading…
Oldest Active Tasks — Velocity Drag
Loading…
Risk Context Notes
Human context about the current risk posture — what the numbers can't tell you.
No context notes yet.