Find the single sub-domain most holding back the others, so the work fixes the cause rather than a symptom.
The five sub-domains sit in a dependency order. Upstream weakness constrains everything downstream, so it is fixed first. The rule: your binding constraint is the lowest-scoring sub-domain that sits highest in this order. A Level 1 in Priorities outranks a Level 1 in Completion, because Priorities is upstream. If two are tied on score, the one higher in the order is the constraint.
| Order | Sub-domain | Why it sits here |
|---|---|---|
| 1 (most upstream) | Priorities | If the team cannot agree what matters, nothing downstream can be aimed correctly. |
| 2 | Capacity | Clear priorities with no capacity discipline still cannot be finished. |
| 3 | Meetings | The cross-cutting coordination layer; bad meetings drain capacity and block alignment. |
| 4 | Completion | Depends on a clear target, room to finish, and status flow. |
| 5 | Individual effectiveness | Partly independent, but undermined by any team-level chaos above it. |
| Sub-domain | Your level (1 to 5) | Dependency order |
|---|---|---|
| Priorities | 1 | |
| Capacity | 2 | |
| Meetings | 3 | |
| Completion | 4 | |
| Individual effectiveness | 5 |
Your answers stay in your browser on this page and are never sent anywhere. Carry the constraint and all five scores into the Action Plan.