Set deadlines at the start of a project for each phase. Work backwards from the event date. Surprise deadlines are usually a sign nobody worked backwards.
Working backwards from the event date is the single most useful PM habit a community organizer can build. Start at the end: the action, the gala, the briefing, the launch. Put it on the calendar. Now ask: what has to be true the day before? The week before? Two weeks before? Each answer is a deadline.
Common phases for community work: Recruitment Period, Surveying Period, The Event, A Debrief, Follow Up. Each phase has its own internal deadlines — recruitment has a "list finalized" deadline before it has a "first ask sent" deadline; the event has a "venue confirmed" deadline well before "day of".
A workable timeline lives in a single shared place. A spreadsheet, a Google Calendar, an Asana board — pick one, and only one. Two timelines means the team will look at the wrong one. If different stakeholders need different views, generate them from the same source.
Build a buffer week into every phase. Things take longer than you think. The PM's job is not to bend reality to the original timeline; it is to surface slippage early so the team can decide what to drop or push. A timeline with no buffer is not a plan; it is a hope.
Learner action
On paper, put your project's end date on the right. Working leftward, write each phase and the deadlines inside it. Add a one-week buffer to each phase. Now transfer it to a single shared calendar.
Action: Complete the learner action above, then slide to continue.