Understanding the Impact Map: Why, Who, How, What

The author revisits a video on impact maps and notes from an agile course, reflecting on how developers often focus on how to implement features without considering why, leading to misaligned business and technical goals.

Through a dialogue between a tester and a developer, the article illustrates the common disconnect where developers prioritize technical work over understanding business intent, a situation likened to the historical quality issues in the U.S. automotive industry despite precise measurement and control.

The piece introduces the impact map framework, organized around four keywords—Why, Who, How, What—explaining each component: the underlying business purpose (Why), the stakeholders responsible for actions (Who), the behavioral changes needed (How), and the deliverables that enable those changes (What).

It emphasizes that optimizing individual stages does not guarantee overall optimal outcomes and that effective collaboration among business, development, and other roles (e.g., Scrum Master) is essential. The impact map visualizes relationships between goals and functions, offering a shared panoramic view and shortest‑path pathways to guide decision‑making.

The article cautions against executing every listed "What" item, as each is based on assumptions that should be validated iteratively; after each validation cycle, assumptions must be reassessed and the map updated.

Finally, the article includes promotional information for the IDCF training camp, encouraging readers to purchase the course via QR code and participate in a referral cashback program.