The Hard Thing About Hard Things

For some reason I was expecting this book to be about how to do hard things. In my mind a “hard thing” was a single project that was technically difficult. I’m not sure where that idea came from, but that isn’t what this book is about. The Hard Thing about Hard Things is about being a CEO and how challenging that job is.

I enjoyed the book and it’s something one could come back to again and again over the span of a career.

Loudcloud/Opsware

I remember hearing about Opsware waaaaay back in the day. At the time it wasn’t something I would keep track of; I wasn’t paying attention to the whole Silicon Valley thing at the time. I was just getting out of school and into a job that was almost as far away from Silicon Valley as you could get (Northern Alberta). I should do some more reading on Loudcloud and Opsware, as it sounds like they were far ahead of the game for a while, and this was prior to even virtualization. (In fact in the book Horowitz mentions that the invention of virtualization was a part of why he decided to sell Opsware to HP, in that they would have had to spend a lot of time and money supporting virtualization in their product.)

A few notes from my reading

  • The right kind of ambition

At a macro level, a company will be most successful if the senior managers optimize for the company’s success (think of this as global optimization) as opposed to their own personal success (local optimization)

When I spoke to Mark Cranney…it was difficult to get him to discuss his personal accomplishments. He really only wanted to discuss how his old company won.

  • Much discussion of wartime vs peacetime CEOs…what wartime CEOs do is much different than peacetime, and most of the time one person is not great at both styles. So if you are “at war” you need a different CEO.

  • “The struggle” of the CEO

…if there is one skill that stands out, it’s the ability to focus and make the best move when there are no good moves. It’s the moments where you feel most like hiding or dying that you can make the biggest difference as CEO…I offer some lessons on how to make it through the struggle without quitting or throwing up too much.

  • Training

This book is very pro-training. I love it. Horowitz quotes Andy Grove:

Training is, quite simply, one of the highest-leverage activities a manager can perform.

  • Andy Grove, Bill Campbell - Horowitz mentions these people many times throughout the book. A new book about Bill Campbell is out. Definitely going to read it.

  • Being honest

If you run a company, you will experience overwhelming psychological pressure to be overly positive. Stand up to the pressure, face your fear, and tell it like it is.

I’m assuming Horiwitz determined when to be honest very carefully.

  • $1.6 billion sale to HP

Everything in the book is working towards this sale. That number is the success of the company. Nothing else matters. Any other choices Horowitz could have made over the lifetime of the company might have watered down this number. He fought hard to get a specific share price and was willing to have the deal fall through if he didn’t get it.

  • Mark Cranney

I found any discussion around Mark Cranney fascinating. I have a pet theory, which I think is more than a theory, that most high ranking managers and sales people are…just tall. Note that I am exactly average height so maybe that has something to do with it. :)

I interviewed Mark Cranney. He wasn’t what I expected: he didn’t fit the stereotype of a hard-charging sales executive. For starters, Mark was average height, whereas most sales executives tend to be rather tall. Next, he was as wide as he was tall. not fat, just square. His square body seemed to fit rather uncomfortably into what must have been a custom-tailored suit–there is no way an off-the-rack business suite would fit a square guy like Mark.

Later in the book Horowitz says that if Cranney had better met the physical stereotype of an executive he would have been CEO of IBM, ie. that Opsware got Cranney at a discount.

  • Hire for strength

He discusses reasons why CEOs fail executives and then have to fire them. One of the reasons is not hiring for strengths.

You hired for lack of weakness rather than for strengths. This is especially common when you run a consensus-based hiring process. The group will often find the candidate’s weaknesses, but they won’t place a high enough value on the areas where you need the executive to be a world-class performer. As a result you hire an executive…who is mediocre where you need her to be great.

There’s much more to get out of this book. Like most of Silicon Valley, I heavily suggest just picking up a copy.