HowMightWe

Beginning

The challenge

Movements with energy and conviction routinely stall for want of shared infrastructure. Conversation lives in one tool, decisions in another, commitments nowhere. Newcomers can't see where they'd add value; organisers burn out holding the thread in their heads. The result is fragmentation — high intent, low coordination — and momentum that leaks faster than it builds. The problem is structural: consumer software, AI included, is architected for one user at a time. The collective is treated as an edge case. For movements, the collective is the unit — so the infrastructure had to be designed for the in-between from the first line of the data model, not retrofitted as a sharing feature.

Phase 1

The approach

The work translates a systems-level conviction — orchestrate, don't control — into a product that feels editorial and human rather than another SaaS dashboard. Three moves shape the experience:

1. 1

   Role before task. A two-minute assessment surfaces each member’s role in a movement — Convenor, Storyteller, Builder or Facilitator — so contribution starts with clarity instead of overwhelm.

2. 2

   An operating loop, not a feed. Circles, proposals and commitments: small groups deliberate, decide and ship — with AI summarising and surfacing patterns, never replacing judgement.

3. 3

   Free text, canonical vocabulary. Members describe themselves in their own words; a normalisation and alias layer keeps the directory matching people on what they actually do, without fragmenting into a thousand near-duplicate skills.

Strategy, design and engineering were built as one artefact. The proposition, the language, the visual system — an editorial broadsheet aesthetic of Fraunces and Bricolage Grotesque, a flat wine accent, hairline rules — and the underlying data model were shaped together, by one pair of hands, so the product and its argument never drift apart.

Phase 2

The opportunity

As civic, climate and community work becomes more networked and cross-disciplinary, the infrastructure gap widens. HowMightWe sits in that gap — member-owned, open-source by intent and structurally incapable of being bought. It is positioned as connective tissue for movements that need to act at the speed the moment demands, without surrendering to platforms whose incentives point elsewhere.

End

The outcome

A defined venture with a working product in production and a distinct visual and narrative identity. The shipped surface area: onboarding and archetype reveal; a member directory with faceted matching; Circles with threaded feeds and the proposal-to-commitment flow; events with before/during/after lifecycles; notifications; a network-level Pulse; and an editorial case-study index. Strategic clarity, technical architecture and design system are aligned — one system, in production.