Jensen Huang

FACT NVIDIA was founded on 5 April 1993 by Huang, Malachowsky and Priem; Huang has been President, CEO and a director since inception [1][2] — 33 years in the chair, with no inherited structure and full freedom over how information moves. He is the clearest documented case of a founder who engineered the information environment rather than the org chart: the condition a CIO or CISO under such a person works inside.

Each is a stated practice in a named venue, not an observed outcome.

1. A very wide span — and no single number is correct. 50 at Stanford GSB, 25 April 2024 [3]; 60 at Stripe Sessions 2024 [4]; 55 in Fortune/Yahoo coverage of 31 January 2025 [5] — three figures inside twelve months, not moving monotonically. Write "roughly 50–60, varying by year and source." Never state one number as fact. His rationale: "CEOs should have the most reports by definition because the people that report to the CEO require the least amount of management" [3]; sixty reports "probably removes something like 7 layers" [4].
2. No one-on-ones with his own staff; discouragement generally. "I don't do one-on-ones and my staff is quite large. Almost everything that I say, I say to everybody" [4]; asked about the convention, "I really discourage 1-on-1s" [4].
3. Information broadcast, not routed. "I don't really believe there's any information that I operate on that somehow only one or two people should hear about" [4] — including feedback, given in front of peers.
4. "Top 5 Things" (T5T) as a weak-signal channel — since narrowed. Employees send short bulleted updates; he samples roughly 100 a day, "looking to detect the weak signals," and sends none of his own so the format is not imitated [6]. Business Insider reported (covered February 2026) that NVIDIA restricted the system to narrower distribution, in a company well past 30,000 employees [7]. Teach it as "as of 2024, subsequently narrowed," never in the unqualified present tense.

None belong to these practices. NVIDIA reached a $5 trillion market capitalisation (reported 30 October 2025) [8] — a company outcome during an AI demand cycle. No public source links the span of control, the absence of one-on-ones or T5T to any NVIDIA result. The company's success is not evidence the practices work.

• The report count, as above.
• "No 1:1s" is routinely overstated. Documented only for his own staff, plus discouragement — not a company-wide ban, and no source says what NVIDIA's managers do.
• T5T is not a live unqualified system. It was narrowed.
• "The mission is the boss" is NOT a verified Huang quotation. Every instance traces to Tae Kim's The Nvidia Way and podcast restatements. Attribute it to Kim, or drop it.
• Everything is self-reported in promotional settings: no audit, no survey evidence, no counterfactual, no public account of decision rights below the leadership team.

INTERPRETATION Four instructions, all about your design.

No back channel — plan without one. "Almost everything that I say, I say to everybody" means no private brief before the board meeting. Influence happens in front of peers: a higher bar on the argument, and no impression management.

Pre-negotiate the escalation exception, in writing. Security has an irreducible private category — live incident, insider investigation, allegation against a named executive. Agree the trigger, attendees and record in advance; doing it mid-incident is a foreseeable, avoidable failure.

Take T5T as a design pattern and inherit its ceiling. A lightweight, high-frequency upward channel built for weak-signal detection is the shape of a good near-miss scheme; strong signals reach you anyway. The narrowing is the better half: flat information mechanisms have a headcount ceiling, and an executive who has not noticed their channel became filtered is running on a stale picture. Instrument volume and source diversity, not content.

When layers are removed, write the decision-rights map yourself. "Least amount of management" describes the leadership team and says nothing about who decides two layers down — where you must find an owner for a risk acceptance. In a hierarchy the chart implies that map; in a flat firm it does not exist until you build it.

Risk Corollary. Here, "Yes — and here is the risk we are accepting, priced" is said in public, to peers. Rehearse it that way.

1. Draft the incident-escalation exception you would ask a broadcasting CEO to agree in month one: trigger, attendees, record, and what you concede for it.
2. Near-miss volume falls 40% in two quarters while headcount grows. Give three explanations and the evidence that separates them. Which is most convenient for you?
3. Write the two-sentence rebuttal to a director who asks: "Huang runs 60 reports with no 1:1s — why does your function need three layers?"