Interview, Fireside Chat
a16z Podcast | Building the Right Technical Advisory Board
- Distinction between board types: A Technical Advisory Board (TAB) differs from a Board Advisor (who sits on the legal Board of Directors) and a Customer Advisory Board (which focuses on product roadmap validation and customer pain points).
- Strategic purpose: A TAB is intended to resolve deep technical and architectural dilemmas, arbitrate internal debates, and provide informed, unbiased opinions from outsiders unburdened by internal politics.
- Expected outcomes: TABs facilitate long-term strategic planning, talent acquisition (hiring referrals), and the cultivation of engineering culture, beyond merely solving immediate "speed bumps."
- Composition: Ideal TABs for startups typically consist of 6 to 8 members; groups larger than 8 tend to become unmanageable with reduced individual contribution.
- Terms: Two-year terms are preferred over four-year terms to allow for refreshing the board as needs evolve or if specific expertise is no longer relevant.
- Meeting frequency: Quarterly meetings are standard for substantive strategy; one-off consultations are acceptable for specific issues, but the board should disband when the company reaches sufficient scale and internal expertise.
- Agenda structure: Sessions should focus on one specific problem statement per meeting, with a strict limit of 10 minutes for presentations to avoid "show-and-tell" formats that waste advisor time.
- Preparation: Advisors should receive problem statements and "homework" prior to meetings to enable preparation, allowing them to offer pattern-based insights rather than reacting to live data.
- Selection process: Members are best recruited via professional networks and vetted through informal coffee meetings where founders present real-world problems to gauge the candidate's ability to provide actionable advice.
- Diversity requirement: Advisors should represent diverse domains (e.g., security in finance vs. healthcare) to ensure multiple perspectives and prevent groupthink.
- Compensation: Standard compensation involves stock options equivalent to a seasoned engineer, typically with a three-year vesting period, though equity may be waived if conflicts of interest exist.
- Ethical considerations: Companies must navigate conflicts where advisors are potential customers; best practice involves securing formal agreements prohibiting equity compensation if the advisor's employer forbids it, or delaying formal advisory roles until after a sales cycle concludes.
- Advisor expectations: Advisors join primarily for the opportunity to mentor founders, share "stupid mistakes" to prevent others from repeating them, and engage with smart peers, rather than for financial gain.
- Organizational involvement: Product management teams should attend TAB meetings as architectural decisions have significant downstream implications on product requirements and data structures.
- Founder growth: Founders often utilize TABs for non-technical mentorship regarding organizational structure, promotion paths, and scaling culture.
- Failure modes: TABs fail when used merely for validation of existing decisions, when meetings become unstructured social gatherings, or when advisors are not given clear context to debate specific problems.