Shared specialist
Several projects depend on one qualified person or team at the same time.
Project priority
When projects share one specialist, starting all of them can delay all of them.
Project status reviewed separately can hide the shared approval, dependency, skill, or intake path that controls several dates.
Portfolio evidence
Look for the repeated dependency across projects.
The shared condition matters more than the number of red project cards.
Shared approval
Ready work accumulates before the same authority or review group.
Shared input problem
Projects arrive incomplete and create rework at the scarce step.
Shared release policy
Every approved project starts, even when downstream capacity cannot absorb it.
Priority record
Make the tradeoff explicit.
A useful portfolio review names which work moves, which work waits, and why the selected sequence serves the exposed result.
ExposureWhich dates matter
Connect projects to goals, customers, deals, owners, and decision dates.
DemandWhat reaches the shared step
Review ready work, incomplete work, queue depth, and average wait.
ChoiceProtect or pause
Release fewer items and protect the sequence from lower-value interruption.
CheckCompletion and wait
Compare project movement, active work, queue, and completed work later.
Bring one result that is late or at risk.
We will map the work behind it, compare plausible causes, identify missing evidence, and define one management action worth testing.