One reason we managed to put together an outstanding team to create the iPod was that our team could get relatively outsized stock and bonus plans that they couldn’t get anywhere else at Apple. The other important reason was that we had Steve Jobs fully behind us. Those two things allowed us to recruit amazing people—even though we couldn’t tell them what they’d be working on before they signed on—and survive the internal antibodies. Steve

gave our tiny team an unfair advantage—gave us air cover and dropped bombs if anyone messed with us. There were times when the internal antibodies at Apple tried to expel us from the organization—we’d constantly hear “We have other priorities, we’ll help you if we have time.” Or “Why are we doing this project—it’s not core to our business.” But as long as our team was making reasonable (or unreasonable but important) requests, the teams who were stalling us would get a call from Steve. “If they’re asking for something, then give it to them for Christ’s sake! This is very important for the company!

I’ve seen way too many people come out of the corporate world, decide to start a company, and be completely unprepared for what it takes. If they’ve never been on a small team starting from scratch, they’re often a fish out of water. They spend too much money too fast. Hire too many people. Don’t put in the time, don’t have the startup mentality, can’t make hard decisions, are buried by consensus thinking. They end up making mediocre products or

nothing at all.

Don’t let that be your story. If you want to start a company, if you want to start anything, to create something new, then you need to be ready to push for greatness. And greatness doesn’t come from nothing. You have to prepare. You have to know where you’re headed and remember where you came from. You have to make hard decisions and be the mission-driven “asshole.” [See also: Chapter 2.3: Assholes: Mission-driven “assholes.”]

So do the work. Know what you’re getting into. Trust your gut.

And when the time comes, you’ll be ready.

The Google teams with whom we’d planned to integrate and codevelop technologies and products were reluctant to work with us. They kept asking their execs for more details to figure out if they really had to help us at the expense of their own projects. Why? Why? Why do we have to help a team that isn’t Google? Over the subsequent months, every time we had to clarify yet again for customers that Nest was separate from Google, our internal reputation took another hit.

I should have remembered what it was like at Apple during the very first months when we started building the iPod. It just didn’t occur to me—Nest was so much bigger and more established than my tiny iPod team, I thought this was a completely different situation. But it was exactly the same. Back then Apple’s executive antibodies saw us coming to take their time and draw away their resources, so they tried to block our way and ignore our requests.

That’s when Steve Jobs gave us air cover, dropped bombs on the teams who were slowing us down, forced the issue, yelled sometimes to make sure we got what we needed. Steve Jobs fighting for us was ultimately what allowed us to succeed.

Plenty of people warned me that the worst thing I could do was let Steve into the company, that he would bully me and everyone else. I always said the same thing: “How can Steve Jobs coming into our company not be a good thing? Even if it comes at my expense? Who wouldn’t want Steve Jobs to have influence over how a company is run?” I wasn’t worried about how he would act, and I was confident that if he did do something that was out of line, I could call him out on it. He was quick to judge people, and when he criticized, it was often quite harsh. That said, he came to all the board meetings and actively participated, giving the kind of objective criticism you’d expect from any board member. He rarely created trouble for me. Not never but rarely.

I’m comforted by something I’ve come to believe more and more in recent years—that it’s not always good for one person to have too much power for too long. Even when a CEO is working productively and effectively, it’s important for a company to have change at the top. I don’t know if other CEOs agree with this, but I’ve noticed that you can accumulate so much power in a job that it becomes harder to keep a check on how you wield it. Little things can start to shift. Your confidence can easily tip over into overconfidence and become a liability. You can start to feel that you’ve heard every idea, and so you become impatient and dismissive of others’ opinions. It’s not intentional, it just comes with the territory. You have to make a conscious effort to listen, to pay attention to the multitude of opinions. I’ve raised the issue with the executives I work most closely with as a kind of safeguard. “If you notice me being too dismissive or impatient, you need to tell me.” They’ve had to on occasion, but I hope not too often.