The ripple effect: how information architecture transforms your product, company ...
summary
A neo‑bank mobile app grows chaotic after rapid feature and compliance changes; a disciplined content and feature audit with annotated screenshots, navigation analysis and semi‑structured stakeholder interviews maps cross‑dependencies. The team centralizes navigation, builds a design system, consolidates editing into explicit flows, removes risky footer actions, separates destructive buttons and increases padding to avoid accidental deletes. The result is less cross‑team confusion, faster onboarding, clearer compliance paths and a foundation that supports regional expansion.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 6:09Defining information architecture
- 8:19Poor IA challenges
- 11:31Neobank IA case study
- 16:39IA impact on teams and users
- 26:38Balancing complexity with clarity
- 29:53Mid-talk break
- 30:37Actions to improve IA
- 41:16Testing and refining IA
- 46:14Aligning IA with roadmap
- 49:23Maintaining IA as a system
- 50:28Expected IA improvements
- 53:02Summary and call to action
related talks
24mYou're Doing UX Unconsciously, Now Let's Make it Conscious and Intentional
52mDefragmenting Complex Products With User-Centric Frameworks
25mJurassic UX: Design Best Practices for Legacy Software
32mThe Road to Excellence
28mTools of Destruction
50mDesign roadmaps for success
43mUser Experience and complexity
15mUX research in a huge agile project