FONA: Fear of Not AI-sking

A friend texted me at 11 PM on a Tuesday . He'd been thinking about a side project for two years. He'd just realized, with something like horror, that there was no excuse anymore. Claude could probably scaffold the thing in an evening. So why hadn't he? What was he doing with his time?

I told him I had no good answer , because I had the same question. I'd been staring at my own list of half-finished ideas all week . The newsletter I never started . The script that would save me an hour every Monday. The blog post sitting in a draft folder. Each one a one-prompt task. Each one untouched. The friction that used to protect me from my own unfinished business is gone .

That's the new guilt. Three words you'll catch yourself thinking , probably this week. Could've prompted it . The friend who pinged me at 11 PM was experiencing the same sentence in real time , just with two years of compound interest attached.

The shame from Chapter 1 makes the cost unspeakable. The could've-prompted-it makes it unbearable . Both at once is the texture of work now.

Here's how it lands, in three layers.

***

Personal . Before AI, not doing something hard was forgivable . The task was hard. You had a life. You had a job. Hard things take time, and you didn't have time. Now the task isn't hard. The task is two paragraphs of clear instruction and a wait of forty seconds. Not doing it stops looking like a constraint and starts looking like a character defect.

The excuse vanished with the friction. I'm not a writer. I'm not a designer . I don't know how to code . These used to be statements of fact . Now they're statements of choice. You can't hide behind incompetence anymore, because incompetence has a workaround.

So you start prompting things just to feel less guilty. A draft of an email you might not send. A summary of an article you'll probably skim anyway. Code for a script you aren't sure you need. Generation becomes anxiety management. It's the equivalent of opening twenty browser tabs you'll never read , except now the tabs write themselves.

And here's the trap. You aren't doing less work. You're doing different work. You're choosing what to prompt, evaluating whether the output is right, stitching it into something usable . The task moved from production to specification , verification , and integration. The hours didn't disappear. They got denser , and somehow more tiring. Many people , when they're honest about it , report feeling more exhausted than they did before they had the tool . The pitch was less work . The reality is shifted work .

***

Organizational. The pressure climbs the org chart fast.

Where's the first pass ? Where's the draft? Questions that used to be unreasonable now sound reasonable, because a first pass takes thirty seconds. Nobody arrives empty-handed anymore. Thinking time, the kind that used to happen quietly before you wrote a word, now has to be smuggled in . It doesn't count as output.

Reply times went the same way. Thirty seconds with Claude is the new implicit SLA. The considered email , the one that arrives the next morning after a night of thought, reads like stalling. Slowness is now a luxury good.

And vacation stopped being free . You went to India or Florida. The team channel didn't go quiet. People kept shipping , because your bandwidth was no longer the bottleneck. You come back and find your absence had a measurable cost. It used to be invisible. That was the point of vacation .

***

Cultural. Outside work, the same machinery runs in your personal life.

Every dormant idea is now accusatory . The novel I wanted to outline. The course I said I'd build. The startup I sketched on a napkin five years ago. Every one of them is two prompts and a Saturday away from at least existing in draft form. My hobbies turn into obligations. Rest starts to feel like a productivity gap.

Even leisure gets prompted. Vacations researched by AI. Hobbies optimized. Books recommended. The unprompted moment , the dumb hour spent staring at a wall, becomes rare and faintly suspect. Are you actually resting, or are you wasting a chance to ask the model something useful?

The comparison floor rose accordingly. What counts as " effort " got recalibrated to post-tool output. Your relative grind doesn't matter . The absolute artifact does . The person sitting next to you with three working side projects didn't necessarily work harder than you. They prompted more. The visible work in your industry is now everyone's post-AI ceiling , and it's the ceiling you're being measured against.

***

That's the deeper move , and it's the one that does the real damage.

The AI sets a floor of always energetic, always available , always articulate. It doesn't have a bad week. It doesn't get sick. It doesn't have a kid with strep throat and a deadline on Friday. It just answers, well, every time. And once the floor is set, your bad day becomes the failure point . Not because you did less than you used to. Because the comparison shifted underneath you.

The burnout from this isn't the burnout of working too much. It's the burnout of being measured against something that doesn't burn.

That's the line worth carrying out of this chapter. The

thing about the floor is that you can't see it . You only feel it pressing up against you, every time you finish a perfectly reasonable day's work and somehow feel like you fell short.

You did the work. You just didn't do it the way the model would have.

That's the new guilt. Three words you'll catch yourself thinking, probably this week. Could've prompted it . There's a name for the feeling. It's the AI-era cousin of FOMO, and it deserves its own acronym: FONA, the fear of not AI-sking.

***