| Name | Logged | Idle % | Tasks |
|---|---|---|---|
| ▾Ariana DoradoLaunch Lead | — | — | 7 |
Tech post-launch QALaunch3× Pre-launch prepLaunch3× Tech Post-Launch QALaunch1× | |||
| ▾Michaelraj ASr. WP Dev | — | — | 5 |
Pre-Launch PrepLaunch3× Tech Post-Launch QALaunch1× Tech post-launch QALaunch1× | |||
| ▾Hardik VagadiyaDevOps | — | — | 7 |
DevOps configure DNSDevOps5× Site LaunchLaunch2× | |||
complete − start). For every completed task we compare its cycle time to a benchmark — the historical median cycle time for that task type & project size. For a team: Efficiency % = Σ(benchmark days) ÷ Σ(actual cycle days) × 100 over its completed tasks, capped at 100%. 100% = tasks closed at or faster than the team's typical pace; below 100% = slower. Only completed tasks with a positive cycle count (same-day/undated excluded). Per-person efficiency is intentionally hidden — it is too noisy at individual volume to be fair. This measures speed-to-done, not hours worked; a beta signal, not a performance verdict.