What Founder Mode Really Means
You got to figure out your technique for cutting through the bureaucracy you've built. Yes, to figure out what's going on. I think the really encouraging thing from Brian's talk is that it doesn't matter how big your company is and how big your bureaucracy is; like, you can change it.
This is Dalton plus Michael, and today we're going to talk about founder mode. Oh jeez, founder mode! So, um, we were at the YC alumni event and saw the founder mode talk, and more than that, like we've interacted with tons of YC late-stage founders over the year and kind of know a lot about what happens when companies get late stage. And, um, I think a lot of people in the room were really excited.
Yeah, yeah. I mean, so to set this up, um, we did a special event just for growth stage, late-stage YC founders. Yes, you know, so picture a room, couple hundred people, you know, pretty full. Y, all the founders of late-stage, growth-stage YC companies—companies making tens of millions or hundreds of millions—not B companies. When you think of YC companies, you may be thinking, "Oh, you know, two-person startups," no, not that. These were the folks that have hit product-market fit and who have a lot of employees. And we brought them together to, like, learn from each other and share notes.
And so, of course, Brian Chesky was one of the speakers that we had there because he is a hero of running a late-stage company, and, yeah, going through all sorts of things. And the prompt, as I understand that he was given, was give a talk specifically tailored for the later-stage companies, right? Like, especially for what you went through with Airbnb. What do people need to hear that are also late-stage founders?
Yes, okay, so that's the setup. That it's worth mentioning we were there; pretty relevant, pretty relevant setup. Yes, and I think that the core message that I really think is hard for early-stage founders to understand is that when you're a late-stage founder and you have to hire executives and then layers of management, it's hard to have a feeling for what's happening in your company. You know, you very quickly hit Dunbar's number, and none of the people include people who are maybe talking to customers or writing actual code or making designs, especially if you don't curate that list well.
And there are a lot of people who are slowly starting to feel like, you know, almost like they're operating a marionette. Like, it's not my own hands and my own eyes anymore doing the work in a company; I'm, like, so separated. It's hard to understand what's happening, and I think that's a problem that a lot of later-stage founders have. And so that's really kind of—yep—the kickoff was like, hey, are you feeling like that?
Yeah, well, again, the context is if you're a later-stage founder. I experienced this at my startup, and I know you did too. It is very typical for your investors and your board to say, "Hey, you need a big management team; you need to delegate, and you need to hire all these experts, and they know better than you, and so you need to stay out of the details." And again, you would never—investors would never say this to a two-person team. So again, to the extent people out there in the world are trying to understand how this relates to their tiny startup, it does not; it doesn't. It's just what you know if you scale.
Yes, scaling means hiring executives and delegating major parts of your business and kind of assuming they know better than you because they have a fancy resume. Okay, and so the real point Brian was trying to make, and then PG in his blog post, I would argue was, hey, this thing that is considered conventional wisdom about how to operate a growth-stage startup seems wrong, and no one's ever talked about that before.
Gee, and I would argue that there's been some critique on this point. I think that critique is accurate. I don't think there's a business book you can find that says, like, you know, what the greatest CEOs did—hired a bunch of execs and went on vacation. So, like, I don't actually think anyone is arguing the other side; that's a no—no one's arguing.
No one's arguing that. I think it's much more like, oh, hiring executives and management's hard. Yep. And when you don't do it well, you kind of get in this trap. Yeah, and I think a lot of what Brian was trying to do is get people advice and, like, how do you get yourself out of this trap?
Yeah, well, here's a really concrete example or rubric for it. It's just how many layers of management there are relative to how large your company is. I was even reading an article recently that Amazon's about to do a big reorg; kind of sounds like it was influenced by founder mode, if I'm real. Maybe not; maybe it's a coincidence. But they're just trying to look at how many layers of management between the entry-level folks and the CEO and just try to move several layers.
And what's hard to understand when you have an org that's, like, 1,000, 2,000 plus people is it sounds so—especially because it's a software company—just knowing what's going on is really hard. Like, just, like, you would be shocked at the questions that a startup can answer about its users and its products that a large company—the answers are tricky. And, like, I've heard of companies, you know, hiring consulting firms because, like, we don't really know how to answer the question, "Who are our users?" And, yeah, let's pay McKinsey to find out who our users are.
Yeah, it's really tricky, um, and like that doesn't—like, it's hard; it's really, really hard. I think the other thing that people don't realize is that when a company gets to these thousands of people, bureaucracy sneaks in. And bureaucracy isn't a government problem; it is an organizational problem.
And how many people need to weigh in on a decision? How many people need to approve a decision? How much—how many additional pieces of approvals are created because one bad thing happened once? Yes, so there's now all this red tape because this one thing happened 10 years ago, years of one-off bad thing—this can never happen again. They just pile up. Yes, and then suddenly the things that are important, which are, you know, talking to your users, understanding what the complaints coming in from customer service are, using your own product, understanding how your product fails, people—those things—it’s weird to say it out loud, but those things somehow get shoved down the list.
And it’s easy to trust other people, like, "Hey, I need to manage this bureaucracy, and it's your jobs to do what I used to do, which is like serve the customers." And I think that mentality is wrong. It's very, very wrong. It's interesting because, you know, Parker from Rippling came to talk to YC and give a similar talk, actually, to Brian's talk. He illustrated what he does when a problem gets to his desk, and I love this explanation because he's basically like, look, if I'm seeing a problem, many, many people below me did not fix it, right?
And he's like sending some message like if a problem is sneaking all the way up the chain to get to me, I'm sending some message all the way down and expecting the person at the bottom to, like, hear it. That's never going to happen. And so he has this technique where he takes every layer of management all the way down to the individual contributor doing the work, and they all together go and talk to the individual contributor and figure out what the hell is going on and how do we fix it.
And there's, like, a subtle message that anyone below him could have done that exercise without him, and maybe the problem would have gotten to his desk. And I think that, like, that's one of many techniques of founders that founders use to cut through that bureaucracy and to figure out what the hell's going on.
And I think a lot of what Brian's was really saying is that, like, you got to figure out your technique for cutting through the bureaucracy you've built, yes, to figure out what's going on. And if people are preventing you from doing that, that you hired—well, he made an interesting point that he was disinvited from his own meetings at his own company because he was seen as causing problems, and not—you know.
And so again, this was one of his points, which was the bureaucracy was so big that it was trying to keep me out of it, and it was my own company. Yes, and so again, is this relevant to a two-person startup? No. Is this relevant to a 10-person startup? No, it's a stretch. Okay, I don't think so—no, not even close. No.
The kind of dysfunctional setup you have is very clearly for what happens when you have such a large number of humans in your organization that the founder is sort of put on the sidelines and told to just stay in their lane and no longer be involved in the mechanics of running their company. And what's interesting is, like, I would flip it around because I think when you hire great managers and great executives, you get a very different vibe.
When you hire great managers and great executives, they understand the power and the authority of a founder, and they often are trying to figure out how to use the founder—use the CEO—to accomplish some goal versus trying to build some wall or trying to protect, you know, the founder from what's really going on. And I think that, um, it's really hard to hire really good executives. Not only are they rare, but there are a lot of big companies that pay a lot of money.
And so for a startup, even at $100 million of revenue, what's the likelihood they're going to nail the best executives? Like, it's really, really hard. It's really, really hard. And I think this is why that talk was so relevant to the people in the room is like you get people trying to figure out how to manage their kind of B and C-grade executives, and it ain't going well.
I will—you should be so lucky to have this problem. This is the problem you want; this is great. Yes, yes. I will say this: I think one of the threads that this took, which I found weird, was it changing it from a conversation about executives and management versus founder CEO to a conversation about investors versus a founder CEO, which was weird. It was kind of like, "Oh, at the board we know what to do, and the founder is not doing it." I thought that was kind of a weird take on it.
But I think if you're an investor commenting on founder mode, maybe it's easiest to just make yourself the main character. Yeah, I didn't get that either, honestly, but that wasn't actually part of the—like, there was no point in the conversation where it was like, "Oh, my investor told me to do this, and I disagree with it." Like, that was irrelevant. And I do think that, like, if your investors are telling you what to do, you have a problem.
It's just different than this. There’s a different name for that problem. Yeah, it's a different problem; it has nothing to do with this. Any idea that goes viral and gets popular becomes a sort of, like, Rorschach test where everyone sees in it their own thing, and they inadvertently—a lot of—I saw a lot of projection, yes, where you could kind of tell who, uh, yeah, who was a little triggered by some of this stuff because I think they may have saw themselves in it.
I don't know; it was fascinating to watch all of the news cycle about this because I feel like I learned a lot about people's minds that they didn't mean to reveal by their reaction to the founder mode essay. Yeah, well, and it was so weird because it was kind of like I didn't realize this would be a conversation for Twitter at all. Exactly.
And so I think this is a good tip for just consuming the news or consuming things on Twitter in general, which is to realize when something gets sufficiently viral, it gets decontextualized from the person that said it and what the context was and just turns into, like, basically a flame war. You click—whatever—a clickbait flame war about whatever your preferred topic is. Yes, you know, "Oh gee, here's something that's getting viral; let's weigh in on it with my preferred thing that I'm mad about."
Yes, I remember when the essay first went out, being like, "Oh, everyone's going to weigh in on this." You could just tell, yeah, that this is going to be one of those things. So remember, friends, don't fall for the clickbait, I guess.
Yeah, yeah, fake news is fake news, and I do think that, like, if you're one of the very, very few founders who do have this problem, like you should talk about it. You might be surprised at other people having this problem. And, like, I think the really encouraging thing from Brian's talk is that it doesn't matter how big your company is and how big your bureaucracy is; like, you can change it. Y, and you can start running your company again.
Well, the key thing is he was saying this was my fault. He wasn't passing the buck. The point of the story is I made a mistake. Learn from me; don't do what I did. It wasn't to blame people working at Airbnb. Only one person messed up. Yeah, right? And he was owning it; that was the message.
Yeah, all right, great chat! Sounds good. Thanks. [Music]