Secrets to Yawn-Free Board Meetings

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

The objective of board meetings should always be to have great conversations that help you and your executive team think clearly about the issues in front of you, as well as making sure your directors have a clear and transparent view of the state of the business. These conversations come from a team dynamic that encourages productive conflict. There’s no sure-fire formula for achieving this level of engagement, but here are three few guidelines you can follow to increase your chances.

Schedule board meetings in advance, and forge a schedule that works. Nothing is more disruptive – or more likely to drive low turnout – than last minute scheduling. Make sure you, or your executive assistant, knows board members’ general schedules and travel requirements, and whether they manage their own calendar or have their own executive assistant. Set your board meeting schedule for the year in the early fall, which is typically when people are mapping out most of their year’s major activities. If you know that one of your board members has to travel for your meetings, work with the CEOs of the other companies to coordinate meeting dates. Vary the location of meetings if you have directors in multiple geographies so travel is a shared sacrifice.

In the startup stage of our business at Return Path, we ran monthly meetings for an hour, mostly call-in. In the revenue stage, we moved to six to eight meetings per year, two hours in length, perhaps supplemented with two longer-form and in-person meetings. As a growth stage company, we run quarterly meetings. They’re all in-person, meaning every director is expected to travel to every meeting. We probably lose one director each time to a call-in or a no-show for some unavoidable conflict, but, for the most part, everyone is present. We leave four hours for every meeting (it’s almost impossible to get everything done in less time than that) and sometimes we need longer.

Many years, we also hold a board offsite, which is a meeting that runs across 24 hours, usually an afternoon, a dinner, and a morning, and is geared to recapping the prior year and planning out the next year together. It’s especially exhausting to do these meetings, and I’m sure it’s especially exhausting to attend them, but they’re well worth it. The intensity of the sessions, discussion, and even social time in between meetings is great for everyone to get on the same page and remember what’s working, what’s not, and what the world around us looks like as we dive into the deep end for another year.

Build a forward-looking agenda. The second step in having great board meetings is to set an agenda that will prompt the discussion that you want to have. With our current four-hour meetings, our time allocation is the following:

I. Welcomes and framing (5 minutes)

II. Official Business (no more than 15 minutes unless something big is going on)

III. Retrospective (45 minutes)

a. Target a short discussion on highlighted issues

b. Leave some time for Q&A

IV. On My Mind (2 hours)

a. You can spend this entire time on one topic, more than one, or all, as needed.

b. Format for discussions can vary—this is a good opportunity for breakout sessions, for example.

V. Executive Session (30 minutes)

This is your time with directors only, no observers or members of the management team (even if they are board members).

VI. Closed Session (30 minutes)

This is director-only time, without you or anyone else from the management team.

This agenda format focuses your meeting on the future, not the past. In the early years of the business, our board meetings were probably 75 percent “looking backwards” and 25 percent “looking forwards.” They were reporting meetings—reports which were largely in the hands of board members before the meetings anyway. They were dull as anything, and they were redundant: all of our board members were capable of processing historical information on their own. Today, our meetings are probably ten percent “looking backwards” and 90 percent “looking forwards”—and much more interesting as a result.

Separate background reading and presentation materials. Finally, focus on creating a more engaging dialogue during the meeting by separating background reading from presentation materials. In our early days, we created a huge Powerpoint deck as both a handout the week before the meeting and as the in-meeting deck. That didn’t create an engaging meeting.

There’s nothing more mind-numbing than a board meeting where the advance reading materials are lengthy Powerpoint presentations, than when the meeting itself is a series of team members standing up and going through the same slides, bullet by excruciating bullet—that attendees could read on their own.

When we separated the background and presentation materials, people were engaged by the Powerpoint—because it delivered fresh content. We started making the decks fun and engaging and colorful, as opposed to simple text and bullet slides. That was a step in the right direction, but the preparation consumed twice as much time for the management team, and we certainly didn’t get twice the value from it.

Now we send out a great set of comprehensive reading materials and reports ahead of the meeting, and then we have a completely Powerpoint-free meeting. No slides on the wall. This changes the paradigm away from a presentation—the whole concept of “management presenting to the board”—to an actual discussion. No checking email. No yawns. Nobody nodding off. Everyone—management and board—is highly engaged

I gave a presentation to a few hundred Return Path employees in January at an all-hands conference we did called “How to Manager Your Career.”

The presentation has three sections — The Three Phases of a Career, How to Get Promoted, and How to Wow Your Manager.

While it’s not as good without the voiceover and interactivity, I thought I’d post it here…see the presentation on Slideshare.

As I said to my audience, if there’s one thing to take away from the topic, it’s this:

Managing your career is up to one, and only one person – you. 

It doesn’t matter how great a corporate culture you have, or how supportive your manager is.  You’re the only person who cares 100% of the time about your career, and you’re the only person with a longitudinal view of what you love, what you’re great at, where you’ve been, and where you want to go.

Getting the Most out of Your Investors

Fred Wilson has been a venture investor and director in Return Path since 2000, first with Flatiron Partners and then with Union Square Ventures.  We’ve been through a lot of wars together.  In a couple of weeks, he and I are team-teaching a class in Entrepreneurship at Princeton, and the professor gave us the assignment of writing two pairs of blog posts to tee up discussion with the class.  The first two posts were mine on selecting investors and Fred’s on selecting investments.  This is my second one…and Fred’s post on the other side of the topic is here.

Once you’ve done a venture financing and the smoke clears, you have to transition the relationship you have with your new investor from the courting phase to building a CEO-Director relationship for the long haul.  Here are a few thoughts on how best to do optimize the relationship once it’s established.

1. Take onboarding seriously.  I always say that the hiring process for new employees doesn’t end when the employee starts…it ends 90 days later after some deliberate onboarding and a two-way review to check in and see how things are going.  Adding a new Board member is the same.  Onboard him or her with some of the same rigor and materials with which you’d onboard a new executive.  Touch base a lot early on.  Schedule an in-person 1:1 check-in after a few months to see how things are going
2. Give news early and often.  CEOs who wait until Board meetings to share all news are missing out on the point of a good director relationship, as well as missing the point of how communications work in the 2010s.  This is especially true with bad news.  No one likes to get it, but the earlier people hear it, the more they can thoughtfully process it and provide help
3. Ask for and give feedback early and often.  Though there are certainly some exceptions, venture investors are notoriously bad about giving and receiving feedback.  If you set the tone by asking for feedback regularly – then being sure to internalize and act on it and check back in to see if improvements are obvious – you can get even the most reticent director to speak up.  And there’s no reason you shouldn’t be providing feedback in near-real time as well.  Just because a director is your boss doesn’t mean he or she is meeting your expectations, and it’s a partnership, not a true hierarchical relationship
4. Ask for help and give assignments.  As a friend of mine says to her kids all the time, You don’t A-S-K, you don’t G-E-T.  If Board members don’t have specific things to work on, they either do nothing, or they do things you don’t need help on.  Drive the work like you would with any team member
5. Foster independent relationships with your team and other directors.  The hourglass model – where the CEO sits in between the Board and the management team and filters all dialog and data from one group to the other – is outdated.  A director will be much more able to add value to you and to the organization if he or she has an independent point of view as to what’s going on with your team and what other directors are thinking
6. Encourage directors to speak their minds.  As awful as company politics are, Board politics are worse.  Try to create an environment where directors aren’t shy about saying what’s really on their mind.  You don’t want to get through a Board meeting and then have someone pull you aside and say “what I really think is…”  This means you need to ask them direct questions, not be defensive in your verbal or body-language reaction, and make sure you allow for Executive Sessions at Board meetings
7. Hold directors accountable.  If you give a Board member an assignment, make sure it gets done on time and the way you asked for it.  If you have a director who is sitting in your Board meetings doing email the whole time, politely (and maybe privately, at least the first time) call him out on it.  If you don’t hold directors accountable, then just like your staff, they will learn that you don’t really mean what you say
8. Use their time wisely.  No one likes to waste time – certainly not professional investors who sit on a dozen boards.  Get Board materials out early, run productive Board meetings, and while you include some social element like a dinner or outing, make sure even that has the right group and is at the right kind of venue
9. Augment the Board with independent directors.  Venture directors can be amazingly helpful resources for you and your company.  But they typically have limitations as to their range of operating experience.  If you want to build a great Board and add some counterweights to your VCs, add one or more independent directors who are experienced business operators with experience serving on Boards as well

Year ago when we both first started blogging, Fred and I wrote a whole series of Venture Cliché and Counter-Cliché posts.  Writing these two makes me realize how much fun that was!  I’m looking forward to the class at Princeton next week and to seeing the kinds of questions these four posts inspire.

Unknown Unknowns

I’ve written a lot over the years about Return Path’s Core Values (summary post with lots of links to other posts here).  And I’ve also written and believe strongly that there’s a big difference between values, which are pretty unchanging, and culture, which can evolve a lot over time.  But I had a couple conversations recently that led me to think more philosophically about a company’s values.

The first conversation was at a recent dinner for a group of us working on fundraising for my upcoming 25th reunion from Princeton.  Our guest speaker was a fellow alumnus who I’ve gotten to know and respect tremendously over the years as one of the school’s most senior and influential volunteer leaders.  He was speaking about the touchstones in his life and in all people’s lives — things like their families, their faith, the causes they’re passionate about, and the institutions they’ve been a part of.  I remember this speaker giving a similar set of remarks right after the financial crisis hit in early 2009.  And it got me thinking about the origins of Return Path’s values, which I didn’t create on my own, but which I obviously had a tremendous amount of influence over as founder.  Where did they come from?  Certainly, some came from my parents and grandparents.  Some came from my primary and secondary education and teachers.  Some came from other influences like coaches, mentors, and favorite books.  Although I’m not overly observant, some certainly came from Hebrew school and even more so from a deep reading of the Bible that I undertook about 15 years ago for fun (it was much more fun than I expected!).  Some came from other professional experiences before I started Return Path.  But many of them either came from, or were strongly reinforced by my experience at Princeton.  Of the 15 values we currently articulate, I can directly tie at least seven to Princeton:  helpful, thankful, data-driven, collaborative, results-oriented, people first, and equal in opportunity.  I can also tie some other principles that aren’t stated values at Return Path, but which are clearly part of our culture, such as intellectually curious, appreciative of other people’s points of view, and valuing an interdisciplinary approach to work.

As part of my professional Reboot project, this was a good reminder of some of the values I know I’ve gotten from my college experience as a student and as an alumni, which was helpful both to reinforce their importance in my mind but also to remember some of the specifics around their origins – when and why they became important to me.  I could make a similar list and trade and antecedents of all or at least most of our Company’s values back to one of those primary influences in my life.  Part of Reboot will be thinking through all of these and renewing and refreshing their importance to me.

The second conversation was with a former employee who has gone on to lead another organization.  It led me to the observation I’ve never really thought through before, that as a company, we ourselves have become one of those institutions that imprints its values into the minds of at least some of its employees…and that those values will continue to be perpetuated, incorporated, and improved upon over time in any organization that our employees go on to join, manage part of, or lead.

That’s a powerful construct to keep in mind if you’re a new CEO working on designing and articulating your company’s values for the first time.  You’re not just creating a framework to guide your own organization.  You’re creating the beginning of a legacy that could potentially influence hundreds or thousands of other organizations in the future.

The Value of Paying Down Technical Debt

Our Engineering team has a great term called Technical Debt, which is the accumulation of coding shortcuts and operational inefficiencies over the years in the name of getting product out the door faster that weighs on the company’s code base like debt weighs on a balance sheet.  Like debt, it’s there, you can live with it, but it is a drag on the health of the technology organization and has hard servicing costs.  It’s never fun to pay down technical debt, which takes time away from developing new products and new features and is not really appreciated by anyone outside the engineering organization.

That last point is a mistake, and I can’t encourage CEOs or any leaders within a business strongly enough to view it the opposite way.  Debt may not be fun to pay off, but boy do you feel better after it’s done.  I attended an Engineering all-hands recently where one team presented its work for the past quarter.  For one of our more debt-laden features, this team quietly worked away at code revisions for a few months and drove down operational alerts by over 50% — and more important, drove down application support costs by almost 90%, and all this at a time when usage probably doubled.  Wow. 

I’m not sure how you can successfully scale a company rapidly without inefficiencies in technology.  But on the other side of this particular project, I’m not sure how you can afford NOT to work those ineffiencies out of your system as you grow.  Just as most Americans (political affiliation aside) are wringing their hands over the size and growth of our national debt now because they’re worried about the impact on future generations, engineering organizations of high growth companies need to pay attention to their technical debt and keep it in check relative to the size of their business and code base.

And for CEOs, celebrate the payment of technical debt as if Congress did the unthinkable and put our country back on a sustainable fiscal path, one way or another!

As a long Post Script to this, I asked our CTO Andy and VP Engineering David what they thought of this post before I put it up.  David’s answer was very thoughtful and worth reprinting in full:

 I’d like to share a couple of additional insight as to how Andy and I manage Tech Debt in the org: we insist that it be intentional. What do I mean by “intentional”

•  There is evidence that we should pay it
• There is a pay off at the end

 What are examples of “evidence?”

•  Capacity plans show that we’ll run out of capacity for increased users/usage of a system in a quarter or two
• Performance/stability trends are steadily (or rapidly) moving in the wrong direction
• Alerts/warnings coming off of systems are steadily or rapidly increasing

 What are examples of “pay off?”

•  Increased system capacity
• Improved performance/stability
• Decreased support due to a reduction in alerts/warnings

 We ask the engineers to apply “engineering rigor” to show evidence and pay-offs (i.e. measure, analyze, forecast).

 I bring this up because some engineers like to include “refactoring code” under the umbrella of Tech Debt solely because they don’t like the way the code is written even though there is no evidence that it’s running out of capacity, performance/stability is moving in the wrong direction, etc. This is a “job satisfaction” issue for some engineers. So, it’s important for morale reasons, and the Engineering Directors allocate _some_ time for engineers to do this type of refactoring.  But, it’s also important to help the engineer distinguish between “real” Tech Debt and refactoring for job satisfaction.

Connecting the Dots

Although I still maintain that the three primary roles of a CEO are to set Strategy and communicate it, develop Talent, and ensure that the business has proper Resources to run (see post here), I am increasingly finding that I play a fourth role in the organization that’s probably somewhat important, which is Connecting the Dots.

What do I mean by Connecting the Dots?  I mean helping others network internally, or helping others connect their work to the work of others, or helping others connect their work to the mission of the company, or even to the outside world.

Here are a few examples of how I’ve done this kind of work recently:

 –          I joined an Engineering all-hands and stood up after each segment to talk about the business impact of that team’s work during the prior quarter

–          I met with a new senior employee and connected him to someone internally that he wouldn’t have otherwise met with…but with whom he had a common outside interest

–          I helped a team that’s a classic “support team” understand why their work was directly, but not obviously, contributing to one of the company’s strategic initiatives

–          I connected someone in one of our international offices who had expressed an interest to me in a new role with an operational leader in the US who was thinking of adding someone to his team outside the US

–          I talked to our professional services team about a customer visit I’d recently done where we got really good feedback on the next release of a product but which also pointed out some needs for services that we hadn’t focused on yet

As a business leader, you are in a really good position to help Connect the Dots in a growing organization because you have a pretty unique view across the organization – and you tend to spend time with people internally across different functions and teams and offices.

I am not going to change my position that there are three primary roles, because I’m not sure that a CEO is required to Connect the Dots – hopefully that role can be delegated and replicated.  It’s something to think about, for sure.  But in the meantime, I like doing that and find it useful for me as well as the organization.

First in my series of posts around creating the best place to work  is to Surround yourself with the best and brightest.  This one is simple.  Build the best team you can possibly build…as you need it.

As a founder, you may be the best person at doing everything in your company, especially if you are a technical founder.  But as my long-time Board member at Return Path Greg Sands always says, when the organism grows, cells start to specialize.  Eventually, you need a liver and a brain.  Just like companies need a head of sales and a CFO (not to imply that Anita likes the occasional cocktail or that Jack likes math – turns out both like both).

How does this come into play as a CEO?

-Don’t be afraid to hire people better than you at their specialty – older, wiser, more experienced, more expensive

– Check references carefully – don’t get suckered in by resume or rolodex – some successful big company people don’t actually know how to do work or build a business, so you have to dig and find back-channel references

– Don’t overhire before you’re ready, but especially as a start-up, better to hire 3 months before you need the position, not 6 months too late

-Remember that you are the CEO.  Even if you hire very experienced people in specific roles, you have the best global view of everything going on in the company.  And you need to pay attention to people on your team and actively manage them, even experts who are older or wiser than you are

Surrounding yourself with the best and brightest can be daunting and even threatening to some CEOs.  But you have to do it to grow your business.  And you have to keep doing it as you keep growing your business (and your staff has to do the same!).

I was talking to a CEO the other day who believed it was “wrong” (literally, his word) to meet directly 1:1 with people in the organization who did not report to him.  I’ve heard from other CEOs in the past that they’re casual or informal or sporadic about this practice, but I’ve never heard someone articulate before that they actively stayed away from it.  The CEO in question’s feeling was that these meetings, which I call Skip-Level Meetings, disempowers managers.

I couldn’t disagree more.  I have found Skip-Level Meetings to be an indispensable part of my management and leadership routine and have done them for years.  If your culture is set up such that you as CEO can’t interact directly and regularly with people in your organization other than the 5-8 people who report to you, you are missing out on great opportunities to learn from and have an impact on those around you.

That said, there is an art to doing these meetings right, in ways that don’t disempower people or encourage chaos.  Some of these themes will echo other things I’ve written in recent posts like Moments of Truth and Scaling Me.  My five rules for doing Skip-Level Meetings are:

1. Make them predictable.  Have them on a regular schedule, whatever that is.  The schedule doesn’t have to be uniform across all these meetings.  I have some Skip-Levels that I do monthly, some quarterly, some once a year, some “whenever I am in town.”
   
2. Use a consistent format.  I always have a few questions I ask people in these meetings – things about their key initiatives, their people, their roadblocks, what I can do to help, what their POV is about the company direction and performance, how they are feeling about their role and growth.  I also expect that people will come with questions or topics for me.  If I have more meaty ad hoc topics, I’ll let the person know ahead of time.
   
3. Vary the location.  When I have regular Skip-Levels with a given person, I try to do the occasional one over a meal or drink to make it a little more social.  For remote check-ins, I now always do Skype or Videophone.
   
4. Do groups.  Sometimes group skip-levels are fun and really enlightening, either with a full team, or with a cross-section of skip-levels from other teams.  Watching people relate to each other gives you a really different view into team dynamics.
   
5. Close the loop.  I almost always check-in with the person’s manager BEFORE AND AFTER a Skip-Level.  Before, I ask what the issues are, if there is anything I should push on or ask.  After, I report back on the meeting, especially if there are things the person and I discussed that are out of scope for the person’s job or goals, so there are no surprises.

 I’m sure there are other things I do as well, but I can’t imagine running the company without this practice.  Doing it often and well EMPOWERS people in the company…I’d argue that managers who feel disempowered by it aren’t managers you necessarily want in your business unless you really run a command-and-control shop.

What Separates Good Teams from Bad Teams?

Every once in a while, I have a conversation that forces me to distill an idea to a sound bite – those frequently become blog posts.  Many happen with members of my team at Return Path, or my friend Matt on our Saturday morning runs, or my Dad or Mom, or Mariquita.  This one happened at dinner the other night with Mariquita and my in-laws Rick and Carmen.

The subject came up about managing a senior team, and different iterations of teams I’ve managed over the years.  And the specific question we posed was “What are the most significant characteristics that separate good teams from bad teams?”  Here’s where the conversation went…“I believe that 100% of the members of good teams can, 100% of the time”

1. Get outside of themselves.  They have no personal agenda, only the best interests of the company, in mind.  They make every effort to see issues on which they disagree from the opposing point of view
2. Understand the difference between fact and opinion.  As my friend Brad says, “The plural of anecdotes is not data.”  And as Winston Churchill said, “Facts are stubborn things.”  If everyone on a team not only understands what is a fact and what is not a fact, AND all team members are naturally curious to understand and root out all the relevant facts of an issue, that’s when the magic happens

Of course there are many other characteristics or checklists of characteristics that separate good teams from bad teams.  But these feel to me like pretty solid ones – at least a good starting point for a conversation around the conference room table.

Stamina

A couple years ago I had breakfast with Nick Mehta, my friend who runs the incredibly exciting Gainsight.  I think at the time I had been running Return Path for 15 years, and he was probably 5 years into his journey.  He said he wanted to run his company forever, and he asked me how I had developed the stamina to keep running Return Path as long as I had.  My off the cuff answer had three points, although writing them down afterwards yielded a couple more.  For entrepreneurs who love what they do, love running and building companies for the long haul, this is an important topic.  CEOs have to change their thinking as their businesses scale, or they will self implode!  What are five things you need to get comfortable with as your business scales in order to be in it for the long haul?

Get more comfortable with not every employee being a rock star.  When you have 5, 10, or even 100 employees, you need everyone to be firing on all cylinders at all times.  More than that, you want to hire “rock stars,” people you can see growing rapidly with their jobs.  As organizations get larger, though, not only is it impossible to staff them that way, it’s not desirable either.  One of the most influential books I’ve read on hiring over the years, Topgrading (review, buy), talks about only hiring A players, but hiring three kinds of A players:  people who are excellent at the job you’re hiring them for and may never grow into a new role; people who are excellent at the job you’re hiring them for and who are likely promotable over time; and people who are excellent at the job you’re hiring them for and are executive material.  Startup CEOs tend to focus on the third kind of hire for everyone.  Scaling CEOs recognize that you need a balance of all three once you stop growing 100% year over year, or even 50%.

Get more comfortable with people quitting.  This has been a tough one for me over the years, although I developed it out of necessity first (there’s only so much you can take personally!), with a philosophy to follow.  I used to take every single employee departure personally.  You are leaving MY company?  What’s wrong with you?  What’s wrong with me or the company?  Can I make a diving catch to save you from leaving?  The reality here about why people leave companies may be 10% about how competitive the war for talent has gotten in technology.  But it’s also 40% from each of two other factors.  First, it’s 40% that, as your organization grows and scales, it may not be the right environment for any given employee any more. Our first employee resigned because we had “gotten too big” when we had about 25 employees.  That happens a bit more these days!  But different people find a sweet spot in different sizes of company.  Second, it’s 40% that sometimes the right next step for someone to take in their career isn’t on offer at your company.  You may not have the right job for the person’s career trajectory if it’s already filled, with the incumbent unlikely to leave.  You may not have the right job for the person’s career trajectory at all if it’s highly specialized.  Or for employees earlier in their careers, it may just be valuable for them to work at another company so they can see the differences between two different types of workplace.

Get more comfortable with a whole bunch of entry level, younger employees who may be great people but won’t necessarily be your friends.  I started Return Path in my late 20s, and I was right at our average age.  It felt like everyone in the company was a peer in that sense, and that I could be friends with all of them.  Now I’m in my (still) mid-40s and am well beyond our average age, despite my high level of energy and of course my youthful appearance.  There was a time several years ago where I’d say things to myself or to someone on my team like “how come no one wants to hang out with me after work any more,” or “wow do I feel out of place at this happy hour – it’s really loud here.”  That’s all ok and normal.  Participate in office social events whenever you want to and as much as you can, but don’t expect to be the last man or woman standing at the end of the evening, and don’t expect that everyone in the room will want to have a drink with you.  No matter how approachable and informal you are, you’re still the CEO, and that office and title are bound to intimidate some people.

Get more comfortable with shifts in culture and differentiate them in your mind from shifts in values.  I wrote a lot about this a couple years ago in The Difference Between Culture and Values . To paraphrase from that post, an organization’s values shouldn’t change over time, but its culture – the expression of those values – necessarily changes with the passage of time and the growth of the company.  The most clear example I can come up with is about the value of transparency and the use case of firing someone.  When you have 10 employees, you can probably just explain to everyone why you fired Joe.  When you have 100 employees, it’s not a great idea to tell everyone why you fired Joe, although you might be ok if everyone finds out.  When you have 1,000 employees, telling everyone why you fired Joe invites a lawsuit from Joe and an expensive settlement on your part, although it’s probably ok and important if Joe’s team or key stakeholders comes to understand what happened.  Does that evolution mean you aren’t being true to your value of transparency?  No.  It just means that WHERE and HOW you are transparent needs to evolve as the company evolves.

• Get more comfortable with process.  This doesn’t mean you have to turn your nimble startup into a bureaucracy.  But a certain amount of process (more over time as the company scales) is a critical enabler of larger groups of people not only getting things done but getting the right things done, and it’s a critical enabler of the company’s financial health.  At some point, you and your CFO can’t go into a room for a day and do the annual budget by yourselves any more.  But you also can’t let each executive set a budget and just add them together.  At some point, you can’t approve every hire yourself.  But you also can’t let people hire whoever they want, and you can’t let some other single person approve all new hires either, since no one really has the cross-company view that you and maybe a couple of other senior executives has.  At some point, the expense policy of “use your best judgment and spend the company’s money as if it was your own” has to fit inside department T&E budgets, or it’s possible that everyone’s individual best judgments won’t be globally optimal and will cause you to miss your numbers.  Allow process to develop organically.  Be appropriately skeptical of things that smell like bureaucracy and challenge them, but don’t disallow them categorically.  Hire people who understand more sophisticated business process, but don’t let them run amok and make sure they are thoughtful about how and where they introduce process to the organization.

I bet there are 50 things that should be on this list, not 5.  Any others out there to share?