Book Short:  Blogging Alone?

I usually only blog about business books, but since I read Bowling Alone: The Collapse and Revival of American Community, by Robert Putnam, because of its connection to the topic of Internet community and social media, I’ll record some thoughts about and from it here.

It’s an interesting read, although a little long.  Putnam’s basic thesis is that America’s social capital — the things that have brought us physically and emotionally together as a country throughout much of the 20th century such as church, voting, and participation in civic organizations like the PTA or the Elks Club — are all severely on the decline.  The reasons in Putnam’s view are television (you knew all those re-runs of The Brady Bunch would eventually catch up to you), suburban sprawl, two-career families, and “generational values,” which is Putnam’s way of saying things like people in their 60s all read newspapers more than people in their 50s, who all read newspapers more than people in their 40s, etc.  He believes the decline is leading to things like worse schools, less safe neighborhoods, and poorer health.

The book does a good job laying out the decline in social capital with some really interesting and somewhat stunning numbers, but the book’s biggest shortcoming is that Putnam doesn’t do the work to determine causation.  I buy that there’s a correlation between less voting and less safe neighborhoods, for example, but the book doesn’t convince me that A caused B as opposed to B causing A, or C causing both A and B.  What I really wanted at the end of the book was for Putnam to go mano-a-mano with the Freakonomics guy for a couple hours.  Preferably in those big fake sumo suits.

The book was published in 2000, so probably written from 1997-1999, and therefore its treatment of the Internet was a little dated — so I found myself wanting more on that topic since so much of the social media revolution on the Internet is post-2004.  His basic view of the Internet is that it is in fact a bright spot in the decline of community, but that it’s changing the nature of communities.  Now instead of chatting with whoever is bowling in the next lane over at the Tuesday night bowling league on Main Street, we are in an online discussion group with other people who own 1973 BMW 2002 series cars, preferably the turbo-charged ones.  So the micro-communities of the Internet circa 2000 are more egalitarian (“on the Internet, no one knows you’re a dog”), but more narrow as well around interests and values.

What has social media done to Putnam’s theories in the last seven or eight years?  How have things like blogging, MySpace, LinkedIn, YouTube, and Photobucket changed our concept of community in America or in the world at large?  I welcome your comments on this and will write more about it in the future.

Book Short:  a Corporate Team of Rivals

One of the many things I have come to love about the Christmas holiday every year is that I get to go running in Washington DC.  Running the Monuments is one of the best runs in America.  Today, at my mother-in-law’s suggestion, I stopped i8n at the Lincoln Memorial mid-run and read his second inaugural address again (along with the Gettysburg Address).  I had just last week finished Doris Kearns Goodwin’s Team of Rivals:  The Political Genius of Abraham Lincoln, and while I wasn’t going to blog about it as it’s not a business book, it’s certainly a book about leadership from which any senior executive or CEO can derive lessons.

Derided by his political opponents as a “second-rate Illinois lawyer,” Lincoln, who arrived somewhat rapidly and unexpectedly on the national scene at a time of supreme crisis, obviously more than rose to the occasion and not only saved the nation and freed the slaves but also became one of the greatest political leaders of all time.  He clearly had his faults — probably at the top of the list not firing people soon enough like many of his incompetent Union Army generals — but the theme of the book is that he had as one of his greatest strengths the ability to co-opt most of his political rivals and get them to join his cabinet, effectively neutering them politically as well as showing a unity government to the people.

This stands in subtle but important contrast to George Washington, who filled his cabinet with men who were rivals to each other (Hamilton, Jefferson) but who never overtly challenged Washington himself.

Does that Team of Rivals concept — in either the Lincoln form or the Washington form — have a place in your business?  I’d say rarely in the Lincoln sense and more often in the Washington sense.

Lincoln, in order to be effective, didn’t have much of a choice.  Needing regional and philosophical representation on his cabinet at a time of national crisis, bringing Seward, Chase, and Bates on board was a smart move, however much a pain in the ass Chase ended up being.  There certainly could be times when corporate leadership calls for a representative executive team or even Board, for example in a massive merger with uncertain integration or in a scary turnaround.  But other than extreme circumstances like that, the Lincoln model is probably a recipe for weak, undermined leadership and heartache for the boss.

The Washington model is different and can be quite effective if managed closely.  One could argue that Washington didn’t manage the seething Hamilton and frothy Jefferson closely enough, but the reality is that the debates between the two of them in the founding days of our government, when well moderated by Washington, forged better national unity and just plain better results than had Washington had a cabinet made up of like-minded individuals.  As a CEO, I love hearing divergent opinion on my executive team.  That kind of discussion is challenging to manage — at least in our case we don’t have people at each other’s throats — but as long as you view your job as NOT to create compromises to appease all factions but instead to have the luxury of hearing multiple well articulated points of view as inputs to a decision you have to make, then you and your company end up with a far, far better result.

The Party's Over?

American party politics have had a few major realignments over the 220 years since we adopted our Constitution.  I took a class on this in school, but that was a long time ago, and I'll never remember all the details.  What I do remember is that they're somewhat chaotic.  And that they typically take several election cycles to take root.

I think we're in the middle of one now.  Arlen Specter's decision to become a Democrat is a particularly poignant example of it, though the fact that something like only 25% of the country now identifies with the Republican party is another.  With Specter, it's not that he changed his ideology — it's that his party changed its ideology.  Whether or not you view his switch as a cynical attempt to keep his job is irrelevant.  He has been a Republican for his whole public life of more than 40 years with a fairly consistent point of view and is a very popular public servant with his constituency at large, and now he believes he can't win a primary voted in mainly by party activists against Republican opponents. 

Something I read today – either the Journal or Politico – had a quote from a Republican hardliner that is further signifying the realignment:

South Carolina Senator Jim DeMint and welcome Mr. Specter's defection as an ideological cleansing. "I would rather have 30 Republicans in the Senate who really believe in principles of limited government, free markets, free people, than to have 60 that don't have a set of beliefs."

That doesn't say much for the future of the GOP now, does it?  That said, I think prognostications of a permanent Democratic majority are unfounded. If I remember my history correctly, a realignment occurs when one party gets too powerful and too big — its opponents are the ones who realign as a check and balance.  Examples range from the Anti-Federalists becoming the original Republicans in the early 19th century, to the rise of the Whig and then Republican Party in the mid 19th century, to the Roosevelt era in the mid 20th century, to the Reagan Revolution in the late 20th century.  American politics are streaky.  Parties usually have a stranglehold on at least one branch of government for long periods of time, then a realignment shakes things up for a while, then control switches.  With the Whigs/Republicans, once they settled down with the election of Lincoln, for example, the party dominated the Presidency for 80 years, winning 6 consecutive presidential elections, 11 of 13, and 14 of 18 from Lincoln up through Franklin Roosevelt. 

I guess my point is that Republicans as we know them today may be doomed, but Democrats shouldn't spend too much time dancing on their grave.  Realignments won't take 20 years to kick in any more.  We move too quickly, information is too freely available, and public opinion is fickle.

What's the lesson here for a business?  It's all about competition.  Having a commanding market share is a great thing, but it's unusual for it to last.  Smaller competitors attack when you least expect it.  They attack in ways that you pooh-pooh based on your perspective of the world.  And they can often combine with other smaller players, whether through M&A or just alliances, in ways that challenge a leader's hegemony.  They redefine the market — or the market redefines them.

So be mindful of market realignment — whether you are CEO of the Democratic Party or CEO of you.com, Inc.  Don't focus on what people have bought from you in the past, or why.  Focus on what they'll be buying in the future, and why.

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.

One of the things I’ve learned over the years is that as the organization scales, you have to be all-in, until you’re not.  What the heck does that mean?

It means that, other than confiding your indecision to a very small number of trusted advisors on a given issue, indecision is poison to the people around you and to the organization in general.  So even if you’re thinking of doing something new or different or making a tough call on something, you generally need to project confidence until you’ve made the call.

One example of this is around a decision to fire someone on the team, especially a senior executive.  Public indecision about this reminds me of years ago when George Steinbrenner owned the Yankees.  Every time he contemplated firing a manager, which was often, he was very public about it.  It turned the manager into a lame duck, ignored by players and mocked by the press.  No good for the manager or for the players, unhelpful for the team as a whole.  It’s the same in business.  Again, other than a small group of trusted advisors, your people have to have your full backing until the moment you decide to remove them.

Another example of this is a shift in strategy.  Strategy drives execution – meaning the course you chart translates into the goals and activities of all the other people in your organization.  Mobilizing the troops is hard enough in the first place, and it requires a tremendous amount of leadership expressing commitment.  If you’re contemplating a shift in strategy, which of course happens a lot in dynamic businesses, and you share your thinking and qualms broadly, you risk paralyzing the organization or redirecting activities and goals without intending to or without even knowing it.

Some people might look at this concept and cry “foul – what about Transparency?”  I don’t buy that.  As I wrote recently in The Difference Between Culture and Values, “When you are 10 people in a room, Transparency means you as CEO may feel compelled to share that you’re thinking about pivoting the product, collect everyone’s point of view on the subject, and make a decision together. When you are 100 people, you probably wouldn’t want to share that thinking with ALL until it’s more baked, you have more of a concrete direction in mind, and you’ve stress tested it with a smaller group, or you risk sending people off in a bunch of different directions without intending to do so. When you are 1,000 employees and public, you might not make that announcement to ALL until it’s orchestrated with your earnings call, but there may be hundreds of employees who know by then. A commitment to Transparency doesn’t mean always sharing everything in your head with everyone the minute it appears as a protean thought.  At 10 people, you can tell everyone why you had to fire Pat – they probably all know, anyway.  At 100 people, that’s unkind to Pat.  At 1,000, it invites a lawsuit.”

The Difference Between Culture and Values

This topic has been bugging me for a while, so I am going to use the writing of this post as a means of working through it. We have a great set of core values here at Return Path. And we also have a great corporate culture, as evidenced by our winning multiple employer of choice awards, including being Fortune Magazine’s #2 best medium-sized workplace in America.

But the two things are different, and they’re often confused. I hear statements all the time, both here and at other companies, like “you can’t do that — it’s not part of our culture,” “I like working there, because the culture is so great,” and “I hope our culture never changes.”  And those statements reveal the disconnect.

Here’s my stab at a definition.  Values guide decision-making and a sense of what’s important and what’s right.  Culture is the collection of business practices, processes, and interactions that make up the work environment.

A company’s values should never really change. They are the bedrock underneath the surface that will be there 10 or 100 years from now.  They are the uncompromising core principles that the company is willing to live and die by, the rules of the game. To pick one value, if you believe in Transparency one day, there’s no way the next day you decide that being Transparent is unimportant. Can a value be changed?  I guess, either a very little bit at a time, slowly like tectonic plates move, or in a sharp blow as if you deliberately took a jackhammer to stone and destroyed something permanently.  One example that comes to mind is that we added a value a couple years back called Think Global, Act Local, when we opened our first couple of international offices.  Or a startup that quickly becomes a huge company might need to modify a value around Scrappiness to make it about Efficiency.  Value changes are few and far between.

If a company’s values are its bedrock, then a company’s culture is the shifting landscape on top of it. Culture is the current embodiment of the values as the needs of the business dictate. Landscapes change over time — sometimes temporarily due to a change in seasons, sometimes permanently due to a storm or a landslide, sometimes even due to human events like commercial development or at the hand of a good gardener.

So what does it mean that culture is the current embodiment of the values as the needs of the business dictate?  Let’s go back to the value of Transparency. When you are 10 people in a room, Transparency means you as CEO may feel compelled to share that you’re thinking about pivoting the product, collect everyone’s point of view on the subject, and make a decision together. When you are 100 people, you probably wouldn’t want to share that thinking with ALL until it’s more baked, you have more of a concrete direction in mind, and you’ve stress tested it with a smaller group, or you risk sending people off in a bunch of different directions without intending to do so. When you are 1,000 employees and public, you might not make that announcement to ALL until it’s orchestrated with your earnings call, but there may be hundreds of employees who know by then. A commitment to Transparency doesn’t mean always sharing everything in your head with everyone the minute it appears as a protean thought.  At 10 people, you can tell everyone why you had to fire Pat – they probably all know, anyway.  At 100 people, that’s unkind to Pat.  At 1,000, it invites a lawsuit.

Or here’s another example.  Take Collaboration as a value.  I think most people would agree that collaboration managed well means that the right people in the organization are involved in producing a piece of work or making a decision, but that collaboration managed poorly means you’re constantly trying to seek consensus.  The culture needs to shift over time in order to make sure the proper safeguards are in place to prevent collaboration from turning into a big pot of consensus goo – and the safeguards required change as organizations scale.  In a small, founder-driven company, it often doesn’t matter as much if the boss makes the decisions.  The value of collaboration can feel like consensus, as they get to air their views and feel like they’re shaping a decision, even though in reality they might not be.  In a larger organization with a wider range of functional specialists managing their own pieces of the organization, the boss doesn’t usually make every major decision, though guys like Ellison, Benioff, Jobs, etc. would disagree with that.  But in order for collaboration to be effective, decisions need to be delegated and appropriate working groups need to be established to be clear on WHO is best equipped to collaborate, and to what extent.  Making these pronouncements could come as feeling very counter-cultural to someone used to having input, when in fact they’re just a new expression of the same value.

I believe that a business whose culture never evolves slowly dies.  Many companies are very dynamic by virtue of growth or scaling, or by being in very dynamic markets even if the company itself is stable in people or product. Even a stable company — think the local hardware store or barber shop — will die if it doesn’t adapt its way of doing business to match the changing norms and consumption patterns in society.

This doesn’t mean that a company’s culture can’t evolve to a point where some employees won’t feel comfortable there any longer. We lost our first employee on the grounds that we had “become too corporate” when we reached the robust size of 25 employees. I think we were the same company in principles that day as we had been when we were 10 people (and today when we are approaching 500), but I understood what that person meant.

My advice to leaders: Don’t cling to every aspect of the way your business works as you scale up. Stick to your core values, but recognize that you need to lead (or at least be ok with) the evolution of your culture, just as you would lead (or be ok with) the evolution of your product. But be sure you’re sticking to your values, and not compromising them just because the organization scales and work patterns need to change.  A leader’s job is to embody the values.  That impacts/produces/guides culture.  But only the foolhardy leaders think they can control culture.

My advice to employees: Distinguish between values and culture if you don’t like something you see going on at work. If it’s a breach of values, you should feel very free to wave your arms and cry foul. But if it’s a shifting of the way work gets done within the company’s values system, give a second thought to how you complain about it before you do so, though note that people can always interpret the same value in different ways.  If you believe in your company’s values, that may be a harder fit to find and therefore more important than getting comfortable with the way those values show up.

Note:  I started writing this by talking about the foundation of a house vs. the house itself, or the house itself vs. the furniture inside it.  That may be a more useful analogy for you.  But hopefully you get the idea.

Book Short:  Continuing to make “sustainability” a mainstream business topic

The Big Pivot: Radically Practical Strategies for a Hotter, Scarcer, and More Open World, by my friend Andrew Winston, is a great book.  It just got awarded one of the Top 10 business books of 2014 by Strategy+Business, which is a great honor.

Andrew builds nicely on his first book, Green to Gold:  How Smart Companies Use Environmental Strategy to Innovate, Create Value, and Build Competitive Advantage (post, book link) (and second book, which I didn’t review, Green Recovery), as I said in my review of Green to Gold, to bring:

the theoretical and scientific to the practical and treat sustainability as the corporate world must treat it in order to adopt it as a mainstream practice — as a driver of capitalistic profit and competitive advantage.

Andrew’s central thesis, with plenty of proof points in the book for our planet of 7 Billion people, rapidly heading to 9-10 Billion, is this:

Whether you take a purely fiscal view of these challenges or look through a human-focused lens, one thing is clear: we’ve passed the economic tipping point. A weakening of the pillars of our planetary infrastructure— a stable climate, clean air and water, healthy biodiversity, and abundant resources— is costing business real money. It’s not some futuristic scenario and model to debate, but reality now, and it threatens our ability to sustain an expanding global economy… If this hotter, scarcer, more transparent, and unpredictable world is the new normal, then how must companies act to ensure a prosperous future for all, including themselves?

Andrew’s writing is accessible and colorful.  The book is full of useful analogies and metaphors like this one:

Climate can also seem easy to write off because the warming numbers don’t sound scary. A couple degrees warmer may sound pleasant, but we’re not really talking about going from 75 to 77 degrees Fahrenheit on a nice spring day. As many others have pointed out, the right metaphor is a fever. Take your core body temperature up one degree, and you don’t feel so great. Five degrees, and you’re sick as a dog. Ten degrees, and you’re dead.

The book also does a really nice job of looking at the externalities of climate change in a different way.  Not the usual “I can pollute, because there’s no cost to me to doing so,” but more along the lines of “If I had to pay for all the natural resources my business consumes, I would treat them differently.”

Some of Andrew’s points are good but general and maybe better made elsewhere (like the problems of short-termism on Wall Street), but overall, this book is a great think piece for all business leaders, especially in businesses that consume a lot of natural resources, around how to make the challenge of climate change work for your business, not against it.

Two things occurred to me during my read of The Big Pivot that I think are worth sharing for the people in my life who still don’t believe climate change is real or threatening.  The first is Y2K.  Remember the potentially cataclysmic circumstance where mission critical systems all around the world were going to go haywire at midnight at the turn of the millennium?  The conventional wisdom on why nothing major went wrong is that society did enough work ahead of time to prevent it, even though the outcomes weren’t clear and no one system problem alone would have been an issue.  I was thinking about this during the book…and then Andrew mentioned it explicitly towards the end.

The second is something I read several years ago in my personal news bible, The Economist.  I couldn’t find the exact quote online just now, but it was something to the effect of “Even if you don’t believe man created climate change, or that climate change is real and imperiling to humanity and can be fixed by man, the risks of climate change are so great, the potential consequences so dire, and the path to solve the problem so lengthy and complex and global…it’s worth investing in that solution now.”

Let’s all pivot towards that, shall we?  If you want to download the introduction to the book for free, you can find it on Andrew’s web site.  Or for a three-minute version of the story, you can watch this whiteboard animation on YouTube.

Book Short:  Scrum ptious 

I just finished reading Scrum: The Art of Doing Twice the Work in Half the Time, by Jeff Sutherland and JJ Sutherland. This reading was in anticipation of an Agile Facilitation training my executive team and I are going through next week, as part of Return Path’s  Agile Everywhere initiative. But it’s a book I should’ve read along time ago, and a book that I enjoyed.

Sutherland gets credit for creating the agile framework and bringing the concept scrum to software development over 20 years ago. The book very clearly lays out not just the color behind the creation of the framework, and the central tenets of practice again, but also clear and simple illustrations of its value and benefits.  And any book that employs the Fibonacci series and includes Theodore Roosevelt’s “Man in the Arena” quote — my all-time favorite — is off to a good start by me.

I’ve always appreciated a lot of the underlying philosophy of Agile, such as regularly checking on projects, course correcting in response to feedback from customers or other stakeholders, and working hard to remove any impediments to progress in real time.

One of the author’s most poignant points is that “multitasking makes you stupid.”  I hadn’t focused in the past how agile allows you to clear away context shifts to focus on one task at a time, but that’s another great take away from the book.

Our Agile Everywhere initiative, which is designed to improve productivity across the organization, as well as increase accountability through transparency, is even more critical in my view after having read this book.

The thing that I am left struggling with, which is still very much a work in progress for us, and hopefully something that we will address more head on in our training next week, is the application of the agile framework to teams that are not involved in the production of a tangible work product, such as executive or other leadership teams.  That is something that our Agile Everywhere deployment team has developed a theory about, but it still hasn’t entirely sunk in for me.

I can’t wait for next week’s training session!  If you have any experience applying the agile framework to different types of teams in your company I’d love to hear more about it in the Comments.

Book Short: Faster Than The Blink of an Eye

Michael Lewis is one of those authors for whom my general point of view is “read whatever he writes.” Flash Boys: A Wall Street Revolt  was no exception.  It’s a book about the high-frequency trading business, how a difference in microseconds can make a difference, and how the complexity of trading has led to enough confusion that virtually no one on Wall Street actually understands how it works any more.

I am a capitalist through and through, and I never begrudge Wall Street for making money, even though I do have moments where I doubt the amount of value that finance creates relative to the amount of income they swallow up.  However, that all goes out the window when there is evidence that some pocket of Wall Street isn’t playing by the rules.  I define “the rules” as either the law, or as something more like “a basic sense of morality and fairness.”

Some of what has been going on in the high-frequency trading business, as Lewis describes in this book, may or may not be legal (let’s assume it is), but is almost certainly not following a basic sense of morality and fairness.  It’s worth noting that I am purely going off what Lewis wrote in the book, so to the extent that his research is incomplete or his writing is misleading, I am happy to retract that statement.  But based on what I read, I’d challenge some of the people in the HFT business to defend what they’re doing publicly, to their mothers or to their own clients.  That’s the ultimate test of morality or fairness.

It’s amazing to me that this topic hasn’t gotten more play in the media or with regulators.  Maybe it’s just too complicated for anyone to understand or to articulate.  In any event, even though not strictly a business book, it’s fascinating and worth a read, as I think all Michael Lewis books are.

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.

Return Path’s Newest Board Member: Jeff Epstein

I’ve written before about how much I love my Board. Well, I’m pleased to announce I have a new reason to love it – today, I’m officially welcoming Jeff Epstein to the Return Path Board of Directors. He is joining an all-star cast that includes Greg Sands, Fred Wilson, Brad Feld, Scott Weiss and Scott Petry.

I first met Jeff back in 2000 when, as CFO of DoubleClick, he and DoubleClick CEO Kevin Ryan agreed to invest in Return Path as our first institutional investor, along with Flatiron Partners.  He is one of the few people who have seen the company grow from its infancy to today.  Jeff has been a formal advisor to the company for more than a year, and he recently agreed to join as a director.

Jeff has all the qualities that make for an awesome board member and he’s already been an influential voice with uncommon insight and an impressive background that complements the rest of our board. As CFO of Oracle Jeff helped guide one of the world’s preeminent technology companies. He’s also served as CFO for large private and public companies including DoubleClick, King World Productions, and Neilsen’s Media Measurement and Information Group, and is a member of the boards of Priceline.com, Kaiser Permanente, Shutterstock, and the Management Board of the Stanford Graduate School of Business. Jeff is currently a partner at Bessemer Venture Partners and a senior advisor at Oak Hill Capital.

Building and managing a board of directors is one of the key functions of a CEO, and the entire Return Path team benefits from a close relationship with great industry leaders. Jeff’s appointment is a perfect example. He’s steered successful organizations through many of the same decisions and challenges that we’re facing. He evaluates issues from multiple points of view – as a senior executive, as a board member, as an investor. And he’s not quiet. On our board, that’s essential. We’re a group of strong personalities—we challenge ideas, we analyze everything, and our views don’t always have to agree.

I’ve said that one secret to running an effective board is to ask for members’ opinions only when you want them. In Jeff’s case I definitely want them. So, on behalf of the board and the entire team at Return Path, Jeff, welcome!