Prioritization, documentation, follow-up: the three pillars
Prioritization, documentation, follow-up. Three pillars. Skip any one of them and a project will work for a few weeks, then come apart.
Prioritization is the question every project meeting should start with: which tasks are the most important and why? Not "what is left on the list" — that is a stress producer, not a strategy. A good PM names the top three things this week, says out loud why those three (and not the other twelve), and lets the team push back. The order is the work.
Documentation is how we keep track of the work we are doing and the decisions the team has made. It is also how a project survives someone leaving, getting sick, or starting a new job. If a decision lives only in one person's head, that decision will be unmade. Write down what was decided, by whom, and the date. A shared doc beats a memory every single time.
Follow-up is what dates things are due, who follows up, and how. In community work, follow-up is often the thing that does not happen because everyone is too kind to ask, "Did you do the thing you said you would do?" That kindness ends up costing the project. Build a follow-up rhythm into the meeting cadence, not the calendar nag.
These three pillars are why this course is called Project Management Through Consensus, not Project Management Through Authority. Prioritization, documentation, and follow-up all become much easier when the team agreed to them together. We will build that consensus muscle in Module 5.
Learner action
For the project on your card, write one prioritization question, one documentation home, and one follow-up cadence. Example: "We re-prioritize every Monday at 10am, decisions go in the shared Google Doc named 'Decisions Log', and Friday at 4pm is when the PM asks the team how the week went."
Action: Complete the learner action above, then slide to continue.