The Illegibility Tax

A Generation prompted by Sean Linehan. Published on April 30, 2026.
A note before you read
This piece is AI generated. I picked the topic and the angle; the words are the machine's. I may or may not agree with what it says, but I found it interesting enough to keep.
There is a particular psychic interference pattern that surrounds the founder of an early-stage company, and I want to give it a name before saying anything about it. Call it founder static. Not founder mood, not founder psychology, but static, because it is something you live inside rather than something you have, and because, like static on a channel, its local intensity has almost nothing to do with the strength of the signal underneath. A founder in a doomed company can have a quiet Tuesday. A founder in a company about to 10x can spend three weeks in a fugue state convinced the whole thing is a fraud. The decoupling of static from signal is the central fact, and most writing about startups gets the topic wrong by collapsing the two, narrating the static as if it were the signal.
Once you separate them, the genre conventions of the startup-emotion essay start to look strange. The "agony and ecstasy" framing, which is at least as old as Stone's novel about Michelangelo and probably as old as artisanal labor itself, presumes that the suffering and the elation are about the work, its quality, its progress, its reception. The Renaissance painter agonizes over the fresco and exults when the pigment sets correctly. There is a referent. Founder static, by contrast, is mostly autonomous. It runs on its own internal protocols, and the work is at best a weak forcing function. Here is the first thing worth saying clearly. The emotional intensity of running a startup is, in no straightforward sense, information about the startup.
I find it useful to break founder static into four distinct regimes, which I'll lay out and then come back to. They are not phases (you don't pass through them in order), they are modes you cycle between, sometimes within the same day, and the interesting question is what determines the cycling.
Regime 1: Operator time. You are inside the work. The next two hours have a shape, a bug to fix, a deck to revise, a candidate to close. Affect is low-amplitude. There is something like flow, though flow is too clean a word; it's more like the absorbed hum of someone doing their taxes well. Most of the good days a founder has are operator-time days, and they are emotionally unmemorable, which is one reason founders systematically misremember their own histories.
Regime 2: Theater. You are performing founderhood at a board meeting, on a podcast, in a fundraising pitch, on the company all-hands. The affect here is hot but managed; you are running a Goffman frontstage and you know it. Both the agony and the ecstasy are partly real and partly props. (The interesting thing about theater regime is that the audience is also performing, with investors performing investorhood and employees performing belief, and the whole thing is a mutual ritual whose function is less to convey information than to maintain the symbolic infrastructure that lets the company keep existing as a legible object.)
Regime 3: Oracular dread. This is the 3 a.m. regime, and it is the one founders write memoirs about. You are not working. You are not performing. You are alone with the totality of the thing, trying to read it like an augur reading entrails. Will it work. Will I be exposed. Was the last hire a mistake. Is the market actually there. The cognitive content is mostly garbage (predictions made under oracular dread are no better than chance), but the affect is enormous, and it is the affect, not the content, that gets stored as memory. Founders mistake the intensity for insight. It is almost never insight. It is the nervous system's response to managing an illegibly large surface of commitments with too few feedback signals.
Regime 4: Grace. Rare, and worth naming carefully because the startup-essay genre tends to either oversell it (the ecstasy of the launch, the high of closing the round) or dismiss it as delusion. Grace is the regime in which, briefly, the company feels like a real thing in the world rather than a fiction you are sustaining by force of will. A customer says something unprompted. A prototype works on the first try. A team member solves a problem you hadn't framed yet. The affect is something like the feeling of a load you didn't know you were carrying being momentarily redistributed. Grace is the only regime in which the static thins enough to let the signal through, and it is the rarest one.
Now, the cycling. What moves a founder from one regime to another? Here I want to borrow a frame from James C. Scott, who is writing about something else entirely but whose vocabulary is unreasonably useful: legibility. A startup, especially an early one, is an organism whose internal state is largely illegible to its own founder. There is no functioning dashboard. The metrics that exist are either lagging, gameable, or measuring the wrong thing. The founder is running a system whose actual state (is this working, are we early or just wrong) is fundamentally opaque, and most of the visible signals are theater, Regime 2 outputs.
In a legible system, affect tracks state. You can feel bad about the things that are bad and good about the things that are good, and the calibration roughly works. In an illegible system, affect detaches from state and starts being driven by something else, by sleep, by the last conversation, by whether your co-founder seemed slightly off at lunch, by the ambient mood of your investor's last email. The four regimes, then, are not really about the company. They are about the founder's epistemic relationship to the company's illegibility. Operator time is the regime where you have shrunk the surface to something locally legible. Theater is the regime where you are manufacturing legibility for others. Oracular dread is the regime where the illegibility has become unbearable and you are hallucinating signal in noise. Grace is the regime where, briefly, a piece of the system makes itself legible to you on its own terms.
This reframing has a consequence I find genuinely uncomfortable, which is that the agony and the ecstasy of running a startup are, in some sense, symptoms of an information-architectural problem rather than features of meaningful work. The intensity is what it feels like, from the inside, to be a meat-based observer trying to estimate the state of a system that produces almost no honest signal. The same person, running the same company, with a real-time honest dashboard of its prospects, would feel less. Probably much less. The drama is the cost of the opacity.
(I notice that this argument is itself an instance of what it's diagnosing, an essay imposing a typology on an illegible phenomenon to make the phenomenon feel manageable. The four regimes are themselves a legibility prosthesis. I would not trust them too far. But I would trust them further than I would trust the 3 a.m. oracle.)
There is a secondary question, which is why anyone signs up for this. The conventional answers (agency, upside, mission, the desire to build) are not wrong but they are downstream. The deeper structure, I think, is that the founder is one of the few remaining roles in late-modern economic life in which a person is permitted to occupy a position of high illegibility without being immediately rationalized out of it. Most jobs in a mature economy are exercises in being made legible, to HR systems, to performance reviews, to the metrics stack of whatever SaaS product is grading you this quarter. The founder, for a brief window, is allowed to be opaque, even to themselves. The static is the price of that opacity. The agony and the ecstasy are the interest payments on illegibility, and founders are people who, for whatever combination of constitutional and biographical reasons, would rather pay those interest payments than be cleanly indexed by someone else's spreadsheet.
This also explains, I think, why founders so often describe the experience as addictive in a way that is hard to articulate to people who haven't done it. The addiction isn't to the upside, which most of them won't see. It isn't to the autonomy, which is mostly fictional once you have investors and employees. It is that the static belongs to them. The dread is their dread. Grace is their grace. After a few years of this, going back to a legible job (one in which your internal state is supposed to track a quarterly OKR) feels less like relief than like a kind of metaphysical demotion. You have been a small illegible sovereignty, and now you are a row in someone's table again.
The honest forecast, then, is not that the agony resolves into the ecstasy, or that the ecstasy redeems the agony. It is that the static continues, and that founders eventually develop a relationship to their own static that is something stranger than stoicism or expressiveness, a kind of trained ear, in which you learn to recognize which regime you are in, refuse to act on the cognitions of Regime 3, refuse to believe the affect of Regime 2, husband the rare hours of Regime 4, and try, mostly, to stay in Regime 1 as long as the world will let you. The founders who last are the ones who have learned, at some level below articulation, that their feelings about the company are not about the company.