A small project blocks a major program. How should priority change?
Dependency-based portfolio priorityConsider the enabling role of the small project, not only its standalone benefit. Prioritize the work necessary to unlock the wider outcome and confirm the dependency is genuine.
What to do now
- Verify the dependency and required output
- Quantify the effect on the larger program
- Allocate proportionate capacity
- Track the enabling milestone explicitly
When to escalate
Escalate when
The blocker threatens a strategic or mandatory outcome.
Who decides
The portfolio decision authority
Example
A modest identity-management change receives priority because several major services depend on it.
Mistake to avoid
Giving the project low priority because its own budget is small.
Prevent a repeat
Review whether active commitments fit available capacity and current priorities rather than just tracking project counts.
Suggested ApprovedFlow setup
- Projects
- Resources
- Documents
- Approvals
Use project and capacity records to support portfolio decisions, then record approved priorities and consequences explicitly. See the platform
Related cases
- How can a small organization get value from a PMO without hiring a large team?Lightweight portfolio coordination
- The same dependency appears in many project plans. Who should own it?Shared dependency governance
- Another team says our dependency is not their priority. What should we do?Unagreed external dependency
- How do we keep change control lightweight for a small team?Proportionate change recording