Paul Graham's 2024 'Founder Mode' essay argued that the conventional wisdom to 'hire good people and delegate' is often wrong for founders — that skip-level.
Paul Graham's September 2024 essay 'Founder Mode' crystallized something many founders had felt but couldn't articulate: the standard corporate advice to hire experienced executives and delegate cleanly through org charts routinely produces disappointing results at founder-led startups. The essay, drawn largely from a talk by Brian Chesky, argued that founders can and often should operate differently — going deeper into operational detail, skip-level with product and functional teams, and rejecting the artificial separation between 'strategy' and 'execution' that traditional management schools teach. The essay landed because the pattern was widely observed but rarely defended.
Not: founders should micromanage everything. Not: don't hire executives. The actual argument: (1) founders have unique context (customer intuition, product judgment, mission conviction) that doesn't survive delegation through 3+ layers of experienced managers. (2) Manager-mode advice was calibrated for large, mature companies where the CEO's job is to allocate capital and hire well; it doesn't fit companies where the CEO's job is to invent the product and the market. (3) Skip-level meetings, product-level involvement, and 'unscalable' founder attention often produce outcomes no professional CEO could replicate. The takeaway is that founders should feel permission to operate in ways that violate MBA orthodoxy — not that they should reject management entirely.
Skip-level engagement — the CEO regularly meets with individual engineers, PMs, designers, salespeople, not just VPs. Not to override them, but to preserve ground-truth understanding of what's actually happening. Deep product involvement — the CEO reviews product decisions and design proposals directly, retains veto power over specific things (usually pricing, brand, and the top of the roadmap). Tight information architecture — the CEO reads select customer support tickets, joins select sales calls, uses the product daily. Direct comms — the CEO writes company-wide updates in first person, not through a comms team. High-signal 1:1s with a small set of ICs on high-leverage projects, alongside standard 1:1s with direct reports.
The essay has been widely misread as permission for founders to reject any executive input, second-guess every decision, and behave erratically. That is not founder mode; that is CEO dysfunction with a new label. Signs you've slipped into the trap: (a) executives don't know when a decision is theirs to make and when the founder will overturn it. (b) senior hires leave within 12 months citing 'no autonomy.' (c) the founder is a bottleneck for decisions that don't require their unique context (procurement, HR policy, engineering tooling choices). Founder mode requires more discipline about scope, not less — the founder must be clear about which areas they operate hands-on and which they truly delegate.
Publish a 'founder scope' document that names: (1) areas where the founder retains direct decision authority (usually product vision, pricing, hiring VPs, brand, key partnerships). (2) areas where the founder participates but doesn't decide (specific product decisions, sales strategy, marketing campaigns). (3) areas where the founder is out (finance operations, HR ops, IT). This document is the antidote to executives never knowing when they'll be overruled. Review and update it every 6-12 months as the company scales — founder scope naturally shrinks; making the shrinkage explicit prevents drift.
Around 500-1000 employees, founder mode has structural limits — no human can maintain ground-truth in every area at that scale. Signals it's breaking: the founder is the top decision bottleneck; the founder feels perpetually behind on what teams are doing; senior executives repeatedly leave with the same complaint. Adaptations at scale: preserve founder mode for 2-3 domains (usually product, brand, and the top strategic bet) and delegate cleanly on the rest. Or hire a strong operating partner (COO, President) who runs the operational surface so the founder can stay in founder mode on the domains that require them. Continuing full founder mode at 2000+ employees is what produces the 'founder overstayed' anti-pattern.
Investor directory · Fundraising library · Articles A–Z · Company funding database