BUSFACTOR.TECH
This is Northwind Engineering, a sample org.Connect GitHub and see yours in minutes →
62
C▼ 1
Organization Health

Northwind Engineering grades C

6 of 8 organs measured · targets: expert baseline · as of 2026-09-25

Organization Health across snapshots

What’s actually wrong

3 confirmed problems · see all of yours →

What’s genuinely working

The eight organs

sub-scores 0-100 · expert baseline targets · A ≥ 85 … F < 40
Delivery Flow
32F
unchanged
How it’s scored

Weighted blend of 4 of 4 inputs = 32 → grade F (0-39).

  • Pickup latency (p50)35%
    120.0 h (~5 days)0/100
  • Pickup latency (p90)20%
    168.0 h (~7 days)40/100
  • Cycle time (p50)30%
    169.0 h (~7 days)40/100
  • Stale work-in-progress15%
    581/100
Code Health
63C
unchanged
How it’s scored

Weighted blend of 5 of 5 inputs = 63 → grade C (55-69).

  • PR size (p50 lines)25%
    24070/100
  • Review depth (comments / 100 lines)20%
    0.2543/100
  • Rubber-stamp reviews20%
    0.0%100/100
  • Hotspot files20%
    483/100
  • Regression Rework Share15%
    12.9%0/100
Knowledge Risk
85A
unchanged2/3 inputs
How it’s scored

Weighted blend of 2 of 3 inputs = 85 → grade A (85+).

  • Bus-factor-1 paths50%
    175/100
  • Blast radius (max)35%
    1100/100
  • Onboarding to 10th PR (p50 days)15%
    not measured yet

Only 85% of the designed weight is observed - the blend renormalizes over measured inputs, so their weights add to 100%.

AI Leverage
Connect AI telemetry
Needs AI-usage telemetry - assistant adoption, agent-authored PR share, spend. Connect Copilot/agent reporting to measure.
Process Integrity
73B
unchanged
How it’s scored

Weighted blend of 3 of 3 inputs = 73 → grade B (70-84).

  • PR-ticket linkage50%
    82.3%96/100
  • Zombie tickets25%
    35.0%29/100
  • Orphan PRs25%
    17.6%71/100
People Signal
84B
▼ 0.4 vs last snapshot
How it’s scored

Weighted blend of 3 of 3 inputs = 84 → grade B (70-84).

  • Review-load Gini40%
    0.660/100
  • Top-person load share35%
    23.7%100/100
  • After-hours work25%
    0.0%100/100
Operational Resilience
23F
unchanged1/2 inputs
⚠ deploy frequency per week is a young signal - its observable history is shorter than the window it claims; treat with care
How it’s scored

Weighted blend of 1 of 2 inputs = 23 → grade F (0-39).

  • Deploy frequency (per week)young60%
    0.3123/100
  • CI duration (p50)40%
    not measured yet

Only 60% of the designed weight is observed - the blend renormalizes over measured inputs, so their weights add to 100%.

⚠ deploy frequency per week is a young signal - its observable history is shorter than the window it claims; treat with care

Strategic Alignment
Add your quarter priorities
Needs the 7-minute intake - your quarter priorities mapped against tickets - to measure how much work actually serves them.

What moved

Pickup p50
120.0 h (~5 days)
unchanged
Linkage rate
82.3%
▼ 1 pp vs previous
Deploys / week
0.31
unchanged
See the rest of the read on your own code →4 of 27 findings shown

Your org, read the same way.

Connect GitHub and the first verdict lands in minutes.

Start the trialSee a sample Board PackOn-Prem Full Audit: talk to us