Issue #16 · May 12, 2026 · The AI Playbook

AI Should be a Painkiller, Not a Vitamin

ai-strategymcpctomusk

Have you ever sat there trying to come up with use cases for all of these insanely powerful AI agents that are hitting the street every day? Be careful. The most obvious stuff is usually just a nice-to-have. A vitamin.

The pattern I see everywhere: smart leader gets back from a conference, fired up, starts brainstorming "what could we point AI at?" By Friday the whiteboard has 18 ideas. By next quarter three got built. And nobody can quite explain why revenue didn't move.

Because nobody asked the only question that matters:

Was that problem actually killing us — or was it just sitting there?


"The most common error of a smart engineer is to optimize a thing that should not exist." — Elon Musk

Most of the AI being deployed inside enterprises right now is a vitamin. It's fine. Might help. Nobody dies if you stop taking it.

Painkillers get bought. Vitamins get forgotten.

So the question I keep asking before pointing AI at anything:

  1. Painkiller? Real, expensive, recurring problem. Worth paying a consultant.
  2. Vitamin? Technically faster. Old way wasn't broken.

And here's the part nobody on LinkedIn wants to say:

We've run businesses on email and spreadsheets for 40 years. Not because we were too dumb to upgrade. Because they work. Cheap. Universal. The switching cost is higher than the savings.

If it ain't broke, don't fix it.


Musk's 5-Step Algorithm (Strict Order)

He uses this at SpaceX and Tesla. The order matters more than the steps.

  1. Question every requirement.
  2. Delete any part or process you can — even if you have to put it back later.
  3. Simplify and optimize.
  4. Accelerate cycle time.
  5. Automate. ← LAST.

Step 5 is where almost everyone fails.

AI is a very smart engineer. It will happily optimize your inherited approval workflow, your 1995 lead-routing process, your six-level expense form — and never once ask whether any of it should exist.

You end up with a beautifully efficient version of yesterday's bureaucracy.


So What IS Worth Automating?

The painkillers. Three filters:

  1. High volume.
  2. Genuinely painful.
  3. Underlying process is something you'd defend on a whiteboard.

Everything else — leave alone. Or better: delete the process and don't replace it.


The Bottom Line

The painkiller list is shorter than you think.

Most of the AI being shoved into your org right now is a vitamin somebody is selling to feel productive. Step back. Question every requirement. Delete first. Automate last.

If the process wouldn't survive a whiteboard defense, don't automate it. Kill it.

(And then read the next one — The CTO's Line in the Sand — for what to do with whatever AI is left after the cull.)


What I'm Watching


What I'm Building


Got a take on this? Drop a comment on this issue at theaiplaybook.com/issues/painkillers-not-vitamins — I read every one. Push back, share where you've drawn your painkiller line, tell me where this is wrong.


Need something? Just reply.

If you need any of this, I can help:

The rest of my stack

Discussion

0 comments

Moderated before appearing