Managing AI Anxiety: Implementing the AHA Framework in High-Stress Tech Roles
The A.H.A. framework turns a vague dread about AI into one belief to change, one habit to keep, and three moves you make in the next thirty days.
Managing AI anxiety in a high-pressure role means working on the belief underneath it. Jacqueline V. Twillie's A.H.A. framework does this in three moves: name the Attitude you're carrying into the change, change one Habit that is quietly working against you, and commit to three specific Actions in the next thirty days. It is one of her four published frameworks. Plans built on motivation alone stop working the first week someone is tired.
Most AI anxiety in mid-career roles comes from the gap between how fast the conversation is moving and how little hands-on time anyone has been given.
A.H.A. stands for Attitude, Habits, Actions. It is a career planning framework from Jacqueline V. Twillie, published as the A.H.A. Action Planner inside Career Lab, and it aligns those three layers against one specific goal instead of treating mindset, routine, and execution as separate problems.
Read that number carefully. It measures what changed in the person after one hour of doing the thing they had been avoiding.
What does AI anxiety actually look like in a senior role?
It rarely announces itself as fear. It shows up as avoidance dressed in good judgment.
You forward the article instead of opening the tool. You wait for the company to pick a platform. You tell yourself you'll look into it after the quarter closes. Meanwhile the person two levels down is already using it daily and you have started to notice, and now there is a second layer of anxiety about the first one.
The people in BNEDai's build sessions are not junior. Registrants, who join as individuals with no employer sponsorship or endorsement, have included senior managers, PhDs and EdDs, MBAs, MPAs, PMPs, and clinical leaders from organizations including Amazon Web Services, ExxonMobil, Moody's Analytics, and the NYC Department of Education. Seniority does not protect anyone from this. In some cases it makes it worse, because senior people have more to lose by being visibly a beginner.
What is the Attitude step, and why does it come first?
Attitude is the belief you're holding about yourself and the change. The planner asks two questions: what is the belief you need to hold to reach this goal, and what story are you currently telling yourself that might be in the way.
The second question is the one that does the work. Common stories in this lane sound like: I am not technical. I am too far into my career to start over. If I ask, they will know I have been faking it. Everyone else already understands this.
Write the actual sentence down. A belief you have never made explicit runs unchallenged, and it will quietly veto every plan you build on top of it.
The replacement belief has to be small enough to be true, something closer to "I can learn one tool well enough to use it on my own work" than "I am an AI expert."
What habit is quietly working against you?
Habits is the layer people skip, and skipping it is why the January plan is dead by February.
The planner asks what daily or weekly practice would move you toward the goal, and what habit is currently working against it. It also tells you to be specific: name the day, the time, the commitment.
The habit working against you is usually consumption. Reading about AI feels like progress and produces none. An hour spent on newsletters and threads leaves you more informed and no more capable, and it burns the exact hour you would have needed to build something.
Trade it. One recurring block, on a named day, where the only thing you do is put your hands on a tool and point it at your own work. Forty-five minutes on a Thursday morning beats four hours of reading spread across a month.
What three actions belong in the next thirty days?
Actions is the commitment layer, and the planner is deliberately strict about it: three specific actions in the next thirty days, named as actual steps rather than categories.
A version that fits this lane:
- 01
Build one working agent on a real task.
Point it at something on your own calendar you'd actually keep using, instead of a demo or a tutorial you're just following along with. The single-session build guide walks the five moves.
- 02
Use it for two weeks and keep notes on what it got wrong.
The failures are the learning. A tool you have watched fail in specific ways is a tool you can speak about credibly in a room.
- 03
Teach one person.
Every participant surveyed in BNEDai's first reporting window made the teach-one pledge, committing to teach one other person what they learned. Teaching is also the fastest way to find the holes in your own understanding.
Three is the number on purpose. A list of nine actions is a way of feeling productive without choosing.
What if the real fear is about your job?
Then say so plainly. Those are different problems, and A.H.A. handles them differently.
Anxiety about the tools responds to competence. An hour of hands-on building moves it, which is what the confidence figure above reflects.
Anxiety about your role is a strategy question, and it deserves a real answer rather than reassurance. Nobody in this field can tell you which roles will still exist in three years. What is knowable is that the people who can describe, in specific terms, which parts of their own work they have automated and what safeguards they put around it are having a different conversation with their leadership than the people who cannot.
There are also constraints that have nothing to do with you. In one BNEDai session, a team's managed-device restrictions blocked the build entirely, and they left with a workaround plan instead of an agent. Every session now opens with a device check. If your IT environment is the obstacle, name it to your leadership as an organizational problem. Reduce IT Dependency covers that side of it.
How do the pieces hold together?
Attitude without Habits is a good intention. Habits without Actions is a routine that goes nowhere in particular. Actions without Attitude falls apart fastest of the three, usually by week two. The belief underneath it never changed, and belief is what you fall back on when you're tired.
A.H.A. is one of four frameworks Jacqueline uses across her leadership and negotiation work, alongside FLOW, R4, and L.A.T.T.E.. They are built to be used under pressure, which is the only condition that matters. For the outward-facing leadership side of this, managing upward to executives and across to peers during a tech shift, see AI leadership skills.
Frequently asked questions
What does A.H.A. stand for?
Attitude, Habits, Actions. It is a career planning framework from Jacqueline V. Twillie, published as the A.H.A. Action Planner inside Career Lab. It aligns three layers against one specific goal: the belief you hold about the change, the recurring practice that moves you toward it, and three named actions you commit to in the next thirty days.
Why does the Attitude step come before the actions?
Because an unexamined belief vetoes the plan built on top of it. The planner asks what belief you need to hold and what story you're currently telling yourself that might be in the way. Stories like "I am not technical" or "I am too far into my career to start" run unchallenged until you write them down, and then they decide what you attempt.
Does hands-on practice actually reduce AI anxiety?
For anxiety about the tools, competence moves it. In BNEDai's first reporting window, 90.5% of surveyed participants reported moderate or extreme confidence to build their next agent independently after a single one-hour build session. Anxiety about your role is a different problem, and it deserves a strategy answer rather than reassurance.
What if my company blocks the tools I want to learn on?
That is an organizational constraint, not a personal failure. In one BNEDai session, managed-device restrictions blocked a team's build outright and the team left with a workaround plan instead. Name the constraint to your leadership as an adoption barrier rather than absorbing it as your own gap.
How many actions should a thirty-day plan have?
Three, named as actual steps rather than categories. The A.H.A. planner is deliberately strict about this: three specific actions in the next thirty days, not nine vague ones. A list of nine actions is a way of feeling productive without choosing, and it will not survive a busy week.
Build something that actually runs your workflow.
A focused, free 60-minute live session with Jacqueline. You build alongside her, on your own real task, and leave with an agent that is already running.