Unfolding the Napkin Summary: Practice Visual Problem Solving

Key Ideas

1. Look at the material before deciding what the picture should prove

Looking is the starting point in Roam’s four-part process. Our application treats that as a reason to gather the material before choosing the conclusion. A drawing can reveal an assumption, but it can also give an assumption the appearance of structure. The difference depends partly on what the people drawing it have actually examined.

The fictional returns team starts with three separate accounts of a parcel arriving. Support describes a customer message, receiving describes a label and the supervisor describes a queue. Instead of immediately joining those accounts with arrows, the facilitator asks what each person has observed. An arrow based on an assumption receives a question mark. Two incompatible descriptions remain visible rather than being averaged into a comfortable story.

Apply this by bringing a few relevant examples to the conversation, using material you are entitled to share. Record the source of each observation and the meaning of important labels. When a participant says something always happens, ask which part of the process they have seen. Avoid turning the exercise into a test of who sounds most certain.

This matters because a process picture can travel far beyond the meeting that created it. Another team may use it as an explanation of current work. Marking what is known, inferred and unresolved protects that reader from mistaking a planning artifact for a verified account. The picture becomes a starting point for inquiry rather than an attractive way of ending it early.

2. Choose the representation for the question someone needs to answer

In the authorized excerpt, Roam contrasts directions that emphasize sequence, spatial context or a destination. Our application carries that distinction into a work conversation. Before choosing a diagram style, identify the question it should help another person answer. A picture can be clear on its own terms and still be the wrong tool for the immediate task.

If the returns team asks who owns an inspection decision, a drawing of the warehouse floor may not resolve the issue. A set of named roles and their handoffs could be more useful. If the question concerns where parcels wait, a spatial sketch may matter. If it concerns what happens before an item enters a queue, an ordered sequence may be the better starting point.

Write a question above the draft. Ask a colleague to point to the part that answers it. If they cannot, revise the representation or narrow the question. When several questions are tangled together, use related pictures with consistent labels rather than forcing every relationship into one crowded diagram. Keep enough context to explain how the views connect.

This matters because familiarity can masquerade as usefulness. A team might reach for its usual flowchart even when the dispute concerns ownership or purpose. Choosing the visual form deliberately helps people notice what the form leaves out. It also makes critique more specific: the group can discuss whether the picture answers the question, instead of arguing about whether diagrams are generally helpful.

3. Imagine alternatives before polishing the preferred version

Imagining is another named part of Roam’s process. Here, it becomes an invitation to produce more than one possible account of a proposed change. The alternatives are working hypotheses, not separate recommendations that the group must implement. Their purpose is to make choices visible before visual polish makes one option feel inevitable.

The returns team considers two ways of clarifying its handoff. One sketch adds a shared reference at arrival. Another gives responsibility for resolving an unclear reference to a named role before inspection is scheduled. Both drawings use the same current-state labels, allowing participants to see what each changes. Neither is called a solution until the team has examined its assumptions and the people responsible have considered it.

For your own exercise, ask participants to vary one meaningful feature at a time. Keep the problem statement visible. Beside each alternative, record the new work it creates, the uncertainty it leaves and the person who would need to assess it. Do not compare a fully developed favorite with a deliberately weak competing sketch.

This matters because pictures can make an idea easy to imagine without making it feasible. Comparing alternatives interrupts that slide from clarity to approval. A participant may accept the diagnosis while preferring a different response. The visual conversation should let that distinction survive. Preserve useful rejected sketches with their reasons so the team does not have to rediscover the same tradeoff at the next meeting.

4. Show the drawing to someone who can correct its meaning

Showing completes the named visual thinking sequence. Our application treats it as an exchange in which another person can change the representation. An explanation is incomplete if the speaker alone can interpret it. Sharing the drawing with the people it describes is a practical way to test whether the labels and relationships carry the intended meaning.

The returns supervisor presents a draft in which an arrow runs from receiving to inspection. A receiving colleague points out that the arrow hides two different situations: a parcel with a usable reference and one whose identity remains uncertain. The correction changes the discussion. The team now has a specific distinction to examine instead of a general complaint that parcels move too slowly.

Ask a participant to narrate the drawing without help. Where they pause, ask which label or connection is unclear. When they disagree, record the reason before changing the picture. A difference in interpretation may reveal missing context; it may also expose a real difference in practice that a single shared drawing should not conceal.

This matters because agreement with a facilitator can be easier than disagreement with a visible diagram. Make revision an expected part of the exercise, especially for people whose work the picture summarizes. A correction is useful information. The outcome should be a representation people can question and explain, not a meeting in which the person holding the pen quietly acquires authority over everyone else’s account.

5. Build the skill through repeated drawing and explanation

The workbook’s exercise-based format makes practice a central distinction from a purely descriptive introduction. In this guide’s application, progress means becoming better at noticing what a drawing clarifies and what it obscures. Producing a memorable diagram once is less useful than being able to revise a rough one when a colleague asks a difficult question.

After the fictional returns workshop, the team uses the draft to explain the handoff to an absent colleague. That colleague asks where an unresolved reference is recorded. The team realizes that its conversation had answered who should respond but not how the next person would see the response. The missing connection becomes the subject of a later discussion. It is not patched with an invented arrow merely to finish the page.

Practice on a bounded, familiar issue first. Draw a current situation, explain it briefly and invite one person to identify an ambiguity. Revise the drawing and explain what changed. Keep successive versions long enough to compare them. This lets you see whether detail was removed because it was irrelevant or because it was inconvenient to the preferred story.

This matters because drawing skill and subject understanding develop together during the exercise. A clearer picture may reveal a harder problem, which is useful even when it feels like slower progress. Treat the workbook as a place to rehearse that process. Its value lies in more accurate and useful conversations, not in making every notebook page look ready for publication.