Project management, minus the jargon

In one paragraph

Every project trades three things. You can have it fast, cheap or complete — pick two, and be honest about which one you have just let go.

Scope is what is included. Time is when it is delivered. Cost is what it takes — money and people. Quality sits in the middle and is what actually degrades when the three are squeezed.

The rule is that the three are connected. Add scope without adding time or cost and something gives, usually quality, usually silently.

The conversation this makes possible

It converts an argument into a choice. 'Can we also add X?' becomes 'yes — and that moves the date by a fortnight, or costs another two thousand, or we drop Y. Which?'

Said out loud at the moment of the request, this is the single most effective defence against [scope creep].

How to actually use it

• Name which of the three is fixed before a project starts. Usually one genuinely is, and knowing which tells everyone what to trade.
• When a change is requested, price all three options rather than refusing. It moves you from obstacle to adviser and the answer is frequently 'leave it as it is'.

Where it breaks down

• It is a simplification — the three are not smoothly interchangeable, and adding people to a late project famously makes it later.

More on operations