PickyFox

technology

What I Stopped Delegating to AI (After Delegating Everything)

February 22, 2026

I went all-in on AI and stopped thinking for myself. Here's what I learned when I tried to actually do my job.

Open notebook with pen and pencils on desk
Photo by Clay Banks / Unsplash

I gave AI everything for three months. Not gradually. Not thoughtfully. All at once.

Client emails went to ChatGPT. First drafts of blog posts went to Claude. Research summaries, project planning, even the initial strategy conversations — all offloaded. I had this feeling that finally, finally, I could focus on the “big picture work” while the machine handled the writing and thinking scaffolding.

By month two, I noticed something odd. My blog voice had flattened. I was editing AI drafts instead of writing, which sounds like a win but felt like watching someone else’s writing through a filter. My emails started sounding corporate in a way that made clients ask if I was okay. And the strategy conversations? They happened in my head less often because I’d gotten used to just asking for options instead of developing instincts.

The strangest part: I felt busier, not freer.


It turns out that the processes I thought were overhead were actually the thinking. The writing was the thinking. The research was the thinking. The planning conversations were the thinking. When I delegated those to a language model, I wasn’t freeing myself up to think bigger — I was just outsourcing the part of the work where the actual thinking happens.

I realized this when a client asked me to explain the strategic direction I’d had AI help draft. I couldn’t. Not because the strategy was bad — it was solid, reasonable, defensible. But I hadn’t done the work to build it. I’d assembled it. There’s a difference.

That’s when I started pulling tasks back.

The writing came first. I stopped sending blog post ideas to Claude’s first-draft machine and went back to the blank page. For about a week, it was painful. My brain had gotten lazy about generating opening lines. But somewhere in the middle of day four, my voice came back. Not because the tool was bad, but because I’d stopped outsourcing the part of the work that makes me a writer.

Next went the client emails. I kept using AI for the boring, repetitive ones — renewal notices, standard project documentation. But anything emotionally loaded, anything where the client relationship mattered more than the output, went back to being handwritten. This felt different immediately. It was slower. It was also honest. The client could tell I’d actually written it, and the communication landed differently because of that.

The research and planning came last, and this one was the hardest to admit. I was using AI to avoid the uncomfortable part of figuring things out. Instead of thinking through strategy and sitting with the decision-making discomfort, I was feeding questions to a model and getting back a menu of options to choose from. It felt faster. It was actually just letting me skip the part where I develop intuition.


Here’s the skeptic’s question underneath all this: what am I actually saving time for?

I had this idea that by automating the “low-value work,” I’d suddenly have hours of space for deep thinking and strategic work. In reality, I had hours of space and no engine to fill it with real thinking. I just scrolled. I checked email more. I opened more apps. The freed-up time became empty time.

The real problem wasn’t that I was doing too much low-value work. The problem was that what I thought was low-value work was actually foundational. Writing emails makes me better at communication. Drafting content makes me better at thinking. Planning things — even simple projects — builds the muscle that lets me spot strategic opportunities.

I’d read about when not to use AI before, but I thought the warning was for other people. People who weren’t as disciplined as me. People who’d actually stop thinking. Not me.

Turns out I was wrong about that.


I’m not anti-AI. I still use it. But I use it differently now — for the actual scaffolding, not as a replacement for the thinking. AI handles the boring repetition. The things where I need my voice, my judgment, my actual understanding of the situation? Those stay with me. I work slower. I work better.

The part that stings a little is how quickly I’d convinced myself that thinking was optional, that I could outsource the discomfort of decision-making and come out ahead. It took three months of watching my own voice disappear to realize that the discomfort was the point — that friction is where skill lives.

I also wrote about how I actually use AI when I’m not letting it run the show. The difference between then and now is discipline. Knowing where to stop.

Most people don’t realize they’ve stopped thinking until it’s hard to start again.