Playbooks for Common Builder Needs

Start a Neighborhood Communication Channel

1. Identify 5 anchor neighbors already informally connected
2. Have 1-on-1 conversations first — don't just add people to a group
3. Choose the simplest tool (WhatsApp, group text)
4. Set the tone with the first message — introduce yourself, name a

specific purpose

1. Seed early activity in the first 48 hours
2. Invite gradually — 2-3 people per week
3. Establish norms by modeling the behavior you want to see

Pitfalls: Starting too big, not setting norms, builder doing all the posting.

Host a First Gathering

1. Low-barrier format — coffee on the sidewalk, potluck, porch hangout
2. Choose a time that works for your street's rhythm
3. Invite personally — door knocks, hand-written notes, texts
4. Have a simple prompt ("What do you love about living here?")
5. Show up 15 minutes early
6. Capture contact info
7. Follow up within 48 hours
8. Name the next gathering before people leave

Pitfalls: Too formal, no follow-up, waiting for perfect conditions.

Launch a Neighborhood Calendar

1. Audit what exists (bulletin boards, Facebook groups, word of mouth)
2. Start a shared Google Calendar
3. Seed with 10-15 events (recurring + one-time)
4. Recruit 2-3 co-curators (café owners, librarians, PTA parents)
5. Share widely through existing channels
6. Consider automation for scraping event sources
7. Keep it alive — update weekly

Scaling: Calendar → Weekly digest → Custom alerts (Sunset Signals model).

Build a Mutual Aid Pod

1. Start with existing trust — don't organize strangers into a pod
2. Keep it small (5-15 households)
3. Define what kinds of help you'll share
4. Dedicated communication channel
5. Weekly check-in rhythm
6. Rotate coordination monthly
7. Practice before crisis with small exchanges

Pitfalls: One-directional giving, no practice, too formal.

Map Neighborhood Assets

1. Physically walk every block
2. Talk to 10 people ("Who should everyone know?" "Where do people gather?")
3. Map people, places, and organizations
4. Look for connection gaps between existing assets
5. Share what you find — even rough lists create immediate value

The Builder Loop (Meta-Pattern)

Listen → Connect → Build → Reflect → Adapt → Share → Repeat This is not a project with an end date; it's a practice.