A diagnostic tool for organizational redesign during M&A integration. Most org design frameworks are prescriptive: they start with what should be and work backward. This one starts with what is. You map decisions as they actually flow today, and the gaps between reality and intent reveal exactly where the structure is broken.

The insight behind this tool comes from Henry Mintzberg: structure doesn't follow strategy. Structure follows power. Your org chart is a photograph of who won the last political fight. A redesign that doesn't surface the actual power dynamics will produce a new chart that looks different and works the same.

To use this canvas: Duplicate this page to your workspace (top right > Duplicate). Fill one row per critical decision. Work left to right. The map will surface problems that no org chart can show.


How to run a decision mapping session

Who should be in the room

6-10 people. You need enough perspectives to expose the real decision paths, but few enough for honest conversation. Include:

Time required

Half day (4 hours). Not a lunch meeting. Not a 90-minute workshop squeezed between other sessions. Decision mapping requires the room to get uncomfortable, and discomfort takes time to surface. Most teams spend the first 90 minutes being diplomatic. The real insights come in hours 3 and 4.

Agenda:

Time Activity
0:00 - 0:30 Frame the exercise. Explain the five columns. Set the ground rule: we're mapping reality, not the org chart.
0:30 - 1:30 Identify 20-30 critical decisions across all five domains. Write each on a separate row. Don't filter yet.
1:30 - 1:45 Break
1:45 - 3:15 Fill columns left to right for each decision. This is where the friction happens. When two people disagree on "who decides today," you've found a structural insight. Don't resolve it. Document both answers.
3:15 - 4:00 Pattern recognition. Group decisions by blocker type. Identify the 3-5 structural fixes that would unlock the most value.

Ground rules

  1. No org charts in the room. The formal structure is irrelevant to this exercise. You're mapping how decisions actually flow, not how they're supposed to flow.
  2. Name names. "The commercial team" is useless. "Sarah Chen" is useful. The map only works with specificity.
  3. Disagreement is data. When the COO says pricing decisions take two days and the VP of Sales says they take three weeks, both are right. They're describing different decision paths, and the gap between them is exactly what the map is designed to reveal.