How To Manage Your Newest Hire, That Never Sleeps, And Lies With Total Confidence
You have a new person on your team. Let me describe them.
They work all night. They never take a break, never call in sick, never ask for a day off. They finish more in an hour than a strong person finishes in a week. When you correct them, they don’t get defensive. You point out the mistake, they fix it right away, no ego, no sulking.
They also forget everything you didn’t write down. And every so often they hand you work that is completely wrong, said in a calm, confident voice, with no sign that anything is off. A real junior would look nervous. They’d stall, or come ask you a question. This one just hands it over and smiles.
You’ve figured out by now that I’m describing an AI agent.
But here’s the thing I want you to notice. When you read it as a person for those first few lines, you already knew how you’d manage them. You’d sit them down on day one. You’d watch their early work closely. You’d learn where they’re strong and where they’re shaky. You’d build a check on the shaky parts.
Have you done any of that for your agents? Or did you just start handing them work?
That gap is the critical problem. And it goes deeper than it looks. Lets walk through it, one question at a time.
1. Did you hire them, or did they just show up?
Think about how a person joins your team. There’s a start date. There’s an onboarding. You tell them what the team does, how you work, what “good” looks like. You give them small things first. You watch. You course-correct.
Now think about how the agent joined. There was no start date. It just started doing work one day, and then more work the next, and nobody sat it down and explained anything.
That’s the first mistake, and it’s an easy one to fix.
An agent is not magic. It’s a set of instructions, some memory, and some context you give it. That’s it. Which means you can onboard it, the same way you’d onboard a person. Tell it what good looks like. Give it examples. Give it the context a new hire would get in their first week. Start it on small things and check the work. Then give it more.
Most people skip all of this. They expect the agent to be great on day one with no setup, and then they’re surprised when it isn’t. You wouldn’t do that to a person. Don’t do it to the agent.
So you can bring the agent in properly. But that raises a bigger question. Once it’s on the team, who decides what it does?
2. Who drew the line between your people and your agents?
Try to remember the meeting where you decided this.
The meeting where you looked at all your team’s work, laid it out, and went piece by piece: this stays with a person, this goes to the agent, this one they do together.
For almost everyone I talk to, that meeting never happened.
Here’s what happened instead. Someone tried a tool. It was good at one task, so it took that task. Then it took another. Then a teammate started using it for something else. And slowly, with nobody steering, the line between what your humans do and what your agents do just... drew itself.
That should bother you. You would never let a new hire quietly take over more and more of the team’s work each month without a word from you. But that’s exactly what you’re allowing when the boundary sets itself.
So here’s my answer, and it’s simple: draw the line on purpose.
Take your team’s work and lay it all out. For each piece, make the call yourself. Human, agent, or both together. And be honest about why. Not “the tool happened to be good at it.” But “I decided this belongs here.” Some work needs a person. Some work an agent can own. And some work is best done as a pair, a person and an agent together, each doing their part.
Draw that map on purpose, and you’re already ahead of most leaders, who are working off a map that drew itself.
But drawing the line is the easy part. Now you have to actually run this team. And the two kinds of teammates need very different things from you.
3. Why do you trust the machine and forget the person?
Here’s a trap you’re probably already in without knowing it.
You over-trust the agent. Not because you’re careless, but because it sounds right. It writes like your most polished employee. And our brains have always taken “sounds confident and clear” as a sign of “knows what they’re talking about.” The agent sets that off by accident. Its best work and its worst work come out in the exact same smooth, sure voice. The signal you always leaned on, a person’s ability to look unsure, is just gone.
And at the same time, you under-serve your people. Not on purpose. But your attention is limited, and the agent is loud. It’s always producing, always there, always asking for the next thing. Meanwhile your best person has gone a little quiet, and you haven’t had a minute to ask why.
So you end up spending your trust in the wrong place. You lean on the confident machine and drift away from the quiet human. It should be the other way around.
The fix is to manage the two differently, on purpose. With the agent, don’t trust the confident tone. Check the work, especially where you know it’s weak. Build a habit of catching its mistakes before they ship, because it will never catch them itself.
And with your people, the skill you already have is the one that matters. A good manager was never the same with everyone. You already talk to ten people ten different ways. One needs directness. One needs encouragement. One needs space. The agent is just one more kind of teammate on that list, the one that wants the bluntest, most direct feedback of all, with none of the emotional care a person needs. Being good with the agent doesn’t make you colder with your people. It’s the same skill: knowing who needs what, and giving it to them.
That handles how you talk to each of them. But there’s a harder question underneath, and it’s about your people, not your agents.
4. When the agent takes the job your best person was known for, what’s left for them?
This is the one most leaders never see coming.
You gave a task to the agent. Good call, it does it faster and cheaper. But that task was the thing your best person was known for. It was their craft. It was the reason they felt good walking in each day.
You solved a speed problem. And you created a different problem, a quieter one. Your strong performer is now sitting there wondering what they’re for.
You can see the speed problem. It’s on a dashboard. You cannot see the other one, until the day that person hands in their notice, and by then it’s too late.
So what do you do?
You move them up. When the agent takes the doing, the human’s job shifts to the parts the machine can’t reach. Deciding what’s worth doing. Catching the thing that’s about to go wrong. Handling the messy call with no clear answer. Owning the outcome. That’s a real job, and it’s a better one, but it’s a shift, and you have to walk them through it, not just announce it.
And here’s the part people get wrong. Don’t move them all the way up into pure thinking, with no doing left at all. That feels hollow, like being kicked upstairs. Keep a real piece of the doing that stays theirs. The work humans are simply better at: the hard conversation, the new situation nobody’s seen before, the thing where a real person needs to be the one accountable. Name that zone out loud. If you leave it as “whatever the agent didn’t take,” it shrinks in the dark, and your best people feel it long before you do.
Now, this all sounds like a promotion for everyone. Everybody moves up. But wait. Is moving up actually good news for everyone on your team?
5. Is moving everyone “up” a gift, or a threat?
Be honest about who your people are.
Most of them were hired for being excellent at doing something. They got promoted because they executed better than the person next to them. That’s what they’re proud of. That’s the ground they stand on.
Now the floor is rising. The doing is going to the machine, and everyone’s being pushed up toward judgment and taste and ownership.
For some of your people, this is the best thing that ever happened. They always wanted to do the bigger thinking, and now they get to.
For others, you just took away the exact thing they were great at and asked them to be good at something they’ve never had to build. That’s not a gift to them. That’s a threat. And they feel it, even if they can’t say it.
The answer is that the rising floor is both, and which one it is depends entirely on the person. Your job is to know which of your people is which. The one who’s ready to climb needs room and a push. The one who’s scared needs you to teach the new skill, patiently, and to make it safe to be a beginner again. Same change, two completely different conversations. If you give everyone the same speech about “moving up the value chain,” you’ll lose the people who needed the other conversation.
Which brings me to the last question. And it’s not about your team at all.
6. And what about you?
Every article about this tells you to manage the agents. Get them adopted. Get them producing. Point your team at the tools.
Not one of them mentions the thing sitting right under your nose.
You’re on that rising floor too.
The same force pushing your people up from doing to judgment is pushing you. And here’s the catch. The skills that made you a great manager of a team that executes are not the same skills that make you a great leader of a team that thinks. Running a team where people ship work all day is one job. Leading a team where the machine ships the work and your people make the calls is a different job. You have to make that shift in yourself first, before you can lead anyone else through it.
That’s the part nobody warns you about. You’re not standing outside this change, running it like a project. You’re inside it, rising with everyone else, and you have to grow too.
7. So what’s the real job here?
When I say “lead a team of people and agents,” I don’t mean one thing. I mean this whole stack, sitting on top of each other.
Bring your agents in like real hires, not magic. Draw the line between human and agent work on purpose, not by accident. Manage each teammate the way they actually need, the agent blunt and checked, the people with the care they’ve always needed. Move your people up without hollowing them out. Know who’s ready to climb and who’s scared. And grow yourself, because the floor rose under you too.
The machine is getting good at the doing. It’s taking the bottom of that stack. But every layer above the doing, the deciding, the leading, the growing, that stays yours. It gets more valuable as the doing gets cheaper, not less.
The only catch is the same as it’s always been. You don’t get good at this by reading about it. You get good at it by doing it, on your real team, and finding out where you were wrong.
If this is the kind of thing you’re wrestling with on your own team, I’m going deeper on it live. I’m running a free 30-minute Lightning Lesson, How to Lead a Team of People and Agents, where we work through the three moves at the heart of this: how to structure the work across humans and agents on purpose, how to run them as one team instead of two, and how to lead your people up without hollowing out the work that keeps them here. Come think it through with me, and bring your own team to the table.
[July 23, 2026 10 AM PT · RSVP Here]