Case Study — 02

CommonShips

Volunteer Coordination Tool for Community-Focused Organizations

Skills
Research, Product Strategy, UX/UI Design, Full-Stack Development
Image placeholder — product screenshot of CommonShips
01

Overview

CommonShips is a volunteer coordination platform for community-focused organizations.

It’s intended to make it clear and easy to contribute to a community, and to be the system coordinators can rely on — replacing manual spreadsheets, email threads, and text chains with automated coordination.

02

Problem Statement

Both organizations are seeing growth in community interest, but not in the number of active volunteers. As a result, a small subset of volunteers absorbs a disproportionate share of the workload, and coordinators absorb whatever is left. It’s a pattern that leads to coordinator burnout.

A review of both organizations’ sign-up records, combined with first-hand experience as a volunteer, surfaced a consistent pattern:

  • Recurring events are largely self-sustaining. Volunteers typically commit to the same recurring slot and coordinate coverage informally with other regulars when unavailable.
  • New and one-off events go unstaffed. These events have no established volunteer base, and visibility is limited to whoever happens to locate the relevant sign-up sheet.
Chart placeholder — roles-per-person-chart.png
Average roles per active volunteer, Jan 2025 – Nov 2026

SF Dharma Collective sign-up records, Jan 2025 – Nov 2026. Figures are approximate.

The problem was never lack of volunteer interest, it was coordinator capacity: onboarding and training new volunteers, identifying who to contact, and, most critically, sourcing a last-minute replacement role themselves when no one else was available.

03

Objectives

  • Reduce the barrier to signing up for any volunteer—new, occasional, or recurring—to broaden participation beyond the current core group.
  • Provide a system coordinators can rely on to surface coverage automatically when a volunteer cancels, without requiring manual follow-up.
04

Design Principles

  • Sign-up is simple and unambiguous
  • Withdrawing a commitment carries no guilt cost
  • Coverage can be picked up easily by someone else
  • Coordinators can trust the system to manage the process
05

Key Decisions

Screenshot placeholder — invite & join flow

1. Private, Invitation-Based Workspaces

Each organization gets a private, invite-only workspace. Coordinators import existing contact lists; volunteers join with a single click.

Screenshot placeholder — one-tap sign-up

2. Single-Tap Sign-Up with Minimal Onboarding

Onboarding requires only two data points: role preference and general availability.

Screenshot placeholder — notification preferences & opt-out

3. Notification Discipline by Design

One reminder per commitment. Each volunteer is asked about a given shift once. Every ask includes a one-click opt-out.

06

Scope & Constraints

To validate the core workflow quickly, the initial release is scoped to what SF Dharma Collective alone needs to replace its spreadsheet for one month. Everything else was designed, then deliberately held back:

  • Notification preferences and a paused status for inactive volunteers
  • Announcements and reach outs
  • SMS notifications
  • Role-specific training and approval workflows
  • A second organization.Hold off Berkeley Alembic’s onboarding, proving the workflow for one community first keeps the initial release small enough to ship and learn quickly.
07

Success Metrics

KPIBaseline (Fall 2026)Target
Unique volunteers signing up per month~16Increase
New/special events with an unfilled shift13 events (Sep–Nov)Decrease
Share of shifts held by the coordinators~33%Decrease
Cancellations resolved without coordinator interventionNot currently trackedMajority
08

Reflection

  • ✓Coordinator capacity, not volunteer interest, was the binding constraint. Designing around the coordinator’s available time and to lessen their manual work, rather than optimizing for sign-up volume, informed every subsequent decision.
  • ✓Existing informal behavior is a stronger design input than a blank-slate solution. The most effective backfill mechanism already existed as an ad hoc group text between regulars; CommonShips formalizes and extends that pattern rather than replacing it.
  • ✓Scoping down is a design decision, not a compromise. Deferring the majority of the originally designed feature set was necessary to get a working system into a real organization’s hands.