Polimake

The project management trilemma: scope, time, and cost

A practical guide to the project management trilemma: the relationship between scope, time, cost, and quality, with examples and a checklist.

· Platform

The team behind Polimake. We explore the intersection of technology, creativity, and automation.

Published:
The project management trilemma: scope, time, and cost

Quick answer: the project management trilemma explains that scope, time, and cost are connected. If you increase one without adjusting the others, the project's quality or viability suffers. It's also known as the iron triangle or the triple constraint, and it applies to everything from construction to digital projects and creative campaigns.

The three corners

  • Scope: what is going to be delivered.
  • Time: when it has to be ready.
  • Cost: resources, budget, and available people.

Quality doesn't live in isolation: it depends on the balance between those three factors.

Example in content

If a campaign needs more pieces, more formats, and more rounds of review, the scope goes up. To keep quality, you normally need more time or more resources. If nothing is adjusted, errors, delays, or weak deliverables will appear.

If the deadline moves up, you have to reduce scope or add resources. Asking for "the same thing, faster, and for the same budget" usually shifts the cost onto quality or the team's stress.

In video production, a classic case: the client asks to go from three pieces to five within the same timeframe. The options are to produce the two extras with the same team (time goes up or quality drops), bring in another editor (cost goes up), or deliver the two extras as cut-down versions of the existing material (limited scope). Any of the three is valid; what rarely works is taking on all five without changing anything and hoping it turns out fine.

How to use it in decisions

When a constraint changes, ask:

  • Which deliverable can be cut?
  • Which date can move?
  • Which resource can be added?
  • What level of quality is acceptable?
  • What risk appears if we don't adjust?

Use Studio to make scope, statuses, owners, and dates visible. Store the brief, references, assets, and approvals in Media to reduce rework.

Common mistakes

  • Accepting changes without updating the date.
  • Adding deliverables without budget.
  • Cutting time without cutting review.
  • Not defining "done."
  • Confusing urgency with priority.

Metrics

Measure delays, scope changes, rounds of review, team load, rejected deliveries, and margin. The trilemma helps you have hard conversations with data, not intuition. A simple quarterly report—how many projects closed on time, how many required renegotiation, and where the delays concentrated—usually reveals useful patterns. Most organizations don't discover their trend until they have the data in front of them. It relates to stakeholders, because part of the manager's job is to align expectations before the trilemma breaks.