Diverge & Converge

Guide
Login

The Rhythm of Sensemaking

Sensemaking isn't a linear path; it's a pulse. You must expand your view to see possibilities (Diverge), then narrow your focus to make decisions (Converge). Mastering this rhythm is key to effective mapping.

Divergence (Taxonomy)

The act of exploring, listing, and categorizing. It creates vocabulary but lacks direction. It asks: "What exists?"

Convergence (Mapping)

The act of scoping, positioning, and deciding. It creates strategy and direction. It asks: "Where are we going?"

1. The Trap of Infinite Lists

A common pitfall is getting stuck in Taxonomy Mode. You list everything related to a topic—"Learning," "Cloud," "Operations"—and organize them into neat buckets.

The Problem: Taxonomies have no stopping point. You can always add more categories. They describe the world but don't help you act on it.

However, you cannot map what you cannot name. You need the raw material of concepts (the "Domain Specific Language") before you can position them. This is where the Diverge/Converge cycle comes in.

2. The Workflow

1

Diverge: Brainstorming

Start messy. List every concept, component, or feeling related to the domain. Don't filter yet. Create your 'clay'.

2

Scope: The Research Question

Apply a filter. Ask: 'Who is the anchor?' and 'What decision are we making?'. Discard concepts that don't help answer this specific question.

3

Converge: Mapping

Position the remaining components. Define relationships (dependencies) and movement (evolution). This is where meaning emerges from the mess.

4

Iterate: Gap Analysis

Look at the map. What's missing? 'I have a user need but no component meeting it.' Go back to step 1 to find the missing piece.

3. Mapping for Learning vs. Deciding

You can use this process for two distinct goals. The workflow is the same, but the Research Question changes.

Sensemaking (Learning)

  • Goal: Understand structure & relationships.
  • Question: "How does this domain work?"
  • Example: "How do engineers acquire expertise?"

Strategy (Deciding)

  • Goal: Make a choice.
  • Question: "Should we do X or Y?"
  • Example: "Should I learn Rust or Go?"
Key Insight: Even for learning, you need a perspective. You can't just "map learning." You must map "learning for a junior dev" or "learning for a system builder."

4. From Taxonomy to DSL

Your brainstorming phase creates a Domain Specific Language (DSL). These are the nouns and verbs you will use on your map.

  • Taxonomy says: "There are 3 types of databases."
  • Map says: "For this problem, SQL is a commodity (buy it) and Graph is custom (build it)."
OUTPUT COMPARISON
Brainstorm
- Content
- Videos
- Practice
- Mentorship
- Feedback
Map
1. User Needs Skill
2. Needs Practice (Custom)
3. Needs Content (Commodity)