Defragmenting Complex Products With User-Centric Frameworks
summary
Org-level audits and a consolidation of journey maps across 7,000 internal tools (2,000 people) and a 200-person product org reveal where work duplicates and flows break. The practical stack: mode = intent + context to map which products support the same user intents, literature review plus card‑sorting and workshops to validate contexts, weekly office hours to onboard teams, and building a foundation team plus user-intent page templates that reuse components. Result: clearer cross-product connections, focused feature scope and fewer reinvented wheels.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker background
- 1:59Fragmentation in large product teams
- 6:33Three causes of fragmented experiences
- 10:25Showing teams the big picture
- 16:25Identifying user connections with MODE
- 23:06Reusing designs with intent-based templates
- 25:59Summary and Q&A introduction
related talks
43mUser Experience and complexity
47mBlending Product Thinking with Architecture
18mOn Product, Empathy and Creating a User Centric Culture
54mThe value of Org Topologies in the era of DIY-frameworks
54mDomain-Driven Design and Team Topologies for Product-led Organizations
13mHolistic approach in product design
24mPanel Talk: Integrating UX for Improved Product Development
55mThe ripple effect: how information architecture transforms your product, company ...
