The meeting about next week is about last week
The weekly meeting has two documents. A report, which says what happened. A look-ahead, which says what happens next.
In practice most of the hour goes on the first, and not even on the first — on explaining why parts of it didn't happen. Each explanation is reasonable and each one takes four minutes, and by the time the look-ahead is reached there are ten minutes left and everybody has stopped concentrating.
The only document in the room that could change next week is the one that gets the least attention.
How the look-ahead becomes an explanation list
Week 9 followed this from the workface: work that is not ready doesn't start, doesn't get removed, and rolls forward. What that looks like from inside the meeting is different, and worse.
An item everybody remembers from last week is no longer planned. It is explained. The conversation about it changes register entirely — from what has to happen for this to start, which is useful, to why it didn't, which is not — and it does so without anybody deciding to change the subject.
The tell is easy to spot. Count how many items in this week's look-ahead were in last week's. If it is most of them, the document has changed function and nobody has noticed
.
Who prepares it
In principle construction prepares the look-ahead, because they are the ones who will do the work and they know what is possible. Project controls consolidates it, checks it against the schedule and the constraints, and challenges what doesn't hold.
In practice project controls often writes it, because the site didn't send enough to consolidate. And the moment that happens the ownership problem from Week 1 reappears in a new place: the plan for next week now belongs to the person who won't be doing any of it.
That is worse than it sounds. A look-ahead written by planning is a proposal.
One written by construction is a commitment. Only the second is worth taking into a meeting, and the difference has nothing to do with the quality of the document.
What the weekly report is for
The report has a narrower job than most of them do.
It records the week for people who were not there, and it feeds the monthly. It is not the place to analyse the project, because the data is a week old and too thin to support conclusions. A weekly report that tries to be a small monthly report is long, late and read by nobody.
What earns its space is the exception: what changed, what is now at risk, and what decision is needed. The rest can be a table.
Turning the meeting round
The structural fix is to reverse the order, and it is more effective than it deserves to be.
Take the look-ahead first, while there is time and attention. Deal with next week's constraints while somebody can still act on them, because a constraint discussed on Friday can be cleared by Monday and one discussed at the end of the hour cannot.
Then handle last week, briefly, and only for items that change something. An activity that didn't start and now has a route is a two-line update. An activity that didn't start and still has no route is next week's problem, which means it belongs in the first half of the meeting rather than the second.
System design
Two documents with two different jobs, and the ownership question decides whether either works.
| Record | Produced by | Required quality | Verified against | Feeds |
|---|---|---|---|---|
| Look-ahead | Construction | Only work passing the six readiness tests | Constraint log | Next week's work |
| Constraint items | Project controls | Moved out of the look-ahead into the log | The six tests | Constraint closure |
| Weekly report | Project controls | Exception and change, not analysis | The week's records | Monthly report |
| Actions | The meeting | Owner, date, and what done looks like | Follow-up | Closure |
The second row is the correction. Blocked items belong in a constraint log where somebody has to close them, not in a plan where they can sit for months looking like work.
Practical insight
Take the last four look-aheads and mark every activity that appeared in more than one. Then mark the ones that appeared in all four.
That second group is not a plan. It is a list of blocked work, and it has been sitting in a planning document rather than in a constraint log where somebody would have had to close it.
Move them. The look-ahead gets shorter and more honest, and the constraints become visible to the person who can clear them.
Key takeaways
- Most weekly meetings spend their time explaining last week rather than planning next week.
- An activity that doesn't start and doesn't leave the list turns the look-ahead into an explanation list.
- Count how many items repeat from last week. If it is most of them, the document has changed function.
- Construction should prepare the look-ahead; project controls should consolidate and challenge it.
- A look-ahead written by planning is a proposal. One written by construction is a commitment.
- The weekly report records the week and feeds the monthly. It is not the place for analysis.
- Take the look-ahead first in the meeting, while there is still time to clear a constraint.
Records born here. Look-ahead · weekly report · action list · the constraint entries moved out of the look-ahead.
What is coming next
The weekly feeds the monthly, and the monthly is the document the project is judged by.
Next week: the monthly report — and why writing it is the easy part.
Enjoyed this lesson?
Join with Google to get each new lesson the moment it's published — and help me see which topics matter most to you. No spam, one email a week, unsubscribe anytime.
Already following on LinkedIn works too — this is just for the weekly email.