To Founder Mode or Not to Founder Mode?
As somebody who is no longer based in Silicon Valley, I make an effort to read the tech Twitter. If you are not doing the same, the hottest topic the last few days has been Paul Graham's essay Founder Mode. The reason I want to talk about it is that the most frequent question I get from managers I work with is "what does it take to be a great manager?" I think this essay is very relevant, even though there are several points to disagree with there.
The point of the essay, which admittedly is not very detailed, is there are two modes of running an org: a "Founder Mode" and a "Manager Mode". The difference is stark. The traditional wisdom is that a great leader is somebody who hires a great team, sets a vision, and then gives the team space to execute. They delegate. More than anything, this traditional leader avoids micromanagement. This is the "Manager Mode", according to PG.
On the contrary, the "Fonder Mode" is about getting into details. It's about making decisions by yourself. It's about not being afraid to sweat the small stuff. This is supposedly how founder-lead companies are run, and why they generally outperform companies that are not run by founders. PG clearly advocates the Founder Mode.
Now, the best part of reading PG is that he always make you think about where you agree with him and where you do not. Here are my thoughts:
I think it is true that great founders are into details to a surprising degree. The few times I've been to Mark Zuckerberg reviews I've been amazed how much he cares about some seemingly minor things, such as design of a screen, the behavior of a feature, a particular metric, a small policy detail, and so on.
领英推荐
But one place I disagree with PG is that it's not just founders who can exhibit this behavior. Several Meta leaders I've observed closely, including top WhatsApp leaders, equally go into details to a great degree. The team being questioned this way may feel a bit awkward about it, but there is no denying that this is impressive and very effective.
Finally, a couple of things what the Founder Mode is not. First, being a great leader does not mean that you get into every detail. Great leaders still delegate very often. But they have an uncanny sense of where to get into details. They know where to delegate and where to drill down. This is very important - otherwise you can't scale at all.
Second, being in a Founder Mode does not mean being an asshole, whatever people think of Steve Jobs and his leadership style. I've never seen great leaders act with disrespect, even when they ask tough questions and get into gory details. This is also important to remember.
Now, you may say, I'm not a founder, how does this all apply to me? My point is that great engineering managers go beyond just managing their team. They develop deep domain expertise. They have a point of view on many questions. They get into details where it's important. They act more like founders do rather than being just typical people managers.
I suggest you read PG's essay, and ask yourself how you can move just a bit closer towards Founder Mode. It may be uncomfortable, it definitely takes an extra effort, but I think it'll be worth it. Just remember to think for yourself how this applies to your particular situation.
Software Engineer @ Google || Daily Content on Software Engineering & Cracking FAANG ||?Ex-Hike,?Amazon
5 个月Mark Tsimelzon I am a tech creator in the SWE niche and I have sent you the connection request to discuss a potential collaboration opportunity Let's chat, thanks
Applied AI | Converting ideas & designs into user-first software
6 个月Great essay Mark! Just on this point - Great leaders still delegate very often. But they have an uncanny sense of where to get into details. Since it's still significantly random what issue is important and which one is not - would it not make sense to get into details as much as possible to hit an issue which is important?
Partnerships, Alliances and Ecosystem Builder (ex-Twitter, Cisco)
6 个月Good perspectives Mark. Your point about when to get into the detail and when not to is key for me. I think that's a learned skill. The article itself didn't discuss one important aspect of when to "founder mode" and when not to, and that's the stage or phase of the business. I imagine that that could be important as well (coming from a non-founder of course).
Senior Engineering Leader | Meta, ex-Google
6 个月Honestly I don't understand the premise of the original post by PG. Surely an outstanding engineering manager (or engineering leader, more generally) understands the domain area well, and has opinion on the most important features grounded in something more substantial rather than "I don't like the colour of that button"?