Module 05 · The board deck~45s dwell · weight 8
Org: headcount plan, key hires, departures
Show current headcount against plan, name the hires that matter, and disclose any departures the board hasn't already heard about.
Directors want to know if the org can execute the plan; Sequoia's guide includes headcount as a leading indicator, not a lagging HR report.
Include
- Headcount actual vs. plan, by function or in total
- Named key hires this quarter and open key roles
- Any departures, especially at leadership level, stated plainly
Cut
- A full org chart with every individual contributor listed
- Softened language around a departure the board should already know is a problem
Red flags a reader notices
- A leadership departure mentioned for the first time in this deck, with no prior heads-up
- Headcount growing faster than revenue with no explanation
Pitfalls behind them
- Calling a firing a 'transition' to avoid the harder conversation
- Listing hiring plans without saying which roles are actually open right now
60-second self-test
- · Has any director already heard about a departure privately, so this isn't a surprise?
- · Does headcount growth track against revenue growth, or outpace it?
Template
Headcount: [actual] vs. [plan]. Key hire: [name/role]. Departure: [name/role], [reason, one line].
Weak
"We've made some team changes and are excited about our growing organization."
Strong
"Headcount: 14 vs. 15 planned. Hired: VP Sales (start Sept 1). Departed: Head of Support (Aug 15, performance), backfilled internally within 2 weeks."
Nimbus names the role, the date, and the reason for the departure, which is what keeps a board from hearing it secondhand.
Quick quiz
Pick an answer. Nothing is graded, and correct answers stay hidden until you choose.
1. How should a leadership departure be handled in the board deck?
2. What should headcount be compared against?