User Experience and complexity
summary
Software complexity always drifts up as features, quick fixes, customer bolt‑ons and tech experiments accumulate; the concrete fixes are to tighten product vision, shrink scope, write assumptions and validate them, and prioritize problem understanding (teams spend ~40% of time on this at Intercom). Use journey maps, user story maps, opportunity/problem statements, pattern libraries and progressive disclosure to group and hide complexity, run design studios to generate focused solutions, and treat discipline and refactoring as non‑optional maintenance.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:55Story
- 4:40Why complexity is bad
- 9:35What contributes to complexity
- 17:07Product vision
- 17:42Questions
- 21:18Tactical vs Strategic
- 24:13Problem prioritization
- 26:16Functionality prioritization
- 30:21Progressive disclosure
- 31:31Consistency and context
- 34:11Why is 37signals so arrogant
- 34:55Summary
- 35:26Tools
- 35:40Journey Maps
- 37:10Story Maps
- 38:19Problem Statements
- 39:19Patent Libraries
- 40:18Design Studios
- 41:35Jobs to be done framework
related talks
42mSimplicity is not simple
36mTog's Paradox: Why Requirements Always Spiral Out of Control
52mDefragmenting Complex Products With User-Centric Frameworks
49mCo-creating with UX and Software
43mDesigning the Right Product
24mPanel Talk: Integrating UX for Improved Product Development
28mDesigning for Success: UX Principles for Internal Developer Platforms
36mUX designers /developers collaboration anti patterns