You're 30 days into leading a team you barely know.

You're still learning first names. You don't know who your strong performers are, or who you can hand something to and then stop thinking about it.

What you do know is that you told your new boss you would hit the ground running.

So your hands are in everything. You review the work before it goes out. You sit in the meeting you don't need to be in. You take the call yourself because it's faster. Every one of those moves feels responsible in the moment.

Here's the cost. The longer you hover, correct, and pull control back, the faster you erode their confidence in themselves and their trust in you. And you end up with a team that waits for you.

Monster polled more than 6,000 workers and found that 73 percent named micromanagement the biggest red flag in a workplace. Forty-six percent said it would be reason enough to leave a job.

And yet I've worked with thousands of leaders and never met one who described themselves as a micromanager.

Here's what people say instead.

"I care about quality."

"I have high standards."

"I hold people accountable."

Every one of those is a good thing. Put them next to low trust and they turn into hovering.

At 30 days, you have a trust deficit. That says nothing about how much you care or how strong these relationships will eventually be. Trust is what you get from doing the right thing consistently over time, and you haven't had the time yet.

So you need a way to give the team room to run that also gives you confidence the work will land.

Three steps that let your team own their work, make the day-to-day calls without you, and still deliver the outcome you expect. All three are required. Skip one and you're back in the middle of everything inside a week.

This is you setting commander's intent. Your job is to be specific about what the finished thing looks like.

Thirty days in, your people are mid-project and mid-quarter, so you're not setting the objective from scratch. You're confirming that you and that person are aligned on it. Ask: What are we trying to achieve? What does done look like? How are we measuring it? When do we need it?

If the outcome is fuzzy, you will get pulled into the work and you'll feel like you have to check on everything. That's how you become the bottleneck on your own team.

The team builds the plan. You review it.

This is where managers get uncomfortable, because you already know how you would do it. Of course you do. What you're after here is ownership.

Look at it from their side. If I hand you my plan and something goes sideways, and it will, it's easy for you to think: that was Jeff's plan, and Jeff should have asked the person closest to the work. If it's your plan, you're all in. When it breaks, you're motivated to fix it, because you own it.

So I ask for a proposed plan. When I review it, I'm not asking whether it's what I would have written. I'm asking one question: is this 80 percent of what I'd consider a perfect plan?

At 80 percent, we run with it. I want to implement their plan, because that's what ownership requires. And there's no such thing as a perfect plan. Mine would hit problems too.

If it comes back at 30 percent, my first thought is what I failed to clarify in Step 1. Was the outcome unclear? Did I leave out context? Or does this person need coaching on how to build a plan? Either way, I don't take it over. We build it up to 80 together, and then they own it.

The plan is approved and the team is executing. Decisions come up every day.

Without boundaries, they escalate everything to you, which burns your time and kills their ownership. Or they make calls they should have escalated, and you're carrying risk you never agreed to. Or they guess with no idea where the line sits.

Your job is to name the triggers that pull you in. Not a long list. Not a policy document. Three or four clear lines.

"If it affects another team, loop me in early."

"If it changes what we've already committed to, I need to be in it."

"If there's real risk to timeline, budget, or quality, bring it to me."

Now they know where they can take action on their own. They stop asking permission for everything, and you stop getting dragged into the same decision every week.

At some point the team will miss. You've been telling your new boss about the early wins this team is going to deliver, and now you have to bring her an early loss.

What you do next either holds this system together or takes it apart.

There's a pull to put a little distance between you and the problem. To say, even subtly, "that was their call."

You're better than that.

Here's the standard. You own it. They built the plan, they made the call, they executed it, and you still own it. You own the outcome, and you own the environment they're operating in.

So when it goes sideways, you step in. Take ownership without taking over. It sounds like this:

"I fell short of this objective."

"Here's the impact of our miss."

"Here's what I'm doing differently going forward."

What your team hears is that stepping up won't leave them standing alone with the blame. That's what makes them willing to take ownership again next time.

Standards don't rise on their own. That's what the debrief is for.

Run a short one after every significant action, and after the wins too, while everyone still remembers what happened. Fifteen minutes. Five if you can. Three questions. What went well? What didn't go well? What are we doing differently going forward?

No blame. No excuses. Just a team that gets better every week.

Define the outcome. Have them build the plan. Set the boundaries. Then own the misses and learn from them together.

That's how you keep your standards while you take your hands off the work.

Best,

Jeff

P.S. If you're in your first weeks with a new team and you can feel yourself hovering, or you handed something off last week and you've already checked on it three times, let's get on a short call. We'll look at what to hand over first and what to hold onto for now. Here's a link to my calendar.