Course contentsShow
← Software Engineering
Lesson 31 of 1,9331. Foundations of Software EngineeringFree lesson

Good-Fast-Cheap: Pick Two

Understanding why projects cannot simultaneously optimize all constraints and how to prioritize based on context.

Good-Fast-Cheap: Pick Two

What you'll learn: Why you can only optimize two out of three project qualities at once, and how to choose wisely.


The Core Principle

The "Good-Fast-Cheap" rule states that in any software project, you can pick at most two of these three qualities:

  • Good — High quality, well-tested, maintainable code
  • Fast — Quick delivery, short timeline
  • Cheap — Low cost, minimal resources

This extends the Iron Triangle concept (scope, time, cost) by focusing on the inevitable trade-offs between quality, speed, and budget.

Why Can't You Have All Three?

Physics and resources simply don't allow it. High quality requires careful design, testing, and review—all of which take time or additional skilled people (cost). Rushing (fast) with minimal resources (cheap) means cutting corners on quality. Delivering cheaply and well means accepting a longer timeline.

Examples:

  • Good + Fast → Expensive (hire more senior developers, pay for overtime)
  • Good + Cheap → Slow (small team working carefully takes time)
  • Fast + Cheap → Poor quality (rushed work with minimal resources creates technical debt)

Choosing Your Two

Context determines which two you prioritize:

  • A startup MVP might choose Fast + Cheap to test the market quickly
  • Mission-critical healthcare software demands Good + Fast (budget is secondary to lives)
  • An internal tool with no deadline might favor Good + Cheap

The key is making this choice explicitly with stakeholders, not discovering it by accident mid-project.


Key Takeaway: You cannot simultaneously maximize quality, speed, and cost-efficiency—consciously choose which two matter most for your project's context, and communicate that trade-off clearly to all stakeholders.