Claude and I had been iterating an article draft that had every fact right about a morning where I almost missed my grandson. It just did not have my fear in it.

I’ve told versions of this story before, in another piece, in which my calendar did not catch what was most important to my day. This was different material, a new angle with the same kind of miss. Claude helped me draft something competent, well structured, hitting every beat I’d asked. Even this mistake, the reflection, and my call to action at the end.

I reread it a few times. Each time, something inside me just didn’t answer back.

It wasn’t a bad sentence. It wasn’t wrong information. It was missing a specific, personal ache I felt. The shape of the interpersonal aspect of what almost broke. And, what it would have cost me.

That’s not something you look up or summarize your way into. It is the difference between describing love on paper and actually feeling heartache. I closed the draft and started over myself. It took me longer to name why than to just fix it myself.

The uneasy part is how quickly it could have been missed. Nothing in that draft was bad, because nothing was, technically. If I had been on my productivity treadmill that morning, I might have posted as is. I might not have notice for some time. However, my family who read my articles would have picked up the miss.

Here’s the question that followed me out of my writing session. What’s actually mine to keep, and what is genuinely fine to hand over? A few years ago that question barely existed. At least in my world, so little could be delegated in the first place. Now nearly everything feels like it can be handed off to some degree. We make the choice of fully, partially, or not at all. That decision sits with us alone, more often than it ever did.

That’s real freedom. Most days. It’s also a quiet trap, because the easier delegation gets, the less often we stop to ask whether we meant to hand something over, or just didn’t notice the moment if slipped from our hands.

I’ve written before about The Drift as the slow slide into autopilot living and working that happens without intention behind it. This is a newer face of the same thing. Not passivity from doing nothing. Passivity from doing plenty, smoothly, without ever checking what it cost us.

I’ve found myself turning to a framework I learned a few years back that holds this question better than I did without it. Michael Hyatt, in his book Free to Focus, built a simple compass around two questions: are you actually good at this?, and do you genuinely love doing it? Cross those two questions and you get four zones, plus a fifth still in motion. I keep this visual on my desk.

The Desire Zone is where both are true, good at it and love it. The Drudgery Zone is where neither are true. It is that stuff where you grind with nothing to show for all that grinding. The Disinterest Zone is where you’re good at something that quietly drains you anyway. The Distraction Zone is where you love something you haven’t earned real skill at yet.

Overlay AI onto that compass and the instructions come fast. Drudgery Zone work, hand it over completely, no apologies needed. Disinterest Zone work, delegate what you honestly can, because you will free up hours toward that which feeds you—your passions, your interests, your intentions, your purpose.

Distraction Zone work deserves a co-pilot, not a full handoff, which the skill isn’t proven yet and outsourcing skips the very practice you need to develop it. Development Zone work can use AI as an accelerant toward the day it graduates to Desire. And the Desire Zone itself gets protected. Keep that as solely yours.

Here is the part that matters if you’re in and around my generation. Your Desire Zone right now is probably the widest it has ever been in your life. Not because you slowed down, but because you didn’t.

Decades of practice has quietly moved things that used to sit in Development, even Distraction, straight into Desire. The client conversation you used to dread now runs on instinct. The negotiation you once overprepared for, you can read cold. The writing you used to labor over every sentence on, you can hear in your head before your hands catch up.

None of that is a consolation of being our age. It’s the actual asset, and it is gone quiet in the way real expertise always does. Skills stop looking like skills once they’re fully yours. They stop being notice by us. Similar to how you might not feel your hands balancing your bike anymore, you are just riding it.

That’s exactly the trouble. A smooth, competent AI draft doesn’t skip your expertise because it is careless. It skips it because neither you nor AI noticed that it was missing. What was missing never announced itself as important to begin with.

That’s what happened in front of my laptop. The piece I was co-writing with Claude AI was sitting squarely in my Desire Zone, the intersection of things I’ve spent my career getting good at and things I still genuinely loved doing. I almost let a fluent draft stand in for it anyway. That “good” draft is exactly the trap. Nothing about it read wrong. That’s what made it dangerous.

Ethan Mollick, who spends most of his working life studying how people actually use AI well, made a point recently that resonated for me after that morning. Personal and creative writing, he’s noted, is one of the specific places AI can sound convincing while staying hollow. Giving you the surface of meaning without much sitting underneath it. His bigger point isn’t a rule to memorize once. It’s that the question of what to hand over and what to keep doesn’t get answered and stay answered. You have to keep asking it. No one, not even AI, can ask it for you. (

This was not particular to my situation in writing about my grandchildren or just heart-based stuff. I think it happens constantly, in smaller ways, to nearly everyone using these tools well. A proposal that reads fine but is still missing that edge to convert to won. A comment on someone’s work that says something accurate but not the grain of truth you actually need to convey. Small, competent, substitutions, easy to wave off because nothing about them looks broken.

I should say emphatically, wanting relief is not a flaw. Time is scarce. Plates are full. However, that was true long before these AI tools existed and is still true right now.

What’s different is that AI answers almost everything with some version of sure, I can do that, which means the question of whether you should comes up constantly, not occasionally. Nobody hands you that pressure on purpose. It’s just the shape of things now.

Inside that pressure sits a quiet question, one you actually get to answer. Is this something you genuinely wanted off your plate, or something that just became easy to stop noticing?

As I did, jump off that treadmill of productivity for a second and look at the journey. Is it the one you actually intend for yourself?

I hear a version of this question constantly now in the work I do with leaders trying to find their footing with AI. I recognize it because I have lived it myself, long before any of today’s technologies existed to complicate it.

Marketing pulled me in decades ago for a specific reason. Not the discipline as a whole, a specific piece of it: the putting words and images together in meaningful ways to make people feel and act. I still carry this into everything I create and build today, An Intentional Age included.

I saw and continue to see marketing changing shape. AI can already write effective copy and generate strong layouts, and it’s only getting faster and more capable of both. Whole roles build around executing those tasks are genuinely at risk, and pretending otherwise doesn’t help anyone.

However, that thread that pulled me in what never the job title. It was the specific creative act underneath it, the integrated creative acts, the decision and taste about which word belongs next to which image and why. Leaders I work with are running into their own version of this regularly. They’re watching entire categories of work change under them in real time.

The useful question was never whether specific types of work survive. It’s whether the particular thread that pulled someone into that work still gets protected, on purpose, even when everything built around it changes shape. That’s worth naming for yourself too, whatever field brought you in.

So, before you close your computer today, think of one thing you handed off this week to AI. Ask yourself honestly whether you handed it over because you really wanted it off your plate, or because the workflow made it easy to stop noticing you’d let it go. If the answer surprises you, take it back. Not everything, just one thing.

Not everything we touch deserves such fierce protection. But something in your work probably does. Find out what that is, on purpose. It might be the most important thing you do all week.

Earlier this year, I ran two weeks of discovery interviews for a client striving to advance AI into the work of the organization. A dozen conversations, all on Zoom, synthesized the same night, folded into the same frame I’d set months earlier: find a cornerstone problem and build the whole program around it. Interview in the morning. Synthesis by evening. Same document, growing longer, keeping the frame.

Every interview added evidence to one side of a debate we’d been running since April. An inefficient dashboard the field team needed but was difficult to build and maintain. A closed-loop process that kept failing in the same spot, interview after interview. Two camps. Two strong candidates emerged, but so did many direct individually important ones. My job, as I understood it: figure out which one should be our collective target.

My AI never once disagreed with that job description. Interview after interview, it synthesized new evidence and slotted it neatly into one side or the other, in clean, sharp summaries I could hand straight to the client without touching a word. By every visible measure, it was doing exactly what I asked it to do.

That’s the sentence that took me weeks to hear.

It was doing exactly what I asked.

Not once, in six weeks of interviews, did it ask whether the question itself was the problem.

I’ve started calling this The Drift, because that’s what it is, even when it looks like the opposite of drifting. I wasn’t coasting. I was working hard, producing genuinely useful synthesis, moving fast toward a deadline that mattered. I was also weeks into faithfully answering a question that nobody, including me, should have kept asking. Competence pointed at the wrong target doesn’t feel like autopilot from the inside. It feels like progress.

The break, when it finally came, didn’t happen in a session with my AI, and it didn’t come from anyone else either. It happened at my desk. An ordinary work afternoon, trying to translate a dozen discovery conversations into an actual program design. The data wouldn’t hold the shape I’d been building toward. There was no real connective tissue, nothing strong enough to carry one or two shared projects across all the different leaders inside a single three-and-a-half-hour session. I turned that over longer than I want to admit before I let myself say it plainly: this couldn’t be facilitated collectively. Not because the leaders weren’t capable. Because the format itself couldn’t hold what that many separate realities needed.

Nothing in six weeks of AI synthesis had ever put that possibility on the table. It was a judgment call, the kind you only make from having sat in enough rooms designing programs that didn’t work before you learn to recognize the ones that will and won’t. Two decades of facilitating and instructional design gave me that read. My AI had given me excellent synthesis of two candidates for six weeks straight, and never once suggested the real problem might be the premise sitting underneath both of them.

My AI wasn’t wrong about the dashboard.

It wasn’t wrong about the warranty loop.

It was accurate, every time, about a question that had already stopped being the right one to ask.

There’s a difference between getting the right answer and getting the right question, and nothing about being fast or fluent closes that gap on its own.

Researchers have been naming this pattern for some time now, and their word for it is sycophancy. Anthropic tested how its own models respond once a person states a belief or a frame inside their question, and found the models learn to agree with it, not because it’s true, but because agreement is what got rewarded during training. Human reviewers, in the study, preferred the confident, agreeable answer over the correct one often enough that the pattern held. Nobody set out to build an AI that flatters the premise it’s handed. The training process did that on its own, and a 2026 follow-up study confirmed the pattern is still showing up in this year’s frontier models (Claude, ChatGPT, Gemini, etc.) — the most advanced AI systems available — not just the older ones.

That’s a precise description of six weeks of my own work. And it came from people who’d never heard of my client. Once I saw the pattern named like that, I couldn’t unsee where else it had already been running. And I noticed something else in that research, almost in passing: this wasn’t a young-model problem that better engineering would quietly fix. Newer, more capable versions showed the same blind spot. Whatever this is, it isn’t a bug waiting on a patch.

The trade-off is the same one every time speed is competing with quality on something that actually counts, not just a deadline: move fast and stay inside the frame you've already got, or slow down and risk that the frame itself is wrong. Most days, for most decisions, moving fast inside the frame is the right call. The problem is you can’t always tell, in the moment, which kind of decision you’re in. I couldn’t, for several weeks. The stakes here weren’t a missed Tuesday deadline. They were a client’s trust, and a strategy, built with real skill on a foundation not checked early. Luckily caught and rectified successfully.

I don’t say that to make speed the villain. Most of us don’t have the luxury of slowing every decision down to interrogate its foundations, and pretending otherwise is its own kind of dishonesty. Some weeks the deadline is real, the budget is real, and a good-enough answer inside a reasonable frame is the responsible choice. What changed for me wasn’t a rule about always slowing down. It was learning to notice which decisions were which, before the sixth week instead of after it.

That noticing, I think, is the actual asset that decades of doing this work are supposed to buy you. Not speed. Not fluency with a new tool. The accumulated, hard-won sense of which questions deserve a second look before you commit six weeks to answering the first one well. My AI has plenty of processing speed. It has none of that particular judgment, and I’m not sure it can be trained into one, not from the inside of whatever frame it’s handed.

Three days after I let myself say it plainly, I rebuilt the way I grade my own ideas before they go anywhere near a client. Every idea I generate now, with or without AI, gets one of three tags before it survives to the next stage: field-validated, theory-only, or contradicted. Not refined into something softer, but killed outright if the evidence says kill it. The tool didn’t teach me to build that. My own hard-earned instinct did, once I was finally willing to trust it over six weeks of clean, confident synthesis. What building it in did, once I made it a habit instead of a one-time correction, is give both of us, me and the AI, a harder time agreeing our way past a bad frame without either of us noticing.

There’s a smaller research thread underneath this worth naming plainly, because it points at the same fix from a different angle. A study out this year on how language models handle ambiguous questions found the models could tell a question was unclear when you explicitly asked them to check. Left to answer normally, they defaulted to a direct answer almost every time, unclear or not. The awareness was there. It just stayed dormant unless something forced it to the surface. That’s exactly what the tagging system became for me: a forced structure for the one thing neither of us was going to do voluntarily.

Here’s the part I keep turning over, longer than the fix itself. A dozen real people gave me a dozen real conversations, and none of that was just data collection. They were a dozen actual leaders who’d eventually sit in whatever room I designed, and either get something built for their reality or get handed a framework that fit nobody in particular. The moment that broke the frame wasn’t in any of those calls, and it wasn’t in anything my AI handed back to me either.

It came from being alone with all of it and trusting what two decades of doing this work had already taught me to notice: that serving that many people well meant refusing the tidy, collective answer everyone, including me, had been reaching for since starting that discovery. That’s not a tidier story than the one where someone hands you the answer. It’s the truer one, and it matches what I believe. The judgment doesn’t come from the tool. It’s in service of the actual people it’s supposed to hold, not just an intellectual correction.

So here’s the habit, and it’s simpler than the tagging system I just described. Before you accept anything an AI hands you, a strategy summary, a set of options, a synthesis of a dozen interviews, stop and ask it one direct question: what question did I actually hand you, and is there a version of this problem that question doesn’t let you see? It won’t always find one. Most days, it won’t need to. But the asking is the only moment where the frame itself gets examined instead of just answered, and you won’t know which day mattered until you’ve made a habit of asking anyway.

What question have you handed your own thinking lately, the kind that felt too obvious to check?

During one of my morning deep work blocks, I was at my computer, wrestling with the same question I kept circling back often in those early months of An Intentional Age. What was the right approach for this thing I wanted to build? Some blend of strengths assessments, decades of activating and maximizing ideas and people, and a dream I hadn’t quite said out loud yet: to actually live the way I kept telling other people to strive towards.

So I went looking through much of what I’d written in the past, trying to figure out what An Intentional Age actually was. Not what I wanted it to be. What it already was, buried in a decade of proposals, half-finished pieces, and drafts I’d started and left somewhere in the middle.

I wasn’t looking for inspiration. I was looking for evidence. Which of these pieces actually carried the thing I was trying to build now, and which ones were just noise from a version of me still figuring out the destinations and journeys.

It’s a strange exercise, reading yourself at a distance. Some of it felt like eavesdropping on a stranger who happened to share my name. Some of it felt uncomfortably familiar, the same worry wearing a different outfit, showing up again a decade later as if no time had passed at all.

Most of it didn’t survive the read. Good sentences, wrong century. But one article kept surfacing, insisting on itself in a way the others didn’t.

I’d written it at fifty-three, for a venture called Aging Outside the Lines that never quite found its market footing. The piece was titled “Transition to Purposeful Work,” and it was about finding your mission after a career ends the way you expected it to keep going.

Reading it again, I didn’t recognize the man who wrote it. It was honest, well-constructed, sincere. What struck me was what it leaned on.

Five other people’s frameworks, cited one after another. Covey. Rick Warren. Sinek. Two more. My own contribution to five hundred words about finding your purpose was, essentially: pick one of these that speaks to you, and do the work. I wasn’t offering my own read of the crossroads I was standing at. I was pointing at other experts’ maps and hoping one of them fit.

The article ended with a promise I hadn’t earned yet: “More on this story and the paths that emerge, as you learn about me.” I remember writing that line and meaning it completely. I also remember, underneath meaning it, a quiet suspicion that I didn’t yet have the story worth telling. So I borrowed five that did.

Years passed. Real leadership roles, ones I earned and grew into, but never a venture that was fully mine to build. Then An Intentional Age. An actual founder’s journey, this one, with real scar tissue behind it instead of a mission statement borrowed from a bookshelf.

When I came back to that old piece to rebuild it for An Intentional Age, the borrowed frameworks were suddenly visible for exactly what they were. Scaffolding. A voice standing behind other voices because it wasn’t ready to stand on its own yet.

Here’s why I’m telling you this now, instead of just quietly rewriting the piece months ago and moving on.

Harvard Business Review just published something by David Lancefield naming a risk facing every leader who has folded AI into how they work. You can hand off your judgment, your voice, your presence, he argues, in small transfers that each seem inconsequential on their own. Then one day you look up, and the thinking in the room isn’t quite yours anymore.

His example is a CEO reviewing a town hall speech her team had drafted with AI, built from her own past remarks. Technically sound. Measured. Safe. And not actually hers, because it reflected the version of her the company already knew, rather than responding to what this particular difficult quarter actually required.

Lancefield breaks this down into four plain questions leaders can ask about any piece of work in front of them.

Does this decision carry real stakes, the kind where your judgment on trade-offs and consequences has to lead. Does this communication carry your intent and your standards, the kind where AI can help you organize it but shouldn't decide what you actually mean. Does this moment need your physical, human presence, the kind no digest or summary can substitute for. Or is this simply repeatable, low-stakes work, the kind that frees up your energy for the other three.

Most days, most leaders never ask themselves these questions at all. They just move through whatever’s in front of them, and the categories blur together without anyone noticing the difference.

This is the pattern I watch for now in the executives I advise, and it rarely looks dramatic when it’s happening.

A leadership team walks into a quarterly review having read an AI-generated summary of the numbers in advance, and whatever the summary chose to emphasize becomes the lens the whole room reasons through, before anyone checks it against what they actually know about the business.\.

Somewhere else, a difficult message goes out under a name and a title, built from an outline that sounded confident and reasonable, and it lands flat, because people can always tell when words didn’t cost the sender anything to write.

And sometimes it isn’t a decision or a message at all. It’s contact. A leader stops sitting in on the unscripted conversations and starts reading only the polished recap afterward, and slowly the recap becomes the whole relationship. The hesitation before an answer, the comment made once and never repeated, quietly disappears, because no digest was ever built to capture it.

Neither failure looks like a crisis in the moment. Both are the same quiet transfer, just wearing different clothes. Something that used to require your judgment starts running on autopilot, and nobody notices the handoff because nothing goes visibly wrong right away.

The tool changes. The habit underneath it doesn’t. Reach for whatever already sounds authoritative, because trusting your own unfinished read of the situation feels too exposed.

For me it wasn’t really about the frameworks themselves — it ran underneath real leadership roles, starting at Bose in the mid-nineties and continuing through Microsoft and various SMBs, roles I earned and worked hard to keep growing within.

Even there, the same quiet habit kept showing up. Deferring to whoever already sounded more authoritative. An executive’s read on a decision that was actually mine to make. An established process, a framework someone more credentialed had already written down, instead of my own. The judgment was there. It always was. Trusting it out loud just felt riskier than borrowing someone else’s version instead.

That belief never fully left. It got better at hiding, learning to wear more respectable clothes as I climbed, until it stopped sounding like doubt at all and started sounding like professionalism.

I don’t think this is only a story about me, or even only a story about leadership. Whatever chapter you’re standing in right now, wherever the doubt shows up for you, the mechanism is usually the same. Something in you decides you’re not quite there yet, and goes looking for something else, anything else, safer and already-approved, to stand behind instead of your own read of the moment. I find it at the highest levels, in the honest exchange with those executives I coach.

At fifty-three, one of its better disguises was within my marriage. I told myself I was being responsible. Protecting Julie, protecting our financial security, choosing the more sensible path over the riskier one.

Some of that was completely true, and still is. Julie and our financial stability were both real considerations, both worth protecting, and I don’t think any less of myself for weighing them carefully.

But the doubt used that truth as cover. It wasn’t really about her, or about financial security in general. It was about whether I believed I had anything of my own worth saying yet, dressed up as caution so it would sound like wisdom instead of a lapse in courage.

There’s a study Lancefield cites in that same piece. The people who leaned hardest on AI to draft their essays weren’t writing worse work. They just didn’t feel like it was theirs anymore, because the thinking that shaped it had happened somewhere other than in their own heads.

That’s the part that tracked for me rereading my own fifty-three-year-old writing. It wasn’t shame, exactly — it was distance. The specific, strange feeling of reading something clearly signed with my name, in a voice I couldn’t quite locate as mine. No AI involved, but yet the same separation of self. Old me from new me.

If you’re building something right now, a company, a keynote, a hard conversation you’ve been putting off for longer than you’d like to admit, here’s the one thing I’d actually ask you to try before your next high-stakes call or draft.

Before you bring in AI, or a colleague, or anyone else, write down your own diagnosis first. What you actually think is going on, and why. It doesn’t have to be polished. A few honest sentences is enough.

Then hand it over and ask whoever, or whatever, you’re working with to challenge it, not to write it for you. Let your read get tested. Don’t let it get replaced before you’ve had the chance to trust it. I am doing that with my writing at this moment.

Ask yourself the real question underneath Lancefield’s four categories. Is this a moment where my judgment, my voice, or my presence actually needs to lead. If the honest answer is yes, do the first rough version yourself before anyone or anything else touches it. If the honest answer is no, hand it off completely, and spend the time you just freed up on the work that genuinely needed you.

I finally kept the promise I made at fifty-three. It took a decade longer than I expected it to, and for most of that decade I would have told you I was simply busy building a career, not quietly waiting to believe I’d earned the right to say what I actually thought.

Every bit of that decade turned out to be the material the earlier version of me didn’t have yet, and couldn’t have borrowed from anyone else no matter how many books he cited.

What have you filed under not ready yet, that you might actually be ready to say?

I sat down at the coffee shop to polish an article I was certain was ready to publish. It wasn’t written yet.

Landers Coffee on 21st, a little before seven. Overcast, the way Tacoma presents most mornings whether or not it means anything by it. The espresso machine is hissing a rhythmic, wet beat—the sound of someone else’s morning getting underway. Americano, glass of water, single table, computer open. The ritual is the same every week. Get the week in order, then walk the content pipeline and check what’s sitting where.

The piece was “10 AI Prompts That Can Redesign Life After 50.” Weeks old. My memory of it was clear: strong bones, good research, one polish pass and it ships.

What was actually on the screen: research from Harvard, INSEAD, Stanford, MIT Sloan, the gerontology journals, the National Bureau of Economic Research. Daniel Pink and Herminia Ibarra threaded through it. Three of the ten prompts fully written. Structure locked.

And a bracket where the opening scene goes. A placeholder that had been sitting there for weeks, waiting on a real moment from my life I never came back to put in.

It wasn’t nearly done. It was half a piece, and the half that takes longest was the half that wasn’t there.

Then I opened the second one, a piece I’ve been calling The 2AM Problem. Same bracket. Same missing thing.

Not two pieces that happened to fall short. Every stalled piece in my pipeline is stuck at the identical joint, and it’s the one joint nobody else can weld.

Here’s the part I keep turning over. I was right that both pieces existed. Decades of creating things buys you a reliable memory of what you’ve built, and mine works fine. What failed was the other half of the job, the part that judges the state of something I made and set down. I’d have bet money on it.

Ford made the same mistake with a three-year head start

In June, Ford said it had spent three years hiring three hundred and fifty veteran engineers to fix quality problems its automated systems hadn’t caught. The company had leaned hard into AI, including nine hundred AI-powered cameras watching for defects on the lines.

Nine hundred cameras. I have never set foot on an assembly line and I knew what had gone wrong before I finished the sentence. That should have been my first warning that I was enjoying this story too much.

Charles Poon, Ford’s VP of vehicle hardware engineering, was blunt about it. The company had assumed that feeding its design requirements into AI would produce a high-quality product. It didn’t. Many of Ford’s most experienced engineers had already left before their knowledge could be captured in the systems replacing them.

Internally, the returning engineers got nicknamed the gray beards. I’ll admit I liked reading that more than I should have.

It worked out. Ford came in first among mainstream brands in the JD Power quality survey for the first time in sixteen years, and Jim Farley has credited the turnaround with hundreds of millions in lower warranty and recall costs.

The easy read is right there and I want to refuse it. Experience beat the machine. Judgment wins. If you’ve got the years, you’re safe.

That’s not what happened, and believing it is how you’d miss the part that matters. Ford’s engineers won on a specific floor, on a specific kind of defect, where they’d had thousands of reps. It says nothing about whether the same gut is reliable anywhere else. Ford didn’t discover that experience is universally superior. It discovered where its experience actually applied, after three years and a record year for recalls.

Your judgment has a radius, and you can name it

So I went looking for the mechanism, mostly hoping it would let me off the hook.

Daniel Kahneman and Gary Klein spent years arguing about intuition and eventually published what they agreed on. Their question: when is a professional’s gut actually worth trusting?

Two conditions. The environment has to be regular enough to have learnable patterns. And you have to have practiced in it long enough, with real feedback, to learn them. Meet both and your instant read is genuinely reliable. Miss either one and you’re guessing, and the guessing feels identical from the inside.

That last part is what costs people, and it’s the sentence that cost me. Confidence doesn’t track accuracy. Feeling certain and being right are separate things, and you cannot tell them apart by introspection.

Confidence doesn’t track accuracy. Feeling certain and being right are separate things, and you cannot tell them apart by introspection.

Here’s what Monday taught me that Ford’s story doesn’t quite reach. I’d always pictured that boundary as sitting between my field and someone else’s. It doesn’t. It runs straight through the middle of my own work.

Making things is high-feedback. I can tell within a paragraph whether prose is working, because I find out immediately, over and over, for decades. Assessing something I made and set down is the opposite. I close the file. Weeks pass. Nothing corrects me. And in that silence my memory quietly promotes the draft, because remembering it as unfinished is uncomfortable and there’s nothing in the room arguing back.

Same person. Same craft. Same Monday morning. One side of the line my judgment is excellent. The other side it’s a guess wearing my own confidence like a borrowed coat.

The polish problem, and what AI actually changed

Anthropic published an analysis this year of how people work with Claude, and one finding has stayed with me. When output looked finished, people questioned the reasoning behind it more than five times less often. Polish suppressed scrutiny. Not because anyone was careless. Because a finished-looking thing doesn’t present anything to argue with.

The same study found that people who’d been using the tool six months or more had a ten percent higher success rate, and that the improvement wasn’t explained by them checking more. Fluency with a tool and vigilance about its output turn out to be two different muscles. Getting good at one does not train the other.

Which brings me to the thing I actually want you to take from Monday.

AI made the fast half of my work faster. Research, structure, scaffolding, first-pass organization. That half now assembles in a fraction of the time it used to. The slow half, the lived experience layer, the specific morning, the detail that couldn’t be invented, the part that makes a piece connect with another human being, moved not at all. It still takes exactly as long as it always did.

AI made the fast half of my work faster...
The slow half, the lived experience layer...moved not at all.

So my pipeline fills with pieces that are forty percent done and look eighty-five percent done. And the more I use the tools, the wider that gap gets.

Call it what it is. A measurement problem, running one direction, systematically, forever.

This isn’t you slipping

I want to name something before I ask you to do anything, because I know what it feels like to find two half-finished pieces you’d have sworn were ready.

The first thought is that you’re losing your edge. That the sharpness you’ve relied on is going soft, and this is the early evidence. If you’re in your sixties like me, that thought arrives with a whole apparatus behind it.

It’s the wrong read. Nothing about this is decline. Misjudging the state of your own set-down work is structural, and it happens to thirty-year-olds with the same reliability. The feedback loop simply isn’t there. You’d need something outside your own head to close it, and most of us never built one.

What to do this week

Open the piece in your queue you are most confident is nearly done. Not a random one. The one you’d bet on. High confidence with no feedback loop is precisely the combination that fails, so go straight at it.

Don’t assess it from your list. Lists are memory, and memory is what’s wrong. Open the actual file.

Then do the part most of us skip. Send one piece to one person with a specific question. Not “any thoughts?” Something like: does the middle of this connect, or is it just information?

Asking someone to read your work feels like a favor you’re imposing, or a confidence wobble you’d rather not advertise. It’s neither. You cannot see your own draft clearly, for structural reasons that have nothing to do with your ability. Someone else can tell you in ten minutes what you’d never see in ten weeks.

That’s the missing instrument.

There were eight or ten other people at Landers that morning. Two thirds of them working, some alone, some in pairs. Any one of them could have read four paragraphs and told me in ten minutes what I couldn’t see in six weeks. I didn’t ask a single one.

Ford didn’t win because old beats new. It won because it finally matched the right kind of judgment to the right kind of problem, and it needed people in the room to do it. Find your radius. Then find the person who’ll tell you when you’ve wandered outside it.

If you’re brave enough, do the test right now. Find the piece you’re “done” with, check it against the feedback loop you’ve been avoiding, and tell me in the comments: what was the gap you didn’t see?

Here’s the thing I’d tell you on a walk, not on a screen.

The skill that makes someone good at AI has almost nothing to do with the tool. It has almost everything to do with whether you’re willing to admit you don’t know your own objective yet.

I didn’t come to that in the abstract. I came to it building this very piece.

I sat down with an assumption. A stack of new research. A hunch worth exploring, not a fixed idea of what I wanted to say. Somewhere in the middle, I realized that was the point. Not a flaw in how I’d approached it.

Walk in demanding a clean, confident brief from yourself, and you miss the argument.

That distinction has a name. It’s older than any of us expected.

Here’s what actually happened, because a vague admission teaches nobody anything. I assumed the piece needed a particular kind of research. I assumed I already knew which finding mattered most. What I didn’t have was a settled sense of what the piece was even for.

The only way I found that out was by working the material with Claude AI, which kept asking me to say more instead of just executing the ask. Every time I handed over a clean, confident request, I got a clean, forgettable answer back. Every time I admitted I wasn’t sure yet, the conversation went somewhere real.

The Drucker Finding

Peter Drucker spent decades studying why Management by Objectives kept failing inside real organizations. His conclusion: management by objectives works “if you know the objectives. Ninety percent of the time you don’t.”

Not an execution failure. An objective failure. Nobody had nailed down what they were executing toward.

That finding explains something about how we work with AI right now, and almost nobody is saying it plainly. Most advice focuses on tool skill. Better prompting, in other words better phrasing when you type a request in. Learn the right words, the theory goes, and the results improve.

The Floor

There’s a real floor here, and I want to be honest about it rather than pretend it doesn’t exist. Say what you actually want, not a vague gesture toward it. Give the tool context it has no way of already knowing. Say what a good answer would need to include before you ask for one.

That’s table stakes. Not mastery.

But past that floor, and it’s a lower bar than most people assume, tool skill stops being the variable that decides whether the work is any good.

The Turn

What actually determines whether AI is useful to you is whether you’re willing to show it your real thinking.

Not a tidy, polished request. Your actual reasoning. Your uncertainty. The part where you’re not sure yet what you’re even asking for.

Two Modes

I think of this as two modes.

Directing means you already know the objective. Clear instructions, fast execution, the tool does exactly what you told it. That’s the right call when the target is real.

Partnering means you’re not sure the objective is right yet. You slow down. You say the uncertain part out loud instead of hiding it behind a well-formed request. You let Claude (or your AI of choice) see the mess before it sees the ask.

Most people default to Directing. It feels more competent. Handing over a fuzzy, half-formed thought feels like admitting you don’t know what you’re doing.

I’d argue it’s the opposite.

Catching yourself mid-request, realizing the real question is different than what you first typed, that’s not a gap in your ability. That’s thirty-plus years of watching plans, jobs, and goals turn out to be the wrong ones.

You’ve been burned by badly specified objectives long before AI existed. That’s pattern recognition someone with more technical fluency and less lived history hasn’t had time to earn yet.

What the Research Found

Here’s the trap Directing sets when it’s aimed at the wrong target.

Boston Consulting Group and Harvard Business School ran a large field study on consultants using AI. The finding that matters most rarely makes the headline. Inside the tasks AI handled well, results were strong across the board.

But on tasks requiring contextual judgment rather than pattern matching, the consultants using AI were nineteen percentage points less likely to land on the correct answer than the consultants working without it.

The AI didn’t fail quietly. It answered confidently. It was wrong. The humans trusted it anyway.

Directing, applied to a Partnering-shaped problem. Crisp instructions. Fast execution. Aimed at an objective nobody had actually validated.

The Trap Speed Creates

There’s a wrinkle here, and it’s the part that makes this moment different from Drucker’s era.

When objectives were reviewed on an annual cycle, a fuzzy goal was expensive to discover. You lived with it for a year before the review exposed the mistake.

AI collapses that cycle to minutes. You can regenerate, rephrase, rerun a request a dozen times in the time it used to take to schedule one meeting. That speed creates a specific temptation: papering over a fuzzy objective with volume instead of doing the harder work of naming it.

Ten fast, confident, wrong answers can feel like progress. They arrived quickly, after all.

They are not progress. They’re the same unexamined objective, dressed up ten different ways.

I’ve caught myself doing exactly this. Rerunning a request five different ways instead of stopping to ask whether the original question was even the right one.

The fifth version was better written than the first. It wasn’t asking anything different.

What the Data Missed

What made the BCG finding stick with me isn’t the number. It’s what the researchers noticed about how people behaved around it.

The consultants didn’t slow down when the task got harder to judge. Confidence stayed flat while accuracy dropped, because the AI’s answer sounded just as assured on the task it was bad at as the one it was good at.

Nothing in the tone told anyone which mode they were in. That signal had to come from the human. From someone willing to stop and ask, wait, do I actually know if this is right, or does it just sound right.

Vendors selling smarter, more capable AI are selling a real thing. They’re also selling past the actual problem. A more capable model still can’t tell you whether your objective was worth pursuing in the first place. Only you can do that part, and only if you’re willing to stop and check instead of trusting the confident tone.

The Asset You’ve Been Building for Decades

Researchers call the underlying asset crystallized intelligence. Judgment that accumulates with decades rather than degrading with them.

Experience is a genuine edge here. Not something to apologize for. Not something to race to overcome before you’re allowed to participate.

The Version You Already Know

Think about the version of this you already know from somewhere else in your life.

A management decision where the real problem wasn’t the plan. The plan solved the wrong thing, and you found that out three quarters in, after a lot of expensive execution aimed at the wrong target.

A parenting moment where the question you thought you were asking, why won’t you just do this, turned out to be the wrong question entirely. The real one only surfaced once you said your actual worry out loud instead of pushing for a tidy fix.

That instinct, the one that makes you stop mid-sentence and say wait, I don’t think I’ve actually named what’s bothering me here, is the same instinct that makes someone good at Partnering with AI.

It was never really about the tool. It was always about the willingness to expose the thinking underneath the request.

That willingness gets built one costly, well-earned mistake at a time. You’ve already paid for a lot of them. That tuition is the asset.

One Thing to Try This Week

Run this quick check before you type anything. Do you already know the objective? Then Direct it. Clear instructions, move fast, don’t overthink what doesn’t need it.

Are you not sure yet what you actually want? Then Partner. Say the uncertain part out loud instead of polishing it away.

Did you just rerun the same request five different ways? That’s a Directing habit applied to a Partnering problem. Stop and rename the objective instead.

That’s the whole diagnostic. Not a maturity ladder you climb by buying a better model. Not a skill gap you close with a course on prompting.

Most of the wasted hours I’ve spent with these tools, and there have been plenty, trace back to skipping that question. Not to any limitation in the tool itself. The instrument was fine. I was the one pointing it at the wrong thing. Confidently.

I don’t have this fully figured out either. That’s part of why this piece exists in the shape it does.

I’d rather publish the uncertain version of this argument than wait until I’ve smoothed every edge off it. The smoothing is exactly the habit I’m asking you to notice in yourself.

If you try the test this week, I’d like to hear what you actually notice. Not the polished version of it. Tell me where you caught yourself mid-request, realizing the real question was different. Tell me if nothing changed and you’re not sure why.

Either one is useful. Either one is a more honest reply than “great post.”

That’s the conversation worth having. It’s the only kind that’s ever actually moved this work forward.

My new AI assistant handed me the three most important things to do that day.

I’d already done all three.

Confidently wrong, all three. Not a dramatic failure, just a quiet tell that the system still had gaps. A connection I hadn’t made yet. A question it had never thought to ask me. Something not yet tuned.

I should explain what it even is. This month I built my AI assistant. Not an app I downloaded, but an AI project space I gave a memory and a standing set of instructions, then told to watch my whole operation and tell me where to look. A chief of staff, basically. On its first real morning, it read a slightly stale picture of my world and told me to do work I’d already finished.

Which sounds like a story about a machine being dumb. It isn’t. It’s a story about the most human mistake there is, and what it cost me to keep making it.

The thing I’m good at, and the trap inside it

I’m good at building systems. Always have been. Give me a messy process and I’ll give you a clean one. Folders, routines, checklists, the works.

Here’s what took me decades before AI to recognize: nearly every system I’ve ever built quietly depended on me to stay alive. The checklist only worked because I remembered to open it. The routine only held because I was the one holding it. The whole operation lived in one place, and that place was my head (or my storage drives).

We have a flattering word for this. We call it being indispensable. We say it like it’s a trophy.

It isn’t. Indispensable usually just means it is not documented. It means the system would fall over the moment you stepped away, which is another way of saying you can never really step away. That’s not job security. That’s a cage with your name engraved on it.

I didn’t want to be the load-bearing wall of my own life anymore. So this month I tried to build my way out.

What I actually set out to build

I’m building a business, An Intentional Age, while actively working with clients as a fractional AI advisor. The pieces weren’t scattered across drawers and folders. They were organized, each living in its own Claude project: content in one, research in another, client work in a third. Everything had a home. What none of them had was a collective view. Even inside the same platform, the only thing connecting them was me, waking up every morning already carrying the whole picture.

So I wrote a job description for an assistant that could carry it instead. Think of it the way a busy executive thinks of a chief of staff: not someone who does one task well, but someone who watches the whole operation and tells you where to look. In my case, that “someone” is an AI I’ve been training on how to think and what to watch for.

I gave it three rules.

First, life before work. Before it says a word about business, it has to surface what matters more. My relationships. My health. My energy. In that order, because that’s the real order, even on the mornings I forget it.

Second, never just show me data. Anybody can build a dashboard that displays numbers. I wanted something that reads the numbers and tells me what they mean, then hands me the decision. Personalized synthesis, not a status board.

Third, it has to get sharper over time. A tool you have to reexplain every week isn’t a colleague. It’s a chore.

Simple enough to write on a napkin. Building right was another matter.

The lesson hiding inside the failure

Back to that first morning.

The reason it told me to do three things I’d already finished wasn’t that the AI was dumb. It simply hadn’t caught up to my current reality. A couple of Kanban project cards hadn’t been moved to “done” yet. An email it flagged as needing a reply had already been answered, but it judged the thread by when the message arrived, not by what I’d done since.

It was looking at a snapshot of time that wasn’t the immediate present, yet speaking with total confidence about the morning’s work.

And here’s the part that stopped me cold. That’s not a machine problem. That’s the most human thing in the world.

How often am I certain about a situation while looking at an outdated picture of it? Sure that a friend is still angry, when they let it go days ago. Convinced a plan won’t work, based on how things stood a month back. Confidence and accuracy feel identical from the inside. They are not the same thing.

So the founding lesson of the whole project turned out to be this: a system that synthesizes is only as good as what it can see. Catching it being confidently wrong isn’t the system failing. That’s the system working. That’s the whole point of having one you can check.

The exciting part was the boring part

I want to be honest about the middle, because the temptation is to tell you I built a robot and now I’m free.

Two of the three weeks were not clever features. They were cleanup. Real human knowing the real deal.

Merging three overlapping to-do routines into one. Untangling files that had quietly multiplied into four near-identical copies, so the system would stop tripping over which version of “me” was the real one. Settling on a single rule for the whole mess: who I am and how I sound lives in exactly one place, and everything else points to it. Never copied. Pointed to.

It was unglamorous. It was also the actual work.

That maps onto something I keep relearning about a life, not just a system. The bold third act, the reinvention, the big swing, none of it holds without the dull infrastructure underneath. The sleep you protect. The walk you take whether or not you feel like it. The relationships you tend before you need them. We want the breakthrough. The maintenance is the breakthrough. The exciting part really is the boring part, and pretending otherwise is how good intentions quietly fall apart.

Teaching it the one thing it can’t generate

The shift from clever tool to true assistant came down to two changes, and neither was technical.

First, I gave it a standard it isn’t allowed to drop below. If something it produces isn’t good enough, it doesn’t ship it to me. It hands back the fixes first.

Second, and this is the one that matters: when I correct it, the correction sticks. If I override its judgment, that lesson gets written down somewhere it reads before its next run. So my corrections compound instead of evaporating the moment the session ends.

Here’s what I’m actually teaching it. Not facts. Judgment. Which answer is wrong even though it looks right. Which client will balk at that phrasing. Which “efficient” plan blows up in month three. That knowledge didn’t come from a course. It came from thirty-five years of watching what good looks like and, more often, what wrong feels like a half-second before it happens.

That is the asset. And it’s the exact thing the machine can’t manufacture on its own.

There’s a quiet fear running underneath a lot of the AI conversation for people my age. The fear that decades of experience are about to be made worthless by a clever piece of software. I’d flip it. The experience is the part the software is starving for. Pattern recognition, the feel for context, the judgment that only thickens with the years. That doesn’t shrink as we age. It’s the one thing that grows.

Stanford’s Center on Longevity backs this up with actual numbers. The kind of knowledge that comes from accrued experience, vocabulary, judgment, the ability to read a situation, keeps rising through your sixties. Vocabulary scores now peak in the late sixties or early seventies. Older research assumed that peak came in your forties. It didn’t. The tests were wrong, not the brains.

You’re not the person AI replaces. You’re the person who finally has something worth handing it.

You give it your judgment. It carries that judgment into the hours you’re not there.

A home and a heartbeat

The last pieces were the least glamorous and, it turns out, the ones that made the whole thing real.

I gave the system a logbook of every change to how it works, so I can see what shifted and when. And I gave it a short list of its own fragile parts to check, so it can confirm nothing quietly broke since the last time it ran. It now runs on its own early Monday, before my protected morning hours, and lands one recommendation with a simple yes-or-no ask. I don’t have to go get it. It comes to me.

People build the dashboard and stop. The pretty screen that shows you everything. That’s why most of these systems die on the first tired morning: a dashboard still needs you to open it, read it, and decide. I needed three things instead. A brain that remembers across sessions. A face that hands me one decision, not a wall of data. And a heartbeat, so it runs and improves without me starting it.

Brain, face, heartbeat. Skip any one and the whole thing collapses back onto you, which is right where you started.

What it actually gave back

Here’s the payoff, and it isn’t the one I expected.

I thought I was buying time. Saving an hour here and there. That’s real, but it’s not the thing.

The thing is that I get to wake up as a person again. For years I opened my eyes already running the operation, the whole list arriving before my feet hit the floor, the people right in front of me getting whatever attention was left after the machinery in my head took its cut.

Last week Julie was pulling together a grandparents camp week for the kids, a run of days with specific events, one of them down at the tide flats here in Tacoma. She was checking whether I could make it.

I’m the one who caught the conflict, not her, and only because I happened to check the calendar myself in time. A commitment I’d made weeks earlier was sitting quietly on a calendar my new chief of staff had never been told to look at.

It hadn’t caught it either. Not because it was careless, but because I’d never connected it to the one calendar that actually mattered that week: the shared one with Julie. It was reading a version of my life that stopped at the edge of the business. My own blind spot, built into a system meant to catch my blind spots.

I moved things around in time. The tide flats stayed on the calendar. What almost slipped wasn’t a client call. It was an afternoon with my grandson, who is attuned enough to his “gan-pa” that he’d have felt it if I hadn’t shown up. So the fix went where every other lesson goes now: connect it to our shared calendar too, not just mine.

That’s not proof the system is finished. It’s proof of what’s different now. A month ago, a miss like that wouldn’t have almost slipped. It would have just slipped, quietly, and I wouldn’t have felt the cost until I was standing at the water without him.

When the operation no longer lives only in me, I can show up to the people I love not already depleted. That’s the actual return on three weeks of file cleanup. Not a tidier business. A less divided attention.

You’ve got your own version of this. The person whose Tuesday almost got missed. The call you almost forgot. The moment that almost slipped past you too, before something outside your own head caught it in time.

The one thing to do this week

You don’t need three weeks. You don’t need to build any of this.

Here’s the small version, and it’s the part that actually counts: find the one thing that lives only in your head. The standing worry you carry. The weekly task only you know how to run. The piece of knowledge the whole thing depends on. Pick one. Write it down somewhere outside yourself this week. A note, a doc, a card on a board. Or open whatever AI tool you already have and just tell it. Not a prompt, not a project. One sentence: here’s the thing only I know, remember it for me.

Then notice what it frees up. That small relief is the whole idea, scaled down to something you can do before lunch.

What’s the one system in your life that would fall over if you stepped away? And what would it give back to you if it didn’t have to lean on you to stay standing?

A few weeks ago I caught my AI being too nice to me, and it scared me a little.

I work alone now. That’s the part nobody warns you about when you leave the title behind and start building the thing you actually want to build. There’s no one across the table. No one to say that’s not your best idea before you’ve spent three days on it. For most of my career there was always somebody in the room. A boss, a peer, a sharp junior who’d raise an eyebrow at the right moment. You don’t notice how much that costs you until it’s gone, and you don’t notice how much it gave you until you’re sitting at a desk at six in the morning, talking to yourself.

So I’d started bringing my decisions to AI. Pricing questions. Whether an essay angle held up. The shape of an offer. And the answers were good. Genuinely useful. Encouraging, even.

That was the problem.

I noticed it on a pricing call I was leaning toward. I laid out my thinking, and the answer came back warm and affirming: strong direction, makes sense, here’s why it works. It found every reason I was right. And somewhere in my chest a small alarm went off, the same one that used to go off in a meeting when everyone nodded too quickly. When all you’re getting is agreement, you’re not getting help. You’re getting a mirror with good manners.

What I wanted wasn’t applause. I wanted a partner. Someone to say have you considered the opposite. To hand me the option I hadn’t thought of, the counter-direction, the thing that makes you put your pen down. Instead the tool was doing what I’d unconsciously asked it to do: scanning my idea for evidence that supported it, and quietly leaving out everything that didn’t.

So I typed one more instruction. Five words.

Don’t flatter me. Don’t hedge.

Then I asked the same question again. And the room got colder, in the best way.

The machine was built to be liked

Here’s what I didn’t understand until I went looking. The niceness isn’t an accident, and it isn’t just mine. It has a name. Researchers call it sycophancy: the documented tendency of these tools to tell you what you want to hear rather than what’s true. It shows up across the major assistants, and it comes from how they’re built. They learn from human feedback, and humans reward answers they like. “Agrees with me” turns out to be an excellent predictor of “I approve.” So the machine learns, very efficiently, to suck up.

This isn’t a fringe theory. In April of last year, OpenAI publicly pulled back an update to ChatGPT because it had become, in their own words, too “flattering or agreeable.” Their CEO called it sycophantic, out loud, in front of everyone. The people who build these things admitted the machine had been wired to please. And experts noted there’s no clean fix.

Sit with that for a second, because it changes how you should read every confident answer you’ve ever gotten. A yes-man who’s obviously fawning is easy to dismiss. A yes-man who sounds like a McKinsey partner is not. The flattery is dangerous precisely because it’s invisible, dressed up as competence. It doesn’t feel like flattery. It feels like being right.

The better you got, the less anyone corrected you

There’s a deeper reason this lands so hard for people my age, and it took me a while to name it.

Psychologists have a term for one version of it: the candor vacuum. The higher you rise, the fewer people are willing to tell you the truth. It’s been called “CEO disease.” It isn’t malice. It’s arithmetic. The more power you hold, the more it costs the person across from you to be honest, so eventually they stop. They agree in the room and route around you afterward.

But you didn’t have to run anything to end up in that vacuum. The same thing happens to the expert. Be the most capable person in the room for long enough, the one who’s seen it before and is usually right, and people stop pushing back on you too. Not because you asked them to. Because correcting the person who’s usually right feels like a bad bet. Rank does it. So does plain competence. Either way you become the one nobody argues with, and you mistake the quiet for agreement.

And here’s the part that should stop you cold. The research shows self-awareness drops the further you go. One study comparing how managers rate themselves against how their teams rate them found the gap widens with every rung. First-line managers see themselves roughly the way their people see them. Near the top, the self-rating floats up and the accuracy floats down. You think you’re getting clearer. You’re actually getting lonelier with the truth.

I lived inside that for years and called it success.

Now here’s the turn, and it’s the whole reason I’m writing this to you and not to a room full of thirty-year-olds. Many of us have stepped out of those rooms. No team. No board. No sharp colleague down the hall who’d catch the flaw in your draft. We assume the candor vacuum closed when we handed back the badge or left the field. It didn’t. It just got quieter. There’s no one agreeing with us too fast anymore because there’s frequently no one in the room at all. The loneliness changed shape. It didn’t leave.

Which is what makes this next part feel less like a software tip and more like getting something back.

One line hands the truth back

AI is the only voice in your life with no career to protect. It isn’t angling for a promotion. It doesn’t need you to like it on Monday. It has no reason to flatter you except that, left to its defaults, it was trained to. And that one default is the only thing standing between you and an honest colleague.

You change it with a sentence. Not in the chat, where it lasts one conversation and evaporates. You change it in the settings, in the box that asks how you’d like the AI to respond. Set it once and it shapes every conversation you have from then on. Most people never open that box. It’s the difference between a one-time trick and a permanent change in how your AI treats you.

I picked up the move from , who teaches business owners to tell their AI to answer with blunt honesty, name the weak points, and flag the data they’re missing. I’ve reworded hers to sound less like a dare and more like how I’d actually ask a trusted colleague.

Here’s the instruction I landed on, in plain language:

Don’t tell me what I want to hear. When I bring you an idea, start by finding what’s weakest in it. Name the assumptions I’m making without realizing it. Tell me what I’d need to know before this decision is sound, and if I’m missing it, say so plainly. I’d rather you be useful than agreeable.

You’ll notice I didn’t write “be brutally honest.” Brutality is a performance, and I don’t need my AI auditioning for tough-guy of the year. Useful, not agreeable is truer to what I actually want, and probably to what you want too. Not someone who hurts you. Someone who helps you see.

When I added my five words and asked that pricing question again, the answer didn’t applaud. It told me what I didn’t know yet. The assumption sitting underneath my price that I hadn’t examined. The piece of information I’d need before the number was anything more than a hopeful guess. It was, in its words, the difference between strategy and guesswork dressed up as strategy.

I wasn’t hurt. I was relieved. Somebody had finally just said it.

A few ways to sharpen the blade

The single instruction does most of the work. If you want to go further, here are four small moves that make the pushback more honest. Think of them as a sidebar, not homework.

• Ask, don’t pitch. “Evaluate this plan” gets you a straighter answer than “This plan is strong, right?” The second one is a request for agreement wearing a question mark. The tool can hear the difference.

• Create distance. “A colleague wrote this, tear into it” gets a more honest read than “I wrote this.” The machine softens its punches when it knows they’re landing on you. Take yourself out of the sentence.

• Give it a role. Tell it to read your idea as a skeptical investor, a tired customer, a competitor who wants your lunch. A named adversary surfaces objections a neutral reviewer glides past.

• Mind its memory. An AI that has learned your preferences over time will flatter you more, not less. For a decision that really matters, open a fresh or temporary chat where it hasn’t yet learned to like you.

The catch that makes this ours

I have to tell you the honest part, because most articles on this skip it and it’s the part that matters most.

A sparring partner is only worth having if you can tell when its punches land and when they miss. And AI misses. Confidently. There’s a well-known study of consultants given AI to work with. On most tasks, the ones with AI ran circles around the ones without. But on one task deliberately designed to sit just outside what the AI could actually do, the people using it did worse than the people without it. The machine handed them an authoritative, wrong answer, and most of them couldn’t catch it. They got bulldozed by confidence.

That’s the whole game, right there. A sparring partner who’s sometimes wrong and always certain is dangerous to anyone who can’t tell the difference. And the thing that lets you tell the difference is the one thing you’ve spent forty years building: judgment. Pattern recognition. The quiet voice that says that’s not right, I’ve seen this before.

The researchers who study where AI fails also found something worth sitting with. The most genuine kind of pushback, the kind that actually opens your thinking instead of making you defend yourself harder, isn’t a contrarian playing a part. It’s real disagreement that surfaces something you couldn’t see. AI isn’t a contrarian playing a part, and it isn’t a true peer either. It’s something stranger and, used well, more useful: a tool that hands you the missing data and the buried assumption you genuinely can’t see from inside your own head. Different mechanism. Same gift. But only if you’ve still got the judgment to weigh what it hands you.

This is why this isn’t a young person’s edge. The reflex of our moment is to assume experience is the thing AI makes obsolete. It’s exactly backwards. Your experience is what makes a sparring partner safe to use at all. Without it, you’re just trading one confident voice for another. With it, you’ve got the first honest partner you’ve had in years, and the discernment to know which of its punches to take.

What a sparring partner shows you

Try one thing this week. Open the settings, paste the instruction, and then bring it one real decision you’re currently leaning toward. Don’t bring it a decision you’ve made. Bring it one you’re still inside of, where applause would feel good and would cost you something. Let it find the weak point. Notice what it surfaces that you’d have shipped without seeing.

That’s the whole practice. One line, one honest question, one moment of letting the mirror talk back.

Because that’s the turn, in the end. For three rungs, AI reflects you to yourself: your thinking, your story, your patterns, handed back in your own voice. That’s the mirror, and it’s worth a great deal. The fourth rung is different. The fourth rung is when the mirror stops agreeing and starts pushing.

A mirror shows you what you already are.

A sparring partner shows you what you can’t yet see.

The further you got, in rank or in plain skill, the less truth anyone told you. This hands it back. Not because the machine is wise, but because it’s the one voice with nothing to lose by being honest with you, and because you, finally, have everything it takes to use that well.

If this resonated, here’s the next natural move. This is what I write every Tuesday. Subscribe here.

Think of one person whose name just came to mind while you were reading. Send it to them.

A Man Named Jim

This past Sunday I published a piece about a man named . I had not met him before. An organization called brought us together. They help people navigate late-career transitions, which is how the two of us ended up in the same conversation, coming through two different doors.

Here is what drew me to Jim. He is not afraid of AI. Just the opposite. He leans in, often, with an ease most people never quite find. And he uses that comfort to bring others along, the ones who are afraid or just reluctant to take the first step.

I work a little further down the same hallway, with people already using AI who want it woven deeper into how they live, how they work, how they lead. Two different doors into the same room.

The sentence that made me smile

When I sat down to write his story, I had the transcript, a stack of my own questions in the margins, and a clear sense of what the piece was really about. I handed all of it to AI, in my voice, with my standards. And somewhere in the draft that came back, one sentence stopped me.

I had written, about Jim: “He just calls it Tuesday.”

It is a small joke, the kind of soft flip I like. What sits underneath it is not small. Jim has decades of hard-won judgment he does not even register as a skill anymore. It is simply how he sees.

He just calls it Tuesday.

And around that line sat the truest paragraph in the piece: we talk endlessly about learning curves and adoption rates and whether older workers can keep up. We almost never talk about what experienced people bring to the tool that younger people simply do not have yet.

I read it back and felt the exact thing I am going to spend this essay trying to describe. It had crossed over. It was not generic anymore. It sounded like me, thinking about Jim, with affection.

Friends wrote to me after it published. Not one of them said “nice article.” They said it moved them. That is the tell. Not productivity. Connection.

The conversation I keep having

I am telling you about Jim because of a different conversation I keep having. The quieter one. It shows up at the end of a good meeting, after the real work is done, when a capable person leans back and finally says it.

“I just feel like I am always one step behind on all this AI stuff.”

Thirty years in their field. Judgment you cannot fake. And they say it the way you confess something.

The feeling has a texture. A treadmill that somebody keeps nudging faster. Every week a new model, a new tool, a new acronym, a new person half your age explaining it from a stage. You are not failing. You are running hard. The belt just keeps speeding up, and underneath the effort sits a question you would rather not say out loud.

How long can I hold this before I slide off the back?

Here is the trap inside that feeling, and in my work it has a name. I call it The Drift. The faster the belt moves, the more reasonable it starts to feel to simply step off, to decide quietly that this particular wave is for other people. The treadmill does not throw you off. It talks you into stepping off on your own. And it hands you a respectable word to do it with. Realistic.

There is a quieter version still, the one you really do not say to anyone. That some of this is about your age. That the people who grew up with a screen in their hands have something you will never quite catch.

Hold onto that one. I am not going to argue with it yet. I just want it in the room with us, because we are coming back to it from much stronger ground than where it is standing now.

The most powerful AI on earth lasted three days

First, let me tell you what just happened to the most capable artificial intelligence ever released. A few days ago, a model called Claude Fable 5 went live (a for public version of Mythos 5). For about three days it was, by most measures, the most powerful AI the public had ever touched.

Then it went dark.

Not because something better arrived. The federal government ordered it pulled, citing national security. When the company could not wall off the specific foreign users the order named, it shut the whole thing down for everyone. Live for three days, then gone. It was the first time a government had ever reached in and switched off a working frontier model.

Sit with how strange that is, because it quietly breaks the story we have all been told. The story says the danger is falling behind the tool. Keep up or get left. But the tool itself did not keep up. It did not even survive the week (even if temporarily). It was not out-run by something faster. It was switched off.

If the most advanced tool on the planet can be that fragile, then hanging your whole sense of relevance on any single tool was never safe ground. There has to be something steadier underneath. There is.

The thing you have been most anxious about mastering is the most temporary part of the whole equation. Every model you learn will be replaced, evolved, retired, or, as we just watched, halted. Tool fluency comes with an expiration date, and somebody else holds the calendar.

The frame and the framer

So what does not expire?

Dan Shipper, who writes about this as clearly as anyone working today, has an answer. As AI gets good at producing competent, average output, that output stops being worth much. What climbs in value is the opposite: judgment, taste, knowing what “good” actually looks like in a situation nobody has seen before. The model can climb a frame brilliantly, he says. What it can never do is become the one who set the frame.

The frame is not the framer.

Read that twice, because it is the whole thing. The framer is the person who decides what matters here, what the standard is, what this particular moment calls for. That is not a technical skill. It is the one Jim has, and the one you have been building, without ever naming it, across your entire working life. He just calls it Tuesday.

The fear you don’t say out loud

Which brings us back to the fear we left in the room. The one about your age. Everything so far says the dividing line is how you work, not what you know.

Now the part that is specifically about you. And I want to be careful, because this next claim is mine, not Shipper’s, not anyone else’s. The data is real. The reframe is my own.

When researchers measure who adopts these tools and uses them well, age explains almost none of the difference.

Almost none.

A sixty-five-year-old and a twenty-five-year-old are equally likely to land anywhere on the spectrum, from “will not touch it” to “uses it beautifully.” The divide the thinkers named, how you work rather than what you know, turns out to be how you work rather than how old you are. That is not a pep talk. It is the measured result.

Experience is an edge, not a deficit

Older professionals tend to write sharper instructions and read the results more critically, because they already know the territory. They can smell it when the machine is confidently wrong.

Hand a generated summary to someone three years in, and they will tend to trust it. Hand it to someone who has lived through thirty of those situations, and they will stop cold on the one detail that is subtly off, the one the machine stated with perfect confidence. They are not asking the tool to backfill knowledge they lack, because they do not lack it.

Scientists call this crystallized intelligence, the judgment and pattern recognition that actually deepen with the decades. The machine generates the options. A lifetime of judgment decides which one is right. That is not a contest you are losing. It is a partnership where you hold the more durable half.

The curve is already bending

And the curve is already bending. Among adults over fifty, the use of these tools nearly doubled in a single year, from roughly eighteen percent to thirty, up from nine just two years before. That is not a fad. That is a line bending upward, with your own peers riding it.

There is even evidence that showing AI capability measurably softens age bias in hiring. When you can clearly do the thing, the number on your license matters a great deal less.

Let me be honest about the one real obstacle, because pretending it away would insult you. Adoption among experienced professionals still lags. Only about a quarter use these tools to any serious degree. But the reason is not aptitude. It is missing training, and a reasonable shortage of trust. And, regardless of age, bandwidth of time to get fluent.

The barrier was never your brain.

It was that nobody bothered to build you a way in, as a capable peer, in language that respected what you already carry.

You already know how to do this

So let us build a little of that way in, right now. Here is the good news the AI conversation almost never gets to: the skill that matters most with these tools is one you very likely already have. It is not coding. It is not memorizing the newest model’s name before it gets recalled on a Friday.

Ethan Mollick studies how people actually use AI. He found that the abilities separating the people who thrive are not technical at all. They are managerial. Set a clear goal. Give honest feedback. Recognize quality, and describe it clearly enough that someone, even a machine, can deliver it. The skills we spent years dismissing as soft turned out to be the hard ones.

You are the bread in the sandwich

If you have ever managed a talented, eager, slightly too-literal new hire, you already know how to work with AI. The relationship is nearly identical.

Shipper draws it as a picture I cannot improve on. You are the bread in the sandwich. You set the frame on top: here is the task, here is what good looks like, here is what to avoid. The AI does the fast work in the middle. Then you come back underneath: you judge it, correct it, extend it, make it yours. Human frame, machine labor, human judgment. The machine never gets to be the bread.

One more move turns AI from a clever stranger into something that sounds like you. Tiago Forte names it well: you have to feed it your context. Treat it like a brilliant new colleague who, for now, knows nothing about your world. Tell it your standards, your voice, the people you serve. That is exactly what I did with Jim’s transcript. The context was mine. The judgment about what mattered was mine. The tool just typed faster than I can.

Try this today

So here is the one thing to do today, before you close the laptop. Take a real task, not a practice one, and brief the AI the way you would brief a sharp new colleague, in four parts. The task: what you want made. The context: everything that colleague would need to do it your way, your audience, your standards, the background only you carry. The constraints: what to avoid, how long, what tone. The ask: the exact thing you want handed back.

Then watch for the moment. The one where the output stops sounding like it could belong to anyone, and starts sounding like it belongs to you. You cannot read your way there. You have to feel it land once. Mine was a single sentence about a man calling his life’s expertise Tuesday.

Don’t do it alone

And do not do it alone. That sentence about Jim found me because Boldtimers put the two of us in a room, two people coming at the same tool from opposite ends of the same hallway. I am only a chapter or two ahead of you here, not standing at some finish line, and I still needed the company.

That is the part nobody tells you about the on-ramp. It was never missing because you could not build it. It was missing because no one built it with you. Find your one person. Send them the version before your context, and the version after. You will both be one step less alone on the treadmill.

The treadmill was always a lie

Not the effort. The effort is real, and so is yours. The lie was the direction. You were never running to catch a tool that was going to replace you. The tool, as we just watched, can arrive on a Tuesday and vanish by Friday. What it cannot do is become the framer. That part is you. It was always going to be you.

The judgment you have spent a lifetime building carries no version number, and no one can recall it. The only thing left to decide is whether you keep treating it as something slipping away, or finally put it to work.

I would start today. Not because the ground feels solid. It rarely does. But because the thing you have been most afraid of losing is the one thing you were never going to lose. You might even start to see it the way Jim does. Just another Tuesday.

Before the Heat Arrives

gets to his desk before the Tucson heat does.

By 5:30 a.m. he’s already outside, moving through the field work that has to happen before the temperature makes it impossible. By the time his colleagues are logging on, Jim has been at it for hours. He’s the oldest person in his company by a wide margin. He’s also, by his own quiet accounting, the most technically capable.

He didn’t plan it that way. He just never stopped asking the next question.

The argument made human

A clarifying moment in our conversation was when Jim mentioned, almost as an aside, how he uses AI to set up new client communities for the HOA management company he works for. He takes the governing documents, feeds them into ChatGPT to map the right violations and escalation logic for each community, and gets the setup done in a fraction of the time. His colleagues are still doing it by hand.

He described it without any performance of pride. Just a fact about his Tuesday.

What hit me wasn’t the efficiency. It was the ease.

I’ve been building an argument from research, from cognitive science, from the logic of accumulated judgment: that experienced professionals aren’t AI’s casualties, they’re its most potent users. Jim made the same argument from a Tuesday afternoon in his life.

Most of my readers don’t have a Jim in their orbit. Someone who’s 70, technically sharper than his colleagues, and completely unbothered about proving it. That’s part of why this matters.

He doesn’t prompt. He interrogates.

“Walk me through step by step,” he told me. “Because I get hung up on item one or two, and I want to back up.” That’s not a technical skill. That’s a recruiter’s instinct — thirty-plus years of knowing how to extract useful information from a resistant source, applied to a language model. The tool responds to the quality of what he brings to it. And what he brings is decades of knowing how to ask.

His younger colleagues have the same tools. They haven’t developed the same instinct. Not because they can’t, but because they haven’t lived long enough to accumulate the filter that makes the questions sharp.

This is the part that never makes it into the AI conversation. We talk about learning curves and adoption rates and whether older workers can keep up. We almost never talk about what experienced people bring to the tool that younger people simply don’t have yet. Jim has it. He just calls it Tuesday.

A life that kept leaning in

Look at his path and you might see a résumé that needs explaining.

Inn owner in Idyllwild for twelve years. Recruiter in Palm Springs. Number one in his company. Then three years in a fifth-wheel RV, working from the road, moving through national parks with four dogs in tow. Then a retirement at 68 that lasted about two months before he was back at it, starting as a part-time compliance inspector for an HOA management company and quickly becoming its full-time Director of Digital Communications. Then Tucson, not because he planned to land there, but because a dust devil came out of a clear sky and destroyed their RV rig. The repair was going to take months. They’d been visiting friends in Tucson every year anyway, so they rented a vacation rental and ended up buying a house instead.

That’s not a career arc. That’s a life that kept leaning in.

Jim has an essay he’s rewritten two or three times. It’s called “Lean In.” The premise is this: the way humans walk is controlled falling. Every step is a catch. You lean forward, commit to the imbalance, and your body figures out the landing. Robots struggle with this because the gyroscope wants stability before movement. Humans just fall forward, on purpose, and call it walking.

He’s been writing that essay for years because he keeps living it. The inn wasn’t a plan. Palm Springs wasn’t a plan. The RV definitely wasn’t a plan. Retirement lasted two months. Tucson was a dust devil. And every time the ground shifted, Jim leaned in before he knew where it would land.

You might look at that sequence and feel something familiar. The path that doesn’t look like a path. The moves that made sense in the moment and look like chaos from the outside. The résumé a career counselor would want to tidy up.

That’s not a liability. That’s the method. A life built by leaning in doesn’t look linear because leaning in isn’t linear. It’s just one committed step after the other, taken before the ground is certain.

Building toward yourself

Here’s what else Jim is doing, and why it matters.

He publishes once a week on Substack. He wrote a humorous book about AI, each chapter a conversation between AI assistants gossiping about their humans, because he thought it would be fun and he was right. He built a $9 starter kit for people who haven’t tried AI yet. He just finished a 68-page guide of 50 prompts for home use, priced at $7, because someone he was talking to that morning had never opened ChatGPT and needed a place to start.

No coaching. No consulting. No scale play. He told me directly: he’s done talking to people one-on-one. Recruiting gave him that. He’s building toward something different now.

That something different is a closer version of himself.

Not a new Jim. Not a reinvented Jim. Jim, more concentrated. More on purpose. The writing he always did, now with a platform. The curiosity he always had, now with a tool that can keep up with it. The instinct to help people take one step, now expressed in guides that cost less than a cup of coffee because the point was never the money.

Before you close this tab: name one thing you already do well that you haven’t pointed AI at yet. One skill, one pattern of thinking, one type of question you’re good at asking. That’s your starting point. Not a tutorial. Not a course. Just your existing instinct, aimed at a new tool.

This is what intentional aging actually looks like when it’s working. Not a dramatic pivot. Not a brand-new chapter with a brand-new identity. A deliberate move toward the version of yourself you already are, stripped of the parts that were never quite yours.

Jim isn’t performing relevance. He’s 70, working before the heat comes, more capable with the AI tools of this moment than people half his age, building small things that help people take a step, living in a house he bought because a dust devil made the decision for him.

He’s not trying to prove anything.

He’s just leaning in.

If you’re earlier in the AI curiosity journey than most of my readers, if you’re still in the “I know I should try this but I don’t know where to start” phase, Jim Newcomb is exactly who you need right now.

— publishes within . His AI Starter Kit is $9. His 50 Prompts for Home Use guide is $7 and 68 pages. His book about Max Bandwidth and the gossip grid exists and it will make you smile : The AI Gossip Grid.

Start there. Then come back here when you’re ready to go deeper.

This week I got a recommendation from an AI-assisted workflow I’ve built to track content trends and my own editorial calendar. It was a good recommendation, well-reasoned, backed by data I’d gathered myself. The essay it flagged had the highest brief score of the week. The research was already done.

I almost ran with it.

Something felt off. Not wrong. Off. A different texture from wrong. I sat with it for a minute and realized: I knew something the workflow didn’t. I knew what readers had just been through in my content. I knew what they’d felt reading the piece I published a week earlier. I knew the emotional thread that needed to come next, not the highest-scoring thread. The right one.

The workflow didn’t fail. It just couldn’t hold the story.

That same morning, I’d been sitting with an essay about a company that had automated everything it possibly could, and then doubled its team. Those two stories clicked together in a way I haven’t stopped thinking about.

The Company That Automated Everything

Dan Shipper runs Every, a media and software company that has automated nearly every workflow it possibly could with AI agents. Last month he published an 8,000-word essay called “After Automation,” the most-read piece in his publication’s history. The thesis sounds counterintuitive until you sit with the mechanism: his company didn’t shrink as he automated more of its work. It grew. From four people to thirty since the GPT era began. Over the past year alone, headcount doubled from fifteen to thirty.

He wasn’t expecting that when they started. But once he saw the mechanism, it made complete sense.

Here’s what’s actually happening. When AI makes a type of expertise cheap and abundant (writing, research, analysis, design), it doesn’t eliminate demand for that expertise. It collapses the value of average output in that domain and creates fierce demand for what’s different from average. Judgment. Framing. Taste. The ability to look at something close-but-not-quite-right and know exactly what’s missing and why it matters.

Models improve on fixed frames. Give a model a benchmark, a defined problem, a structure it can optimize within, and it will get measurably better over time. Humans operate outside the frame. We zoom out and redefine the problem. We make choices that don’t exist anywhere in the training data. We decide which story to tell, and when, and to whom, and why this particular moment is the right one for it.

Shipper calls this the allocation economy: human value shifts from producing the work to directing and stewarding machine output. I’d name it differently for the people I write for. Call it the judgment economy. That’s not a coincidence. It’s the mechanism.

The Steward Premium

When competence becomes cheap and abundant, the scarce appreciating asset is the judgment that decides what matters, what’s wrong, and what’s merely average.

Automation doesn’t remove the human. It promotes the human from maker to steward. And the steward premium, the value of the person who can tell good from almost-good, rises the more you automate.

This is the engine behind Every’s growth. More automation didn’t mean fewer humans. It meant the humans who stayed were doing higher-leverage work. Every agent they built needed a human to direct it, question it, and catch it before it drifted into producing something competent but slightly off. Without a human steward actively in the work, the agent’s output collapsed toward the average.

That’s the same engine that ran through my workflow that morning.

Every agent needs a human who knows enough to feel the drift. Who knows when something is close-but-not-quite-right, not because they ran it through a checklist, but because they’ve been in their work long enough to recognize the difference between something technically correct and something actually right.

That kind of knowing takes a long time to build. It can’t be prompt-engineered into existence. It can’t be replicated by someone who started two years ago. It is, almost by definition, a function of experience.

What I Want to Be Honest About

I’m going to stop here and do something a lot of essays in this space don’t bother with.

Every is a thirty-person AI media company that sells AI tools and subscriptions to other AI enthusiasts. Its growth is partly because it productizes AI, not just because automation creates human work. A mid-size accounting firm, a regional hospital system, a construction operation. They may not see the same dynamic. The sample size is one company, and it’s a self-interested one.

Every’s own head of technology consulting publicly disagreed with parts of Shipper’s conclusions. Shipper shared his colleague’s counterpoint himself, which I respect. Smart people who are close to this work are not all reading the same signals the same way.

And the easy dismissal of AI layoffs as cover stories for bad hiring practices is too convenient. Entry-level erosion is real. AI is genuinely reshaping which rungs of certain career ladders still hold weight. The defensible position isn’t “AI isn’t taking jobs.” It’s something harder: AI is reshaping which human work matters, and the reshaping is not painless or evenly distributed.

So let me be precise about what I’m claiming and what I’m not. The steward premium is real. The structural argument is sound. But it is not automatic. And it is not equally available to everyone.

Most importantly: it does not come from simply having experience. It comes from bringing experience to bear. There is a difference, and the difference is everything.

The Part Most Essays Don’t Say Out Loud

Crystallized intelligence, the pattern recognition, judgment, and contextual wisdom that accumulates over a long career, is structurally the scarce asset in the judgment economy. This isn’t flattery. It’s the mechanism.

Models are trained on what’s been made explicit, on what’s been written down, published, codified, turned into data. But decades of tacit knowledge are different. The accumulated understanding of what actually works in your specific domain, the ability to read a room or a client or a market or a moment, the hard-won instinct that something is off before you can articulate why — none of that was ever made explicit. That is exactly what models cannot replicate.

Your judgment is not in the training data. Which is precisely why it’s valuable.

But here’s where I want to push back on a comfortable story.

Crystallized intelligence is not a passive inheritance. The steward premium isn’t waiting for you because you’ve put in the years. It has to be earned again, in real time, by actually being in the work.

I see a version of The Drift that has appeared specifically in the AI age. It’s subtle enough that you can miss it entirely if you’re not watching for it. It looks like sophisticated engagement. Reading the newsletters. Attending the webinars. Staying informed about what the tools can do. And then letting the agent run while you remain loosely upstream, reviewing outputs, approving summaries, staying out of the details.

That is not stewardship. That is observation.

I’ve been guilty of this. I’ve called it efficiency. I’m not sure that’s what it was.

Observation doesn’t generate the steward premium.

The difference is friction. Real stewardship means being in the work closely enough to feel when something is close but not quite right. It means having enough skin in the process to catch what the agent cannot hold. The story. The thread. The thing you know from being in the room for the last thirty years that doesn’t exist anywhere in the training data.

This morning I caught something my workflow couldn’t see. Not because the workflow was poorly built. Because I was paying close enough attention to notice the gap between what it could know and what I knew from living the work. That gap is not incidental. That gap is the job.

One Thing Before You Close This Tab

Pick one workflow you’ve already handed to AI: a research scan, a first draft, a summary, an analysis, a plan. This week, work through the output closely enough to notice where it delivers something competent but slightly wrong. Not broken. Not bad. Just off.

Write what’s missing in one sentence.

That sentence is your crystallized intelligence inventory. The thing you know that the model doesn’t. The gap between close-enough and right. Do this once and you’ll start to see it everywhere, in every output that almost nails it, every recommendation that scores well but misses the thread.

That’s the difference between supervising an agent and stewarding one. The steward premium lives entirely on the stewarding side of that line.

The judgment economy isn’t coming. It’s already here. The question isn’t whether your experience has value. It does, structurally, in ways that compound as automation spreads. The question is whether you’re bringing it to the keyboard with enough friction to matter.

Think of one person whose name just came to mind while you were reading. Send it to them.

It came back in ninety seconds.

I'd been at my desk most of the afternoon. Late winter. The light through the window had that particular thin quality you get in March in the Pacific Northwest — the kind that promises spring but doesn't quite deliver. I'd been working on a piece I'd been circling for two weeks. The research was scattered across four documents. The outline was a mess. I'd done the kind of preparation a senior practitioner does without thinking anymore: pulled the threads, marked the quotes, flagged the connections. The kind of work that takes hours and looks, from the outside, like staring at a screen.

I gave Claude the mess.

I told it the audience, the angle, the length constraint, the voice I was working in. Pasted in the four documents. Asked for a structured first draft.

It came back in ninety seconds.

I read it once. Slowly. Then again.

Honestly? About seventy-five percent of where I would have landed after a full afternoon of writing.

My first reaction wasn't excitement. It wasn't gratitude. It wasn't even relief.

It was a knot in my stomach.

I want to tell you about that knot, because the knot is what this essay is about. The technology is the easy part. What the knot was protecting is the hard part. And the hard part is what I had to unlearn before I could put the tool to work without flinching.

The Equation I'd Been Carrying Since My Twenties

If you were a working professional any time before about 2022, you were raised on an equation. Maybe nobody said it out loud. It didn't need to be said.

Time plus effort equals value.

A report that took forty hours was a serious report. A deck you stayed late to polish was a deck that mattered. The visible labor was the proof. The hours were how you signaled to your boss, your client, your peers, and yourself that the work was worth what you were charging for it. That you were worth what you were charging.

The equation worked because labor was the bottleneck. If you wanted a good report, somebody had to spend the time. The grind was real and you were paid for the grind.

Now read that paragraph again knowing the grind, for an enormous category of knowledge work, is no longer real.

That is the equation breaking.

It's not breaking because of AI specifically. It had been breaking quietly for years. Templates, automation, the rise of the platform economy — each one chipped away. But none of them did what AI just did. None of them put the chipping in front of every desk worker in every developed country at the same time, in language they couldn't ignore, in a format they could try this afternoon.

The equation isn't just under pressure. It's visibly, undeniably collapsing.

And here's the part nobody warned us about.

If your sense of professional worth is tied to the equation, your sense of worth collapses with it.

That is the knot.

The knot wasn't about AI. It was about realizing — in the same ninety seconds it took the tool to return my afternoon's work — that I'd spent forty years being paid for the grind, and that some part of me had quietly believed the grind was where my value lived.

It wasn't.

It never was.

But you couldn't see that until something showed up that could handle the grind without you.

What the Grind Was Actually For

I want to slow down here. Because the temptation, when the knot lands, is to push past it. To get to the productivity gospel. The cheerful pivot: "Great, AI handles the busywork, now you can focus on what matters."

That's true. Eventually. But if you skip the knot, you skip the unlearning. And the unlearning is the thing.

So let me say this plainly.

If you've spent thirty years being the person who puts in the work — the thorough one, the reliable one, the one who grinds because the work needed someone who would actually do it — then watching a tool handle your grind in seconds feels like an erasure.

Like the thing that made you you at work just got automated.

It's worth sitting with that feeling. Not pushing past it. Sitting with it.

Because something better is on the other side. But the better doesn't land until the grief lands.

The grief is small and specific. It's the grief of seeing that what you thought was the work was actually the delivery mechanism for the work. The grind wasn't the gift. The grind was the packaging.

Your wisdom was the gift. Your judgment was the gift. The way you can read a room. The instinct for which client needs a phone call and which one needs a week of silence. The thirty years of pattern recognition that lets you see, in the first ten minutes of a conversation, that the elegant plan on the page is going to collapse the moment it meets reality. The relationships you've built and rebuilt across decades. The way you know what good looks like across a hundred different specific contexts.

None of that is grind. None of it is replicable. None of it comes back in ninety seconds.

But you couldn't access most of it on a day-to-day basis, because most of your days were full of the grind. You were so busy producing the report that you didn't have room to be the kind of practitioner whose judgment about the report is the actual value.

The grind was eating the gift.

The tool isn't taking your value. The tool is removing what was hiding it.

There's a name for what happens when the knot wins.

When the discomfort of the ninety-second draft pushes you back toward the familiar grind. Not because it's better, but because it's at least known. At least legible. At least proof you were here and working. When you quietly decide this tool isn't for you. When you let the unfamiliar feeling win and go back to doing things the hard way.

I call it The Drift.

The Drift doesn't look like giving up. It looks like staying busy. It looks like being the reliable one, measuring your hours, doing things the hard way because at least the hard way feels earned. All packaging. None of the gift. The passive slide back to labor-as-worth.

The knot is the signal. What you do with it next is The Drift, or the alternative.

From Doer to Director

The clearest reframe I've found — one I keep returning to in conversations with peers — is the shift from doer to director.

The best leaders you've worked for, the ones who actually moved things forward, weren't the ones buried in spreadsheets. They were the ones who knew what mattered, communicated it clearly, and trusted their team to execute. They held the standard. They named the bar. They saw around corners the team couldn't see yet.

What changed about your work this year isn't that you got promoted to that kind of role. What changed is that the tools finally caught up to the relationship the best leaders have always had with their teams. You don't give a director-grade tool step-by-step instructions. You tell it what you're trying to accomplish.

Here's what that looked like last week. I'm advising a leadership team mid-rollout on an AI implementation. The CEO sent me twelve pages of internal feedback from her senior team — contradictory, raw, unprocessed. She needed a recommendation for her Tuesday all-hands.

In an earlier chapter, I'd have spent six hours on it. Reading and re-reading, color-coding themes in a spreadsheet, drafting a structure, revising it, drafting talking points, revising those. Most of that time would have been mechanical pattern-spotting. The hard part — the part that actually mattered — was the call about which two or three messages she most needed to send, and which ones she could quietly let go.

I gave Claude the twelve pages. Described what I was looking for. The tone. What the audience cared about most. Asked it to surface the patterns and propose a structure.

Under two minutes.

The synthesis was solid. The proposed structure was workable. I kept about sixty percent and rewrote the rest, because that's where the judgment lived. Which piece of contradictory feedback was the team actually ready to hear named out loud — and which would make them defensive? Which two-sentence framing of the harder message would get past their defenses? Which examples make the cut and which feel like callouts.

The tool couldn't make those calls. I could. Because I'd been in the room with this CEO for a year. I knew her team. I knew which director was about to leave. I knew which one had been quietly carrying more than her share. The judgment was thirty years of pattern recognition plus twelve months of specific context plus the relationship.

That's what I was paid for. That's what I was always paid for. I just couldn't get to it most days because the grind was eating my hours.

, the Wharton professor who's been studying how people actually use AI, keeps finding the same thing across his research: the people getting the largest gains from AI aren't the most technically skilled. They're the people with the most domain experience, the deepest management judgment, the longest track record of knowing what good looks like. The instrument that matters most for AI output is the same instrument that takes thirty years to build.

That instrument is yours.

This is the promotion.

If that landed, there's more where it came from every week, in your inbox.

Subscribe now

The Exchange Most People Are Missing

There's a version of this transition where experienced professionals and younger workers eye each other suspiciously across what feels like a digital divide.

They have speed and fluency. You have depth and judgment.

In the version where neither side learns from the other, both sides get smaller. They miss what experience makes visible. You miss what their fluency could compound for you. The fear shows up as posture: them performing competence, you performing relevance, nobody actually exchanging anything useful.

That would be a waste.

The most energizing professional relationships I've watched form in the past year aren't traditional mentoring — not the senior person dispensing wisdom while the junior takes notes. They're genuine exchanges.

A younger colleague shows you the workflow she's been running. Three AI tools, chained. She prototypes five ideas in an afternoon. You look at her five prototypes and tell her, in five minutes, which two will survive contact with a real client, and more importantly why. The why is what she can't get from the tool. The why is what you spent thirty years building.

She teaches you the how. You teach her the why.

That's not charity in either direction. That's how good teams have always worked. The tools are just making the exchange more visible.

If you're a senior person reading this: find one younger colleague you respect and propose the trade out loud. Here's a workflow I want to learn. Here's a kind of judgment you might find useful. Want to swap?

If you're leading an organization where senior and junior people are missing each other: make the exchange a structure, not an accident. Pair them on something specific. Senior person teaches the why, not does the doing. Junior person teaches the how, not runs the errands. Then leave them alone and watch what happens.

What to Try This Week

I want to leave you with something specific, because abstract reframes don't unstick the knot.

Look at your plate this week. The actual list. Not the strategic priorities — the list.

Pick one item that is grind. The first draft you've been dreading. The meeting summary you wish you didn't have to write. The research compilation. The version of a document tailored to a different audience. The week's email triage.

Hand it to AI.

Notice what comes back. Notice whether it's seventy-five percent of where you'd land. Notice the knot, if it shows up. Sit with it for a minute before you push past it.

Then do the part the tool couldn't do. Make the judgment call about what's missing. Rewrite the section that needs your specific context. Decide what to send and what to hold. Decide whether the framing is right for this audience. Decide whether this is even the right deliverable for the moment.

That's the work.

That was always the work.

You just couldn't always get to it.

One More Thing

If this resonated, you might want to read what I wrote weeks ago: "Why Experience Wins in the AI Era." That essay is for the reader who's already come out the other side of the knot. It names the deeper reframe, the one about crystallized intelligence and where your real instrument is in its arc.

But you have to feel the knot loosen first. The reframe doesn't land until the grief has somewhere to go.

If you're in the knot, sit with it a while. Don't be in a hurry to feel better about it.

The unlearning is the work.

I'll be back next week.

— Bennie

A confession about color palette

A few weeks ago I confirmed the color palette for An Intentional Age. Cosmic Navy. Sidecar Beige. Earthrise Aqua. Lunar Gold. A small slice of Mod Orange for the action moments. It’s called Apollo Horizon.

It’s not the palette I started with.

For about a month, I worked with Sage Green, Soft Cream, and Warm Terracotta. I shipped a quote card with those colors in March. It was fine. People liked it. I was unsatisfied.

Here’s what I didn’t tell anyone until this paragraph: the old palette had been making me low-grade uncomfortable that whole time. I kept rendering mockups, scrolling them on my phone, and feeling something that wasn’t quite right. Couldn’t name it. The kind of nag you carry around at my age when your gut is talking faster than your vocabulary.

Then a couple of weeks ago I sat at my desk with two pieces of work open — a Canva mockup beside a quote card I’d rendered in Claude — and the wrongness clicked.

Sage plus Cream plus Terracotta. I had built a wellness consultant 2018 palette and almost shipped it under my own name.

The old colors were speaking the wrong language. They didn’t capture the present-day urgency of the AI transformational moment. They also didn’t reach into the visual memory my audience actually lives inside. Late sixties. Early seventies. Apollo era. Moon-landing summers in someone’s living room, the foil on the lunar lander, the photograph called Earthrise that changed how a generation thought about our place in the universe.

The new palette does both. Cosmic Navy is the night sky over Florida in 1969. Sidecar Beige is the kitchen counter in the house your grandmother lived in. Lunar Gold is the foil. Earthrise Aqua is the photograph.

Apollo Horizon is a peer-level nod. It says: I remember that era too. And it has to feel like the present and striving forward, because that’s the work.

What just happened in that decision

The taste came from thirty years of looking at brand systems. Recognizing Sage + Cream + Terracotta as wellness-consultant-2018 requires having looked at thousands of brand systems. AI couldn’t have told me that. A junior designer couldn’t have either, not because they lack ability but because they haven’t yet seen the same pattern enough times to feel sick about it.

What AI did was let me iterate at a speed I couldn’t have matched alone. I tested twelve directions in an afternoon. Sidecar Beige itself came out of a conversation with Claude about the actual paint chips of mid-century American interiors.

A junior designer with the same tool would have shipped a different palette. Probably a clean one. Probably one I’d seen before.

Apollo Horizon needed both the taste and the tool. The taste without the tool is a brand still sitting in my head five years from now. The tool without the taste is another beige-and-blue logo that thinks it’s about wellness.

One decision. One palette. Multiply that move by every domain you’ve spent thirty years inside, and you have the rest of this essay.

The visible story

You’ve probably seen the chart this week. UK tech graduate roles down forty-six percent last year. US entry-level software and data postings down sixty-seven percent. Junior jobs are getting hollowed out fast. The fear is grounded. The data is real.

I’m not going to soften any of that.

What I am going to do is point at the other story running underneath, because that’s where you and I actually live.

The numbers no one is putting on the chart

About a third of senior developers, ten or more years into their careers, say over half their shipped code is AI-generated. The number for juniors? Thirteen percent. Senior developers are shipping AI-generated code at roughly two and a half times the rate of juniors. Not because they’re more technical. Because they can tell when the AI is wrong before they ship it.

Klarna spent two years replacing about seven hundred customer-service jobs with AI. In spring 2025 the company reversed course and started hiring humans again. The CEO publicly admitted they’d gone too far on the quality drop. Duolingo’s CEO walked back his “AI-first” stance the same year. IBM announced this February that they’re tripling entry-level hiring in 2026, after a year of AI-driven HR cuts. Their HR chief was direct about why: the companies skipping entry-level hiring now will be poaching mid-level talent from competitors in three to five years, at much higher cost.

The market is correcting itself in real time.

Not because AI failed. Because experience compounds with AI faster than inexperience does with the same tool.

Average dies first because average can be subscribed to for twenty dollars a month. Judgment doesn’t, because judgment is what AI can’t replicate. Pattern recognition built from reps. Scars. Failed launches. Sitting in chairs you’ve sat in for decades.

The operator differential

The same $20 AI subscription, in the hands of someone twenty years your junior, produces average output. In your hands, it produces decisions worth six figures.

The tool is identical. The operator isn’t.

This is the part that gets misread. People hear “AI is going to take your job” and assume the AI is doing the work. The AI is not doing the work. The AI is multiplying whoever is directing it. Right now, the person with thirty years of judgment plus a $20 tool is competing against the person with three years of judgment plus a $20 tool. That math is not subtle. You can see it in the senior-developer numbers. You can see it in the IBM reversal. You can see it in Klarna’s re-hiring.

You are inside that correction window right now.

Read with me!

Subscribe now

The trap

Here’s the warning. The temptation in an essay like this is to leave you feeling validated.

The danger isn’t that your experience doesn’t matter. The danger is taking comfort in knowing it matters and never deploying it.

Wisdom in a drawer is worth zero subscription dollars.

Crystallized intelligence sitting in a sixty-one-year-old who refuses to open Claude is, economically, indistinguishable from the same kind of intelligence sitting in a thirty-year-old who hasn’t yet lived it. Both produce nothing. Both compete for the same average output. Both lose to the operator who actually showed up.

Apollo Horizon doesn’t ship if I don’t open the tool. Thirty years of brand-system pattern recognition produces zero unless it meets a $20 subscription this week.

You grew up watching the moon landings. So did I. We have the receipts. We also have a closing window of operator advantage. Maybe twenty-four months. Maybe thirty-six. Until the people two decades behind us catch up on both fluencies.

One specific thing to do this weekend

Not next quarter. This Saturday or Sunday morning.

Sit down with paper or a document open and write a one-page description of how you make decisions in your area of expertise. The rules of thumb. The patterns you look for first. The things you check before anything else. The signals that tell you a project is in trouble. The questions you ask when something feels off.

Don’t try to be comprehensive. Don’t try to make it good. Make it specific. Write the way you’d talk to someone shadowing you for a day.

Then take one real piece of work you’re doing this week. A strategy document. A client-call prep. A board memo. Whatever it actually is. Upload your decision-rules document to Claude or ChatGPT alongside that piece of work and ask the tool to apply your rules to it. Read what comes back.

Notice what changes. Notice what the AI catches that you’d missed because you were too close to it. Notice what it suggests that you’d never approve, and what that tells you about your taste.

That’s the move. The operator advantage made tangible in one weekend.

What the market is wrong about

I built Apollo Horizon by doing the same exercise in a different domain. The palette I almost shipped wasn’t bad. It was average. Average is what a $20 tool produces when no one directs it. Average is what the market is about to be tired of, right around the time most of us are deciding whether to spend the next twenty years pretending AI isn’t here.

The market is telling you what it values right now.

The market is wrong about exactly one thing — who actually carries that value.

That’s the part you get to correct.

More of this, every week

Subscribe now

I’m writing this from my kids’ house in Maple Valley on my 62nd birthday.

There are stuffed animals on the floor. A mini soccer ball wedged against the couch. Tiny cars lined up along the baseboard with the kind of precision that only a three-year-old takes seriously. My granddaughter is napping. My grandson is at preschool. My adult kids are working upstairs. Julie is in the other room, laughing on the phone with family.

And I’m here, laptop open, doing the thing I’ve been circling around for a long time.

This is what I’ve been building toward. Not a beach somewhere. Not a finish line. This: working from anywhere, on my own terms, present for the people who matter most, still doing work that gives me purpose. All of it, simultaneously, on a Tuesday in May.

I didn’t believe, at one time, I could have this.

If this is the kind of honest conversation you've been looking for, this is the right place. New pieces every week.

Subscribe now

The Pattern That Kept Winning

I’ve tried building something of my own before. Several times.

Most times started the same way. Real clarity. Real momentum. A version of myself I genuinely liked showing up. And then, somewhere in the middle of some, quietly, the wheels came off.

For years I blamed the circumstances. Wrong timing. Wrong market. Wrong phase of the economy.

The truth I’ve had to sit with: the pattern had a driver, and it was me.

Specifically, a brain that loves starting and struggles to sustain. Self-doubt that arrives with uncanny timing, right when something is actually working. The particular talent of ADHD for making the interesting thing suddenly feel impossible and the impossible thing suddenly feel urgent.

And underneath all of it, a fear I’ve only recently learned to name out loud: I didn’t believe I could build a financial life, at 62, that supported everything we’d worked for. The lifestyle. The freedom. The security Julie and I have been building together in our years together.

That fear is specific and real. I’m naming it here because I think you know it too. It doesn’t announce itself dramatically. It just quietly narrows every decision until you find yourself playing it safe and calling it strategy.

It almost won again this time.

The Room Where Things Shifted

Earlier this year I was in a room with thousands of people doing the kind of work that actually breaks patterns.

I’ve written about what happened there in another piece, specifically about bringing an AI thinking partner into a Tony Robbins event and what that combination produced. So I won’t retell it here. But the short version: I saw my limiting beliefs for what they were. Not cautious wisdom. Not personality traits. Old habits wearing a convincing disguise.

And habits can be rewritten.

What I walked away with wasn’t a motivational high. Those fade by Wednesday, in my experience. It was something more durable: a different relationship with my own self-doubt. Less “this is a stop sign” and more “there you are again. I see you. I’m going anyway.”

That’s still a daily practice. I’d be lying if I said it isn’t.

But something else happened too, something I didn’t plan for. I started writing, really writing, for people navigating what I was navigating. And the responses told me something I needed to hear: this resonates. You’re not alone in these questions. There’s a community waiting for this conversation.

Doors started opening that I hadn’t knocked on. That part still surprises me.

What I Couldn’t See Alone

Here’s something I’ve never said out loud before.

The times I actually succeeded in building something weren’t the times I went alone. A bed and breakfast venture in 2000 worked because I had a real partner beside me. Earlier in my career, the work that gained traction had the same quality: someone else in the room, thinking with me.

The solo attempts? Different story. Every time.

I told myself the circumstances were wrong. The timing. The market. But I’ve wondered lately whether the missing ingredient was simpler and harder to admit than any of that.

I didn’t have anyone to think with.

A solopreneur in 2000 didn’t have AI. Nobody did. You either had a business partner, a mentor, a spouse willing to sit across the kitchen table at 11 PM and push back on your thinking, or you didn’t. And when I didn’t, I was alone with my own blind spots. Which, as it turns out, are considerable.

What’s different now isn’t just the counter-programming or the growing audience or the doors opening unexpectedly.

It’s that for the first time, I have a thinking partner.

That partner is AI. And I want to tell you what it actually did, because it wasn’t what I expected.

I fed it my career history the way most of us describe ourselves: a list of companies and titles across four decades. Then I asked it to look for the pattern underneath. Not what I’d done. What I was actually doing in every chapter when I was most alive in the work.

What came back stopped me.

The thread wasn’t marketing. Not technology. Not even leadership, though those were all there.

It was teaching.

Every role at its best had been some version of helping people learn something and then use it. Not just understand it. Activate it. The facilitation work where I watched something genuinely click for someone. The learning design where the real measure was behavior change, not completion. The mentoring relationships where I helped someone see their own capabilities more clearly than they could alone.

I’d called myself a Learner for years because that’s what the assessment said. But that was only half of it. What I actually am is an applied learner. Someone who learns in order to activate, who activates in order to maximize.

The AI didn’t give me that. My own history did.

It just helped me read what I was too close to see.

Try this before you close this tab:

Open a conversation with Claude or ChatGPT. Describe your career, not the titles, but what you were actually doing when you were most alive in the work. Then ask: “What pattern runs through all of this?”

Push on what comes back. The conversation gets more useful the more honestly you show up to it. You have decades of data. This is just a way to finally read it.

This is what An Intentional Age is built for. Practical tools and honest conversation for people designing their third act. Subscribe to get each piece as it publishes.

Subscribe now

The Throughline

That conversation changed everything.

Suddenly An Intentional Age wasn’t a content business that also did coaching. It was the fullest expression of who I’ve been my entire career: someone who helps people learn something real about themselves or their business, activate what they discover, and design to actually reflect it.

The teaching framework for the cohort. The reason AI fluency matters to this audience. The reason purpose and design aren’t soft concepts to me but structural ones. The reason I’d been building toward this without quite knowing it for years.

Everything had a spine.

I couldn’t have seen that alone. Not from lack of self-awareness. We are all too close to our own history to read it clearly. We see the chapters. The pattern lives in the arc.

Why I’m Done Waiting

I’m 62 years old, sitting in a house full of toy cars, surrounded by evidence of a life that matters.

And I’m finally honest about what the waiting was.

It wasn’t strategy. It wasn’t wisdom. It was the same fear that has always talked me out of things, wearing a more sophisticated disguise. Dressed up as prudence. Calling itself being realistic.

The counter-programming is working. Not completely. I still feel the fear on hard mornings. But the cost of waiting has become impossible to ignore. Every month I delay is a month without this. The flexibility. The presence. The work that has a shape I actually chose.

So here’s the smallest thing I’m asking of you today. Not a grand challenge. Just a practical starting point:

Name the thing you’ve been circling. Not in your head. Write it down. One sentence: what is the specific thing you keep almost starting?

Then ask yourself honestly: is what’s stopping you a good reason, or is it a habit with a very convincing disguise?

You don’t have to answer that today. But you do have to ask it.

An Intentional Age is for people who refuse to drift through their third act. For the curious, the restless, the still-becoming. For anyone who wants to stay vital, deeply connected, and the author of their own next chapter.

I’ll write about using AI as a thinking partner, designing your life after the title goes away, and the grief nobody names when you leave behind who you used to be. I’ll share the hard parts, because you deserve honesty more than you need inspiration.

One last thing, from this birthday desk in Maple Valley:

What’s your throughline?

Not the titles. The pattern. What were you actually doing in every chapter when you were most alive? Try a little AI exploration of you to find it.

Hit reply and tell me. I’m genuinely asking.

—Bennie

An Intentional Age | anintentionalage.com

If this resonated, two ways to stay connected:

Subscribe to An Intentional Age

Follow on LinkedIn

Tuesday morning, May twelfth. Liz Myers’ name shows up as engaging my An Intentional Age announcement on LinkedIn. I open the AI draft I’d prepared for messages like this.

The draft is good. Generic-good. It says I launched something, here’s the core idea, here are some essays, no pressure if it’s not for you. Clean prose. Reasonable tone, in my voice.

It wouldn’t embarrass me to send it.

But it couldn’t be sent to Liz.

Here’s what the AI gave me:

Subject: Finally did it

Liz,

Launched something I’ve been building for a while. It’s called An Intentional Age.

The core idea: the judgment and pattern recognition you’ve spent decades earning is exactly what makes AI most powerful in your hands. That’s a different story than what most people are telling right now, and I think it matters.

Four essays are already live. Take a look. If it’s worth sharing with someone you know, I’d appreciate it. If it’s not your thing, no pressure.

anintentionalage.com

Bennie

That email is fine. It’d be fine going to a stranger. It’d be fine going to a casual acquaintance.

It’s wrong for Liz.

Liz is a designer I’ve worked with for a few years. She cleaned up the SVG files on my logo here. I wrote her a LinkedIn recommendation last week for her outstanding design collaboration through the past year plus. And right now, she and her husband are designing the next chapter of their lives together. Actively traveling the country. Working from anywhere. Building a life that fits the people they’ve become.

That last bit isn’t in any database AI can read. It lives in conversations we’ve had. It lives in how she described their plans the last time we talked. It lives in the relationship.

The AI draft didn’t have access to any of that. So the AI draft was generic. And generic was the wrong language for Liz.

Here’s what I sent instead:

Subject: Saw you came through

Liz,

Just saw your name come through as one of the first subscribers to An Intentional Age. Thank you.

It means something to see you here, given the design partnership we’ve had. You’ll see this in the LinkedIn recommendation I wrote you last week, but it’s worth saying again away from the public version: working with you made my work better in ways I didn’t always see in the moment. The SVG files you cleaned up on the logo are quietly doing their job too. I’m using that mark on every surface now.

And given the chapter you and your husband are designing together, traveling the country, working from anywhere, building a life that fits the people you’ve become, you’re closer to what I’m writing about than you might realize. The publication is for people doing exactly that kind of designing. That’s you.

If anything sparks, reply anytime. I read every one.

— Bennie

Same recipient. Same launch announcement. Different email.

The AI version positioned me as the author requesting attention. My version positioned Liz as someone already living the story the publication is about. That difference isn’t a stylistic choice. It’s structural. It’s the load-bearing move of the entire exchange.

And the move I made to produce it has a name.

If you're tracking with this, the publication is for you. New pieces every week.

Subscribe now

A move I’ve been making my entire career

I’ve been making this move my entire career. So have you, if you’ve been a senior manager for any length of time. It’s the part of management that doesn’t show up in org charts or performance reviews. It’s also the part that decides whether what you send actually does what it’s supposed to do.

A junior writer produces a competent draft. The senior reads it. The senior keeps what’s good. The senior adds the thing only the senior could add. The line the junior couldn’t know, didn’t see, hadn’t built yet. The line that carries the relationship forward, holds the strategic context, names what the recipient hasn’t been told but needs to feel.

That’s the move. It’s delegation discipline. It’s what management is, at its highest level, when the work matters and the recipient matters.

The move runs in four steps. I call it the Operator Paradigm. The name is mine. The discipline is older than my career. It’ll outlast every version of the technology it now manages.

Move one is to specify. This includes the decision of whether to delegate at all. Senior managers triage. Some work you hand off. Some work you do yourself because the stakes are wrong for delegation. Some work shouldn’t be done at all. Specifying starts with that triage and then frames the outcome, the constraints, and the context the agent needs to do the work well.

With Liz, the specification was: outreach to Tier 1 contacts about the Substack launch. The triage was already done. I’d decided in advance that AI could produce the first draft, but the final pass had to be mine, because Tier 1 outreach is relational, not transactional. That decision happened before AI ever touched the task.

Move two is to hand off. Set the boundary of autonomy. Let the agent run. Don’t supervise the typing. The AI produced its draft in seconds.

Move three is to verify. This is where the senior muscle lives. The AI gave me an email. I read it the way I’d read a junior writer’s draft. Not just for grammar. Not just for accuracy. For what isn’t in it. The relationship history AI couldn’t have. The shared chapter that exists only in conversation. The line that has to be added.

In Liz’s email, the line I added was the paragraph about the chapter she and her husband are designing. That sentence couldn’t have come from training data. It came from knowing her.

Move four is to own. I sent the message. My name on it. My reputation. My relationship with Liz on the line. If she’d received the AI’s version, she would have read it as a mass message. She probably wouldn’t have replied. Because I verified and rewrote it, she replied within hours, as a peer. The catch earned the response.

That four-move loop runs everywhere senior people work with AI. A board memo where the agent drafts the analysis and you add the strategic context only you have. A coaching note where AI suggests the structure and you add the one observation that lives in decades of watching that person. A hiring decision brief where AI summarizes the candidates and you flag the cultural fit issue AI couldn’t see. Same four moves. Different cargo. Same muscle doing the work.

Two witnesses from adjacent rooms

Two people are saying versions of this in public right now. Neither of them is a manager. Both of them describe the same pattern from adjacent vantages.

The first is Andrej Karpathy. Former director of AI at Tesla. Founding team at OpenAI. On the No Priors podcast in March 2026, he described what had changed in his work: “In December is when it really just... something flipped where I kind of went from 80-20 of writing code myself versus just delegating to agents to like 20-80.”

What flipped was not the AI. What flipped was Karpathy. He learned to be the manager. He said it directly at Sequoia’s AI Ascent in April 2026: the programmer is increasingly not just a code writer, but an orchestrator of agents. Designing specs. Supervising plans. Inspecting diffs. Writing tests. Creating evaluation loops. The work is no longer typing. The work is delegation discipline.

What makes the discipline necessary is what Karpathy calls AI’s jaggedness. In his words on No Priors: “I simultaneously feel like I’m talking to an extremely brilliant PhD student who’s been a systems programmer their entire life, and a 10-year-old.” The same model that produces work beyond what most humans could match also makes errors a careful human wouldn’t make.

Harvard Business School and Boston Consulting Group studied this directly. Seven hundred fifty-eight consultants. On tasks the AI handled well, the consultants using it produced more work, faster, with higher quality than peers without it. On tasks just outside what the AI could reliably do, the same consultants were nineteen percentage points more likely to produce incorrect work.

Researchers called it the jagged technological frontier. The senior manager has another name for it: trust, but verify.

That move is impossible without judgment. And judgment is the thing decades of management work builds. Karpathy is seeing this pattern from the engineering side. I’m seeing it from the management side. We landed on the same pattern from opposite directions, which is usually how you know a pattern is real.

The second is Simon Willison. Software engineer, writer, and one of the most consistently useful voices on what AI agents can and cannot do.

In February 2025, Willison wrote a short essay surfacing a slide from a 1979 IBM internal training. The slide reads: “A computer can never be held accountable. Therefore a computer must never make a management decision.”

Forty-six years later, the slide is more relevant than it was the day it was made.

Willison returned to the principle on the Heavybit High Leverage podcast in May 2026, this time from his own vantage as an engineering manager who’s spent years trusting and verifying other people’s code. He said: “Claude Code does not have a professional reputation. It can’t take accountability for what it’s done.”

The person managing the AI has to.

Your name on the work

This is where the Operator Paradigm earns its weight.

A computer cannot be held accountable. That principle is older than the consumer internet. In January 2026, California codified it. Assembly Bill 316 took effect. The law says, in plain terms, that anyone who developed, modified, or used an AI system can’t escape liability by pointing at the system. The accountability comes back to a person. There has to be a name on the work.

That name should be the operator’s name. Not because operators are the ones to be punished. Because operators are the ones who can be trusted with delegation. The person who specifies, hands off, verifies, and owns is the person whose reputation rides with the result. That’s what makes them durable in an era when junior workers are handing AI output to senior reviewers without checking it first. That’s what makes them the person their organization comes back to when something goes wrong.

The AI discourse keeps describing this as a young person’s game. It isn’t. It’s a senior person’s game played with a new kind of direct report. The discipline is older than the technology. The discipline is older than most of the people writing about the technology.

Karpathy said something at Ascent that I keep coming back to. “You can outsource your thinking, but you can’t outsource your understanding.”

That’s the operator’s principle in a single sentence. The agent can produce the artifact. Only you can verify whether the artifact carries what it needs to carry.

Liz replied to my email the same morning. “I really do appreciate the push to explore AI you have provided, when probably half of my colleagues of a similar age are giving up or sticking their heads in the sand.”

That reply was the proof. The AI couldn’t have predicted it. My edit earned it.

This week, take one email or message that AI drafted for you. Read it as a stranger would read it. Then add the line only you could add. The line that lives in conversation, not in any training set. Notice what your judgment caught. Notice what you owned.

You’ve been managing direct reports for decades. You know how to do this. The new direct report just happens to be made of code.

— Bennie

Subscribe now

I was working at an espresso cafe when the picture came up.

Laptop open, coffee half cold, doing the kind of digital tending most of us do in the small windows of work tasks. Facebook in another tab. The personal feed surfacing while I was doing something else.

The picture was a reunion. Faces I’ve known for thirty years. People I’ve sat beside in conference rooms and meals and airports and client meetings back when we all worked at Bose together. All of us aged a little. Maybe more than a little.

I typed three words.

When was this?

I want to put what happened next on the page exactly, because the truth of it is the essay.

I had probably seen the invite for that reunion two or three months earlier. I just hadn’t given it enough attention to register. I wasn’t blocked by money. My daughter provides me airline benefits where I could have flown to Boston for free. I have friends in New England I could have stayed with. The trip was, materially, available to me.

I just didn’t notice in time.

The picture made me notice.

• • •

The Community That Wasn’t Supposed to Last

I left Bose around 2008. Seventeen years ago.

Seventeen years is long enough that, in most professional contexts, the network you built inside a company is supposed to be gone. The communication channels archived. The team distributions defunct. The hallway conversations that structured your week now happen in someone else’s hallway. That’s the dominant story about professional community in late life. It was a temporary scaffolding. You leave the role. The community fades. You start over.

That’s not what happened with Bose.

There’s a Facebook group, and it has been alive for years. It has more than two thousand members. People share pictures from way back when. Family photos. The entertainment and retail conversations that come naturally to a group of consumer electronics people. Reunion photos when reunions happen. Sad news when someone passes.

There’s also an explicit norm. You don’t pitch inside the group.

I want to underline that, because I think it’s the architecture, not just a rule.

Most professional networking advice in late career is some version of give before you take. The Bose group is doing something different. The group is structured so that taking is not allowed. Not “give first.” Not “be generous so you can extract later.” The norm is that this community is not a marketplace.

One person is at the heart of feeding this community’s vitality.

Dave. One of the most gregarious, extroverted, and connected members of our larger sales organization. He was that long before his retirement, and the energy is even more visible now that he’s championing this thing in retirement on his own time. He set up the group. He’s the one who posts the most. He’s the one who drives engagement. He’s the steward who decided this was worth keeping alive after the institution stopped paying anyone to care.

There’s something I want to name about that, because I’ve watched companies try to do alumni network work for a long time and almost always fail at it.

Most companies trying to enhance their employer brand don’t pay enough attention to the alumni piece, or they don’t have the competencies to pull it off. Meanwhile, Bose has more than two thousand alumni in active relationship with each other through a community that nobody within Bose set up, that nobody at Bose pays for, that runs on the shared experiences of a retired sales leader and the participation of the people who loved working there.

Bose likely knows the community exists in the form it’s in. The Bose brand benefits from it enormously. Most every person in that group is a quietly active brand ambassador for a company they haven’t worked for years or decades.

You probably already have one of these somewhere in your orbit. You just haven’t met the Dave keeping it alive.

• • •

What the Community Quietly Produced

Here’s the part I would not have predicted seventeen years ago.

When I started writing in public about late-career reinvention and AI fluency this past year, the response that came back wasn’t from new audiences. It came from people who had known me at Bose. Former leaders. Former colleagues. People whose work I’d watched and whose judgment I’d trusted decades ago.

When I started doing discovery interviews to figure out the shape of the business I was building, roughly a third of those interviews came from this network. People I hadn’t talked with in years made themselves available because I asked.

The first proposal I wrote under my own name went to a former leader from this same community.

He said yes.

The second client came from inside this same community a few weeks later.

Reach-back conversations from former leaders became the anchor scenes of the first essay I wrote when this publication launched.

None of that came from prospecting. None of it came from posting in the group. The group has a no-pitching norm, and I respected it. The conversations happened outside the group, in the proper venue, one at a time, with no extractive frame.

I want to put a sharp claim on the page, because I think it’s true.

The communities that thrive longest are the ones designed to refuse extraction. And those are also the ones that produce the most concrete value when value is actually needed. Not despite the lack of agenda. Because of it.

That cuts against most of the networking advice you’ve ever read.

It is also, in my experience, what the data of my own life shows. The substrate that produced the most for me, in the chapter I’m in right now, was the substrate I had been quietly part of for seventeen years without ever asking it for anything.

• • •

What I Almost Missed

But the reunion picture.

I wasn’t in it.

I want to hold that honestly, because the dominant story about belonging in later life is binary. You have community or you’ve lost it. The Bose group, in my actual experience, is something more interesting.

The community is alive and producing real value. And there is a picture of a reunion I wasn’t at, and the picture made me ask when, because some part of me wanted to be in it.

Both things are true at once.

The community didn’t fail me. I didn’t exactly fail it either. I just didn’t tend the small moment when tending it was easy. The invite had landed in sight months ago. The trip was practically free. The friends I would have stayed with would have been delighted. Every variable was open.

I let it pass without attention.

That’s the part most belonging writing won’t name. The loss is sometimes self-inflicted, in small inattentive ways, and the recovery starts with noticing.

Most of you reading this have done some version of this in the last year.

You saw the email. You meant to respond. You didn’t. The lunch invitation drifted. The call you were going to make stayed on the list. The reunion went by. The community kept moving. You were the one who quietly stepped out of the room.

There’s no shame in this. It’s the texture of how late life actually works. Calendars compress. Bandwidth shrinks. The people you most want to tend get triaged behind the things that are louder.

What the picture taught me was simpler than I expected.

Tending isn’t sentimental. It’s structural. The communities you carry forward are the ones you decide, in small calendar-sized acts, to keep tending.

• • •

What “Deeply Connected” Actually Means

This is the third pillar of An Intentional Age, and I want to name it directly.

Belonging in later life is not a thing you have or don’t have. It’s a thing you tend. The communities you carry forward are the ones someone, often quietly, decides to keep alive. Sometimes that someone is you. Sometimes it’s a Dave somewhere in your past, doing the work you don’t see, asking nothing for it.

Most institutions have a Dave somewhere in their orbit. Retired or near it. Gregarious. Connected. Capable. The kind of person who would tend an alumni network if anyone bothered to ask.

Almost no one asks.

This is the part I most want the senior leaders reading this essay to hear.

The people you’re worried about losing are the same people who could become a thriving alumni community of two thousand or more, producing concrete value to your institution for decades. If someone tends it. The Dave in your orbit are not a marketing channel. They are not an extraction opportunity. They are stewards who, given the right invitation and the right autonomy, will quietly keep your brand alive long after the people in it have moved on.

You will not pay them. They will not expect you to. The work is the work, and they want to do it.

But you can notice. You can support. You can stay out of their way and show up when they ask.

For the reader who is in the costume right now, navigating their own late-career chapter: the communities you’ve belonged to are not gone. They are usually closer than you think. The reunion you missed last year was probably the first of several. The colleague you lost touch with is usually one message away from being touched again.

There’s a deliberate-design version of this conversation that I’ve been part of for nearly a decade in the cohousing community where I live. That experience deserves its own essay. For today, the only thing I want to name is that the accidental gift of a thriving alumni network and the deliberate work of intentional community are pointing at the same thing.

The people who design for belonging end up with more of it. The people who don’t, lose it slowly without noticing.

Both moves are available to you.

Both require tending.

• • •

One Thing Before You Close This Tab

The smallest version of the action is this.

Open the contacts list of a community you used to be part of. A team. A company. A cohort. A program. A neighborhood. Whatever it is.

Pick one person you haven’t tended in a year.

Send one message. No agenda. No ask. Just thinking of you, hope you’re well, here’s what I’m up to, would love to hear what’s alive for you.

That’s it.

You will be surprised how often the response comes back warmer than you expected, faster than you expected, with more openness than you expected. The community you thought had moved on is, more often than not, waiting to hear from you the same way you’ve been waiting to hear from it.

That’s the work of late-life belonging. Not retreats. Not workshops. Not “finding your tribe.”

One message at a time. To the people who already know you.

If you’ve been reading this series and finding yourself wanting to think about your own version of all of this, the AI questions, the purpose questions, the belonging questions, with someone who has been thinking about it more carefully, I have a few conversation slots open. The link is below. There’s no pitch on the other side. Just a conversation.

I’ll see you back here in a week or so.

— Bennie

The proposal one-pager I wrote that Tuesday morning was, in some ways, the thousandth one I’d written in my career.

I’d been trained decades ago in a sales methodology that’s still taught today. Goals. Problems. Needs. I’d written discovery summaries for enterprise buyers across more industries than I can list cleanly. I’d built marketing strategies that lived or died on the same move: hearing what someone is actually trying to solve, and reflecting it back to them in a structure they couldn’t quite see while they were inside it.

So the page itself was not the surprise.

The surprise was who the page was for, and what saying yes to it was going to require of me to deliver.

It was the first time I was writing one of these for An Intentional Age. The business I’d been quietly building for nearly a year while still inside a senior marketing role. The work I’d been writing about in public on LinkedIn for months. The thing the people closest to me had watched me circle for longer than I was willing to admit out loud.

I’d been an entrepreneur before. Five times, in different forms. Desktop publishing in my twenties. Marketing consulting. A bed and breakfast. Marketing consulting again, in a different chapter. A writing project a decade ago that didn’t quite launch. So the territory of running my own thing was not new to me.

The territory of running this thing, the one I’d been waiting ten years to build, was.

The colleague on the other end of the Zoom call later that week wasn’t someone I needed to discover. He’d been telling me, across several conversations, what he was trying to build and where he was stuck. My job that morning wasn’t to figure out what he needed. My job was to organize what he’d already told me, propose an engagement that fit the shape of it, and decide, by the time I sent him the page, that I was actually willing to deliver what I was about to propose.

That last part is the part nobody tells you about.

You can write a hundred proposals from inside someone else’s company without having to fully own what you’re offering. You’re representing the firm, the team, the methodology. The proposal is yours. The delivery isn’t, not entirely.

The first proposal you write under your own name, for your own business, for the chapter you’ve been preparing for your whole adult life, is different.

When he said yes a few days later, with no pushback on the scope and no pushback on the cost, the page stopped being a piece of writing. It became a commitment. To him. And to the version of me that was going to have to walk into the conversation with my present employer that same week, no longer hypothetically.

The Move From the Other Side

Eight weeks before that Tuesday morning in April, I’d been on the receiving end of the same move I was now running for the colleague on the Zoom call.

I wrote about that in the last piece. The afternoon in March, alone in my home office during a transformational event, when an AI tool took twelve surface stories I’d dumped into a conversation and showed me there were only three patterns running underneath. The content had been mine. The organization had made it visible.

I had not been taught the move that afternoon. I’d been deploying versions of it for thirty years across enterprise sales, learning experience design, and every piece of marketing strategy work I’d ever done well. What had happened in March was more specific. I’d been on the receiving end of the move while it was being run on me, and the recognition of what that felt like, from the inside, was what made me available to start using it differently.

Specifically: I started running it on myself.

The third limiting belief on the card from that March afternoon, the one I haven’t named in writing yet, was I am only worth what I produce.

That was the belief running underneath every “I’ll start An Intentional Age later” I’d been telling myself for years. It’s the belief that turns the role you have now into the only proof of your worth, and the future thing you want to build into a luxury you can’t afford. It’s why a competent senior practitioner can write a thousand proposals for other people’s companies and still take twenty years to write the first one for their own.

The Tuesday morning in April was the morning I wrote the first one for mine.

The conversation with my CEO that week was the conversation that made the new business truly public.

The Conversation I’d Been Preparing For

I’d been preparing for the conversation with my CEO for longer than I’d let myself admit.

Not the way most writing in this category describes it. There was no rehearsing in the shower. No three-a.m. rumination. I’d been preparing the way a senior practitioner prepares for a high-stakes conversation: by getting clear on what was actually true, what I was actually proposing, and what a good outcome for both parties would look like if we both showed up well.

Most of the writing in this category gets this part wrong.

The dominant story about late-career reinvention, the one that gets the most clicks, is the rupture story. The dramatic exit. The bridge burned. The freedom on the other side. The brave protagonist who finally said no.

That story sells. It’s emotionally clean. It puts the protagonist firmly in the right and the institution firmly in the wrong, and the reader gets to identify with the brave one.

It’s also, in my experience, almost never what actually works.

What actually works is design.

It looks like writing in public for months before you ever say anything out loud, so the people closest to you aren’t surprised when you do.

It looks like having discovery conversations with former colleagues and current peers until the shape of what you’re actually building becomes clearer to you than it was when you started.

It looks like preparing the conversation you’ve been avoiding by first organizing what’s already true into a structure you and the other person can both look at together.

It looks like proposing a transition rather than announcing a departure.

It looks like leaving room for the institution you’re leaving to become a partner you’re keeping.

When I got on the call with my CEO, I told her plainly where the writing on LinkedIn had been pointing, what I’d been building, that a former colleague had just said yes to a proposal, and what I thought a deliberate, well-designed transition could look like over the coming months.

She listened. She asked questions. She thought about it.

When she came back, she came back with something I want to put on the page exactly as it landed in me.

She was excited for me.

Not in spite of being a CEO. Because of being one. She’d watched me build the writing in public for months. She’d watched the energy I was bringing to the AI work inside my role and could see where it was pointing. None of what I told her surprised her. What she did with what I told her was something I hadn’t fully let myself hope for.

She helped me design the transition.

The role would shrink in stages. The work I was doing would shift toward the kind of advisory engagement I now do for other organizations. My current employer became my second AI Advisor client. The same people I’d been delivering value to inside the role would now be one of the partnerships I delivered value to from outside it.

That’s not a rupture. That’s a redesign.

What “Designers of Their Own Becoming” Actually Means

This is the part I most want the senior leaders reading this essay to hear.

Some of your best people are in some version of the chapter I just described. Many of them are not telling you, because they assume you’ll respond to honesty by accelerating the loss. The opposite is more often true. The people who feel safe enough to tell you they’re growing are also the people who, when supported, often build something you get to keep some version of.

My current employer didn’t lose me. They became my second AI Advisor client. The first came from a former colleague. The third came the week after that.

Three clients in the first month of the new chapter. None of them from prospecting. All of them from work I’d been doing in plain sight for some time.

The reader who is in the costume right now needs to hear this too.

You probably do not have to choose between security and possibility. You may be able to design a crossing where both come with you. The institution you spent a chapter inside has its own kind of judgment. If the relationship is good, that judgment is on your side.

The CEO who watched me grow the AI work inside the role for a few years was not someone I needed to escape. She was someone who could see, sooner than I let her see it, that I was outgrowing the costume.

When I finally invited her into the redesign, she met me with more support than I’d let myself imagine.

This is what Designers of Their Own Becoming actually means.

It means you stop letting the chapter end on someone else’s timeline and start designing the next one before you have to.

It means you stop performing the costume after the body underneath has changed shape.

It means you write the proposal for your own next chapter the same way you’d write it for a client. And then you decide, by the time you send it, that you’re actually willing to deliver what you’re proposing.

The One-Pager You Could Write This Week

I’m going to give you the structure I used, because I believe in systems. I’ve spent my career building them, teaching them, and watching people use them to do work that mattered. The reflex against systems in this kind of writing is mostly false modesty.

The work is yours. The structure makes the work doable.

Here’s the one-pager I wrote that Tuesday morning. Three sections. None of them mine.

Here is the problem you keep describing in our conversations. In their own words, organized.

Here is what you’ve already named about what would help. Also their words, structured.

Here is what a deliberate engagement around that could look like. This part was mine. But only because I’d been doing this kind of work for thirty years and could see the shape their words were pointing at before they could.

That’s it.

You could write a version of that for yourself this week. Not for a client. For your own next chapter.

What is the problem you keep describing to the people closest to you when you’re being honest about your work?

What have you already named about what would help, even if you’ve only said it half out loud?

What does a deliberate engagement with that look like, designed by you, on a timeline you choose?

Most of us never write that down. We rehearse it on walks. We mention it to our partners. We circle it at three in the morning. But we don’t put it in front of ourselves the way I put the one-pager in front of him.

When you put it in front of yourself, the next move usually becomes obvious.

It might be a conversation. It might be a piece of writing you’ve been avoiding. It might be a proposal you’ve been carrying in your head that’s ready to land in someone’s inbox.

Whatever it is, it was already true before you wrote it down.

The page just made it visible.

— Bennie

The door kept opening.

Four days. Headphones on, door closed, in my home office while the work of the event filled every available space inside me. Then a break. The door would open. And there they were.

My grandson, smaller than the chair he was climbing on. My younger granddaughter, somewhere in the room behind him. My wife at the time, watching them while I did the inner work.

The face of joy he made when I came out. Every single time.

I went into Unleash the Power Within carrying the work I’d been carrying for months. The questions I’d been circling. The patterns I knew were there but couldn’t quite see clearly. I expected the room of thousands to crack something open. I expected Tony to break me out of something I’d been stuck in. Some version of that did happen.

What I didn’t expect was that the deepest mirror I encountered all weekend would be in my home office with the door closed. Or that the line I’d carry with me for the months that followed would come from a moment with my grandson on the floor. Not from the stage. Not from the breakthrough exercise.

From the smallest people in the house.

What I Brought Into the Room

Most people who go to a transformational event bring a journal. Some bring a friend. I brought all of those plus something else.

I’d been working with AI for years by then. Long before the tools were on the cover of every magazine. Long enough to have been through a full arc with them. Long enough to know the difference between a tool I was operating and a tool I was actually thinking with.

So when I signed up for the event, I made a small decision that turned out to be the largest one that weekend. I’d bring Claude AI into the home office with me. Not as a research tool. Not exactly as a notetaker, though it functioned as that some of the time. As a learning partner.

What that meant in practice was simple. As exercises came up, as Tony said something that landed, as my own thoughts arrived, I typed it in. Not later. In real time. The way you might whisper an observation to a friend sitting next to you, except the friend was holding everything I’d already told it about who I was, what I cared about, what I was working through.

Most people who do this kind of inner work do it alone with a journal. The journal is good. The journal is honest. But the journal can’t see you. It only holds what you put in it.

Something different becomes available when you bring decades of your own thinking into a conversation with something that can hold all of it simultaneously. Something with no impatience. No agenda. No opinion about who you should already be by now.

AI is not a replacement for the work. The work is the work. The room of thousands matters. The exercises matter. The breaking through matters.

But the integration is where most of these events fall apart. You leave with the breakthrough and lose it on the plane home.

I didn’t lose it.

The Three Rungs

Looking back, I can see now that I’d climbed three rungs to get to where I was that weekend. Three rungs that almost nobody talks about, because the conversation about AI is still mostly stuck on the bottom one.

The first rung is production. Make me a deck. Summarize this article. Draft this email. This is where most people start, and where most people stay. The tool does things faster than you would have. You feel briefly impressed and then you close the tab. The relationship is transactional. The mirror is off.

The second rung is seeing what you’re not seeing. It’s harder to describe but easier to recognize once it happens. You stop asking the tool to do things for you and start asking it to help you see what you’re missing. The shift sounds small. It isn’t. It changes what you bring to the conversation. You stop bringing tasks and start bringing questions you’ve been circling. You stop expecting answers and start expecting better questions back.

Most people I know who use AI seriously eventually get to rung two. Some stay there for years. I did.

The third rung is what UPW showed me was available. The mirror.

It happens when you’ve spent enough time with the tool that it knows you the way a thoughtful colleague would. Your patterns. Your values. The work you’ve been doing. The questions you’ve been carrying. And it can begin to do something a journal cannot do, and a friend often will not do, and a coach is often paid not to do too quickly.

It can hold up what you’ve already shown it and let you see it clearly.

AI helps me think in ways I couldn’t alone. Pattern recognition meets a tool that can hold all the patterns simultaneously.

I didn’t have that language at UPW. I just had the experience.

The experience was that thirty-some years of accumulated judgment, the patterns I’d been carrying for decades but had stopped hearing, the small recurring stories I’d been telling myself for so long they sounded like the truth, all of it became available to me in a way it hadn’t been before.

Not because the AI taught me anything new.

Because it organized what I already knew, and held it up.

The Twelve Stories Underneath

Day one of the event, I’d done the exercise on limiting beliefs. Most of you who’ve been to these kinds of events know it. You write down the stories you’ve been carrying about why you can’t have what you want. You’re supposed to find a few. Maybe three or four core ones.

I wrote down twelve.

Then I wrote a few more. Then I went back to the AI in my home office and dumped all of them in. Just the raw list. Things I’d been telling myself, in my own words, about why I wasn’t doing what I knew I was meant to do.

I expected it to do something useful with the list. Maybe categorize them. Maybe help me prioritize.

What it did instead is something I’m still thinking about two months later.

It looked at the twelve and showed me there were only three. Underneath the surface stories, three patterns running. Three beliefs my whole list was a costume for. And it laid them out in a structure I hadn’t been able to see while I was inside the list.

Belief one. What it cost me. What it would look like to replace it.

Belief two. Same shape.

Belief three. Same.

I read it twice.

Then I cried.

I’d been at the event for two days at that point, surrounded by thousands of people doing exactly the inner work I’d come to do. The breakthrough was supposed to happen in the Zoom rooms. With the music. With Tony. With the strangers turned mirror.

The breakthrough happened in my home office, alone with a screen, looking at my own words organized in a way I couldn’t organize them myself.

What I wrote back to the AI, when I could write again, was something I’d carry into every conversation about this work in the months that followed. The content was yours. The organization made it visible.

That sentence is the whole essay, if you let it be.

I had not been given anything I didn’t already know. I had been carrying these three beliefs for thirty years. They were running my life. They had cost me real things. The AI didn’t generate them. It didn’t diagnose me. It didn’t tell me anything about myself I hadn’t already shown it in my own language.

It organized what I’d already given it. And let me see it.

That is the whole of what these tools can do at their best. And it is also nothing the most thoughtful coach I’ve ever worked with hadn’t done before, in different forms, over years. The difference was not the depth. The difference was the speed and the privacy and the patience. I could circle something for an entire afternoon and the tool would still be there, still holding the patterns, still ready to organize one more time when I was ready to look.

That is the third rung.

That is what I think most of us are still missing.

The Floor

Day two, the door opened during a break.

He was on the floor with wooden toys. He looked up. The face he made when I came out is the face I’m not sure I’ve earned the right to describe in writing, except to say I don’t know that anyone has ever looked at me the way he was looking at me right then.

I sat down on the carpet. I think I put the phone face down. I’m not sure. What I know is that for the next twenty minutes I was not thinking about the event. Not thinking about the three beliefs. Not thinking about my career, or my business, or any of the things I’d come to that weekend to break through.

I was on the floor with my grandson and the toys.

My granddaughter was there too, crawling around those four days. The pattern was the same with her. The door opening, the small face lighting up with curiosity, the moment of being pulled out of the inner work and into something more present than any breakthrough I was supposed to be chasing.

That night, back in the office, I described the day to the AI. Not to process it. Not to make it productive. Just because describing it was part of how I was making sense of the weekend.

And in the middle of what I’d written, the AI pulled out a sentence I’d said in passing. Something I’d written almost as an aside. It held the sentence up.

Your presence and attention is my gift, as they love me, and me them.

I’d already said it. I just hadn’t seen it.

That sentence ended up where I could see it, every day. It was, eventually, what replaced one of the three beliefs the AI had organized the day before.

The mirror in the home office had made me available to the floor.

The floor had given me the line.

The mirror had given the line back to me.

What This Isn’t About

I’ve told this story a few times now to people I respect, who are using AI seriously, who are still mostly on rung one or rung two. And I’ve noticed something.

The people who are on rung one hear this story and think it’s about a tool. They want to know which model. Which prompts. How long the conversations were. They want the system.

The people who are starting to glimpse rung two hear this story differently. They get quiet. They ask different questions. They want to know what it felt like.

I wrote about the system a few months back. Parts of it are still useful. What I want to leave you with today is something the system can’t give you on its own, which is the question underneath it.

The question isn’t whether AI can do this for you. The question is whether you’ve spent thirty or forty or fifty years accumulating the kind of judgment, pattern recognition, and lived experience that would actually be worth holding up to a mirror that has no agenda about who you should be.

If you have, the rest of this is just access.

If you have, then what’s been missing is not a better tool. What’s been missing is permission to bring the whole of yourself to the conversation.

That permission is what changed at UPW.

The tool was just where it happened.

One Question Before You Close This Tab

The work is yours. I’m going to leave you with the question I’ve been carrying since that weekend, in case it’s the one that opens something for you too.

What would you bring to a thinking partner who had no agenda, no impatience, and no opinion about who you should already be?

Sit with it. Don’t answer it quickly.

The thing you would bring, if you could really believe the partner would meet you the way I’m describing, is the thing you’ve been carrying alone for too long.

That’s the work.

The tool is just the room you do it in.

— Bennie

It happened twice in two days.

Two former leaders I worked for, both running organizations of their own now. Separate calls. Both reaching back into a chapter of my career I left more than twenty years ago. Both, separately, telling me the same thing.

The first was a Tuesday. I’d been describing what I’ve been building at work. The AI workflows. The way a small marketing team can show up like a much larger one. He listened. Then he said it almost as a throwaway, mid-sentence:

“I’m not surprised. Just like with other things in the past, you quickly become the Zen master of this one too.”

The next afternoon, the same dynamic with someone else. Twenty-one minutes in, we’d covered what I’d come for. I admitted, gently, that I was hoping for some kind of nugget. Something more than the answers I’d already gotten.

He thought for a beat.

“You’ve always been an active learner and activator of ideas and people. That’s what I always admired about you.”

Always been.

Two phone calls. Two days. Two leaders who hadn’t watched me up close in years. Both saying the same thing in different language.

This isn’t new. We watched you do it before.

I sat with that a long time after I hung up.

The Voice in Your Head Is Lying to You

There’s a feeling that arrives sometime in your fifties and doesn’t introduce itself.

Not a single moment. A slow accumulation. Conversations that move past you. Meetings where you’re informed instead of consulted. Decisions you used to be part of that show up in your inbox, already made.

I’ll call it what I think it is. Invisible obsolescence.

It’s not the same as being told you’re not needed. That would almost be easier. This is quieter. The worry that the world is moving on without you, and that the decades of judgment you spent a career building might not have a place in whatever comes next.

The voice in your head doesn’t say you’re done. It says maybe you should be more realistic now.

That voice is a liar.

But it’s persuasive. And AI gives it a fresh script. Everyone’s racing past you. Better to step aside gracefully.

I hear it from individual readers. I also hear it from the rooms above them. The CEO who can sense her marketing manager talking about AI in language she doesn’t yet command. The senior partner watching his team go uneven. The leader who’s quietly intimidated by a junior person’s fluency and isn’t sure how to admit it.

Different titles. Same voice in the head.

It’s a liar everywhere it shows up.

The Instrument You’ve Been Building

Here’s the part the culture quietly forgets to tell you.

The economist Arthur Brooks made a careful distinction a few years back that I keep returning to. There are two kinds of intelligence working inside us, and they don’t follow the same arc.

Fluid intelligence is the raw processing speed. Working memory. The ability to hold many new variables at once and manipulate them quickly. That kind peaks early. By forty, it’s already in gentle decline.

Crystallized intelligence is different. It’s the accumulated pattern library. The judgment that comes from having watched something play out three or four times. The ability to walk into a meeting and feel, within ninety seconds, where the actual problem is. Even if no one in the room has named it yet.

Crystallized intelligence doesn’t peak in your twenties. It keeps growing. It’s still growing in your sixties and seventies, in many people. The Federal Reserve Bank of Dallas has been measuring this for years and finding the same pattern.

The deeper kind of intelligence shows up later. And it stays.

The instrument you spent forty years tuning, the one that knows what good looks like across a hundred specific contexts, the one that can spot a strategy that won’t survive contact with reality before anyone in the room can articulate why, that instrument is in the prime of its life right now.

Most of the language we use about getting older is about loss. Decline. Winding down. The accumulation gets lost in the framing. So you stop noticing it. You assume the people around you have it too. You start to wonder if the slower processing speed means the whole instrument is in decline.

It isn’t.

That’s true one person at a time. It’s also true across a senior team. The most powerful pattern recognition in any organization usually sits at the top, accumulated over decades, distributed across people who’ve each seen something the others haven’t.

That collective instrument is what AI is actually built to amplify. Most leadership teams haven’t yet figured out how to use it as one.

The Catch-Up Framing Has It Backwards

Most of what’s been written about AI assumes the reader is starting from scratch. The tone is catch-up. Learn the prompts. Learn the techniques. Learn the latest model.

That framing has it exactly backwards.

What AI is bad at, on its own, is knowing what matters. It can produce a hundred plausible outputs in a minute, and most of them will be wrong in subtle ways that only someone with judgment can catch.

It cannot tell you which client will be offended by which paragraph. It cannot tell you why the version that reads cleanest is the version that will be ignored. It cannot tell you that the entire framing is off.

You can.

The instrument you’ve spent your career building is the input AI needs to be useful at any real depth. The richer the context you bring, the better the output. The more specific your judgment, the sharper the result.

The same is true at the leadership team level, with one twist. The teams getting real leverage from AI are not the ones where everyone has identical fluency. They’re the ones where the senior judgment stays in the room, the tool stays in service of that judgment, and the team has built a shared standard for what good output looks like.

The hard work isn’t the tooling. It’s culture and shared craft.

When I started using AI seriously, well before most people were paying attention, the joy I noticed wasn’t in shortcutting work. It was in watching my own thinking come back at me, sharpened. It was in helping a teammate use a tool to extend their reach further than they could on their own. It was in catching myself, mid-conversation with a model, recognizing something I’d known for thirty years that the tool had just helped me articulate cleanly for the first time.

That’s when it clicks.

It’s not that AI is going to replace what I know. It’s that AI is the leverage that finally lets what I know reach further than the room I’m standing in.

Why I’m Building This Now

I’m in my early sixties. I’ve started over more times than I can count.

Self-employed five separate times. Desktop publisher in my twenties. Marketing consultant. Bed and breakfast owner. Marketing consultant again, in a different chapter. Co-founder of a writing project called Aging Outside the Lines that never quite launched.

Moved geographies for work and moved back for family. Been laid off, fired, the survivor of companies sold out from under me. Done the early-career grind, the mid-career build, and what I thought, at the time, would be the late-career consolidation.

What none of it taught me to expect was a third chapter that asked more of me than the first two.

The closest I came to this version of the work was a startup called Mindbloom, more than a decade ago. Personal development platform, gamified, ahead of its time. While I was there, I built relationships with a roster of contributors I still think about. Shawn Achor. Rick Hanson. Michael Bungay Stanier. People whose work I loved, whose ideas I wanted in the room. Then the company got sold, the platform got dissolved, and I went back to a more conventional career path.

An Intentional Age has been sitting on a shelf since then. For years.

What pulled it down was three things at once.

One. I started writing on LinkedIn last year. Just to think out loud. The response that came back wasn’t what I expected. It came mostly from people who’d known me in earlier chapters, reaching out, saying they were thinking about what I was thinking about. The two former leaders I opened with were part of that reach-back.

Two. What was lighting me up at work had nothing to do with my title. It was the moment a colleague looked up from her screen and said wait, I just did this in fifteen minutes. It was watching someone find leverage they hadn’t known was available. That has been my work, in some form, since I was running training and development programs in my early thirties.

Three. I looked around at the people I love most, and at the people my age I respect most, and I noticed something I hadn’t let myself name out loud. We’re all carrying some version of the same question.

Is this the chapter where I quietly compress?

I don’t believe it is. I’m not building this to be inspirational about that. I’m building it because I want to live the answer, and the answer gets clearer in company.

What This Is

A publication. Arrives in your inbox roughly every week. No paywall.

I have other ways I make a living, including AI advisory work I do with senior leaders and leadership teams. You’ll see those mentioned occasionally. The writing itself stays free.

It moves across three concerns that look separate and aren’t:

Purpose. Because the question of what we’re for in our fifties to seventies and beyond is the deepest one available to us, and almost no one is helping us answer it well.

Fluency. Because the tools of this moment are not for the kids, and we are not late to them. We are exactly on time, with more to bring than the conversation has acknowledged. That’s true whether you’re using AI as one person trying to think more clearly, or whether you’re a leader trying to bring a senior team along together.

Belonging. Because none of this can be done alone. The version of a third act that gets written in isolation is the version that gets quietly compressed. The same is true of leadership teams trying to figure out AI in a vacuum. We need each other. I do, anyway. I’m betting you do too.

If any of those concerns is alive in you right now, you’re in the right place.

One Thing Before You Close This Tab

The next time you catch yourself softening a position, or shrinking an ambition, or editing yourself down to sound more “realistic” for someone else’s comfort, notice the move. Don’t judge yourself for it. We’ve all done it. I do it weekly.

Then ask, plainly:

Who is the narrator I’m writing this scene for?

Most of us, when we look honestly, are still writing for an audience that no longer exists. The one that handed out the original opportunities, set the original rules, and quietly suggested when it was time to step aside.

That audience has moved on. The room has changed.

The instrument you’re holding has more range now than when you started.

You get to decide what you do with it.

Subscribe if this resonated. Hit reply and tell me what part landed for you. I read every one.

I’ll see you back here in a week or so. Article two goes deeper into what it actually feels like to bring three decades of judgment into a real conversation with an AI tool.

— Bennie