No 1-on-1 meetings: How Jensen Huang runs NVIDIA | Lex Fridman Podcast Clips
Jensen Huang explains NVIDIA's extreme co-design approach, where they optimize across the entire technology stack from software to hardware to systems. He manages 60 direct reports without one-on-one meetings, instead using group discussions where all experts collaborate on problems since every component affects others.
Summary
Jensen Huang describes NVIDIA's unique approach to building complex AI systems through what he calls 'extreme co-design.' This involves optimizing across multiple layers simultaneously: software architectures, chips, systems, system software, algorithms, and applications. The challenge extends beyond just CPUs and GPUs to include networking chips, switches, power delivery, and cooling systems, all of which must work together efficiently in power-hungry AI systems. Huang emphasizes that company organization should reflect the product being built, criticizing the standard 'hamburger' organizational charts used by most companies regardless of their output. His management structure reflects this philosophy - he has 60 direct reports, mostly with engineering backgrounds, who are experts in different areas like memory, CPUs, optics, GPUs, and algorithms. Rather than conducting one-on-one meetings, which would be logistically impossible, he uses group problem-solving sessions where all relevant experts participate. This approach works because when discussing any component (like cooling or networking), other team members can immediately identify conflicts or dependencies with their areas (power distribution, memory, etc.). Team members are expected to know when to contribute and are held accountable if they miss opportunities to provide valuable input. This collaborative approach enables the extreme co-design that NVIDIA requires to build integrated AI systems.
Key Insights
- Replace one-on-one meetings with group problem-solving sessions when building complex integrated products, as experts in different components can immediately identify cross-functional conflicts and dependencies
- Design your company's organizational structure to mirror the architecture of the product you're building rather than using standard organizational templates
Topics
Full transcript available for MurmurCast members
Sign Up to Access