Co-creating with UX and Software
summary
Argues that embedding UX into development saves rework and surfaces hidden failure modes, showing concrete practices: use event storming, journey maps and sequence diagrams to reveal error flows and dependencies; map front‑ and back‑end actions in a blueprint before tickets; run fast prototypes (developer built a demo in 1–2 hours vs designer’s two days) and A/B tests to validate. Recommends team structures (operation/process/feature/project), one designer per feature team, shared ownership of the end product, and monitoring tied to user goals.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 7:11Common concerns about collaboration
- 8:35Building effective teams
- 11:47Team purpose and vision
- 13:11Team structures for co-creation
- 17:50Design and DevOps cycles
- 24:56Tools for design and development
- 34:59Building and testing features
- 42:19Monitoring and improvement
- 45:57Key takeaways and conclusion
related talks
41mCo-creation between UX and Software
32mPairing with designers to create a seamless user experience
51mUX + Engineering: A Tale of Two Cities
40mHow to make UX & Devs build killer products
36m"UX for Developers, Seriously!"
48mGet your screen together: Design skills for frontend people
36mUX designers /developers collaboration anti patterns
41mDesignOps - How I Built UX Teams from Scratch in a Company