0.3The golden triangle & stakeholders
The essentials in 30 seconds
- Golden triangle: cost, schedule and quality/scope are interdependent — you arbitrate, you don't maximize everything.
- Ask for THE priority: the date, the budget or the scope? Then propose costed scenarios.
- Stakeholders: their sometimes contradictory expectations weigh directly on these trade-offs.
Running mini-case — Bilal faces "everything, right now"
Bilal's client wants the site more complete, delivered sooner, with no extra budget. Bilal pulls out his triangle: date imposed by a trade show, fixed budget, so he proposes two scenarios — a reduced version by the date, or the full version three weeks later. He also lists stakeholders: client, owner, developers, end users — and gets the sponsor to decide.
Sequel to cases 0.1-0.2 — Bilal turns an impossible request into a trade-off.
1. The golden triangle
The golden triangle (or iron triangle) sums up every project's central tension: cost, schedule and quality/scope are interdependent. You cannot maximize everything: expanding scope lengthens schedule or raises cost.
Managing a project means constantly arbitrating between these three corners — and avoiding unkeepable promises ("faster, cheaper, and more complete").
2. Stakeholders
In parallel, you must identify the stakeholders: everyone who influences the project or is impacted by it (client, sponsor, team, users, management).
Their expectations, sometimes contradictory, weigh directly on the triangle's trade-offs.
🔎 Concrete example — 🔎 Concrete example — "Faster, cheaper, more complete"
The impossible request.
You cannot improve all 3 corners at once.
→ ask for THE priority: the date? the budget? the scope?
Then propose costed trade-off scenarios.Outcome: explicit constraints, not magic promises.
Reflex: reduce scope rather than sacrifice quality.
Section vocabulary
- Golden triangle
- Model linking cost, schedule and quality/scope: these three constraints balance out; you cannot optimize them all at once.
Simple example: Bilal shows the full site before the show would require more budget.
What it is not: promising faster, cheaper and more complete at the same time.
Reflex: translate every request into "which corner moves, and which compensates?"
- Scope
- Everything the project must deliver. Expanding it without adjusting cost/schedule unbalances the project.
Simple example: Adding an online shop to Bilal's showcase site expands scope.
What it is not: finish quality (that's a requirement level, not the deliverable list).
Reflex: cost every addition in schedule or money before accepting it.
- Trade-off
- Balancing decision between constraints: what to favor (schedule? cost? quality?) given project priorities.
Simple example: Bilal proposes a reduced version by the date or the full version delayed.
What it is not: flatly refusing with no alternative scenario.
Reflex: always propose 2 costed scenarios to the sponsor.
- Stakeholder
- A person or group who influences the project or is affected by it: client, sponsor, team, users, management.
Simple example: The site's end users, the client, the owner and Bilal's team.
What it is not: a passerby with no interest in or influence on the project.
Reflex: list everyone and note what they expect — including contradictions.
- Sponsor
- The stakeholder who carries the project, funds it and arbitrates. The project manager's key supporter.
Simple example: The SME owner in Bilal's case decides between the two proposed scenarios.
What it is not: a doer with no decision power or budget.
Reflex: get each trade-off validated by the sponsor, in writing.
In practice — In practice — Arbitrating with the triangle and listing stakeholders
- For a project, identify which of the 3 constraints is TOP priority (imposed deadline? fixed budget? non-negotiable quality?).
- Simulate an unforeseen event (a task takes 2× longer): which corner do you adjust — schedule, cost or scope?
- List all project stakeholders (internal and external) and what each expects.
- Spot any contradictory expectations (e.g. the client wants more, management wants cheaper): that is where trade-offs happen.
Ready-to-say script — asking for the priority and proposing 2 scenarios (1 min)
"We can't have all three at once: more complete, sooner, with no extra budget. What is non-negotiable: the date, the budget or the scope? I propose two costed scenarios: a reduced version by the date, or the full version three weeks later. You decide."
Say to the client with the triangle in view: turn refusal into a choice owned by the sponsor.
Copy-paste template — triangle trade-off sheet
PROJECT: _______________
NON-NEGOTIABLE PRIORITY (schedule / cost / quality): _______________
ADJUSTABLE CORNER: _______________
SCENARIO A (costed): _______________
SCENARIO B (costed): _______________
STAKEHOLDERS AND EXPECTATIONS: _______________
SPONSOR DECISION: _______________Small business / tight budget
Tiny budget, tight schedule: state upfront what is out of scope to meet the date without ruining yourself.
Algerian SME
Bilal builds local contingencies (client availability, payment delays) into his scenarios instead of promising a magic date.
Client who wants everything
Facing "faster, cheaper, more complete", write the three scenarios and get the choice signed: it protects against blame.
Internal project with no budget
Cost = team time: arbitrate between date and scope, and reduce scope rather than cut quality.
✓ Best practices
- Always ask for the triangle's priority (non-negotiable vs adjustable).
- Propose costed trade-off scenarios rather than a blunt refusal.
- Identify stakeholders' contradictory expectations.
✗ Common pitfalls
- Promising "faster, cheaper AND more complete".
- Cutting quality (debt paid later) instead of scope.
- Neglecting an influential stakeholder.
Key takeaways
- Cost, schedule and quality/scope are interdependent: don't maximize everything.
- Expanding scope necessarily impacts cost and/or schedule.
- Managing a project = continuously arbitrating between these three corners.
- Stakeholders and their (sometimes contradictory) expectations weigh on these trade-offs.
48h Challenge — apply tomorrow
For 1 real project, note its triangle priority and write 2 costed trade-off scenarios (template above). Present them to the sponsor.
- I can explain the golden triangle in one sentence.
- I can ask for THE priority and propose 2 scenarios.
- I've listed 1 project's stakeholders and their expectations.
Frequently asked questions
What to do when asked for "faster, cheaper and more complete"?
Explain the triangle: you can play on one corner by adjusting the others, but not improve everything simultaneously. Ask for the priority ("what is non-negotiable: the date, the budget or the scope?") and propose costed trade-off scenarios. Making constraints explicit protects the project from unkeepable promises. That is the project manager's role: turning an impossible request into concrete choices owned by the sponsor.
Is quality really negotiable?
Scope (what we deliver) is often distinguished from quality (finish/reliability level). You can reduce scope (deliver fewer features) without sacrificing the quality of what is delivered. Cutting quality itself is risky: it creates debt paid later (bugs, rework, dissatisfaction). In practice, facing a constraint, better to deliver less but well than more but badly.
The client wants the site more complete, sooner, with no extra budget. What does Bilal do?