Skip to content

Node Generation

Definition

A node is any artifact considered as a piece of a larger system — one idea, one sticky note. Node generation is the opening-stage discipline of producing as many nodes as possible before any sorting or evaluation happens, and doing it in a specific way: each person writes ideas silently, one idea per note, rather than calling ideas out loud into a shared list. The book's example is a grocery list: instead of a facilitator writing down ideas as people shout them out, each person writes their own items on separate sticky notes.

In the Book

Chapter 2 presents node generation as essential #4, directly following Artifacts (essential #3) as its natural next step: once you understand that an artifact is a unit of information, the first move in any inquiry is to generate as many of those units as possible, starting "from as wide an angle as possible." The book explains the mechanism behind the silent, one-note-per-idea method (called Post-Up, detailed further in Chapter 4) as solving two problems at once: silent generation produces a more diverse set of ideas than calling out loud, because people aren't anchored by what others just said; and one-idea-per-note produces modular, movable artifacts that can later be shuffled, sorted, and reorganized — setting up the Meaningful Space and affinity-mapping techniques described immediately after. The subsequent report-back step (each person reads their notes aloud and places them on a shared board) is identified as a specific instance of the book's broader break out/report back pattern.

Why It Matters

Node generation names why "everyone shouts ideas at a whiteboard" produces worse output than the same people writing silently on individual cards: calling ideas aloud anchors the group on whatever was just said and suppresses ideas that don't fit the emerging frame, while writing independently first and sharing after preserves the diversity that later sorting depends on. It's a general principle for any group ideation process — survey design, requirements gathering, root-cause brainstorming — that the order of operations (generate independently, then converge) matters as much as the technique used within each step.