liveBook · Manning

Impact mapping

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

An impact map is a visual model linking business goals to actors, impacts, and potential deliverables.

Impact mapping structures stakeholder conversations around how potential deliverables connect to business goals. It makes the path from objectives to solutions visible without treating the solution as the starting point. section 4.3.2

Build the map from broad intent toward possible action:

  • Start with a business goal. section 4.3.2
  • Identify actors who may help achieve the goal. section 4.3.2
  • Describe impacts as metric improvements or behavior changes associated with each actor. section 4.3.2
  • Connect impacts to potential deliverables, then use gaps or vague deliverables to guide further discovery. section 4.3.2

Revenue-growth mapping

A stakeholder identified increasing revenue by $20 million in one business area as a top goal. The map focused on a user subset representing 45% of users, two possible revenue-related impacts, and a deliverable connected to both impacts. Because “using data better” remained vague, the map directed follow-up discovery toward concrete uses such as better recommendations. section 4.3.2

Modernization workshop

During modernization planning at a large Scandinavian enterprise, participants used impact mapping to connect business goals with initiatives and deliverables touching capabilities in a tightly coupled monolith. Those connections helped frame later work on domain exploration, a first modernization slice, architecture, and delivery. section 4.4.2

Figure 4.1 Impact Mapping syntax

Use the syntax diagram to inspect the visual relationships among goals, actors, impacts, and deliverables. section 4.3.2

Figure 4.2 Impact Mapping extract

Use the map extract to examine how a business goal, user group, impacts, and a shared deliverable expose a high-leverage opportunity. section 4.3.2

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines goals, actors, impacts, and deliverables, then stops short of specifying vague solutions without further discovery.
Examples
Uses a $20 million revenue goal, a 45% user subset, shared deliverables, and monolith-modernization workshop planning.
What it assumes
Assumes access to stakeholder priorities and business objectives while teaching the map’s structure from goals through deliverables.
What you can do after
Apply it to prioritize discovery, identify high-leverage opportunities, and relate modernization deliverables to business objectives.
How it connects
Connects business goals with actors, impacts, deliverables, metrics, behavior change, and modernization initiatives.

Also explained in

Compare how 3 books explain impact mapping →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.