ABOUT 3 HOURS AGO • 4 MIN READ

Who's Covering For Your Struggling Teammate?

profile

Learn Leadership

We are Learn Leadership. We turn real leaders’ stories into practical lessons you can use at work. New editions every Sunday and Thursday.

Hello Learners,

This is Learn Leadership. Every issue takes one thing that quietly goes wrong between managers and their teams, shows it happening through a real story, and leaves you with something to try this week.

Today it's the teammate who's quietly struggling and the one person silently covering the gap until they break. You'll leave with a single question to ask in your next one-on-ones that surfaces the hidden carrier before they hand in their notice.

The code holding up half the web

There's a piece of software called CoreJS. You've never heard of it, and you use it constantly. It sits quietly inside a huge share of the world's websites, Apple, Netflix, Spotify, and millions of smaller ones, doing an unglamorous job that makes modern web pages work in older browsers. Billions of downloads. More than half of the most-visited sites on earth lean on it.

For most of its life, core-js has been maintained by one person: Denis Pushkarev. There was no company behind it and no team. Just a single developer, mostly unpaid, keeping a load-bearing piece of the internet running on his own time.

In early 2023 he posted a long, tired message. He'd turned down jobs to keep the project alive. Donations barely covered his costs, he said, working out to less than two dollars an hour. His family was asking him to go earn real money.

And he wrote the sentence every maintainer of a thing like this eventually writes: free open source is fundamentally broken, and he wasn't sure he could keep going.

Half the web was resting on one exhausted person, and almost nobody knew his name.

The person you can't see

What core-js shows, at the scale of the whole internet, is something that happens on ordinary teams every day. Someone is quietly holding up far more than anyone realizes, and because it's working, nobody looks.

On your team it usually starts small. One person is struggling, slipping, missing things. And someone sitting close to them starts quietly covering the gap.

They fix the report before it reaches you, finish the piece that didn't get done, quietly rewrite the section that came in wrong. They don't announce it, because good colleagues don't. They just make the problem disappear.

Which is exactly why you stop seeing the problem. And the person doing the covering.

Call it quiet compensation. Your numbers look calm because someone is paying for the calm out of their own evenings, and they will keep paying until the week they can't.

Why you lose two people, not one

Covering works, right up until it doesn't, and the failure is brutal because it arrives all at once.

The carrier burns out, or takes a better offer, or simply hits the week they can't do it anymore. The day they step back, two things surface together. The gap they were hiding, suddenly visible. And the loss of the person who was hiding it, usually your most capable one, because capable people are the ones who can absorb someone else's work on top of their own.

That single step-back costs you two people. Your strongest one walks, and a problem you thought was handled walks back in, in the same week. You'd been counting a quiet, functioning team. You actually had two people failing and one of them about to leave.

It almost happened to the whole internet

Core-js is far from a freak case. A lot of critical internet infrastructure runs this way. One study of essential open-source projects found that nearly half were maintained by just one or two people. The time zone database that billions of phones rely on is updated by one man largely in his spare time.

In 2024, that fragility nearly turned into a catastrophe. A small compression tool called xz, buried inside most of the world's Linux servers, was kept going by a single overworked volunteer. An attacker spent months being helpful, earning his trust while he was stretched thin and stepping back, then slipped a hidden backdoor into the code. It was caught by luck, days before it would have shipped to millions of machines.

The lesson lands the same at every scale. When one invisible person carries something critical, what you have is a single point of failure wearing a calm face.

Find your carrier

You find this the same way, whether you run a team of six or a chunk of the internet. Look at the people around the one who's struggling, and find whose load has quietly climbed.

In your next few one-on-ones, ask one question and then stop talking. "Whose work are you finishing besides your own?" People won't usually volunteer that they've been covering, because they've convinced themselves it's no big deal. Asked directly, in private, they'll usually tell you.

When you find them, do two things at once. Take the covering off their plate, out loud, so they know you saw it and it's done. Then turn to the real gap and manage it as the actual problem it is: a real performance conversation, a support plan, or an honest call about whether the role fits. The covering was buying you time and charging it to your best person.

The person to talk to first

If you do one thing this week, find your carrier before you touch anything about the person struggling. Start with the one who's been quietly keeping a problem off your desk, the one whose name you probably already know.

They're the person who leaves without drama, with a good reference and a better offer, and you only understand what they were holding once it's gone. Core-js nearly found that out. The internet nearly found it out with XZ. You can find it out now, while you still have time to do something.

Find them first. Say thank you, say you saw it, and take the weight off their plate before the door becomes their easiest option.

Feedback

​Subscribe to participate in polls.

If you have specific feedback or anything interesting you’d like to share, please let us know by replying to this email.

600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246
​Unsubscribe · Preferences​

Learn Leadership

We are Learn Leadership. We turn real leaders’ stories into practical lessons you can use at work. New editions every Sunday and Thursday.