For professionals who feel behind on AI

AI Anxiety: Why Capable Executives Feel Behind—and What Actually Helps

AI anxiety—the quiet worry that everyone at work is using these tools better than you—is common, rational, and fixable. In most cases the feeling means you have not yet had one structured week with a single tool on real work. This page names the anxiety, separates fact from noise, and gives you a seven-day plan.

1-on-1 with Pete Enestrom, on your actual work

Pete Enestrom

Written by Pete Enestrom

Yale & Columbia, ex-Microsoft & Intel — 1-on-1 AI coaching for executives

Pete Enestrom — executive AI coach and Zaigo co-founder

Your coach’s background

YaleCOLUMBIAUNIVERSITYMicrosoft

Here is the feeling, named precisely. You have run a company or a career through several technology shifts, and somewhere in the last couple of years a quiet sentence moved into your head: “everyone else is further along on AI than I am.” A colleague mentions ChatGPT casually in a meeting. A peer's emails suddenly read tighter and faster. Nobody announces their AI use, so there is no way to see who is actually doing what. The worry sits quietly, it feels slightly embarrassing to say out loud, and it does not go away on its own.

This page is for that exact reader: the owner, founder, or executive who is worried about AI not as an abstract threat to humanity but as a specific gap in their own working week. If you are afraid of AI in the existential sense, the psychology journals and the think pieces cover that angle thoroughly. Almost nothing on the first page of search results covers the workplace version: competent, non-technical professionals who feel behind and want a straight, practical answer about what to do this week.

I coach executives through AI anxiety for a living. The worry is real, it is far more common than anyone admits in public, and in my experience it is fixable with a method rather than a personality change. Most of what follows is the same material I cover in the first two sessions with a new client.

Why does AI anxiety feel different from past technology shifts?

Two properties make AI anxiety different from the discomfort executives felt with personal computers, the internet, or smartphones. The first property is speed: earlier shifts arrived on a calendar a company could plan around, while the current AI tools went from novelty to board topic remarkably fast and keep changing every few months, so there is no stable version to learn once and keep. The second property is invisibility: when competitors adopted a website or a CRM system, the change was visible, but AI use leaves no public trace—a competitor whose proposals suddenly sharpen, a colleague whose meeting prep seems effortless. Because nobody can see anyone else's AI usage, each professional privately assumes they are the only one behind. Among the executives I coach, that assumption is nearly universal, and it is nearly always wrong.

A third difference is more personal. Earlier technology arrived as a department—IT handled the computers, the web team handled the website—and an executive could stay strategic while specialists absorbed the change. AI lands directly on the executive's own desk work: the writing, the reading, the preparation, the first drafts. Those tasks were never delegable to a department, so feeling behind on AI feels uncomfortably close to feeling behind on the job itself. That proximity is why AI anxiety stings more than the email transition or the smartphone transition ever did, and it is also why the fix has to be personal practice rather than a procurement decision.

What is actually true about AI at work, and what is noise?

The honest picture, from real companies rather than headlines: the current AI tools are genuinely useful at a short list of ordinary work—drafting and editing prose, summarizing long documents, preparing for meetings, and getting unstuck on a first draft. Professionals who use one tool on real tasks every week get meaningfully faster at those tasks, usually within a month or two. The required skill is not technical; most of the executives I coach are in their fifties and sixties, and none of them write code. Most encouraging of all, the gap between a dabbler and a competent weekly user is measured in weeks, not years—so catching up is a plan, not a fantasy.

The noise is loud enough to deserve its own paragraph. The claim that everyone else has already figured AI out is false: most professionals are dabbling—an occasional question typed into a chat window between meetings—and dabbling is not fluency. The headlines predicting that entire professions will disappear are written to be clicked, often by people with something to sell, and nobody honestly knows the ten-year shape of any industry. The demonstration videos show the tool's strongest minute, not its average Tuesday. The professionals who appear to be keeping up with AI are usually just a few weeks further into the same practice you are about to start. None of this makes the tools overhyped—they are not—but the distance the anxiety describes is much longer than the distance that actually exists.

What does a 7-day plan to get past AI anxiety look like?

This is the same first week I give new coaching clients, written down. One tool, one real task per day, about twenty minutes a day. Pick ChatGPT or Claude—either is fine, and the skill transfers almost completely. The rule that makes the plan work is simple: every task must come from your actual to-do list, because real stakes are what shrink the anxiety.

  1. Day 1: Open one account and ask one real question

    Create a free account at chatgpt.com or claude.ai with your work email. Skip the party tricks and ask one question you genuinely need answered this week—a decision you keep circling, or background on a topic coming up in a meeting. The goal of day one is not a perfect answer; the goal is breaking the seal.

  2. Day 2: Hand the tool one piece of writing you owe someone

    Pick an email or a short document from your real to-do list. Paste the context first—the thread, the background, who the reader is—then ask for a draft in plain language. Notice how much the output improves when the context is real; that relationship between context and quality is the core lesson of the whole week.

  3. Day 3: Feed the tool a long document

    Take a report, a contract, or an article you have been avoiding and paste it in. Ask for a summary in ten bullet points, then ask what questions a skeptical board member would raise about the material. Long documents are where AI tools save the most executive time, and most professionals never try them.

  4. Day 4: Prepare for one real meeting

    Choose a meeting on tomorrow's calendar and ask the tool to help you prepare: the likely objections, the questions worth asking, a tighter agenda. Bring the output into the room with you. Using AI for preparation is the fastest way to feel the tools working inside your actual job rather than next to it.

  5. Day 5: Push back on a draft

    Take an earlier output and argue with it: “shorter, plainer; the second paragraph is wrong, and here is why.” The edit conversation is where the quality lives. Learning to push back is the single skill that separates fluent users from dabblers, and it takes minutes, not months, to learn.

  6. Day 6: Save the two prompts that worked

    Copy the exact prompts that produced useful results this week into a note on your phone or computer. Those prompts are the beginning of a personal playbook—a meeting-prep prompt, a document-summary prompt—and each saved prompt gets better every time it is reused and refined.

  7. Day 7: Write your shortlist and your boundary

    Write down the three recurring tasks where the tool earned its keep this week, and decide when it touches them next week. Then write one line about what you will not paste—confidential client material, personal information about employees—until your company has a written policy. Small wins, written down, are what the anxiety cannot argue with.

When is AI anxiety actually a management problem?

Sometimes the unease in your chest is not about your own fluency at all. When the real sentence is “my team is falling behind,” the fix is not personal practice—it is structure. These are the four patterns I look for when an owner describes a company-wide worry about AI.

No guardrails

  • Employees are pasting company material into personal AI accounts with no rule about what is allowed.
  • Nobody has said in writing which tools are approved and what may never be pasted.
  • The fix is a one-page written policy, not another worried memo.

No training

  • The company expects AI adoption, or has even bought licenses, but nobody has taught the team how to use the tools on real work.
  • Left alone, most employees try once, get a mediocre answer, and quietly stop.
  • Structured practice on real tasks is what converts licenses into hours saved.

No shared language

  • The leadership team cannot say, in one sentence, what AI is actually for in this business.
  • Every department invents its own answer, so nothing compounds across the company.
  • A shared vocabulary—what we use AI for, what we never use it for—turns scattered experiments into a capability.

Silent shadow use

  • Capable people are already using AI privately and hiding it, because the company's silence reads as disapproval.
  • The anxiety then runs in both directions: employees worry about being caught, and ownership worries about being behind.
  • A clear, permissive policy with real guardrails brings usage into the open, where it can actually be managed.

Where do you go from here?

If your AI anxiety is personal—your own practice, your own fluency—the seven-day plan above is the complete answer for now: repeat the week four times, and the worried feeling is usually replaced by a working habit. If the anxiety is about your company, two pages on this site carry the next step. My AI usage policy template gives you the one-page guardrail document, clause by clause, and the page on AI training for employees walks through how a team gets fluent together instead of one anxious person at a time.

One honest boundary belongs here. If worry about AI is costing you sleep or showing up in your health, that conversation belongs with a physician or a therapist, not with a coaching page—workplace anxiety and clinical anxiety are different things, and this page addresses only the work side. On that work side, if you want a person to walk the plan with you—a human teacher, not an AI coach bot—that is what my 1-on-1 coaching is for: your real workload, your real week, and someone who has guided many executives across exactly this ground.

1-on-1 coaching

Get the guardrails—and the training—right.

A policy nobody understands protects no one. We'll set the rules and teach your people to work well inside them.

Format1-on-1Sessions
LocationNYCor Remote
Duration2-4 hrsFocused
ResultClarityWalk away ready
Pete Enestrom in a 1-on-1 coaching session

Your coach

Coached by Pete Enestrom

Yale and Columbia grad, former Microsoft and Intel, and a venture-backed exited founder. Pete has spent the last four and a half years going deep on every major AI tool, and he teaches the way operators learn: on your real work, at your pace, with nothing assumed.

YaleCOLUMBIAUNIVERSITYMicrosoft
Pete Enestrom's signature

Common questions

Straight answers, the way I'd give them across a table.

Keep reading

Beyond coaching

When the workflow needs to be encoded, not just learned — that's what our team at Zaigo builds.