Jensen Huang’s Leadership System: Stop Work Getting Stuck

Imagine this. A customer says something is broken. One person sees the message. Another person owns the fix. A third person can approve the change. By the time the right person hears the full story, the day is almost over. The work did not stop because people were lazy. It stopped because the problem had to pass through too many people.

Jensen Huang runs Nvidia. Around 60 senior leaders report straight to him. Most bosses would split that group into smaller groups and hold private meetings with each one. Huang does the opposite. He tries to make sure the right people hear the same problem at the same time.

That does not mean you should copy his setup. You probably should not. The useful part is much simpler: when a problem matters, do not make people chase the story before they can help solve it.

A handoff is just work passing from one person to another. Some handoffs are needed. Many are not. This article will show you how to spot the bad ones and remove one this week.

The Simple Rule Behind Huang’s System

Huang has said that his 60-direct-report setup is right for his senior team. He has also said that it would not work at every level of a company. That matters. The number is not the lesson.

The lesson is this: put the problem, the facts, and the next choice in one place. Then let the people who need it see it. A shared note can do this. A simple project page can do this. So can a short meeting that ends with a clear answer.

I love that there is no privileged access to information.Jensen Huang, Stripe Sessions, 2024

In normal English, that means this: do not let one person hold the only copy of an important problem. If your team needs a private call just to learn what changed, the work is already slow.

Think about a website launch. The designer knows the page changed. The writer knows the offer changed. The person running ads sees that sign-ups dropped. If each person sends a separate update, nobody sees the whole picture. They all work hard. The launch still drifts.

Now change one thing. Put the problem in one shared place. Write what changed. Write what needs deciding. Name the person who will make the next move. Suddenly the team is no longer passing messages. It is solving one problem together.

That is why this matters for your life as well as your team. Your inbox, notes app, task list, and calendar can also pass work around in circles. If they do not point to one clear next move, they create the same delay.

Run This 15-Minute Reset Today

Pick one problem that keeps coming back. Maybe a client keeps waiting for an answer. Maybe you keep talking about a project but never start it. Maybe your team has met three times and still does not know what it is doing next.

Set a 15-minute timer. Do not try to fix the whole project. Your only job is to make the next useful move easy to see.

Minute 1: Name the live decision. Write one sentence: What do we need to choose? If you cannot answer that, stop. You are not ready for a meeting yet.

Minute 4: Write the facts that changed. List only what changed. A customer reply. A missed deadline. A new cost. A hard limit. Do not write the whole history of the project.

Minute 8: Name one owner and one next move. Write a sentence anyone can check: Alex will send the new offer by 3 PM Thursday. “We will look into it” is not a next move.

Minute 12: Make the reasoning reusable. Save the answer where the people involved can find it. The next person should not need a private call to learn what happened.

You Can Use This Even If You Work Alone

You do not need a big team to have this problem. You can hand work off to yourself. You read an email, tell yourself you will deal with it later, add a vague task, and never put time aside to do it. The task sits there because nobody owns the next move. Even though that person is you.

The solo version is one simple page. At the top, write: What am I deciding? What changed? What will I do next? When will I do it? Then put that last step in your calendar. A thought becomes work when it has a time and a place.

For a small team, try a weekly problem meeting. Keep it short. Do not go around the room asking everyone for an update. Bring only problems that need a decision. Before the meeting ends, write the answer, the owner, and the deadline where everyone can see it.

This is not about making every meeting public. Some talks need privacy. It is about stopping useful lessons from disappearing into private calls when the rest of the team could learn from them.

Feedback is learning.Jensen Huang, Stripe Sessions, 2024

There is one rule that matters just as much. Do not use openness to embarrass people. A good team can say, “We missed this. Here is why. Here is what we will do now.” People need to feel safe enough to point at a problem before it gets expensive.

Google’s team research reached a similar point. Good teams need clear roles and a safe place to speak up. You need both. Clear roles without safety make people quiet. Safety without clear roles creates long talks with no finish.

A Real Example You Can Copy

Say you run a small business. A client is unhappy with a project. The account manager knows why. The person doing the work knows what changed. You need to decide whether to redo the work, give money back, or offer something else.

The bad version looks familiar. The account manager sends a long message. The work team replies with their side. Someone says, “Let’s jump on a call.” The client waits. Nobody has made a choice yet.

Try the reset instead. Write: “We need to choose what we offer this client today.” Under that, add only the facts: what was promised, what changed, and what the client asked for. Then write the owner and deadline: “Maya sends the final answer by 4 PM.”

Notice what changed. You did not need a better app. You did not need a longer meeting. You gave the problem a shape. Once the choice is clear, people can help. Before that, they are only reacting to pieces of a story.

Three Questions That Fix a Bad Meeting

Use these three questions when a meeting starts to wander. They are simple on purpose. Simple questions are easier to use when everyone is busy.

What are we deciding today? If there is no answer, end the meeting or turn it into a short working session. Do not spend an hour talking around a problem that nobody has named.

What changed since the last decision? This keeps people close to the facts. It stops the loudest person in the room from winning with the oldest story.

Who does what by when? Write it before the call ends. If you leave with no name and no date, you did not make a decision. You had a conversation.

What Not To Copy From Jensen Huang

Do not use this article as an excuse to remove every private meeting. A new employee may need coaching. A hard personal conversation may need privacy. A team dealing with a sensitive problem may need a smaller room.

Do not copy the 60 direct reports either. Huang leads senior people in a company he has built for decades. Your job is not to act like him. Your job is to borrow the part that helps: fewer lost messages, clearer choices, and faster next moves.

The 7-Day Test

For the next seven days, keep a small count. Each time work stops, ask one question: Is the work hard, or is someone missing the information they need? Write the answer down.

If the answer is missing information, do not book another long update meeting. Make the smallest note that gives the next person what they need. Then give the next move a real time in your calendar.

At the end of the week, look for one repeated delay. Fix that one first. You may not change your whole life in seven days. You can remove one place where work gets stuck. That is enough to make next week better.