a builder's codex
codex · operators · Brian Halligan · ins_lock-s-ceo-evaluation-rubric

Evaluate CEOs and senior operators on Lovable, Obsessed, Chip-on-shoulder, Knowledge, Student

By Brian Halligan · Co-founder & former CEO, HubSpot; in-house CEO coach, Sequoia · 2026-04-28 · podcast · CEO craft, the LOCK(S) algorithm, distribution as the new moat

Tier B · TL;DR
Evaluate CEOs and senior operators on Lovable, Obsessed, Chip-on-shoulder, Knowledge, Student

Claim

Use a five-letter rubric for evaluating CEOs and senior operators: Lovable (would a 28-year-old version of you crawl across glass to follow them?), Obsessed (deep founder-market fit, evidence of going down rabbit holes), Chip on the shoulder, Knowledge of the domain, Student (learn-it-all, not just know-it-all). The Student dimension is the under-rated differentiator.

Mechanism

Conventional CEO rubrics weight pedigree, charisma, and visible domain knowledge — all of which are pattern-matchable and easily faked. The LOCK+S rubric forces an operator to demonstrate the harder-to-fake dimensions: would the best people you have ever known follow them? Have they actually obsessed over their problem or are they performing? Are they still curious, or have they stopped learning? The Student check filters for operators who will adapt to the next era; the Knowledge check filters for operators who can lead today.

Conditions

Holds when:

Fails when:

Evidence

The rubric: L (Lovable) — would a 28-year-old you crawl across glass to follow them? O (Obsessed) — evidence of going deep. C (Chip on shoulder). K (Knowledge of domain). S (Student) — learn-it-all, not know-it-all.

Brian Halligan ran HubSpot for ~20 years and now coaches Sequoia portfolio CEOs. The rubric is what he uses across that cohort.

— Brian Halligan on Lenny's Podcast, 2026-04-28

Signals

Counter-evidence

The rubric encodes Halligan's preferences for founder-style leadership and may filter out steady operators who run mature companies well. Operators who succeed in turnarounds, regulated industries, or pure execution roles may not fit cleanly into LOCK+S.

Cross-references

Open the interactive view → View original source → Markdown source →