PM Through ConsensusA Project Management Course
Module 7 · Refine and end: building the plan, practicing, reflecting 7.5 Module 7 checkpoint: share out and reflect
Subsection 7.5

Module 7 checkpoint: share out and reflect

~7 min

Reading

The final move: share out and reflect. Every project owes itself the question, "What would we do differently?" Write down the answer. Carry it forward.

A real reflection has four questions. (1) Does the project plan you built reflect the project scope you wrote? (2) What was this process like — for you personally and for the team? (3) Were there pain points, and what caused them? (4) What worked well, what did not, and what would you do differently next time?

Write the answers down. A team that reflects and forgets is doing therapy, not improvement. A team that writes down its reflections and reads them at the start of the next project is doing organizational learning. The difference is a Google Doc and a calendar reminder.

Share out the reflection with one person outside the project team. A peer in another org. A mentor. A funder you trust. The act of explaining the project to someone outside it surfaces things you did not see from inside. Listen to what they ask back; their questions are usually the right ones.

You started this course with a project on a card. By now, that project has a scope, a style, roles, deadlines, agreements, a consensus rhythm, a free tool stack, and a plan. The next project will be easier because of this one. The one after that will be easier still. That compounding — discipline that survives across projects — is what becoming "the most Xingona/Xingon/Xingone project manager in community projects" actually looks like.

RETRO · the four questions the team owes itself 1 · WHAT WORKED specific, named, not generic praise Multilingual phone bank actually filled MOCHA chart held; no role drift midproject Buffer weeks absorbed two real surprises 2 · WHAT DIDN'T honest, without blaming a person Survey draft turnaround was twice as long Decisions Log went a month untouched Two members felt overlooked at the close 3 · WHAT WE LEARNED about how the team works, not just the task Translation review needs its own buffer week A 30-min Friday close cadence works Member 1:1s before launch were the actual unlock 4 · WHAT WE'LL DO DIFFERENTLY turned into next project's plan, not aspiration Add translation buffer to every timeline Decisions Log = standing agenda item Member 1:1s become a planning requirement

Learner action

Write your reflection on this course. What is the one project habit you are committing to keep? Schedule a calendar reminder for 30 days from now to check whether you actually kept it.

Action: Complete the learner action above, then slide to continue.