Founder Mode vs Manager Mode Explained
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
"Founder mode" and "manager mode" are two labels for how a company's top leader can run a growing organization. Manager mode means hiring capable executives, giving them room, and dealing with the company mainly through direct reports. Founder mode, as its proponents describe it, means the founder stays close to the details and reaches past the org chart when needed.
The labels come from a single essay, and the debate that followed was loud. This article lays out what was actually claimed, what critics said back, and how the argument connects to older management ideas. We're not going to hand down a verdict. The honest position is that the idea is partly useful, partly unproven, and easy to misuse.
Where the idea came from
In September 2024, Paul Graham, co-founder of Y Combinator, published a short essay titled Founder Mode. It was prompted by a talk Brian Chesky, Airbnb's co-founder and CEO, gave at a YC event. Graham says he wasn't going to reproduce the talk. Instead he wanted to address a question it raised.
According to Graham, Chesky's theme was that conventional wisdom about running larger companies is mistaken. As Airbnb grew, people advised him to run it in a certain way in order to scale. Graham summarizes that advice as "hire good people and give them room to do their jobs." Chesky followed it, and in Graham's telling the results were disastrous. Chesky then worked out another approach, partly by studying how Steve Jobs ran Apple.
Graham adds that many of the founders in the audience said the same thing had happened to them. His explanation: the advice they got describes how to run a company you didn't found, how to run it as a professional manager. From that he draws the central claim of the essay: "In effect there are two different ways to run a company: founder mode and manager mode."
Two things are worth noticing about the source. First, it's an essay, not a study. Graham says plainly that "there are as far as I know no books specifically about founder mode" and that all we have are the experiments of individual founders. Second, he spends more time on what we don't know than on what we do.
What manager mode means
Graham describes the standard model through an engineering analogy. Managers are taught to treat subtrees of the org chart like black boxes: you tell direct reports what to do, they work out how, and you don't get involved in the details, because that would be micromanagement.
That's a fair description of mainstream management practice, and it exists for good reasons. It lets one leader oversee far more work than they could personally track. It protects people from a boss who second-guesses everything. And it limits the damage a weak leader can do, a point Graham himself concedes in a footnote (more on that below).
In practice, manager mode usually involves:
- Hiring experienced executives to own functions such as sales, finance and engineering
- Communicating through the reporting line, with the CEO engaging mainly with direct reports
- Setting goals and reviewing results rather than reviewing the work itself
- Writing down decision rights, often in something like a delegation of authority matrix
Graham's critique is that, as it was described to founders, this advice often turned into "hire professional fakers and let them drive the company into the ground." That's a strong claim, and he offers founders' reports as the evidence for it. Notice the limits of that evidence: it comes from founders who felt burned, and it tells us little about the many companies where the same advice worked.
What founder mode claims instead
Graham is candid that founder mode isn't a defined method. His argument is that it will break one specific rule: the principle that the CEO should engage with the company only through direct reports. He writes that "skip-level" meetings will become "the norm instead of a practice so unusual that there's a name for it."
His one concrete example is Steve Jobs's annual retreat for the 100 people he considered most important at Apple, who weren't the 100 people highest on the org chart. Graham's own verdict on whether that's a good idea? "We still don't know."
Putting the essay's claims together, founder mode is described as:
- Skip-level engagement. The founder talks directly with people several layers down, not only with their own reports.
- Staying in the details. The founder doesn't treat parts of the company as sealed black boxes.
- Selected, not formal, networks. Influence runs through the people the founder considers important, not only through the hierarchy.
- Some delegation anyway. Graham says founders obviously can't run a 2,000-person company the way they ran it at 20 people, and that the borders of autonomy will vary by company and by period, "as managers earn trust."
Look at that last point again. The essay doesn't argue against delegation. It argues against a particular, rigid model of it. That nuance gets lost in a lot of the retelling.
| Manager mode | Founder mode (as Graham describes it) | |
|---|---|---|
| Main channel | Direct reports | Direct reports plus skip-level contact |
| Involvement in details | Avoided, treated as micromanagement | Accepted, with delegation that varies by trust |
| Typical advice source | Business schools, investors, executive hires | Individual founders' experiments |
| Evidence base | Decades of management practice | A talk, an essay, and anecdotes |
| Main risk | Executives who manage up and hide problems | Founders who can't let go |
The criticisms and risks
The essay set off a wave of responses. Here are the main lines of critique, with sources, because the quality of the argument matters more than the volume.
It can excuse micromanagement. The most common worry is that "founder mode" becomes a respectable name for refusing to delegate. Graham saw this coming. In a footnote he predicts that founders unable to delegate things they should delegate will use founder mode "as the excuse." He also notes that managers who aren't founders might try to act like founders, with messy results, and that the modular approach "does at least limit the damage a bad CEO can do." So the essay's own author flags the main risk. That connects directly to founder's syndrome, where holding on to every decision becomes the problem instead of the solution.
It rests on a small, selected sample. The argument draws on Chesky and a roomful of successful founders who agreed with him. Founders who stayed hands-on and failed aren't in the room. Sam Gerstenzang, in a September 2024 response, argues that the real distinction isn't founder versus professional manager. In his reading, great leaders, founders or not, combine hiring exceptional people with real agency, deep involvement in the area where they're strongest, and good ways of getting information.
Hands-on needs a theory of when. Eric Nehrlich, in a post from September 3, 2024, asks what would make founder mode effective. His answer: founders have to make their implicit knowledge explicit, pass context and principles to leaders so they can decide independently but stay aligned, and focus their own attention on the few things that matter most. That's less "stay in the details" and more "know which details."
Trust is the real mechanism. Bryan Cantrill, CTO of Oxide Computer Company, broadly supports the idea of founder mode but argues it depends on mutual trust, built through a writing-heavy culture, and warns that founders risk reading it as a license to micromanage.
Burnout and dependence. None of the sources above present hard data on burnout, but the structural risk is easy to see. A leader who is the hub for every important decision becomes a bottleneck and a single point of failure. That's the territory of founder dependence, and it's why a management team below the founder matters even in a founder-heavy culture.
How it relates to older ideas
Founder mode isn't a brand-new observation. It sits in a long line of thinking about what happens to a leader and a company as they grow.
Bain's Founder's Mentality
Bain & Company's Founder's Mentality is the closest cousin. Bain defines it as three traits: an insurgent mission, an owner mindset, and an obsession with the front line. These companies, it says, behave as insurgents, foster deep personal responsibility, abhor complexity and bureaucracy, and are obsessed with the details of the business. Bain also names three crises that come with scale: overload, stall-out and free fall. It lists "the unscalable founder" among the forces that pull companies off course.
There's one key difference from Graham's framing. Bain treats the mentality as something any leader or company can try to keep or regain, not as a trait only founders possess. Graham, by contrast, ties founder mode to being a founder. The overlap is the shared worry that scale drains the energy and detail focus that made a company succeed. We cover this lens in more depth in the Founder's Mentality.
Greiner's growth model
Larry Greiner's classic Harvard Business Review article, "Evolution and Revolution as Organizations Grow," argues that organizations move through phases of growth, and that each phase ends in a crisis the previous management style can't solve. As Toolshero's overview of the model describes it, one of those is the crisis of autonomy: a directive, centralized style that worked early becomes too restrictive for a larger, more varied organization, and the usual response is to move toward more delegation.
Read next to the founder mode debate, Greiner points both ways. He supports Graham's claim that a style can work in one stage and fail in the next, so "run it the way you did at 20 people" won't hold at 2,000. But he also supports the manager-mode side: the way out of the autonomy crisis is more delegation, not less. And Greiner's model continues past delegation, to a later crisis where leaders try to regain control over what delegation produced. Neither mode is permanent.
Founder-led performance and succession
The wider question is whether founders should stay in charge at all. That's covered in what a founder-led company is and in the leadership material on the founder-CEO transition. Founder mode, read generously, is an argument that the answer isn't a simple yes or no. It's a claim about how a founder who stays should behave.
Reading the debate fairly
A few questions help separate useful insight from slogan.
- Is "founder mode" being used as a description or as a defense? Describing how a specific founder gets leverage from skip-levels is useful. Using the label to end an argument about delegation isn't.
- What happened to the executives? Graham says capable managers can earn autonomy over time. If a founder's version of founder mode has produced constant executive turnover, that's information.
- Is the founder's involvement selective? The sources that take founder mode most seriously, such as Nehrlich's and Cantrill's, stress choosing where to go deep and building trust and shared context. Indiscriminate involvement is a different thing.
- Does the company still work when the founder is away? If not, the structure has a dependency problem regardless of the label.
- Who benefits from the story? An essay praising founders will be popular with founders. That doesn't make it wrong, but it's a reason to look for outside evidence.
Key Facts: Founder mode vs manager mode
- Paul Graham's Founder Mode essay was published in September 2024 after a Brian Chesky talk at a Y Combinator event.
- Graham defines manager mode through the advice to "hire good people and give them room to do their jobs," and argues it describes how to run a company you didn't found.
- He says founder mode will break the rule that the CEO engages with the company only via direct reports, making skip-level meetings normal.
- Graham states there are, as far as he knows, no books specifically about founder mode, so the claim rests on anecdote and a small number of examples.
- His own footnote predicts misuse: founders unable to delegate may use the label as an excuse.
- Bain's Founder's Mentality names overload, stall-out and free fall as crises of scale, and lists "the unscalable founder" among the forces that erode it.
- Greiner's growth model describes a crisis of autonomy, where a directive style becomes too restrictive as an organization grows.
Related reading
