It’s f@#ked up when your mind’s playin’ tricks on ya
—The Geto Boys, Mind Playing Tricks on Me
By far the most difficult skill for me to learn as CEO was the ability to manage my own psychology. Organizational design, process design, metrics, hiring and firing were all relatively straightforward skills to master compared to keeping my mind in check. Over the years, I’ve spoken to hundreds of CEOs all with the same experience. Nonetheless, very few people talk about it and I have never read anything on the topic. It’s like the fight club of management: The first rule of the CEO psychological meltdown is don’t talk about the psychological meltdown
At risk of violating the sacred rule, I will attempt to describe the condition and prescribe some techniques that helped me. In the end, this is the most personal and important battle that any CEO will face
If I’m Doing a Good Job, Why Do I Feel So Bad?
Generally, someone doesn’t become CEOs (sic) unless she has a high sense of purpose and cares deeply about the work she does. In addition, a CEO must be accomplished enough or smart enough that people will want to work for her. Nobody sets out to be a bad CEO, run a dysfunctional organization, or create a massive bureaucracy that grinds her company to a screeching halt. Yet no CEO ever has a smooth path to a great company. Along the way, many things go wrong and all of them could have and should have been avoided
The first problem is that everybody learns to be a CEO by being a CEO. No training as a manager, general manager or any other job actually prepares you to run a company. The only thing that prepares you to run a company is running a company. This means that you will face a broad set of things that you don’t know how to do that require skills that you don’t have. Nevertheless, everybody will expect you to know how to do them, because, well, you are the CEO. I remember when I first became CEO, an investor asked me to send him the “cap table.” I had a vague idea of what he meant, but I didn’t actually know what the format was supposed to look like or what should be included or excluded. It was a silly little thing and I had much bigger things to worry about, but everything is hard when you don’t actually know what you are doing and I wasted quite a bit of time sweating over that stupid spreadsheet
Even if you know what you are doing, things go wrong. Things go wrong, because building a multi-faceted human organization to compete and win in a dynamic, highly competitive market turns out to be really hard. If CEOs were graded on a curve, the mean on the test would be 22 out of a 100. This kind of mean can be psychologically challenging for a straight A student. It is particularly challenging, because nobody tells you that the mean is 22
If you manage a team of 10 people, it’s quite possible to do so with very few mistakes or bad behaviors. If you manage an organization of 1,000 people it is quite impossible. At a certain size, your company will do things that are so bad that you never imagined that you’d be associated with that kind of incompetence. Seeing people fritter away money, waste each other’s time, and do sloppy work can make you feel bad. If you are the CEO, it may well make you sick
And to rub salt into the wound and make matters worse, it’s your fault
Nobody to Blame
You can’t blame Jazz Musicians
Or David Stern with his NBA fashion issues
—Nas, Hip Hop is Dead
When people in my company would complain about something or other being broken such as the expense reporting process, I would joke that it was all my fault. The joke was funny, because it wasn’t really a joke. Every problem in the company was indeed my fault. As the founding CEO, every hire and every decision that the company ever made happened under my direction. Unlike a hired gun that comes in and blames all of the problems on the prior regime, there was literally nobody for me to blame
If someone was promoted for all the wrong reasons, that was my fault. If we missed the quarterly earnings target, that was my fault. If a great engineer quit, that was my fault. If the sales team made unreasonable demands on the product organization, then that was my fault. If the product had too many bugs, that was my fault. It kind of sucked to be me
—The Geto Boys, Mind Playing Tricks on Me
By far the most difficult skill for me to learn as CEO was the ability to manage my own psychology. Organizational design, process design, metrics, hiring and firing were all relatively straightforward skills to master compared to keeping my mind in check. Over the years, I’ve spoken to hundreds of CEOs all with the same experience. Nonetheless, very few people talk about it and I have never read anything on the topic. It’s like the fight club of management: The first rule of the CEO psychological meltdown is don’t talk about the psychological meltdown
At risk of violating the sacred rule, I will attempt to describe the condition and prescribe some techniques that helped me. In the end, this is the most personal and important battle that any CEO will face
If I’m Doing a Good Job, Why Do I Feel So Bad?
Generally, someone doesn’t become CEOs (sic) unless she has a high sense of purpose and cares deeply about the work she does. In addition, a CEO must be accomplished enough or smart enough that people will want to work for her. Nobody sets out to be a bad CEO, run a dysfunctional organization, or create a massive bureaucracy that grinds her company to a screeching halt. Yet no CEO ever has a smooth path to a great company. Along the way, many things go wrong and all of them could have and should have been avoided
The first problem is that everybody learns to be a CEO by being a CEO. No training as a manager, general manager or any other job actually prepares you to run a company. The only thing that prepares you to run a company is running a company. This means that you will face a broad set of things that you don’t know how to do that require skills that you don’t have. Nevertheless, everybody will expect you to know how to do them, because, well, you are the CEO. I remember when I first became CEO, an investor asked me to send him the “cap table.” I had a vague idea of what he meant, but I didn’t actually know what the format was supposed to look like or what should be included or excluded. It was a silly little thing and I had much bigger things to worry about, but everything is hard when you don’t actually know what you are doing and I wasted quite a bit of time sweating over that stupid spreadsheet
Even if you know what you are doing, things go wrong. Things go wrong, because building a multi-faceted human organization to compete and win in a dynamic, highly competitive market turns out to be really hard. If CEOs were graded on a curve, the mean on the test would be 22 out of a 100. This kind of mean can be psychologically challenging for a straight A student. It is particularly challenging, because nobody tells you that the mean is 22
If you manage a team of 10 people, it’s quite possible to do so with very few mistakes or bad behaviors. If you manage an organization of 1,000 people it is quite impossible. At a certain size, your company will do things that are so bad that you never imagined that you’d be associated with that kind of incompetence. Seeing people fritter away money, waste each other’s time, and do sloppy work can make you feel bad. If you are the CEO, it may well make you sick
And to rub salt into the wound and make matters worse, it’s your fault
Nobody to Blame
You can’t blame Jazz Musicians
Or David Stern with his NBA fashion issues
—Nas, Hip Hop is Dead
When people in my company would complain about something or other being broken such as the expense reporting process, I would joke that it was all my fault. The joke was funny, because it wasn’t really a joke. Every problem in the company was indeed my fault. As the founding CEO, every hire and every decision that the company ever made happened under my direction. Unlike a hired gun that comes in and blames all of the problems on the prior regime, there was literally nobody for me to blame
If someone was promoted for all the wrong reasons, that was my fault. If we missed the quarterly earnings target, that was my fault. If a great engineer quit, that was my fault. If the sales team made unreasonable demands on the product organization, then that was my fault. If the product had too many bugs, that was my fault. It kind of sucked to be me
Comments (0)
The minimum comment length is 50 characters.