Why? + Impact Mapping
summary
The talk explains how the team used Impact Mapping to avoid unclear, risky requirements when a project had tight business deadlines. It describes asking basic questions (why/for whom/how) to align requirements with business impact and shows how that approach saved time, reduced rework and stress during delivery.
AI-written summary · about
related talks
41mConnect Business Goals and Your Daily Work with Impact Mapping
41mMapping Experiences: From Insight To Action
31mFrom funding to delivery: ensuring alignment from start to finish
32mAligning Organizational Stakeholders with User Story Mapping
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
22mSustainability: A designer's approach
42mVisualize Test Scenarios Using Mind Maps
39mHow do we make architecture more user centered?