Build: The Commitment Ledger

Build the fifth question — what commitments do we make to each other? — into a tool a small team actually keeps open.

The core object is a commitment: who committed, to what specific action, by when, asked by whom, and its current state (asked / committed / done / renegotiated). Around that core, encode the handbook's retention discipline: a follow-up queue that flags any new commitment not confirmed within 48 hours; event planning that assumes half of yeses will no-show (need four? the tool tells you to schedule eight); and a 'nobody leaves without a next date' check on every gathering's attendee list.

Make the mutual-accountability visible: the ledger shows commitments in both directions — including the ones leaders made to members ('find childcare for Thursday', 'get the flyers printed'). A team where only volunteers have rows is doing hierarchy, not organizing.

Dashboard: commitments kept rate over time (celebrate it at debriefs), and a gentle escalation view — who's followed through repeatedly and might be ready for an escalation 1:1 and a bigger role.

Constraint: renegotiated is a first-class state, not a failure. The three nos — not now, not that, not ever — all deserve a graceful path.

Details

• builds on: the-hard-ask, launch-a-team, snowflake-model
• guardrails: commitments run both directions — leaders' rows too, renegotiation is a state, not a shame, no-show math is planned, not punished
• practice kind: prompt