The meeting finishes on time, but the same blocked decision returns next week. A short project check-in should turn current delivery evidence into decisions and owned actions. A 20-minute agenda is a useful starting format when the reporting information is prepared beforehand, not a rule for every project.
Photo by Beatriz Cattel on Unsplash.
Send the update before the meeting
Ask owners to update accepted deliverables, the next milestone, blockers and decisions needed. Read the information before joining. Use meeting time for disagreements and choices, rather than asking each person to reconstruct their week aloud.
Try this agenda
First three minutes: what changed in the outcome, scope or forecast?
Next five minutes: is the next milestone supported by accepted work and available capacity?
Next eight minutes: resolve the most consequential blockers and decisions.
Final four minutes: confirm actions, owners, dates and escalations.
Adjust the allocation to the work. Move detailed technical problem-solving into a smaller follow-up with the right people. Keep its required decision and delivery effect visible to the wider project.
End with a decision record
For an illustrative client-portal project, testing is waiting for representative data. The useful result is a named data owner, a delivery date and a sponsor decision if the date cannot be met. “Everyone to chase testing” is not an adequate action.
Read the agreed actions aloud. Ask whether the named people have the authority and capacity to complete them. Record any changed forecast or accepted trade-off in the working plan, not only in meeting notes.
Related guidance: small-team project planning guide.
At the next check-in, start with unresolved actions that affect delivery. If the meeting repeatedly produces no decisions, inspect whether the necessary decision-maker attends and whether the questions arrive with evidence. Hili Consulting can help establish a review rhythm that supports delivery without adding meeting overhead.
