He could do Everything. That was the problem

The Immigrant Ladder | Week 2: Letting Go Without Losing Control

Delegation

* Names and identifying details have been changed to protect privacy. The stories are real.

Opening Story

He Could Do Everything. That Was the Problem.

I used to mentor a coworker I'll call Marco. He came to Atlanta from Bogotá about eight years ago. Engineering lead at a mid-size software company. His team had five developers, and Marco could outcode every single one of them. When a deploy went sideways at 9 PM, Marco jumped in. When a junior dev's pull request was messy, Marco rewrote it himself. When a sprint was behind, Marco absorbed the overflow.

His performance reviews were glowing. "Incredibly reliable." "Always delivers." But when a director-level role opened up, the feedback from his VP stopped him cold: "Marco is a phenomenal individual contributor. But we need to see him build capacity in others, not just carry the load himself."

Marco did what many of us were taught to do: prove your value by being indispensable. In the culture he grew up in, you didn't hand work off. You handled it. Asking for help was a sign of weakness. Trusting someone else to do it "your way" felt like a gamble you couldn't afford, especially when your name, your accent, and your visa status already made you feel like you were on probation.

But here's what Marco's story teaches: the thing that got you here, doing it all yourself, is the exact thing that will keep you from getting to the next level. Leadership isn't doing the work. It's building the conditions for others to do it well.

This week, we talk about the hardest shift for high-performing immigrants: letting go without losing control.

This Week's Scenario

The "I'll Just Do It Myself" Moment

A report is due Friday. You assigned it to someone on your team two weeks ago. It's Wednesday afternoon and you open their draft. It's... not great. The analysis is shallow. The formatting is off. There are errors in the second table.

You have two choices. You can stay late, redo the whole thing yourself, and submit something perfect under your name. Or you can sit down with your teammate, walk them through what needs to change, and let them resubmit it, knowing it might still not be exactly how you'd do it.

Most of us pick option one. Every time. Because it feels safer. Because we've been taught that our personal output is our proof of worth. But here's what I've learned from watching people I've mentored navigate this: every time you redo someone else's work, you're training them to need you and training your leadership to see you as the doer, not the developer.

Tool of the Week

The 70% Rule

Here's the reframe that changed everything for Marco, and for others I've mentored over the years: if someone can do the task at least 70% as well as you, delegate it.

Not 100%. Not 90%. Seventy percent. That's the threshold. Why? Because the remaining 30% is where they grow. And where you get your time back to do the work that only you can do: thinking strategically, building relationships upward, shaping the direction of your team.

I know what you're thinking. "But what if they mess it up?" Maybe they will. And that's okay. A leader who never lets anyone fail is a leader who never lets anyone learn. Your job isn't to prevent all mistakes. Your job is to create the conditions for recovery and improvement.

For many of us, delegation feels like a risk we can't afford. We came from places where a single mistake could cost you the opportunity. But holding everything yourself doesn't protect you. It buries you. And it makes you invisible in exactly the way Week 1 warned about: people see you as the worker, not the leader.

Delegation isn't losing control. It's choosing where to put your control. Put it on outcomes, not tasks.

Steal These Scripts

For Delegating Without Micromanaging

"I'd like you to own this. Here's what the end result needs to look like: [specific outcome]. How you get there is up to you. Let's check in on [day] so I can support you if anything comes up."

Use for: assigning a project or deliverable to a direct report or teammate

"I noticed a few things in the draft. Instead of me fixing them, I want to walk you through what I'm seeing so you can strengthen it. Can we do 15 minutes tomorrow morning?"

Use for: giving feedback on work without taking it back

Notice the pattern: define the outcome, give them the space, and schedule the check-in. That's delegation with structure, not abandonment.

🧪 Micro-Assignment

This week, pick one task you normally do yourself and hand it off. Choose something that matters but isn't mission-critical. A recurring report. A meeting agenda. A client follow-up.

Define the outcome. Set the check-in. Then step back.

When you feel the urge to take it back (and you will), sit with the discomfort for ten minutes. That urge is not a signal that something is wrong. It's the old story telling you that your worth depends on doing everything yourself. Let the story pass. Let someone else grow.

🪟

Reflection Question

"What would my week look like if I only did the work that no one else on my team can do?"

✎️

The Deeper Cut

There's a version of this I think about a lot: the immigrant instinct to over-deliver comes from a real place. Many of us watched our parents work two jobs, never complain, never ask for help. We inherited that. And it served us for a long time. But at a certain point, carrying everything yourself stops being strength and starts being a ceiling. The leaders who get promoted aren't the ones who do the most. They're the ones who make the people around them better. That's a different kind of excellence, and it's one you already have the foundation for. You know how to work hard. Now practice working through others.

He could do Everything. That was the problem

Keep reading

The Immigrant Ladder