Presentation Tips for Project Managers: The Status Update
By Daniel Harper · Career & Business
How should a project manager present a status update? Lead with what the room has to decide or worry about, not the activity list. Give the status in one line, then what changed, what is at risk and what you need from them. Report bad news early and plainly, with your recommendation attached: optimistic reports protect nobody, and they make the next update harder to believe.
Most of what a project manager presents is not a pitch or a keynote. It is the weekly update, the steering committee, the stakeholder review and the kickoff: the same few people, on a cycle, deciding whether to keep trusting your picture of the project. Those presentations reward different skills from a conference talk, and most presentation advice is not written for them.
Start with what the room has to do
The people in a status meeting want to know one thing first: is there anything they need to decide, approve or worry about? Put that at the top. An update that opens with "here's what the team did this week" makes everyone sit through the activity list to reach the part that concerns them, and that part then gets less time.
A shape that works for most updates:
- The headline. One sentence: on track, at risk or off track, and why. "We're on track for the March launch, with one risk on the vendor integration."
- What changed since last time. Not everything that happened: the two or three things that moved the date, the scope or the budget.
- What is at risk. The specific risk, its likely effect, and when you will know more.
- What you need. A decision, a resource, an escalation. If you need nothing, say so.
Then stop. The detail belongs in the written report, where people can read it at their own pace.
Report bad news early, and plainly
The hardest presentation a project manager gives is the one where the project is in trouble. It is also where status reporting most often fails, and that failure has been studied.
Psychologists have a name for the general reluctance to pass on bad news, the MUM effect, from a 1970 paper by Rosen and Tesser.1 Smith and Keil later applied the idea to troubled software projects, describing how evidence that a project is failing can exist lower down an organisation and still not reach, or reach only in distorted form, the people with the authority to change its course.2
The cost shows up in the numbers. In a survey of 561 project managers, Iacovou and colleagues found that better status reporting went with better project performance, and that optimistic biasing, presenting a project as healthier than it is, degraded the quality of the reporting.3 The same study found that how selectively project managers reported depended partly on the executive they reported to: that executive's power, the project manager's trust in them, and how well the executive communicated.
The lesson cuts both ways. If you present status, say the bad news while it is still small: plainly, in the first minute, with your recommendation attached. If you receive status, the way you react to the first bad report decides whether you get honest ones afterwards. And when the room pushes back on your recommendation, objection handling covers how to answer it.
One sentence pattern does most of the work: what happened, what it means, what we recommend, what we need from you.
"The vendor's API won't be ready until the 14th, two weeks late. That moves user testing and puts the March date at risk. We recommend testing against a mock of their API from Monday, which keeps March if their new date holds. We need sign-off on an extra week of contractor time."
Use the colours honestly
Traffic-light status is useful because it is quick to read, and it stops being useful the moment amber starts to mean "red, but I'd rather not say so". Agree with your stakeholders what each colour means (for example: red means the date or budget will be missed without a decision from this group) and hold to it. A project that sits on green for three months and turns red overnight costs you more credibility than an honest amber in month one.
Show only what the decision needs
Steering committees are short of time, not intelligence. Working memory holds only a handful of items at once,4 so a slide with twelve risks on it is read as "lots of risks" and nothing more. Show the two or three that need this group, and leave the rest in the risk register, where they can be read properly.
A chart should answer one question. "Will we make the date?" is a milestone line or a burndown, not a Gantt chart of every task. If a chart needs a minute of explanation, it is the wrong chart for this room.
A kickoff is a different presentation
A kickoff is the one meeting where your audience is the team rather than the sponsors, and its job is shared understanding rather than a decision. Cover why the project exists, what done looks like, how the team will work and how decisions get made. Then leave real time for questions: the questions at a kickoff are the cheapest place to find the misunderstandings that would otherwise surface in month three.
Rehearse the hard sentence
Most of a status update can be read off the report. The part worth saying out loud beforehand is the hardest sentence: the delay, the overspend, the risk. Say it until it comes out plainly, with no hedges stacked in front of it, because a qualified, apologetic version ("so, it's possible we may be looking at a small slip...") is heard as worse news than the plain one. The speech pattern that undercuts you explains why hedges stacked on a fact weaken it.
References
- Rosen, S., & Tesser, A. (1970). On reluctance to communicate undesirable information: the MUM effect. Sociometry, 33(3), 253. https://doi.org/10.2307/2786156
- Smith, H. J., & Keil, M. (2003). The reluctance to report bad news on troubled software projects: a theoretical model. Information Systems Journal, 13(1), 69–95. https://doi.org/10.1046/j.1365-2575.2003.00139.x
- Iacovou, C. L., Thompson, R. L., & Smith, H. J. (2009). Selective status reporting in information systems projects: a dyadic-level investigation. MIS Quarterly, 33(4), 785. https://doi.org/10.2307/20650327
- Cowan, N. (2001). The magical number 4 in short-term memory: A reconsideration of mental storage capacity. Behavioral and Brain Sciences, 24(1), 87–114. https://doi.org/10.1017/S0140525X01003922