Bottleneck tiers
The real bottleneck stays visible: is it handoffs, tools, ownership, evidence overhead, or raw decision delay?
This view keeps each lane tied to the dominant friction dimension so leadership can simplify the right thing first.
| Lane | Tier | Dimension | Risk headline | Blocking issue | Friction | Handoffs | Tools | Latency | Ownership |
|---|---|---|---|---|---|---|---|---|---|
| AI governance and agent controls | PRESSURED | DECISION_LATENCY | Executive demand is outpacing approval capacity and creating avoidable delay. | Approvals still depend on too few shared reviewers and too many memo handoffs. | 71 | 68 | 39 | 76 | 81 |
| Procurement and trust operations | PRESSURED | EVIDENCE_OVERHEAD | The team is spending too much time repackaging evidence that should already be standardized. | Evidence packaging standards are not yet consistent enough across trust, procurement, and diligence rooms. | 66 | 61 | 42 | 58 | 84 |
| Biotech and diagnostics operations | CONSTRAINED | HANDOFF_COMPLEXITY | Regulated credibility is high, but execution still stalls between evidence creation and release-ready decisions. | QA, CAPA, specimen, and GxP lanes still hand work across separate checkpoints instead of one narrower closure flow. | 74 | 79 | 47 | 69 | 63 |
| FinTech and treasury controls | CONSTRAINED | CHANGE_FRICTION | Commercial opportunity exists, but change overhead is still too high for confident scaling. | Merchant, KYC, and treasury changes are not yet isolated enough to prevent repeated regression checks. | 78 | 65 | 52 | 63 | 58 |
| Nonprofit and foundation ops | PRESSURED | OWNERSHIP_AMBIGUITY | Work is getting done, but too many decisions still depend on informal ownership rather than visible accountability. | Too many adjacent workstreams share responsibility without a single final owner per packet. | 64 | 59 | 28 | 57 | 48 |
| Robotics and override operations | BROKEN | TOOLING_FRAGMENTATION | The lane is interesting, but the toolchain is still too fragmented to justify heavier operating investment. | Fleet, sensor, and override flows are not yet consolidated enough to keep response work continuous. | 83 | 73 | 86 | 67 | 54 |