CDD is the shorthand for both Community Driven Design and Community Driven Development. Our aim is to combine the best feaures of both into one continuous practice. It treats design and development as a single community loop: discover what matters, build what helps, learn from reality, and iterate in public with the people who will live with the result.
CDD exists to prevent the classic split where “design” becomes a workshop theatre and “development” becomes a technical priesthood. Instead, it keeps purpose, usability, maintainability, and governance connected, so we do not ship a beautifully built thing that the community cannot trust, run, or adapt.
The design half of CDD is about meaning. It engages diverse stakeholders early, uses methods like backcasting to describe a future worth building, and turns values into concrete constraints that shape prototypes, priorities, and success measures.
The development half of CDD is about capability. It ensures the community can actually build and sustain what it designs, by investing in documentation, testing, modular architecture, onboarding, and local maintainers, so that the system remains forkable and resilient rather than dependent on a few heroic experts.
CDD assumes most community problems live in the complex domain, so it favours safe-to-fail experiments and short feedback cycles over grand plans. That posture aligns naturally with the Cynefin Framework, which helps us decide when to use best practice, expert analysis, or exploratory probes, and when to stop pretending certainty is available - wikipedia 
In Hitchhikers, CDD is also a governance stance. It makes decision-making legible, distributes ownership, and treats maintenance as part of the work, not an afterthought. The goal is not just to “ship software,” but to grow local agency and shared infrastructure over time.
CDD becomes especially powerful when paired with Agentic Development and Local First tooling. Agents can accelerate implementation and documentation, but the community remains responsible for meaning, trade-offs, and stewardship, so we get speed without surrendering agency.
The CDD promise is simple: build with people, not for people, and build in a way that leaves behind capability, not dependency. When it works, the community does not just receive an outcome - it gains the power to keep designing and developing its own future.