Founder Mode

Paul Graham's essay on Founder Mode struck a nerve across the tech world. Based on a talk by Airbnb CEO Brian Chesky, it challenges the conventional wisdom about how founders should run their companies. Here are my thoughts.

The Core Idea

Graham argues there are two ways to run a company: Founder Mode and Manager Mode.

Manager Mode is the conventional approach. Hire good people, give them room to do their jobs, and treat each part of the org chart as a black box. Do not get involved in the details -- that would be micromanaging, which is bad.

Founder Mode is the opposite. It involves the founder's direct engagement with various levels of the organization, breaking traditional managerial hierarchies. Think skip-level meetings, hands-on involvement with product decisions, and a refusal to fully delegate critical areas of the business.

Why It Resonated

The essay resonated because so many founders have experienced the pain of the "hire good people and get out of the way" advice. Chesky himself followed that playbook initially at Airbnb -- and found that it did not work. Managers sometimes did more harm than good. He switched to a more hands-on approach, and the company turned around.

Steve Jobs ran Apple this way. He was famously involved in details that most CEOs would never touch -- the curvature of a corner radius, the exact shade of a color, the weight of a product in your hand. It worked for Apple, and Graham suggests this is not the exception but a pattern worth studying.

The Danger

Here is where I think the conversation gets more nuanced than the essay allows. Founders are at real risk of misinterpreting "Founder Mode" as a license to micromanage. There is a meaningful difference between:

• Caring deeply about product quality and staying close to the work
• Micromanaging your team because you do not trust them

The former is Founder Mode at its best. The latter is seagull management -- swooping in, making a lot of noise, and leaving a mess behind.

When to Use Each Mode

I think the real insight is not that Founder Mode is always better. It is that you need to know when to switch between the two.

Founder Mode makes sense when:

• You are in the early stages and product-market fit is not yet established
• A critical initiative needs to be rescued or redirected
• The company is going through a fundamental strategic shift
• Quality is slipping and standards need to be reset

Manager Mode makes sense when:

• You have proven leaders who have earned trust through results
• The domain is outside your expertise and you have someone better
• You are scaling and physically cannot be everywhere
• Your team needs autonomy to grow and develop

The Gender Dynamic

One aspect of the discussion that deserves more attention: Bumble founder Whitney Wolfe Herd noted she was "in founder mode for 10 years and got attacked for it every single day." The reality is that founder mode is celebrated when practiced by certain founders and criticized as controlling or difficult when practiced by others. That double standard is worth examining.

My Take

Founder Mode is not a permanent state -- it is a tool. The best founders know when to go deep on a problem and when to step back and let their team run. It is about having the judgment to know when the situation calls for each approach.

The essay is most useful as permission. Permission for founders to stay close to the details when they know something is off, even when well-meaning advisors tell them to "let go and delegate." Sometimes the founder's instinct is right, and the org chart is wrong.