One of the most painful parts of the Google acquisition of Nest was losing our board. We had an amazing board at Nest—structured and informed, operational and active. We could go to the board, get firm agreement on a clear strategy and plan: yes, we’re going to do this, I’ll get back to you in a week with next steps.

When we were acquired, our beloved board was dissolved and replaced with . . . nothing. We were supposed to have a governing board of several Google execs, but our meetings were either perpetually rescheduled or barely attended. We’d propose a path forward and everyone would say, “Yeah, well, let’s think about that a little bit more.” The can would get kicked down the road to the next meeting that nobody went to and we’d be left sitting

on our hands.

One might look at that and say, “So what’s the problem? If the board doesn’t give you guidance, then just go do it yourself. You’re the CEO.”

But that is not the solution. Even the most incredible CEOs in the world still need a board. Not the meetings, necessarily, but the advice of smart, invested, experienced people. Even big projects within a company should have a mini-board—a collection of helpful execs who can work to guide a project lead and step in if things go sideways.

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.

Google Ventures, now known as GV, was an investor. They knew our financials and had always been extremely supportive, so I wasn’t worried about the number. I was worried about which teams we’d work with, what technology we’d share, what products we’d build. Nest wasn’t joining Google for the money—we were joining to accelerate our mission. So it was always mission first, money second.

Together with Google, we went through every single function—marketing, PR, HR, sales, every part of the company. We established where we could create synergies and where we couldn’t, figured out which managers would be assigned to us, how we would do the hiring, which perks people would get, which salaries they could expect, which teams would be working together closely, and how those relationships would be established.

It took a lot of time. In fact I was starting to get a lot of eye rolls. “Really, Tony? You want to get into the details of this now?” Yes, yes, I do. It’s important.

And it was—critically important and usually overlooked.

Most acquisitions are driven and overseen by bankers, and bankers only make the real money if the deal goes through, so they’re motivated to move fast and get paid. They don’t care about getting every detail of what happens to employees right. They don’t really care about cultural fit. Not deeply.

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.

And while some of the specific do’s and don'ts for CEOs are unique to their role, most essential things like setting expectations, developing a vision, establishing a management process, creating priorities, building your management team, and doing an exceptional job on your earliest projects apply equally to anyone in a new leadership role.

When Ron Daniel was the managing partner of McKinsey & Company from 1976 to 1988, he sent a memo to new recruits when they started, entitled, “On Becoming an Associate.” His advice is still memorable all these years later: “Recognize the necessity of getting off to a good start in the firm. Your first few engagements are critical. During these studies, you can establish an internal clientele for yourself - that is, by performing in an outstanding way, your reputation will be quickly established in your office and even the firm.” (We’ve incorporated Ron’s memo in the Appendix of the book.)

This is especially important because whenever you assume a new role, you’re in what Max DePree, former CEO of furniture company Herman Miller and author of Leadership Is an Art, calls “a temporary state of incompetence.” Even if you think you know a company - or a department or a division - before you take over its leadership, think again. As GE’s Immelt reminisces, “I worked for this place for twenty-one years before I got the CEO job and there were still things that shocked me when I took over.”

The knowledge gap is even wider for outsiders. “Anyone coming into a new situation is faced with the fact that they often have to do the most at a point they know the least. You may have previous experience and you may be smart and have insight into how things work, but you know the least about the actual company you’re engaged in at the same time you have to set things in motion,” says AOL chairman and CEO Jonathan F. Miller, himself recruited into the company from the outside.