CR-059 · Theme 6 · Meeting & Participation Redesign

Project Team Huddles

Help the club move detailed project coordination into short team huddles and keep whole-club time for shared matters.

What could this idea change?

The work is designed to produce a de-identified themes record and response register showing how participant input affected the decision; the central local boundary is that the trial must protect valid formal decisions, accessible participation and members who contribute outside meetings.

A simple way to start

  1. Write the decision brief for Project Team Huddles: define which meeting purposes and participation options should be separated, retained or redesigned, the starting evidence, people affected, local authority, resource limit, success signals and stop conditions. Who could lead it: Club board sponsor and renewal lead
  2. Invite members with varied experiences and affected community partners where appropriate, show what is open or fixed, make access practical and record trade-offs and minority views. Apply this specifically to Project Team Huddles and record which relevant experiences or users are still missing. Who could lead it: Club board sponsor and renewal lead with the access and privacy contacts
  3. Build and test a facilitated conversation with a published influence boundary and balanced participation for Project Team Huddles; complete the Project Team Huddles Facilitation and Influence Run Sheet, rehearse the boundary wording and confirm who may decide, refer, pause, recover or close the work. Who could lead it: Facilitator and workstream owner
  4. Use a time-bounded change with named authority, capacity and stop conditions; compare evidence with the starting point and make unfinished work, unintended effects and resource pressure visible. Capture only the evidence needed to judge whether Project Team Huddles advances more useful and inclusive participation. Who could lead it: Facilitator and workstream owner
  5. Compare the evidence with the starting point, validate meaning with affected participants or users, record gaps and unintended effects and prepare a de-identified themes record and response register showing how participant input affected the decision without overstating what the trial proves. Who could lead it: Facilitator and workstream owner with an independent reviewer

What should we look for?

  • Review Project Team Huddles after 90 days. Look for whether participants find meetings or alternative touchpoints worth their time and agreed actions move sooner, and write down one decision the evidence supports.
  • Project Team Huddles produces a de-identified themes record and response register showing how participant input affected the decision by the promised decision date, with evidence limitations, participation gaps and unintended effects stated.
  • People affected can explain the purpose, their choices, the boundary and how to raise an access, privacy, safety or governance concern.
  • The trial shows whether more useful and inclusive participation improved from the recorded starting point without shifting hidden workload, risk or exclusion elsewhere.
  • Every accepted action has an owner, due date and completion evidence, and the club records a reasoned continue, adapt, refer, scale or stop decision.

Before we say yes

  • Does it fit a real local need?
  • Can people take part safely and fairly?
  • Are the facts, permissions and Rotary branding right?
  • Who will lead it, and when will we review it?