Score where your engineering organization will bottleneck under the next program
Ten questions, scored out of 100 against the level an organization needs to take on a major new program without restructuring around it.
- Free
- About five minutes
- See your score before giving an email
Five places a program loses time
Late programs are rarely late because the engineering was hard. They are late because a decision waited on a meeting, two teams built to different readings of the same interface, or scope moved and the schedule did not move with it. These are the five failure modes, and each one is measurable.
Decision Latency
Decisions wait on a meeting that has not been scheduled yet.
Interface Control
Two teams each built to their own reading of the same interface.
Critical Path Visibility
The schedule shows a critical path nobody believes.
Resource Contention
Your best engineer is the critical path on four programs at once.
Requirements Volatility
Scope changed; the schedule and the budget did not.
Ten questions. No email until you have seen your score.
The diagnostic asks how your organization behaves, not what it is building — nothing in it requires you to disclose a program, a customer or anything export-controlled. Most people finish in four to six minutes.
- Free
- Ten questions, about five minutes
- See your score before giving an email