Co-creation between UX and Software
summary
Argues that embedding design into development prevents gaps by sharing responsibility for the final product, recommends concrete rituals and artifacts: plan-phase check-ins, yearly user visits, event storming sessions using sticky notes, journey and opportunity maps, and technical outputs like sequence diagrams and entity diagrams shown to designers. Recommends a single point of contact between design and feature teams, creating technical designs before coding, aiming for seven delighters per pain point, using A/B or beta releases, and adding monitoring-driven tickets for next cycles.
AI-written summary · about
chapters (8)
- 0:00Introduction to co-creation
- 1:58The importance of the why
- 5:55Team structure and alignment
- 11:24Operational team models
- 16:06Addressing collaboration friction
- 22:59Tools for technical design
- 32:07Implementing technical blueprints
- 37:38Release and continuous learning
related talks
49mCo-creating with UX and Software
32mPairing with designers to create a seamless user experience
18mCollaboration in product design
40mHow to make UX & Devs build killer products
51mUX + Engineering: A Tale of Two Cities
30mBuilding Better Products Faster
43mDesign Beyond Deliverables
29mEffective design and engineering collaboration