Most AI transformation advice is written as if companies were empty buildings you install software into. Then the rollout meets an actual team — people with mortgages, identities, twenty-year habits, and very good radar for leadership that isn't telling them everything — and the owner discovers what I learned rebuilding my own company: becoming AI-first isn't a technology project with a people problem. It's a people project with a technology component.
The good news is that the struggles are not mysterious. Having lived them through the 320-to-38 rebuild and watched hundreds of companies start the same climb, I can tell you they're predictable enough to plan for. Here they are — and the moves that get a team through.
Struggle one: fear wearing a skepticism costume
"I just don't think customers want this" often translates to "I'm scared about what this means for me." Argue the surface objection and you'll lose for months. Answer the real one and the resistance drains. The move: say the fear out loud before they have to — I'm scared and all in at the same time, and both are true — and then answer the only question each person actually has: what happens to me? Truthfully. Early. Individually.
Struggle two: identity welded to the old role
Your best people built self-worth on being the one who knows. When a system starts knowing too, it doesn't just threaten their job — it threatens who they are. The move is the SME Inversion, made explicit as a career path: expert → engineer of your own replacement → steward of the system you built. Put it in writing, attach pay and title to it, and make encoding what you know the most prestigious work in the building. Nobody defends the old world when the new one is a promotion.
Struggle three: uneven adoption
Three people race ahead, ten wait to see what happens, two quietly refuse. Left alone, this hardens into camps — the enthusiasts get resented, the resisters get protected, and the middle watches which side leadership actually rewards. The moves: make the racers teachers, not exceptions (their tricks become team playbooks, and teaching is compensated); give the middle structured on-ramps — real training, starting with the skeptics, not the fans; and give the refusers honesty instead of avoidance: the standard is coming, here's every support you'll get, and here's the date.
Struggle four: the middle-management squeeze
The layer that carried information up and decisions down feels the change first and hardest — much of what filled a manager's day is exactly the coordination work that moves from hours to tokens. If you don't redefine the role, managers will quietly defend the friction that justifies it. The move: redefine management as stewardship — owning systems, developing people through the inversion, and handling what machines escalate. Layers shrink; judgment gets promoted.
Struggle five: trust — in outputs, and in you
Early AI outputs will be wrong sometimes, and every miss becomes ammunition for "see, it doesn't work." Meanwhile the team is auditing something bigger: whether your story stays consistent when things wobble. The moves: put humans in the loop where errors are expensive and remove them where they're just slow; treat every miss as a system to improve, not a verdict; and never oversell — the fastest way to lose the room is promising magic and delivering a draft.
Struggle six: recalibrated expectations
Strangest of all: succeed, and your team's sense of normal resets in weeks — seven minutes becomes an outrage because it used to be five, and the three-year miracle disappears from memory. Once you're AI-first, you have to catch your emotions — yours and theirs. The rituals: keep the old baselines written down, celebrate trendlines quarterly instead of increments, and triage regressions by the line, not the feeling.
What it sounds like from the inside
Don't take my word for how these struggles feel — my team wrote it down themselves, on the record, for the book. Camille, who runs our digital marketing strategy, on the pace:
"We move fast here. Like, sometimes uncomfortably fast… There have been more than a few times I've had to physically get up from my home office, walk outside, plant my bare feet in the grass, and just breathe for a second before going back in." — Camille Porco, Sr. Director of Digital Marketing Strategy
And Clay, nine years in, on what it took to stop resisting the constant reinvention:
"It took me a good two years to fully make peace with that rhythm… I made a decision: I was going to go with the flow, whatever the flow was, because in all my years working for her, not once has she steered us down the wrong path." — Clay Howard, Sr. Director of Business Development
Notice what both are describing: the struggle is real, it does not fully disappear, and the people who come through it aren't the ones who found it easy — they're the ones who watched the results long enough to trust the direction. Their full, unedited entries are in Voices from the Team.
The through-line: the letter you owe your people
Every struggle above has the same root — uncertainty about whether leadership sees them, and the same medicine — the truth, early, with a path attached. That belief is why I wrote Hands Up as a letter to the generation that will inherit what we build, and why the people who came through our rebuild got the closing chapter of it (Voices from the Team). Bring your team with you and the transformation compounds — leave them behind and you'll rebuild twice: once for the technology, and once for the trust.
If your leadership team needs to hear this before they'll move, that's the keynote — and the Operator's Field Guide turns the book into the meeting agenda.