WAJD Learning

Module 1 of 2 · 45 minutes

Scope, estimates and the amber that lasted four months

By the end of this module you will be able to

  • Write scope that makes change visible
  • Estimate in ranges and communicate uncertainty honestly
  • Run status reporting that surfaces problems early
  • Escalate before it is a crisis

Work through it

1 interactive for this module, built on the WAJD Teach engine. Nothing moves until you ask it to, and every one has a written version if you would rather read it.

Amara I inherited a project that is already late and I have no certification.

Nadia Which puts you in the majority. Most projects are run by people who were good at something else, and most project failure has nothing to do with methodology.

Amara What does it come from?

Nadia Three things. Scope nobody agreed. Estimates nobody believed. And a status report that said amber for four months and then said red two weeks before the deadline.

Amara Scope creep.

Nadia Except scope creep is not the problem, and this is where most advice goes wrong. Scope changing is normal and usually correct. The world moved, or somebody learned something.

Amara So what is the problem?

Nadia Scope changing invisibly. Absorbed quietly by a team who did not want to seem difficult, until the original date arrives and the work is not done, and nobody can point at when it went wrong.

Amara So how do I stop absorbing things?

Nadia One sentence. Yes, and here is what that displaces.

Amara That is it?

Nadia That is it, and it does an enormous amount of work. It does not say no, so you are not obstructive. And it forces the conversation about consequence that everybody was avoiding, with somebody who actually has the authority to make the trade.

Amara Estimates. I get asked how long and I have to say something.

Nadia Then say a range with a confidence, because a single number is a lie. Give one and it is heard as a commitment, and every conversation after that treats it as one.

Amara People hate ranges. They want a date.

Nadia They want certainty, which does not exist, so give them something better. Six to ten weeks. Six if the data is as clean as we have been told, ten if it is not, and we will know within a fortnight.

Amara The last bit is the useful part.

Nadia It is the whole thing. It converts uncertainty into a scheduled decision point instead of an argument. Nobody can be annoyed with a range that comes with a date for resolving it.

Amara Should I estimate for my team if they are busy?

Nadia Never. Manager produced estimates are consistently optimistic, and worse, the people doing the work do not own them. Then when it slips it is your number, not theirs, and nobody is accountable.

Amara Status reporting. Ours is amber constantly.

Nadia Watermelon reporting. Green on the outside, red in the middle. And amber for months is the most dangerous status there is, because it sounds like it is being managed.

Amara Why does everybody do it?

Nadia Because red is treated as a confession rather than as information. In a culture that punishes red, you get green reports right up until delivery fails, and then everybody is surprised.

Amara So what do I write instead?

Nadia Report against a specific dated commitment. Not amber, some challenges. Instead: we committed to migrating forty records a day, we are achieving twenty two, and at that rate we finish three weeks late.

Amara That is much harder to ignore.

Nadia It is impossible to ignore, and that is the point. It is also much harder to blame you for, because you have given a number and a forecast rather than a mood.

Amara Last thing. Escalation feels like admitting I cannot cope.

Nadia Which is why people wait, and by the time they escalate all the good options have gone. Escalate when a decision is needed above your authority, when a risk has actually materialised, or when you need something you cannot get yourself.

Amara How do I do it without looking like I am struggling?

Nadia Bring the problem, the options with their consequences, and your recommendation. That turns you from somebody bringing a problem into somebody bringing a decision. Same escalation, completely different impression.

The written material

Scope creep is not the problem

Scope changing is normal and usually correct: the world moved, or somebody learned something. The problem is scope changing invisibly, absorbed by a team who did not want to seem difficult, until the original date arrives and the work is not done.

So the job is not preventing change, it is making change visible. Every addition gets a decision: what comes out, what moves, or what extra resource arrives. Somebody with authority makes that trade, in writing, and it is recorded.

The phrase that does most of the work: 'Yes, and here is what that displaces.' It is not obstructive, it does not say no, and it forces the conversation about consequence that everybody has been avoiding.

A single number estimate is a lie

Asked how long something will take, the honest answer is a range with a confidence attached. Give a single number and it is heard as a commitment, and every subsequent conversation treats it as one.

Estimate in three points: optimistic, most likely, pessimistic. Give the range, and be explicit about what would move it. 'Six to ten weeks. Six if the data is as clean as we have been told, ten if it is not, and we will know within a fortnight.'

That last clause is the valuable one, because it converts uncertainty into a scheduled decision point rather than an argument.

And never estimate on behalf of the people doing the work. Estimates produced by a manager alone are consistently optimistic, and the team who did not produce them do not own them.

The watermelon report

Green on the outside, red in the middle. Status reporting fails in a specific and predictable way: a project reports amber for months because amber is comfortable, then goes red two weeks before the deadline, at which point nothing can be done.

The cause is that reporting red is treated as a confession rather than information, so people avoid it until avoidance is impossible. A culture where red is punished produces green reports right up until delivery fails.

Fix it by reporting against a specific, dated commitment rather than a vibe. Not 'amber, some challenges', but 'we committed to migrating 40 records a day, we are achieving 22, and at that rate we finish three weeks late'. That is a status. Everything else is mood.

  • Report against a measurable commitment, not a colour and a feeling
  • State the forecast consequence in dates, not adjectives
  • Say what decision you need and by when
  • Escalating early is information; escalating late is a confession

Escalation is not failure

New project managers treat escalation as admitting they cannot cope, so they wait, and by the time they escalate the options have narrowed to bad ones.

Escalate when a decision is needed above your authority, when a risk has materialised that changes the forecast, or when you need something you cannot obtain yourself. Bring the problem, the options with their consequences, and your recommendation.

That last part converts you from somebody bringing a problem into somebody bringing a decision, and it is the difference between being seen as struggling and being seen as running it.

Knowledge check

The knowledge check and your certificate need a free account, so that your progress and results can be saved as evidence.

Create a free account Sign in

The learning itself stays free and open. You are reading all of it right now without an account.