Debugging social systems with patience, people, and care.
Because every broken system was built by humans — and can be repaired by them too.
Every system has a story.
How we look at systems that need care
We start by listening. Every community has its own diagnostic language — its own way of naming what's broken. Our first step is learning to hear it.
Step 1: Listen before you lookThe best patches come from the people closest to the problem. We build bridges between expertise and experience.
Not replacing, not disrupting — repairing. We stitch broken connections back together with care and intention.
“We don't fix communities. We sit with them until the fix becomes obvious to everyone in the room.”
— A SocialDebug facilitator
Every repair becomes a seed. We document what works, share what we learn, and let communities build on each other's breakthroughs. Growth is not scale — it's depth.
The seed splits openBugs are just unasked questions.
A debugging session for social systems
Map the system. Find where the signals cross, where information gets lost, where people fall through cracks.
Follow the thread back. Every social bug has a history — a policy changed, a resource removed, a voice excluded.
Design interventions with the people affected. Not top-down fixes, but collaborative solutions stitched together from lived experience, local knowledge, and shared commitment.
The best patches are co-authored“The most elegant fix we ever deployed was a weekly dinner. That's it. A room, some food, and an hour of unstructured time where neighbors could actually talk.”
— Community debug log, 2025
Run the patch. Measure what changes. Listen for new bugs. Social debugging is never a single deployment — it's a practice of ongoing attention.
The patch is people.
What happens when you debug with care
Between institutions and neighborhoods. Between policy language and kitchen-table conversation. We build the connective tissue.
Every process is documented and shared. Our debug logs are public — so other communities can learn from what we tried, what worked, and what didn't.
“They didn't come in with a plan. They came in with questions. And somehow that made all the difference.”
— Neighborhood council member, Eastside project
SocialDebug is an open community of listeners, stitchers, and patient debuggers. If you believe that broken systems can be repaired — not replaced, not disrupted, but carefully, lovingly repaired — there's a seat at the table.
Start a debug session →Pull up a chair. The conversation is already underway.