01

Senior TimeDiagnoses · The Senior Staff Bottleneck

0 / 4

1.In an average week on this project, how many hours of senior staff time (Principal / Associate / Senior Architect) are spent on production-level work - drawing, detailing, redlining, rewriting documentation?

Less than 4 hours / week4-10 hours / week10-20 hours / weekMore than 20 hours / week

2.When a coordination issue arises on this project, who is most often the one resolving it?

Project manager or mid-level lead, independentlyProject manager, after escalating to senior staffSenior staff, directlySenior staff, because the issue keeps recurring

3.How many decision points on this project - in the last 30 days - were waiting on a specific senior person before the project could move forward?

Fewer than 33-67-12More than 12

4.If your two most senior people on this project were unavailable for one full week, what would happen?

Continue normally - execution owned at delivery layerSlow slightly but continueStall on most active frontsStop almost entirely

02

Documentation LoadDiagnoses · Documentation Creep

0 / 4

5.How many revision cycles has this project gone through in its current phase that were not triggered by client changes?

0-12-34-6More than 6

6.For the documentation work currently active on this project, can you name a single owner for each major decision (drawing set, spec section, coordination zone)?

Yes, ownership is fully clear and lockedMostly clear, with some gapsPartially clear - multiple people, no defined ownershipUnclear - most decisions are committee-style

7.In the last 60 days on this project, how many late-stage direction changes have caused work to be redone?

01-23-5More than 5

8.What percentage of the hours billed on this project in the last month do you estimate were spent on rework, RFI response, or unbilled clarifications - work that didn't exist in the original scope?

Less than 10%10-20%20-35%More than 35%

03

Delivery FlowDiagnoses · Blocked Movement

0 / 4

9.When you look at this project's progress over the last 30 days, where did time go?

Mostly active execution - teams working forwardMix of execution and waitingSignificant time waiting on reviews / approvalsMostly waiting - execution in short bursts

10.How long, on average, does a documentation package or design decision sit in review before it moves forward?

Less than 2 days2-5 days5-10 daysMore than 10 days

11.Does this project have defined checkpoints where senior staff engage - and clear ownership in between those checkpoints?

Yes - checkpoints exist and are respectedCheckpoints exist but are bypassed regularlyInformal - engagement is reactiveNo defined checkpoints - engagement is random

12.When a team member on this project is blocked, what's the most common reason?

External - waiting on client or consultantMixed external and internalInternal - waiting on internal review or decisionInternal - and they don't know who to escalate to

THE PIPELINE HEALTH DIAGNOSTIC

See your personalized diagnosis