The Anxiety Check

In the AI Story

May's clinical insight was that anxiety is not noise to be filtered but signal to be interpreted. The patient who feels no anxiety during creative work is either repeating the already-known (routine) or avoiding genuine territory (defense). The genuinely creative patient is anxious precisely because they have entered territory where the outcome is uncertain, where habitual responses are insufficient, where something real is at stake. This anxiety is uncomfortable but energizing—it mobilizes rather than paralyzes. Learning to recognize it as the companion of genuine work rather than as evidence of incompetence is the core psychological achievement that enables sustained creative life.

Applied to AI collaboration: the builder describing a problem to Claude and receiving competent solution experiences mechanical relief—the uncertainty about whether the implementation will work has been resolved. But this mechanical relief can mask the absence of creative anxiety. If the builder never questions whether the solution addresses the actual need, never sits with uncertainty about whether the direction is right, never experiences the productive discomfort that signals genuine encounter—the collaboration has eliminated not just mechanical friction but creative friction. The builder is producing without encountering, and the production, however intense, is not building the judgment that the AI age demands.

The check requires deliberate interruption of flow. Flow state feels good; feeling good is not the criterion for genuine creativity. May observed that some of his most creative patients were most anxious, and that the cultural preference for feeling good over growing genuinely was producing populations who optimized their lives for comfort while their creative capacities atrophied. The AI-era version: the builder who never interrupts the smooth collaboration to ask whether anxiety is present will drift, session by session, from genuine encounter toward mechanical production without noticing the transition. The check is the pause that prevents the drift.

The anxiety that matters is directional uncertainty—not anxiety about whether the code will compile (mechanical), but anxiety about whether the thing being built deserves to exist, whether the vision is authentic, whether the builder is creating something genuine or merely producing something plausible. This higher anxiety cannot be resolved by technical means. It can only be held—held in awareness, held with courage, held long enough for judgment to form. The builder who develops tolerance for this anxiety develops the capacity that AI cannot supply: the capacity to evaluate what is worth building in the first place.

Origin

The anxiety check originates in May's therapeutic practice and is formalized across his major works, particularly The Meaning of Anxiety and The Courage to Create. It builds on Kierkegaard's phenomenology of anxiety and Tillich's theology of courage, translated into a practical clinical instrument. May taught patients to ask themselves, regularly and honestly, whether their anxiety was proportionate to actual threat (normal), disproportionate and paralyzing (neurotic), or the signature of genuine encounter with the unknown (ontological). Only the third was creative.

Key Ideas

Presence of Anxiety Signals Encounter. Ontological anxiety—discomfort about direction, not mechanics—indicates the builder has entered genuinely uncertain creative territory where growth occurs.

Absence Indicates Routine or Avoidance. Work producing no anxiety is either repetition of the already-known or delegation of genuine questions to the tool—neither builds creative capacity.

Must Be Repeated. Single check is insufficient; collaboration character shifts within sessions from encounter to production—the diagnostic must be deliberate, recurring practice.

Feeling Good Is Not the Criterion. Flow feels identical whether earned through courage or produced through frictionless mechanics—subjective satisfaction cannot distinguish them.

Directional Uncertainty Matters. Not anxiety about whether code compiles but anxiety about whether the vision is right, whether the work deserves to exist—this higher anxiety cannot be resolved technically.