← Tin's Posts · November 18, 2026 · 3 min read

Have a Second Name

Last week Jensen Huang, NVIDIA's CEO, left - effective immediately. The board handed the job, for now, to the CFO. She'll still be the CFO, too.

The reasons are tabloid material and I'll skip commenting on them here. It's odd to see Jensen like this. I remember him from when I was a teenager dreaming about GeForce 8800 GTX and Crysis. He was the cool guy on magazine covers.

The verdicts on Jensen aside, what caught me is everything around this. The man has talked about having as many as 60 direct reports. No chief operating officer. No successor to be named. The stock dropped more than 10% since (at time of writing).

NVIDIA had known the risk itself, for a fair while. Succession planning has sat in NVIDIA's own risk factors for years.

They knew what the problem was, but the solution was too difficult to discuss.

Your company has one too

You (probably) don't have 60 direct reports. You probably have one person who knows how the billing code works.

Or the releases. Or the integration with the client who pays half the bills. The one person who gets a call on holiday, and answers. You had to call them, and that's "normal". Everybody likes them. Everybody sends the problem through them, which is one way to never solve it.

I call them many names - wizards, greybeards, magic engineers, rockstars. I'm often sarcastic, but rarely wholly so. They're good - often the best on the team. That's what makes the situation dangerous. Nobody plans to depend on one person. You end up depending on the wizard because they were fast, and fast was what you needed for that client. Magic.

I've let a few go, as a manager. Not for being good. For refusing to stop being the only one. "I can do it faster myself", and "Others will do it wrong", and "I don't have time to write the documentation". The weeks after were rough, but then the team found out it could... which is how it works - nobody likes being thrust out of their comfort zone. Then they get used to the new normal.

Nobody gets to choose why the person goes. NVIDIA's reason made the front pages. Yours will be a better offer, a burnout, or a visa refusal, and it'll be in no news. It can still happen on a Tuesday with no warning.

An afternoon, not a program

This doesn't need a consultant (but if you want one...) or a framework. It needs an afternoon and some honesty.

  1. List what would stop the business this week. Not the org chart - the jobs. Deploying. The billing run. Payroll. The client who'd call you straight away. Five to ten items.
  2. Write who can do each one today. Not "could learn". Can, today, without a call.
  3. Circle every item with one name. That's your Huang.
  4. Run the drill. The second person does it this week, for real, while the first one watches from the side. Every question they ask goes in the doc.
  5. Write the handoff the way you'd want to find it. Per item: done, partial, or tricky. Known issues. What's next. "Here are the files" doesn't count as a good job.
  6. Make it the wizard's job. Put it in their goals, pay for it, congratulate them in public. Making themselves replaceable is the most senior thing they'll do this year.

If they refuse, you have a more difficult conversation ahead of you. It isn't the one you wanted, but at least it's on your own terms.

The fair objection

The wizard is often the reason you're winning. NVIDIA ran everything through one desk and became one of the most valuable companies on Earth. Speed comes from that shape, and I wouldn't trade it away for a nice sounding presentation.

I'm not telling you to fire the person. Let them cook. I'm warning you against there being only one place where their knowledge lives.

Write down a second name. Find one if you can't.


Enjoyed this? Subscribe to get future posts by email.

Book a discovery call