Deep-dive sub-tree
One node decomposed into its own tree.
Purpose
Zoom into one node of the full tree and give it its own tree: its causes, its parts, its sub-problems, or what solving it would take.
When to create it
- A node is a complex decision that needs its own analysis.
- A problem is big enough to deserve its own mapping session.
- A subgroup has taken ownership of an area and needs space to work without disturbing the full tree.
These usually come up during Decompose.
What it contains
- A header: "Deep Dive," followed by the name of the node being decomposed.
- The parent node, at the entry point of the sub-tree, drawn with a bold double border to mark that it comes from the full tree.
- The sub-tree around it: causes, components, or whatever the analysis needs.
A deep dive may use node types or arrow styles that the full tree does not. If it does, its own legend explains them.
Diagram as text: Deep dive on a problem from the onboarding tree
Nodes:
- Root / Problem: "Questions in public channels go unanswered"
- Root / Problem: "Past questions were met with impatience"
- Root / Problem: "No one is assigned to help"
- Root / Problem: "New hires are afraid to ask questions" (node from the full tree)
- Action / Intervention: "Hold a weekly open question hour"
- Desired State / Outcome: "Every question gets an answer within a day"
Arrows:
- "Questions in public channels go unanswered" influences "New hires are afraid to ask questions"
- "Past questions were met with impatience" influences "New hires are afraid to ask questions"
- "No one is assigned to help" influences "New hires are afraid to ask questions"
- "No one is assigned to help" influences "Hold a weekly open question hour"
- "New hires are afraid to ask questions" influences "Every question gets an answer within a day"
- "Hold a weekly open question hour" influences "Every question gets an answer within a day"
How it relates to the full tree
It supplements the parent node; it does not replace it. The node stays in the full tree, ideally with a link or comment pointing to the deep dive: "see Deep Dive: New hires are afraid to ask questions."
Example
In one observed tree, the action "Assign a tech lead with a proven track record" became a deep dive that mapped the role's required characteristics, the strengths and weaknesses of candidates, and the role's key responsibilities. The group used it to make a hiring decision.
When you don't need it
Most nodes never need one. Deep-dive only the few nodes where understanding is weakest and the stakes are highest. Decomposing every node turns the technique into an endless recursion.