Here we explore options and next steps for the Book Wyrm Project. Either option addresses the “design should not lead” concern, because both treat design as listening-first, while still letting design lead through synthesis and proposals.
# Option A Option A is to run design workshops that produce shared artefacts: stakeholder stories, interaction sketches, role-switching journeys, and prototype concepts that can be validated quickly.
# Option B Option B is to adopt Domain Driven Design as a bridge: it preserves architectural seriousness while forcing careful thought about domain language, roles, boundaries, and the shape of interactions.