Iron Triangle
The classic trade-off between scope, time, and cost in engineering projects.
The Iron Triangle (also known as the Project Management Triangle) illustrates the fundamental constraints in any project: scope, time, and cost. These three factors are interconnected—changing one inevitably affects at least one of the others.
The Three Constraints
Scope
What needs to be delivered—the features, functionality, and requirements of the project.
Time
When the project needs to be completed—the schedule and deadlines.
Cost
The resources available—budget, team size, and tools.
The Core Principle
The triangle demonstrates that you cannot change one constraint without impacting at least one other:
- Increase scope → Need more time or cost
- Reduce time → Need to reduce scope or increase cost
- Reduce cost → Need to reduce scope or extend time
Quality: The Hidden Fourth Dimension
Quality sits at the center of the triangle. If you try to fix all three constraints simultaneously without adjusting resources, quality suffers.
When to Use This Model
Use the Iron Triangle when:
- Planning project timelines and resources
- Negotiating scope with stakeholders
- Making trade-off decisions
- Communicating constraints to leadership
- Prioritizing features for an MVP
In Practice
Effective engineering leaders use this model to set realistic expectations and guide conversations about what's possible. Rather than viewing constraints as limitations, see them as forcing functions for clarity and prioritization.