Hybrid in practice: the campaign rhythm

A campaign rhythm is what most community PMs actually run: agile cycles between waterfall anchors. The rhythm is the artifact.

In practice, most community project plans look like this: there is a calendar of fixed dates (the action, the launch, the report). Between those dates, the team works in roughly two-week cycles. Each cycle starts with a 30-minute planning meeting, ends with a 30-minute "what did we learn" meeting, and produces one small thing that moves toward the next fixed date.

The cadence is what matters. Not the framework, not the certification, not the tool. A team that meets twice a month with a clear purpose for each meeting can run a great project on a Google Doc. A team that does not have a cadence will fail on Asana, on Notion, on Monday — on anything. Tools amplify rhythm; they do not create it.

For community PMs new to this: start with one cycle. Pick a two-week window. Hold one planning meeting and one retro. End with one thing shipped. After three cycles you have a rhythm; after six you have a team that runs itself.

The campaign rhythm also matters for sustainability. Volunteer-heavy teams burn out when the cadence is invisible. People can carry a known weekly ask much longer than they can carry an unknowable one. Even when the ask is hard, the predictability is rest.