Hari was deep in the research for Chasing the Scream. He had built the argument that the war on drugs was a catastrophe. He knew Portugal had decriminalized all drugs. He needed to go to Portugal to see what happened next. He kept not going. He kept putting it off. He was, in his own words, blocked around it. I was — this is weird. Why? Why am I doing this?1
When he finally looked at the block, the answer arrived. I was afraid. What if I go to Portugal and that didn't work either? This will be the most depressing book in the world because I'll be saying, well, nothing works then, right? The block wasn't laziness. It wasn't time-management. It was fear of finding the wrong answer. The wrong answer would have collapsed the book into nihilism. He was protecting the book from the discovery he might make.
He went. Portugal turned out to be a success — the decriminalization had worked. The book wasn't collapsed. But the block had been correct as a signal. It was the wisdom of his unconscious telling him something important is at stake here, look at what's at stake before you proceed. The block contained the diagnosis.
His general claim, after this experience: We demonize writer's block. As if you've caught malaria or something. If you are blocked, there is a reason why you are blocked.1
Hari is making a structural claim about writer's block that runs against the dominant frame. The dominant frame treats block as a malfunction — something to push through, work around, fix with discipline. Hari treats block as information — the unconscious's report on the actual state of the writer's project. The block is symptomatic, not pathological. The diagnosis is in the symptom.
The frame has three load-bearing parts.
Part 1: Block contains wisdom. When the writer cannot write, the unconscious is reporting something the conscious mind hasn't yet articulated. The report might be: what you're saying isn't true. It might be: you don't have the material yet. It might be: you're afraid of what you'll find. It might be: the structure is wrong. Different blocks point at different diagnoses. The discipline is to read the block, not to fix it.
Part 2: Pushing through is the wrong move. The writer who treats block as obstacle and forces past it will produce work whose problems they've now made structural. The forced-through work carries the unaddressed wisdom of the original block as a hidden flaw. The flaw shows up later — in revision, in editor's notes, in reader confusion. The original block was trying to prevent the flaw. Pushing through built it in.
Part 3: Confess the doubt that produced the block. Once the block has been read — once the writer knows what the unconscious was reporting — the operational move is often to write the doubt into the piece itself. I was afraid to go to Portugal because I thought it might have failed. Here's why I was afraid; here's what I found when I went. The doubt becomes part of the work, and the reader gains the writer's actual epistemological situation, not the false-confident performance the original block was protesting against.
Hari's account points at a specific kind of block: the fear that the truth, when found, will undermine the project. This is operationally common in long-form work. The journalist who has built an argument that X is wrong, and is about to investigate the place where X is supposedly right, faces the same fear. The biographer who has built a sympathetic portrait, and is about to investigate the documented betrayal, faces the same fear. The memoirist who is about to write the chapter about a parent, faces the same fear.
The fear is evidence the writer cares about truth. The writer who didn't care about truth would write the convenient version and move on. The blocked writer is being held by their own commitment to not write the convenient version. The block is the commitment doing its work. Reading the block correctly means honoring what the block is protecting.
This page connects directly to Confess Doubt to Reader (Hari) — the Portugal case is the canonical example. Hari was blocked by doubt; he resolved the block by going to Portugal; he then wrote the doubt into the book. The pair describe the full cycle: block reveals doubt; investigation tests doubt; honest confession of the doubt's history becomes part of the work.
It strongly resonates with Courage as Writing Bottleneck (Karlsson) — Karlsson's claim that courage is the actual bottleneck of writing, not craft. Hari's block-as-wisdom is the Karlsson principle in operational form. The block is what the lack of courage looks like; the resolution of the block requires the courage to go to Portugal. The two pages combined describe a unified frame: writing-craft is downstream of the writer's relationship to fear.
It sits in productive tension with Writing Routine as Engineering (Pink) — Pink's daily-target discipline can produce a frame in which not-writing-today is treated as failure. Hari is saying some not-writing-todays are wisdom. The vault should hold both: routine is operationally useful for sustaining work over long periods, and the routine should be interrupted (not pushed through) when the block contains structural information. The discipline of telling the difference is what mature writers develop.
The block lasted weeks. Hari had the flight ticket information, the contacts, the introductions, the schedule. He was not procrastinating in the ordinary sense — he wasn't watching TV or scrolling. He was working on other parts of the book. Just not on the Portugal section. Every time he started toward Portugal, something would pull him back. He'd find another interview to do. Another chapter to write. Another archive to visit.
The pattern is recognizable to any long-form writer. The systematic-avoidance-of-one-specific-section. The avoidance pattern is the diagnostic. The pattern points at exactly what the writer needs to look at.
Hari names the operational move: I was kind of blocked around. I realized I was afraid. The realization is the work. Once the realization is on the page, the block is no longer mysterious. I am afraid that Portugal failed, and if it failed, my book becomes nihilistic. Once that is articulated, the writer can ask: is the fear well-founded? If the fear is the truth might be inconvenient, the answer is go find out anyway. If the fear is I don't yet have the courage to find out, the answer is do the personal work that makes the courage available, then go. Either way, the block's content has been named, which is what the unconscious was waiting for the writer to do.
Hari went. Portugal had worked. The book got the case study it needed. The block had served its function — it had ensured Hari approached Portugal with the honest expectation that it might have failed, rather than with a confirmation-biased eagerness to find what the book wanted to find. The approach was epistemically cleaner because the block had forced the writer to confront the possibility of disconfirmation.
You're three weeks behind schedule on a specific section of a long project. The rest of the work is moving. This one section keeps not happening. You sit down to write it; you find a reason to do something else.
Stop. Don't push through. Read the block.
Sit at your desk with a blank page. Write at the top: Why am I not writing this section? Then write whatever comes. Don't edit. Don't filter. The unconscious is closer to the page than you might expect — your hand will produce material your conscious mind hasn't yet articulated.
The output might be: I don't have enough material yet. That diagnosis points at more research. I don't believe what I'm trying to say. That points at rethinking the argument. I'm afraid the truth will undermine the book. That points at going to find the truth anyway. The structure of this section is wrong. That points at restructuring before writing. Each diagnosis points at a specific operational move.
The block is the only place where the diagnosis can be done quickly. After the diagnosis, the move is usually clear. Most blocks resolve within an hour of being correctly read. Most blocks last weeks when they are not read.
Then, if the diagnosis was fear of disconfirming evidence, you do the harder thing: you let the section confess its own history. I avoided this for three weeks because I was afraid you would find what I might find. I'm going to tell you what I found anyway. The reader receives the writer's actual epistemic process. The trust this builds is substantial. It's the same architecture as Hari's vulnerability-shared-goal-evidence opening, but at chapter scale.
You'll know you've pushed through a block when, in revision, you find a specific section that doesn't quite hold up. The argument is there but the energy isn't. The evidence is correct but the framing feels off. The section is technically functional but it carries a hidden flaw the rest of the work has to compensate for. The flaw is the unread block. The unconscious was reporting; the writer suppressed the report; the report has now become structural debt in the manuscript.
You'll know you've read a block correctly when the section resolves with unexpected clarity after the diagnosis. The hour spent reading the block produces an hour of clear writing afterward. The two hours together replace three weeks of stuck. The math, once you've experienced it, makes the practice essentially mandatory.
The principle has substantial support across writing-craft literature — Anne Lamott, Stephen King, Annie Dillard all discuss block-as-information at different angles. The cognitive-psychology literature on unconscious processing (the work of Mihaly Csikszentmihalyi on incubation, Anders Ericsson on deliberate practice) provides supporting mechanism: the conscious mind isn't the only system working on the project, and the other systems sometimes report through felt-resistance rather than through articulate thought.
The tension Hari leaves unresolved: blocks that are not wisdom. Some blocks are produced by depression, by anxiety unrelated to the work, by life-circumstances that have nothing to do with the manuscript. The discipline of reading the block assumes the block has something to report; some blocks don't. The likely refinement: most prolonged, specific-section blocks contain wisdom; blocks that are diffuse, global, and accompanied by other symptoms may be psychological rather than craft-symptomatic. The writer's job is to distinguish.
Hari and Karlsson converge tightly here. Karlsson's courage as writing bottleneck explicitly names craft-questions as excuse-mechanisms for what is actually courage-failure. Hari's block-as-wisdom is the operational version of the same insight. Both writers are saying: what looks like a craft problem is often an emotional problem in disguise. The convergence is one of the more robust agreements in the writing-craft section of the vault. The vault should mark it as established.
Hari and Pink offer a productive tension on routine. Pink's writing-routine-as-engineering is structurally agnostic about whether a given day's not-writing carries information. The discipline is to write the daily target regardless. Hari's frame would interrupt the routine when the block contains diagnosis. The vault should preserve both: routine is operationally useful for sustaining a long project, and the routine should be smart enough to recognize when not-writing is reporting on the project rather than failing at it. Mature practice integrates both.
Psychology: Symptom as Information, Not Malfunction — the depth-psychology tradition (Jung, Hillman, contemporary somatic-experiencing work) treats psychological symptoms as the psyche's reporting mechanism rather than as malfunctions to be eliminated. The depression that won't lift, the anxiety that returns, the block that holds — all of these are symptoms that contain diagnosis. The writer's block is one case of this broader operation. The patient learning to read her own anxiety as information about an unattended life-situation is doing the same move as the writer learning to read her block as information about an unworkable manuscript structure. The doctor's nausea-as-diagnosis frame, the patient's symptom-reading practice, and Hari's block-as-wisdom are three forms of the same principle deployed across three different clinical scales.
Behavioral Mechanics: Resistance as Strategic Information — the negotiation and operational-strategy literatures both observe that resistance from a counterpart contains intelligence about the counterpart's actual position. The negotiator who pushes through resistance loses the diagnostic value of the resistance. The negotiator who reads the resistance learns what the counterpart actually needs. Hari's writer's-block discipline is one application of the broader principle — resistance is information; pushing through forfeits the information. The negotiator who reads counterpart-resistance, the doctor who reads symptom, and the writer who reads block are running the same diagnostic move in three rooms.
The Sharpest Implication If Hari is right, the contemporary productivity-discourse around writing — write every day, hit your word count, push through the block, butt-in-chair — is systematically training writers to suppress diagnostic information about their own projects. The discipline that sustains the work is also producing the blindness that prevents the writer from noticing when the work needs structural revision. The implication: writers who have been most successful at internalizing productivity-discipline may be most at risk of producing work that has unread structural problems. The push-through reflex is operationally effective at producing daily output and operationally destructive at producing high-quality output. The vault should mark this as an active tension in the writing-craft literature.
Generative Questions