I usually don’t comment on things we see happening in the news, or about a specific company or individual. But I think there are some important lessons we can learn about Jensen Huang’s departure from Nvidia.
I can’t comment on the events leading to his resignation.
I have huge admiration for the company he founded and built. It is a fascinating story that all of us can continue to learn from. But Huang’s success as a leader will be judged by what happens with Nvidia in the coming months and years.
Huang’s model for building Nvidia is fascinating. It was a very flat organization. His goal was to empower teams and their leaders, to spread information throughout the organization. This strategy was key to much of Nvidia’s success.
And this empowerment is something I have advocated for strong organizations for decades. Whether it’s a flat organization with Huang at the center, or a structured hierarchical organization that we see in most others, building capability throughout the organization is the key to success.
But the challenge is that building capable people is not the same as building potential successors. Running an organization, particularly the size of Nvidia, is very different than running a function in the organization.
The informal structure at Nvidia, put him at the center of everything. While people throughout the organization could drive the performance of their own teams, it’s not clear they could see the impact of on the rest of the organization. In these types of “networked” structures, only those at the critical nodes or the center can see how everything comes together.
Decisions, context, judgment is all centered on those at the center, not building the capability for others in the organization.
We see the same challenges in organizations designed the opposite of how Nvidia works. Rigidly hierarchical organizations sometimes force too many decisions to the top.
Alternatively, we see other cases where top leaders reach into the organization, micromanaging. They don’t trust the people in the organization or have not developed the capabilities and judgment of people in the organization.
Being the center of things feels like success to those at the center or those at the top. But the real job of leadership is developing the capabilities and judgment of others
But at some time, the leader leaves. It may be retirement. It may be burnout. Sometimes there is some planning for these, but it may be too late. But what about the sudden exit? Anyone might be hit by a car crossing the street. Or a leader is suddenly forced out of the organization.
How well prepared is the organization to continue without skipping a beat?
This is the ultimate test of the leader, “What happens when that leader leaves?”
But this isn’t a post about succession planning. It’s about “How do we build high performing organizations capable of sustaining performance without its leader?”
The organization that, regardless of its success, that is dependent on the presence of a strong leader has a capability problem. The best leaders develop the capabilities of the people in the organization. They focus building their ability to make decisions consistent with the strategies and priorities of the company.
They build the ability to exercise judgment, often through modeling how the leaders exercise judgment, themselves.
One of the things we talk about is empowering our people. This appeared to be a cornerstone to Nvidia’s operational strategies. But we can have very empowered organizations that are still dependent on a few people.
Empowerment enables people to make decisions and act within their own parts of the organization. But organizational capability requires more than empowerment.
It requires the ability to see how decisions made in one part of the organization may impact other parts of the organization. It requires understanding the tradeoffs that must be made between competing priorities that inevitably arise in the organization, particularly in high performing organizations.
It requires exercising judgment that optimizes the performance and capability of the organization, not just a part of the organization.
The problem isn’t the structure of our organizations. Whether flat like Nvidia’s or hierarchical like many of our traditional organizations. They all face the same problem, the concentration of judgment in one or a very small number of people.
At some point, these become limitations to the organization and its growth.
There’s another perspective here. Highly successful organizations can also be very fragile.
One example is Apple. After Steve Jobs was forced out in 1985, the organization foundered. The vision and capabilities hadn’t been instilled in the organization at the time and Apple wandered. When he returned, he started building the capabilities in the organization. Tim Cook was developed for years and Apple continued to grow and thrive when he took over.
WeWork and Uber offer interesting contrasts. Among the hottest companies of the 2010s. Both CEOs were forced out because of controversies. One of the reasons WeWork failed was because the capabilities to adapt and grow weren’t built into the organization. Uber rebuilt itself and continued to grow.
One of my early mentors counseled me, “How do you design yourself out of the job?” He focused me on developing the capabilities of my people, so they could continue without me. I focused on helping them develop judgment, so they didn’t have to depend on me to make every decision.
What we see too often is leaders spending their careers demonstrating their value to the organization. Whether it’s how they work within the organization, or how they position themselves externally. They want to be indispensable.
But this is a limiting strategy, both to the organization and to the individual leader.
I learned to develop the capabilities of my people to do the things that required my involvement. The more successful I was in developing them, it freed me up to develop capabilities to address new things. Whether it was expanding what my team could do or moving to different roles in the organization.
As I grew in my leadership roles, I became aware of the need to develop myself even further. Designing myself out of the organization became relatively easy, sometimes something that my people seemed too eager to do (Hmmmmm, maybe they were telling me something.)
Originally, I thought of it as “delegation.” This was a popular concept at the time. I realized it wasn’t just delegation. It wasn’t my reaching out to someone on my team saying, “Tag you’re it! You’re accountable for this!” Delegating responsibility without developing the capabilities and judgment isn’t empowerment. It’s only transferring accountability.
Over time, both the people on my teams and I recognized the importance of adaptability. We couldn’t anticipate everything that might happen, some things were out of our control. But we couldn’t ignore them, we had to figure things out, shift and change direction.
If all the capability had been centered in me as a leader, there were huge risks. What if I didn’t recognize what was happening? If I did, could we adapt quickly enough? In developing the capabilities of my team, the whole team started recognizing risks and changes that might need to be made. And they had the capability, perhaps with some guidance, to make those changes.
In today’s world it is dangerous to concentrate everything in one or a small number of individuals.
But what do these things mean in the real world? What should a first line manager get from this post?
First, there is too much going on, even in a small team, for managers to be the decision point for everything going on. Managers can’t dive in to win every deal; they can’t micromanage everything going on.
Managers must focus on developing the capabilities of their people to manage deals, accounts, territories on their own. Training, coaching, and developing those capabilities with their people. Helping people build their judgment and confidence in executing that judgment, and learning when things aren’t working.
Second, managers need to facilitate their teams’ abilities to work together. Developing their capability to collaborate, make decisions and take action. Only escalating issues to the manager when they are beyond the capability of the team to address.
Third, managers must develop the capability of their people to work across the organization, prioritizing organizational success over the team success. In my own experience, sometimes I gave up headcount and funding, because it could be better used in other parts of the organization.
Finally, developing the team and organization’s agility and nimbleness to recognize changes and disruption, without their needing your direction. Developing the ability and judgment to figure things out is one of the most critical capabilities of great organizations.
If you are a manager and want to test your ability to do these, try this test: Could you go on a week’s vacation and be confident that your people can manage without you? Could stay on that vacation without calling your people, checking on a deal, telling them what to do and to text you with the result. Do you have the confidence the people can manage things for a week without you?
We tend to celebrate indispensable leaders. We admire their vision and ability to make things happen. We admire leaders that attract press and are held up as the very best.
I think we may have misunderstood what it takes to make a great leader.
The greatest leaders aren’t those that build organizations that can’t succeed without them. It’s those that build organizations that can.
Afterword: Last week I started a series on Organizational Design. As I reflect on this article, while it doesn’t fit in the sequence I had imagine, what I talk about is critical to designing organizations that can thrive when leaders depart.
Afterword: Another outstanding AI generated discussion of this post. It’s worth listening to.