The talent trap I fell into for years

Everyone wants talented people on their team. But here's what nobody tells you: talent without responsibility is a liability, not an asset.

I learned this the hard way. Multiple times. And it cost me years of stress, team dysfunction, and opportunities I'll never get back.

‍

The first time I saw the difference clearly was back in 2012. We'd just survived a crisis — my first business partner couldn't deliver sales, and I had to let a lot of people go. I realized I was dangerously dependent on him, so I started looking for clients myself. That's when I offered one of our developers — let's call him Alexei — a partnership. I'd handle sales, marketing, business development. He'd handle technical delivery, estimates, client communication on the engineering side. He agreed, and for a while he tried to step into that role. But slowly, I started noticing a pattern. Whenever we needed his support on client calls, technical estimates, or showing our expertise — he'd find ways to avoid it. He kept gravitating back to pure coding.

‍

One evening, after everyone had left the office, we sat down in the break room — the one with the ping-pong table the team loved. And he told me something I didn't expect:

"I just want to write code. I'm more interested in diving into technical problems and learning new technologies. The role you're offering me has too much organizational work and not enough hands-on practice."

‍

He was honest. He turned down the equity, turned down the partner role, and said: "This isn't for me."

‍

I respected him for that. Still do. That was probably the only time in my career someone admitted upfront that they weren't ready to take responsibility — and walked away before it became a problem.

‍

The trap I fell into

‍

Years later, I had someone running a key department. Incredibly talented. Clients loved him. He could deliver work that made people's jaws drop. But managing? Delegating? Taking ownership of problems? That was a different story.

‍

There were constant small things that added up. He'd message in Slack that people weren't listening to him. He'd reply to my messages saying he was "on break" or "busy" — during work hours, when our policy required availability. He wouldn't show up to the office without warning, even though our hybrid schedule required advance notice to HR.

‍

In person, he'd seem engaged. We'd talk, he'd show initiative, even propose ideas. But later, I'd find out the things we discussed were never done. And when problems came up in his department, he'd bring them to me instead of solving them. Not with solutions — just problems. "This person won't listen." "That project is stuck." "The team isn't cooperating." Every time, I'd step in and fix it. Because he was talented. Because clients praised him. Because I was afraid of what would happen if he left. I told myself: "He's just not a manager. But his work is too valuable to lose."

‍

That was the trap.

‍

Eventually, I couldn't ignore it anymore. Tasks weren't getting done, instructions were ignored, team morale in his department was deteriorating. We had the conversation over Slack — I suggested we talk on a call, but he said he needed time to "think" and wanted to take vacation first. I told him: "There's nothing to think about. We're done. You don't need to work the two-week notice — we'll pay it out. You can stop coming in tomorrow."

It was one of the hardest terminations I've ever done, not because he deserved better treatment, but because I'd let it go on for so long.

‍

I promoted a project manager to take over the department. He wasn't the most technically brilliant person on the team, but he was diligent, reliable, and proactive. He'd been with us for a while as a newer PM, but he stood out. Every week in our rhythm updates, he didn't just report problems — he proposed solutions. He wrote about what he'd tried, what worked, what didn't, and what he planned to do next. His teams loved working with him — developers and designers both. People felt heard and supported. When I told him we were parting ways with the previous lead and asked if he'd step up, he was honored. And within weeks, the department stabilized. Issues that had been chronic for months started getting resolved. The team wasn't coming to me anymore — they were solving things themselves.

‍

And I realized something uncomfortable: I'd wasted years tolerating dysfunction because I confused talent with value.

‍

The signal I missed

‍

Looking back, the difference was obvious. The talented person brought me problems. The reliable person brought me problems and solutions. Sometimes his solutions were wrong — he didn't have full context at his level. But the fact that he tried to solve it before escalating? That's what mattered. That willingness to own the outcome, not just report the issue — that's the signal I should have been watching all along.

‍

I saw it in our HR lead too. She started as a PM, but I noticed her drive toward people work and moved her into HR. She was constantly learning, proposing improvements, taking initiative. She didn't wait for permission.

‍

Same with our Chief Project Management Officer. She systematized everything, listened to feedback, wasn't afraid to push back when she thought something could be better. She built an entire department from scratch because she owned it.

‍

Those are the people who made the company work. Not the brilliant ones who needed constant management. When I build systems for founders now, I bake this principle in from the start. In the rhythms and status updates I design, employees aren't just asked to report problems — they're asked: "What's the issue, and how do you think we should solve it?" It's built into one-on-ones, into escalation protocols, into decision-making ladders. And yes, this applies to managers more than line employees. But even at lower levels, I encourage founders to notice: who brings solutions, and who just brings complaints?

‍

Because the first group scales. The second group drains you.

‍

Look at your team this week and ask yourself honestly: who brings you problems and solutions? Who just brings problems?

‍

You don't need to fire anyone today. But start paying attention to the pattern. The people who propose solutions — even wrong ones — are the ones ready for more responsibility. The people who only escalate? They're not ready. And if they're senior, that's a bigger problem than you think.

‍

So here's my question to you: Have you ever kept someone too long because they were talented — even though they made everything harder? Hit reply and tell me. I'm curious how many of us have fallen into this same trap.

‍

P.S. That project manager I promoted? He wasn't flashy. But his teams delivered consistently, morale stayed high, and I stopped getting endless messages about fires in his department. Turns out, reliability beats brilliance every time when you're trying to scale.