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

Book Short:  Steve Jobs and Lessons for CEOs and Founders

First, if you work in the internet, grew up during the rise of the PC, or are an avid consumer of Apple products, read the Walter Isaacson biography of Steve Jobs (book, kindle).  It’s long but well worth it.

I know much has been written about the subject and the book, so I won’t be long or formal, but here are the things that struck me from my perspective as a founder and CEO, many taken from specific passages from the book:

• In the annals of innovation, new ideas are only part of the equation. Execution is just as important.  Man is that ever true.  I’ve come up with some ideas over the years at Return Path, but hardly a majority or even a plurality of them.  But I think of myself as innovative because I’ve led the organization to execute them.  I also think innovation has as much to do with how work gets done as it does what work gets done.

• There were some upsides to Jobs’s demanding and wounding behavior. People who were not crushed ended up being stronger. They did better work, out of both fear and an eagerness to please.  I guess that’s an upside.  But only in a dysfunctional sort of way.

• When one reporter asked him immediately afterward why the (NeXT) machine was going to be so late, Jobs replied, “It’s not late. It’s five years ahead of its time.”  Amen to that.  Sometimes product deadlines are artificial and silly.  There’s another great related quote (I forget where it’s from) that goes something like “The future is here…it’s just not evenly distributed yet.”  New releases can be about delivering the future for the first time…or about distributing it more broadly.

• People who know what they’re talking about don’t need PowerPoint.”  Amen.  See Powerpointless.

• The mark of an innovative company is not only that it comes up with new ideas first, but also that it knows how to leapfrog when it finds itself behind.  This is critical.  You can’t always be first in everything.  But ultimately, if you’re a good company, you can figure out how to recover when you’re not first.  Exhibit A:  Microsoft.

• In order to institutionalize the lessons that he and his team were learning, Jobs started an in-house center called Apple University. He hired Joel Podolny, who was dean of the Yale School of Management, to compile a series of case studies analyzing important decisions the company had made, including the switch to the Intel microprocessor and the decision to open the Apple Stores. Top executives spent time teaching the cases to new employees, so that the Apple style of decision making would be embedded in the culture.  This is one of the most emotionally intelligent things Jobs did, if you just read his actions in the book and know nothing else.  Love the style or hate it – teaching it to the company reinforces a strong and consistent culture.

• Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!’” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.  There’s always a tension between listening TO customers and innovating FOR them.  Great companies have to do both, and know when to do which.

• What drove me? I think most creative people want to express appreciation for being able to take advantage of the work that’s been done by others before us. I didn’t invent the language or mathematics I use. I make little of my own food, none of my own clothes. Everything I do depends on other members of our species and the shoulders that we stand on. And a lot of us want to contribute something back to our species and to add something to the flow. It’s about trying to express something in the only way that most of us know how—because we can’t write Bob Dylan songs or Tom Stoppard plays. We try to use the talents we do have to express our deep feelings, to show our appreciation of all the contributions that came before us, and to add something to that flow. That’s what has driven me.  This is perhaps one of the best explanations I’ve ever heard of how creativity can be applied to non-creative (e.g., most business) jobs.  I love this.

My board member Scott Weiss wrote a great post about the book as well and drew his own CEO lessons from it – also worth a read here.

Appropos of that, both Scott and I found out about Steve Jobs’ death at a Return Path Board dinner.  Fred broke the news when he saw it on his phone, and we had a moment of silence.  It was about as good a group as you can expect to be with upon hearing the news that an industry pioneer and icon has left us.  Here’s to you, Steve.  You may or may not have been a management role model, but your pursuit of perfection worked out well for your customers, and most important, you certainly had as much of an impact on society as just about anyone in business (or maybe all walks of life) that I can think of.

Book Short:  Like Reading a Good Speech

Leaders Eat Last, by Simon Sinek, is a self-described “polemic” that reads like some of the author’s famous TED talks and other speeches in that it’s punchy, full of interesting stories, has some attempted basis in scientific fact like Gladwell, and wanders around a bit.  That said, I enjoyed the book, and it hit on a number of themes in which I am a big believer – and it extended and shaped my view on a couple of them.

Sinek’s central concept in the book is the Circle of Safety, which is his way of saying that when people feel safe, they are at their best and healthiest.  Applied to workplaces, this isn’t far off from Lencioni’s concept of the trust foundational layer in his outstanding book, Five Dysfunctions of a Team.  His stories and examples about the kinds of things that create a Circle of Safety at work (and the kinds of things that destroy them) were very poignant.  Some of his points about how leaders set the tone and “eat last,” both literally and figuratively, are solid.  But his most interesting vignettes are the ones about how spending time face-to-face in person with people as opposed to virtually are incredibly important aspects of creating trust and bringing humanity to leadership.

My favorite one-liner from the book, which builds on the above point and extends it to a corporate philosophy of people first, customer second, shareholders third (which I have espoused at Return Path for almost 15 years now) is

Customers will never love a company unless employees love it first.

A couple of Sinek’s speeches that are worth watching are the one based on this book, also called Leaders Eat Last, and a much shorter one called How Great Leaders Inspire Action.

Bottom line:  this is a rambly book, but the nuggets of wisdom in it are probably worth the exercise of having to find them and figure out how to connect them (or not connect them).

Thanks to my fellow NYC CEO Seth Besmertnik for giving me this book as well as the links to Sinek’s speeches.

Book Short:  Choose Voice!

I took a couple days off last week and decided to re-read two old favorites.  One –Ayn Rand’s The Fountainhead — my fourth reading — will take me a little longer to process and figure out if there’s a good intersection with the blog.  One would think so with entrepreneurship as the topic, but my head still hurts from all the objectivism.  The second — Exit, Voice, and Loyalty, by Albert O. Hirschman — is today’s topic.

I can’t remember when I first read Exit, Voice, and Loyalty.  It was either in senior year of high school Economics or Government; or in freshman year of college Political Philosophy.  Either way, it was a long time ago, and for some reason, some of the core messages of this quirkly little 125 page political/economic philosophy book have stayed with me over the years.  I remembered the book incorrectly as a book about political systems, and I think it was born consciously in the wake of Eugene McCarthy’s somewhat revolutionary challenge to a sitting President Johnson for the Democratic Party nomination in 1968.  But the book is actually about business; it’s just about businesses and their customers, not corporations as social structures (the latter being more of an interest to me).  Written by an academic economist (I think), the book has its share of gratuitous demonstrative graphs, 2×2 matrices, and SAT words.  But its central premise is a gem for anyone who runs an organization of any size.

The central premise is that there are really two paths by which one can express dissatisfaction with a temporary, curable lapse in an organization:  exit (bailing), or voice (trying to fix what’s wrong from within).  The third key element, Loyalty, is less a path in and of itself but more an agent that “holds exit at bay and activates voice.”

You need to read the book and apply it to your own circumstances to really get into it, but for me, it’s all about breeding loyalty as a means of making voice the path of least resistance, even when exit is a freely available option (few of us run totalitarian states or monopolies, after all).  That to me is the definition of a successful enterprise, both internally and externally.

With your customers:  make your product so irresistible, and make your customer service so deep, that your customers feel an obligation to help you fix what they perceive to be wrong with your product first, rather than simply complain about price or flee to a competitor.

With your employees:  make your company the best possible place you can think of to work so that even in as ridiculously fluid a job market as we live in, your employees will come to their manager, their department head, the head of HR, or you as leader to tell you when they’re unhappy instead of just leaving, or worse, sulking.

With your company (you as employee):  make yourself indispensible to the organization and do such a great job that if things go wrong with your performance or with your role, your manager’s loyalty to you leads him or her to give you open feedback and coach you to success rather than unceremoniously show you the door.

Ok, this wasn’t such a short book short — probably the longest I’ve ever written in this blog, and certainly the highest ratio of short:actual book.  But if you’re up for a serious academic framework (quasi-business but not exclusively) to apply to your management techniques, this short 1970 book is as valid today as when it was written.  Thanks to David Ramert (I am pretty sure I read it in high school) for introducing it to me way back when!

In Search of Automated Relevance

A bunch of us had a free form meeting last week that started out as an Email Summit focused on protocols and ended up, as Brad put it, with us rolling around in the mud of a much broader and amorphous Messaging Summit.  The participants (and some of their posts on the subject) in addition to me were Fred Wilson (pre, post), Brad Feld,  Phil Hollows, Tom Evslin (pre, post), and Jeff Pulver (pre, post).  And the discussion to some extent was inspired by and commented on Saul Hansell’s article in the New York Times about “Inbox 2.0” and how Yahoo, Google, and others are trying to make email a more relevant application in today’s world; and Chad Lorenz’s article in Slate called “The Death of Email” (this must be the 923rd article with that headline in the last 36 months) which talks about how email is transitioning to a key part of the online communications mix instead of the epicenter of online communications.

Ok, phew, that’s all the background. 

With everyone else’s commentary on this subject already logged, most of which I agree with, I’ll add a different $0.02.  The buzzword of the day in email marketing is “relevance.”  So why can’t anyone figure out how to make an email client, or any messaging platform for that matter, that starts with that as the premise, even for 1:1 communications?  I think about messaging relevance from two perspectives:  the content, and the channel.

Content.  In terms of the content of a message, I think of relevance as the combination of Relationship and Context.  The relationship is all about my connection to you.  Are you a friend, a friend of a friend, or someone I don’t know that’s trying to burrow your way onto my agenda for the day?  Are you a business that I know and trust, are you a carefully screened and targeted offer coming from an affiliate of a business I trust, or are you a spammer? 

But as important as the relationship is to the relevance of your message to me, the context is equally important.  Let’s take Brad as an example.  I know him in two distinct contexts:  as one of my venture investors, and as an occasional running partner.  A message from Brad (a trusted relationship) means very different things to me depending on its context.  One might be much more relevant than the other at any moment in my life.

Channel.  The channel through which I send or receive a message has an increasing amount to do with relevance as well.  As with content, I think of channel relevance as the combination of two things –  device, and technology.  For me, the device is limited to three things, two with heavy overlap.  The first is a fixed phone line – work or home (I still think cell service in this country leaves a lot to be desired).  The second is a mobile device, which could mean voice but could also mean data.  The third is a computer, whether desktop or laptop.  In terms of technology, the list is growing by the day.  Voice call, email, IM, Skype, text message, social network messaging, and on and on.

So what  do I mean about channel relevance?  Sometimes, I want to send a message by email from my smartphone.  Sometimes I want to send a text message.  Sometimes I want to make a phone call or just leave a voicemail.  Sometimes I even want to blog or Twitter.  I have yet to desire to send a message in Facebook, but I do sometimes via LinkedIn, so I’m sure I’ll get there.  Same goes for the receiving side.  Sometimes I want to read an email on my handheld.  Sometimes a text message does the job, etc.  Which channel and device I am interested in depends to some extent on the content of the message, per above, but sometimes it depends on what I’m doing and where I am.

So what?  Starting to feel complex?  It should be.  It is.  We all adjusted nicely when we added email to our lives 10 years ago.  It added some communication overhead, but it took the place of some long form paper letters and some phone calls as well.  Now that we seem to be adding new messaging channels every couple weeks, it’s becoming increasingly difficult to get the relevance right.  Overlaying Content (Relationship and Context) with Channel (Device and Technology) creates a matrix that’s very difficult to navigate.

How do we get to a better place?  Technology has to step in and save the day here.  One of the big conclusions from our meeting was that no users care about or even know about the protocol – they just care about the client they interact with.  Where’s the ultra flexible client that allows me to combine all these different channels, on different devices?  Not a one-size-fits-all unified messaging service, but something that I can direct as I see fit?  There are glimmers of hope out there – Gmail integrating IM and email…Simulscribe letting me read my voicemail as an email…Twitter allowing me to input via email, SMS, or web…even good old eFax emailing me a fax – but these just deal with two or three cells in an n-dimensional matrix.

As our CTO Andy Sautins says, software can do anything if it’s designed thoughtfully and if you have enough talent and time to write and test it.  So I believe this “messaging client panacea” could exist if someone put his or her mind to it.  One of the big questions I have about this software is whether or not relevance can be automated, to borrow a phrase from Stephanie Miller, our head of consulting.  Sure, there is a ton of data to mine – but is there ever enough?  Can a piece of software figure out on its own that I want to get a message from Brad about “running” (whatever channel it comes in on) as a text message on my smartphone if we’re talking about running together the next day, but otherwise as an RSS feed in the same folder as the posts from his running blog, but a voicemail from Brad about “running the company” (again, regardless of how he sends it) as an email automatically sorted to the top of my inbox?  Or do I have to undertake an unmanageable amount of preference setting to get the software to behave the way I want it to behave?  And oh by the way, should Brad have any say over how I receive the message, or do I have all the control?  And does the latter question depend on whether Brad is a person or a company?

What does this mean for marketers?  That’s the $64,000 question.  I’m not sure if truly Automated Relevance is even an option today, but marketers can do their best to optimize all four components of my relevance equation:  content via relationship and context, and channel via device and technology.  A cocktail of permission, deep behavioral analysis, segmentation, smart targeting, and a simple but robust preference center probably gets you close enough.  Better software that works across channels with built-in analytics – and a properly sized and whip smart marketing team – should get you the rest of the way there.  But technology and practices are both a ways off from truly automated relevance today.

I hope this hasn’t been too much rolling around in the mud for you.  All thoughts and comments (into my fancy new commenting system, Intense Debate) are welcome!

Book Short:  The Religion of Heresy

At the end of Tribes: We Need You to Lead Us, Seth Godin’s new book, Seth says this:

I’m going to get a lot of flak from people about what you just read. People might say that it’s too disorganized or not practical enough or that I require you to do too much work to actually accomplsh anything. That’s ok.

He’s kind of right. The book is a little breezy and meanders around, just like riffing with Seth. It’s not practical in the sense that if the entire world operated this way in the extreme, we’d have serious problems. But the fact that he requires you to do “too much work to actually accomplish anything” is part of the brilliance of his message.

This was Seth’s best book in years, mostly because it is fresh. It is not a rant about marketing; it is a wonderfully succinct look at how we as a society are rallying and organizing around causes, campaigns, companies, and collective beliefs. It’s not about the Internet, though its principles are easily implemented and amplified using online tools. It’s not a how-to guide to being a fancy corporate leader, but it’s one of the most pointed descriptions of the ethos of a certain type of leader (the upstart, or as Seth says, the heretic). It’s not about a particular revolution; it’s about how mini-revolutions are becoming the norm these days.

Tribes is short, inspirational, and pure Seth. Though quite different in its nature and mission, it really evoked for me Mark Penn’s Microtrends (post, link) — a study of larger tribes and heretics in contemporary America.

A listing of Seth’s books over the years follows:

• Permission Marketing — the original

• Unleashing the Ideavirus — good follow up on viral marketing

• Really Bad Powerpoint (ebook) — the standard for not being boring when you present

• The Big Red Fez — the standard on designing great web sites

• Survival Is Not Enough — motivating about being a nimble company

• Free Prize Inside — on being buzzworthy

• Purple Cow — on being remarkable, a great book

• The Big Moo — good follow-up with remarkable examples

• Small Is the New Big — not worth it if you read his blog

• All Marketers Are Liars — fine, a little “more of the same”

• The Dip — haven’t read it

• Meatball Sundae — haven’t read it

• Tribes — see above

Book Short:  Which Runs Faster, You or Your Company?

Leading at the Speed of Growth, by Katherine Catlin at the Kauffman Center for Entrepreneurial Leadership is a must read for any entrepreneur or CEO of a growth company.  It’s one of the best books I’ve ever read targeted to that audience – its content is great, its format is a page-turner, and it’s concise and to the point.

The authors take you through three stages of a growth company’s lifestyle (Initial Growth, Rapid Growth, and Continuous Growth) and describe the “how to’s” of the transition into each stage:  how you know it’s coming, how to behave in the new stage, how to leave the old stage behind.

I didn’t realize it when I started reading the book, but Brad had one of the quotes on the back cover that says it all:  “There are business books about starting a company, but they tend to deal with the mechanics of business plans and financing.  Then there are books about ‘how to be the CEO of a Fortune 500 company.’  This is the first book I’ve seen that details the role of the CEO of a small but growing company.”  Thanks to my colleague George Bilbrey for pointing this one out to me.

UPDATE:  Brad corrects me and says that I should mention Jana Matthews, who co-wrote the book with Katherine Catlin and is actually the Kauffman Center person of the duo.

Book Short: Not About Going With The…

Flow: The Psychology of Optimal Experience, by Mihaly Csikszentmihalyi (book, Kindle), was a great read and a nice change from either strictly business books or my regular fiction/non-fiction reading. It’s basically about the process of achieving happiness through control over one’s inner life, but it’s far from a self-help book. It’s almost more of practical psychology deep dive into what brings about happiness and peak performance – a state the author calls Flow but others have called other things over time, like being “in the zone.”

The author talks about achieving this control as synonymous with the enviable ability to persevere despite obstacles and setbacks and transform hopeless situations into challenges to be overcome, just through the force of personality. This ability comes directly from ways to order consciousness so as to be in control of feelings and thoughts. The normal entropy/chaos of the mind is the enemy. There were a few key moments or takeaways in the book for me.

1. When one’s experience is most positive – when one is achieving Flow – people cite the following conditions in this order of importance:

– Confront tasks we have a chance of completing

– Able to concentrate

– Concentration is possible because the task has clear goals and…

– …provides immediate feedback

– Act with a deep but effortless involvement that removes from awareness the worries and frustrations of everyday life

– Exercise a sense of control over actions

– Concern for the self disappears, yet paradoxically the sense of self emerges stronger after the experience is over

2. Becoming more Autotelic – learning how to make experiences ends in and of themselves – coming from the Greek words for “self” and “goal,” this concept is savoring a given activity for its own sake, NOT for its consequences and is a key to achieving Flow. Whether you create a mental construct around beating a personal record, doing math or pattern matching in your head, or something else, being able to focus enough energy on the task at hand and not be distracted by the world around (present or future) is key. It’s a little like what I wrote a few months ago about how achieving mental discipline in the small areas of one’s life can lead to much greater things by building confidence and clearing mental clutter.

3. The concept of the “Flow channel” – as skill increases, challenges must also increase proportionally in order for us to continue learning, growing, and excelling – and achieving Flow.

4. Transformational coping is the ability to cheat chaos – transforming a hopeless situation into a new flow activity that can be controlled and enjoyed and emerge stronger from…

– Unselfconscious self-assurance – ego absent but confident, not at odds with environment but part of it

– Focusing attention on the world – looking outward, not inward

– The discovery of new solutions – being able to perceive unexpected opportunities as a result

5. How to develop the autotelic self

– Set clear goals

– Become immersed in the activity

– Pay attention to what’s happening

– Learn to enjoy immediate experience

The book reminded me of a couple other things I’ve read, in case any of these resonate with you. First, Tim Gallwey’s “Inner Game” books where he talks about “relaxed concentration,” basically the Flow state, and the inner conflict between focus on the event and focus on the consequences, between mental chaos and mental discipline, personified as Self 1 and Self 2. If you haven’t read these, any are good and give you the general idea, depending on which piques your interest the most: The Inner Game of Golf (book, Kindle), The Inner Game of Tennis (book only), and The Inner Game of Work (book, Kindle). Second, David Allen’s Getting Things Done theory about how a clear, uncluttered mind can do its best work. As Flow says, achieving an ordered mental condition is difficult – unless a person knows how to give order to his or her thoughts, attention will be attracted to whatever is most problematic at the moment.

I’m not sure this book short does the book justice. It’s pretty complex and is rich with examples, but Flow (book, Kindle) is well worth a read if you’re into the theory of self control leading to better results and more happiness in life. Thanks to my friend Jonathan Shapiro for this book.

Half the Benefit is in the Preparation

This past week, we had what has become an annual tradition for us – a two-day Board meeting that’s Board and senior management (usually offsite, not this year to keep costs down) and geared to recapping the prior year and planning out 2009 together.  Since we are now two companies, we did two of them back-to-back, one for Authentic Response and the other for Return Path.

It’s a little exhausting to do these meetings, and it’s 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 off the high dive for another year.

The most exhausting part is probably the preparation for the meetings.  We probably send out over 400 pages of material in advance – binders, tabs, the works.  It’s the only eco-unfriendly Board packet of the year.  It feels like the old days in management consulting.  It takes days of intense preparation — meetings, spreadsheets, powerpoints, occasionally even some soul searching — to get the books right.  And then, once those are out (the week before the meeting), we spend almost as much time getting the presentations down for the actual meeting, since presenting 400 pages of material that people have already read is completely useless.

By the end of the meetings, we’re in good shape for the next year.  But before the meetings have even started, we’ve gotten a huge percentage of the benefit out of the process.  Pulling materials together is one thing, but figuring out how to craft the overall story (then each piece of it in 10-15 minutes or less) for a semi-external audience is something entirely different.  That’s where the rubber meets the road and where good executives are able to step back; remember what the core drivers and critical success factors are; separate the laundry list of tactics from the kernel that includes strategy, development of competitive advantage, and value creation; and then articulate it quickly, crisply, and convincingly. 

I’m incredibly proud of how both management teams drove the process this year – and I’m charged up for a great 2009 (economy be damned!).

Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.

Book Short: The Anti-Level-5 Leader

The Five Temptations of a CEO, another short leadership fable in a series by Patrick Lencioni, wasn’t as meaningful to me as the last one I read, The Four Obsessions of an Extraordinary Executive (post, link), but it wasn’t bad and was also a quick read.

The book to me was the 30 minute version of all the Level-5 Leadership stuff that Collins wrote about in Good to Great and Built to Last. All that said, it was a good quick read and a reminder of what not to do. The temptations are things that most CEOs I’ve ever known (present company very much included) have at least succumbed to at one point or another in their career. That said, you as a CEO should quit or be fired if you have them in earnest, so hopefully if you do have them, you recognize it and have them in diminishing quantities with experience, and hopefully not all at once:

– The temptation to be concerned about his or her image above company results

– The temptation to want to be popular with his or her direct reports above holding them accountable for results

– The temptation to ensure that decisions are correct, even if that means not making a decision on limited information when one is needed

– The temptation to find harmony on one’s staff rather than have productive conflict, discussion, and debate

– The temptation to avoid vulnerability and trust in one’s staff

I’m still going to read the others in Lencioni’s series as well. They may not be the best business books ever written, but they’re solid B/B+s, and they’re short and simple, which few business books are and all should be!