How to Write a Project Retrospective People Actually Read
Turn a finished project into lessons the next one uses. What to include, what to leave out, and how to stay blameless without going soft on the facts.
Read article →Topic
9 articles tagged Project Management. For the wider topic, see Productivity & Operations.
Turn a finished project into lessons the next one uses. What to include, what to leave out, and how to stay blameless without going soft on the facts.
Read article →Decisions, owners, and dates, sent within an hour. The recap that stops a meeting from having to be repeated three weeks later.
Read article →Record a project decision so future readers can see what was chosen, why, who approved it, and when it should be reviewed.
Read article →Report a project risk with evidence, probability, impact, mitigation, owner, and the decision or support you need.
Read article →Explain a project scope change clearly, including the request, impact, options, owner, and approval needed.
Read article →The first email of a project sets its rhythm. How to align on goal, scope, roles, and the first milestone before anyone does the wrong work.
Read article →A written standup should inform without a meeting. How to report progress, surface blockers, and stay scannable for a distributed team.
Read article →Make dependencies visible without blame by naming the requested input, current owner, due date, and next follow-up.
Read article →A short weekly update structure for progress, decisions, blockers, ownership, and next steps across active projects.
Read article →