Community Driven Design

Community Driven Design is a way of building tools, services, and institutions where the community is not “consulted” at the edges, but treated as a co-designer throughout the process, with real influence over priorities, trade-offs, and definitions of success.

For Hitchhikers, the point is not to optimise for a market segment or a national agenda or a technology roadmap. The point is to build things that are locally meaningful, maintainable, and trustworthy, because the people who will live with the system are the people who must shape it.

Community driven design starts by widening the circle of stakeholders, including the inconvenient ones: the quiet users, the sceptics, the maintainers, the frontline workers, the people harmed by past systems, and the people who will have to explain the tool to others. This is not bureaucracy, it is how you avoid building a beautifully engineered mistake.

Hitchhikers uses Backcasting as a practical method for this. Instead of arguing endlessly about today’s constraints, we invite diverse stakeholders to describe a shared future that would be worth living in, and then we work backwards to identify the steps, prototypes, governance choices, and near-term actions that could plausibly move us in that direction - wikipedia

Backcasting works especially well when stakeholders disagree, because it moves the conversation from “my solution versus yours” to “what would we recognise as a better future, and what would have to become true to get there.” It turns conflict into design material, and it makes hidden values visible as explicit design constraints.

The Cynefin Framework helps Hitchhikers choose the right design posture at each stage. In simple contexts we can apply established practice and standards. In complicated contexts we can rely on expertise and analysis. In complex contexts we must probe with safe-to-fail experiments, learn quickly, and let patterns emerge, because certainty is a trap and premature consensus can be harmful - wikipedia