Keeping people aligned.
WHAT MEETINGS A PROJECT TYPICALLY NEEDS
A kickoff A regular progress meeting Decision meetings, as required A closing review
WHAT A KICKOFF ESTABLISHES
Why the project exists What success looks like Who does what How you will work together What the schedule is
WHY IT MATTERS
It is the only time everyone shares the same picture.
WHAT A PROGRESS MEETING SHOULD COVER
What has been completed What is late, and why What is blocked Decisions needed Risks that have changed
WHAT IT SHOULD NOT BE
Everyone describing their week.
WHY
It is slow, and most of it concerns nobody else.
WHAT TO DO INSTEAD
Collect status in writing beforehand, and use the meeting for problems.
HOW LONG
Short. Thirty minutes is usually enough.
WHAT TO AVOID
Solving detailed problems with everyone present Meetings held because they are scheduled
WHAT TO DO ABOUT DETAILED PROBLEMS
Take them offline with the people involved.
WHAT TO END EVERY MEETING WITH
Decisions, actions, owners and dates.
WHAT TO SEND AFTERWARDS
Those, promptly.
WHAT TO CANCEL
Any meeting with nothing to decide.
WHY
It buys credibility for the ones that matter.
