Before You Reorg, Map the Work

The problem to solve

Most reorganizations begin with a visible symptom: too many meetings, missed handoffs, slow decisions, or a leader who has become a bottleneck. An org chart may need to change, but it cannot tell you where work actually stalls.

Moving reporting lines before understanding the work simply relocates the ambiguity. It may also create disruption around a problem that could have been solved with clearer interfaces or authority.

The Work & Theory principle

Start with the work. Design follows the work that must move reliably across the organization, not the preferences of individual leaders or the names of existing departments.

Diagnostic questions

Map one recurring workflow with the people closest to it. Treat the map as evidence, not a referendum on the current structure.

• What triggers this work and what outcome ends it?
• Where does it cross a functional or leadership boundary?
• Which decisions delay the flow, and who can make them?
• What information arrives too late, incomplete, or in conflicting forms?
• Where are people compensating through heroics or informal relationships?

Practical next actions

Run a short work-mapping session on a high-value workflow. Use plain language: stages, owners, decisions, inputs, outputs, and constraints. Then identify one interface that needs a clearer agreement before proposing a structural move.

• Map the current flow, not the intended process.
• Circle the two longest waits or most frequent rework loops.
• Test one interface change for 30 days.
• Only then decide whether a structural change is necessary.

Related artifact and pathway

The resulting map is a foundation for the Organization Blueprint. The Blueprint makes functions, roles, decision rights, workflow, and critical interfaces visible enough to design deliberately.