How to embed the IA as part of normal product development? A PO's perspective
summary
Argues that information architecture becomes normal when framed in product terms and tied to metrics and workplans using concrete steps: run customer interviews to map users' words, turn findings into prototypes, involve the product owner in sessions, and run side‑by‑side experiments. Uses a concrete target — lift a 2% bundling rate to 5% — to justify effort, reports outcomes regularly, and recommends a dedicated owner in design or content to champion IA so it actually gets scheduled and funded.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:02Why IA matters in product development
- 2:49Barriers to adopting IA
- 5:56Working with product managers
- 8:06Communicating IA value clearly
- 10:14Framing IA in business terms
- 12:42Who owns information architecture
- 13:46Normalizing IA in organizations
related talks
37mInformation Architecture: build it better
46mUX Mastery via Information Architecture
27mMore than words: Reviewing and updating your information architecture
19mWorkshops to Help Your Team Do Good
18mCollaboration in product design
36mMore than words: Reviewing and updating your information architecture
24mPanel Talk: Integrating UX for Improved Product Development
40mUser Experience for Product Managers