Book Short:  Wither the Team

I have one or two more to go, which I’ll tackle in due course and am looking forward to.

Holiday Cards c. 2007

Every year, I get a daily flood of business holiday cards on my desk in the second half of December. Some are nice and have notes from people with whom we do business – clients, vendors, partners, and the like. Some are kind of random, and it takes me a while to even figure out who they are from. Occasionally some even come in with no mark identifying from whence they came other than an illegible signature.

And every year, I receive one or two email cards instead of print & post cards, some apologetic about the medium. Until this year.

I think I’ve received about 10-15 cards by email this month. None with an apology. All with the same quality of art/creative as printed cards. It’s great! A good use of the email channel…much less cost…easier overhead for distribution…and of course better for the environment.

I wonder what made 2007 the tipping year for this.

Book Short:  Bringing it on Home

Book Short:  On The Same Page

Being on the same page with your team, or your whole company for that matter, is a key to success in business.  The Four Obsessions of an Extraordinary Executive, by Patrick Lencioni, espouses this notion and boils down the role of the CEO to four points:

1. Build and maintain a cohesive leadership team
2. Create organizational clarity
3. Overcommunicate organizational clarity
4. Reinforce organizational clarity through human systems

Those four points sound as boring as bread, but the book is anything but.  The book’s style is easy and breezy — business fiction.  One of the most poignant moments for me was when the book’s “other CEO” (the one that doesn’t “get it”) reflects that he “didn’t go into business to referee executive team meetings and delivery employee orientation…he loved strategy and competition.”  Being a CEO is a dynamic job that changes tremendously as the organization grows.  This book is a great handbook for anyone transitioning out of the startup phase, or for anyone managing a larger organization.

I haven’t read the author’s other books (this is one in a series), but I will soon!

New Del.icio.us for: Tag

As usual the laggard behind Fred and Brad, I just set up a for:mattblumberg tag on del.icio.us.  Feel free to tag away for me!  If you don’t know what this means, you can read either of their postings about it here or here.

The Advantage: Why Organizational Health Trumps Everything Else In Business is Patrick Lencioni’s newest book.  Unlike most or all of his other books (see the end of this post for the listing), this one is not a fable, although his writing style remains very quick and accessible.

I liked this book a lot.  First, the beginning section is a bit of a recap of his Five Dysfunctions of a Team which I think was his best book.  And the ending section is a recap of his Death by Meeting, another really good one.  The middle sections of the book are just a great reminder of the basic building blocks of creating and communicating strategy and values – about driving alignment.

But the premise, as the subtitle indicates, is that maintaining organizational health is the most important thing you can do as a leader.  I tell our team at Return Path  all the time that our culture is a competitive advantage in many ways, some quantifiable, and others a little less tangible.

A telling point in the book is when Lencioni is relaying a conversation he had with the CEO of a client company who does run a healthy organization – he asked, “Why in the world don’t your competitors do any of this?” And the client responded, “You know, I honestly believe they think it’s beneath them.” Lencioni goes on to say, “In spite of its undeniable power, so many leaders struggle to embrace organizational health because they quietly believe they are too sophisticated, too busy, or too analytical to bother with it.”  And there you have it.  More examples of why “the soft stuff” is mission critical.

Lencioni’s “Recipe for Organizational Health” (the outline of the book):

–          Build a Cohesive Leadership Team

–          Create Clarity

–          Overcommunicate Clarity

–          Reinforce Clarity

And his recipe for creating a tight set of “mission/vision/values” (the middle of the book):

1. Why do we exist?

2. How do we behave?

3. What do we do?

4. How will we succeed?

5. What is most important, right now?

6. Who must do what?

While there are lots of other good frameworks for doing all of this, Lencioni’s models and books are great, simple reminders of one of the CEO’s most important leadership functions.  We’re recrafting our own mission and values statements at the moment at Return Path, and we’re doing it using this 6-Question framework instead of the classic “Mission/Vision/Values” framework popularized a few years back by Harvard Business Review.

The full book series roundup as far as OnlyOnce has gotten so far is:

• The Three Signs of a Miserable Job (post, book)
• The Five Temptations of a CEO (post, book)
• The Four Obsessions of an Extraordinary Executive (post, book)
• Death by Meeting (post, book)
• The Five Dysfunctions of a Team (post, book, Field Guide)
• Silos, Politics and Turf Wars (post, book)
• Getting Naked (post, book)
• The Advantage (book)

Startup CEO “Bibliography”

A couple people who read Startup CEO:  A Field Guide to Scaling Up Your Business asked me if I would publish a list of all the other business books I refer to over the course of the book.  Here it is — I guess in some respects an all-time favorite list for me of business books.

• The Lean Startup by Eric Ries
• The Four Steps to the Epiphany by Steven Gary Blank
• Running Lean by Ash Maurya
• The Entrepreneur’s Guide to Customer Development: A Cheat Sheet to the Four Steps to the Epiphany by Brant Cooper and Patrick Vlaskovits
• Profitable Growth Is Everyone’s Business by Ram Charan
• The Innovator’s Dilemma by Clay Christensen
• The Innovator’s Solution by Clay Christensen
• Purple Cow by Seth Godin
• The Goal by Eliyahu M. Goldratt
• It’s Not Luck by Eliyahu M. Goldratt
• Blue Ocean Strategy by Chan Kim and Renee Mauborgne
• Crossing the Chasm by Geoffrey Moore
• Inside the Tornado by Geoffrey Moore
• Escape Velocity by Geoffrey Moore
• Climbing Mount Improbable by Richard Dawkins
• Topgrading by Brad Smart
• The One Minute Manager by Ken Blanchard
• Whale Done by Ken Blanchard
• High Output Management by Andy Grove
• Three Signs of a Miserable Job by Patrick Lencioni
• The Five Temptations of a CEO by Patrick Lencioni
• The Four Obsessions of an Extraordinary Executive by Patrick Lencioni
• Death by Meeting by Patrick Lencioni
• The Advantage: Why Organizational Health Trumps Everything Else in Business by Patrick Lencioni
• Hardball by George Stalk and Rob Lachenauer
• The Seven Habits of Highly Effective People by Stephen Covey
• The Eighth Habit by Stephen Covey
• Good to Great by Jim Collins
• Built to Last by Jim Collins

And here’s the list of books in Brad Feld’s Startup Revolution series other than Startup CEO:

• Startup Communities: Building and Entrepreneurial Ecosystem in Your City by Brad Feld
• Startup Life: Surviving and Thriving in a Relationship with an Entrepreneur by Brad Feld and Amy Batchelor
• Startup Metrics: Making sense of the numbers in your startup by Brad Feld (not yet published)
• Startup Boards: Getting the Most out of Your Board of Directors by Brad Feld and Mahendra Ramsinghani
• Venture Deals by Brad Feld and Jason Mendelson
• Do More Faster: TechStars Lessons to Accelerate Your Startup by Brad Feld and David Cohen

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:  Culture is King

Joy, Inc.:  How We Built a Workplace People Love, by Richard Sheridan, CEO of Menlo Innovations, was a really good read. Like Remote  which I reviewed a few weeks ago, Joy, Inc. is ostensibly a book about one thing — culture — but is also full of good general advice for CEOs and senior managers.

Also like Remote, the book was written by the founder and CEO of a relatively small firm that is predominately software engineers, so there are some limitations to its specific lessons unless you adapt them to your own environment. Unlike Remote, though, it’s neither preachy nor ranty, so it’s a more pleasant read.  And I suppose fitting of its title, a more joyful read as well. (Interestingly on this comparison, Sheridan has a simple and elegant argument against working remotely in the middle of the book around innovation and collaboration.)

Some of the people-related practices at Sheridan’s company are fascinating and great to read about. In particular, the way the company interviews candidates for development roles is really interesting — more of an audition than an interview, with candidates actually writing code with a development partner, the way the company writes code. Different teams at Return Path interview in different ways, including me for both the exec team and the Board, but one thing I know is that when an interview includes something that is audition-like, the result is much stronger. There are half a dozen more rich examples in the book.

Some of the other quotable lines or concepts in the book include:

• the linkage between scalability with human sustainability (you can’t grow by brute force, you can only grow when people are rested and ready to bring their brain to work)
• “Showcasing your work is accountability in action” (for a million reasons, starting with pride and ending with pride)
• “Trust, accountability, and results — these get you to joy” (whether or not you are a Myers-Briggs J, people do get a bit of a rush out of a job well done)
• “…the fun and frivolity of our whimsically irreverent workplace…” (who doesn’t want to work for THAT company?)
• “When even your vendors want to align with your culture, you know you’re on the right path” (how you treat people is how you treat PEOPLE, not just clients, not just colleagues)
• “One of the key elements of a joyful culture is having team members who trust one another enough to argue” (if you and I agree on everything, one of us is not needed)
• “The reward is in the attempt” (do you encourage people to fail fast often enough?)
• “Good problems are good problems for the first five minutes. Then they just feel like regular problems until you solve them” (Amen, Brother Sheridan)

The benefits of a joyful culture (at Return Path, we call it a People-First culture) have long been clear to me. As Sheridan says, we try to “create a culture where people want to come to work every day.” Cultures like ours look soft and squishy from the outside, or to people who have grown up in tough, more traditional corporate environments. And to be fair, the challenge with a culture like ours is keeping the right balance of freedom and flexibility on one side and high performance and accountability on the other. But the reality is that most companies struggle with most of the same issues — the new hire that isn’t working out or the long-time employee who isn’t cutting it any more, the critical path project that doesn’t get done on time, the missed quarter or lost client.  As Sheridan notes though, one key benefit of working at a joyful company is that problems get surfaced earlier when they are smaller…and they get solved collaboratively, which produces better results. Another key benefit, of course, is that if you’re going to have the same problems as everyone else, you might as well have fun while you’re dealing with them.

If you don’t love where you work and wish you did, read Joy, Inc. If you love where you work but see your company’s faults and want to improve them, read Joy, Inc. If you are not in either of the above camps, go find another job!

Book Short:  Vulnerability Applied to Leadership

Getting Naked:  A Business Fable About Shedding The Three Fears That Sabotage Client Loyalty (book, Kindle), is Patrick Lencion’s latest fable-on-the-go book, and it’s as good a read as all of his books (see list of the ones I’ve read and reviewed at the end of the post).

The book talks about the power of vulnerability as a character trait for those who provide service to clients in that they are rewarded with levels of client loyalty and intimacy.  Besides cringing as I remembered my own personal experience as an overpaid and underqualified 21 year old analyst at how ridiculous some aspects of the management consulting industry are…the book really made me think.  The challenge to the conventional wisdom of “never letting ‘em see you sweat” (we *think* vulnerability will hurt success, we *confuse* competence with ego, etc.) is powerful.  And although vulnerability is often uncomfortable, I believe Lencioni is 100% right – and more than he thinks.

First, the basic premise of the book is that consultants have three fears they need to overcome to achieve nirvana – those fears and the mitigation tactics are:

1. Fear of losing the business:  mitigate by always consulting instead of selling, giving away the business, telling the kind truth, and directly addressing elephants in the room
2. Fear of being embarrassed:  mitigate by asking dumb questions, making dumb suggestions, and celebrating your mistakes
3. Fear of feeling inferior:  mitigate by taking a bullet for the client, making everything about the client, honoring the client’s work, and doing your share of the dirty work

But to my point about Lencioni being more right than he thinks…I’d like to extend the premise around vulnerability as a key to success beyond the world of consulting and client service into the world of leadership.  Think about some of the language above applied to leading an organization or a team:

• Telling the kind truth and directly addressing elephants in the room:  If you’re not going to do this, who is?  There is no place at the top of an organization or team for conflict avoidance
• Asking dumb questions:  How else do you learn what’s going on in your organization?  How else can you get people talking instead of listening?
• Making dumb suggestions:  I’d refer to this more as “bringing an outside/higher level perspective to the dialog.”  You never know when one of your seemingly dumb suggestions will connect the dots for your team in a way that they haven’t done yet on their own (e.g., the suggestions might not be so dumb after all)
• Celebrating your mistakes:  We’re all human.  And as a leader, some of your people may build you up in their mind beyond what’s real and reasonable.  Set a good example by noting when you’re wrong, noting your learnings, and not making the same mistake twice
• Taking a bullet for your team, making everything about your team and honoring your team’s work:  Management 101.  Give credit out liberally.  Take the blame for team failings.
• Doing your share of the dirty work:  An underreported quality of good leaders.  Change the big heavy bottle on the water cooler.  Wipe down the coffee machine.  Order the pizza or push the beer cart around yourself.  Again, we’re all human, leaders aren’t above doing their share to keep the community of the organization safe, fun, clean, well fed, etc.

There’s a really powerful message here.  I hope this review at least scratches the surface of it.

The full book series roundup as far as OnlyOnce has gotten so far is:

• The Three Signs of a Miserable Job (post, book)
• The Five Temptations of a CEO (post, book)
• The Four Obsessions of an Extraordinary Executive (post, book)
• Death by Meeting (post, book)
• The Five Dysfunctions of a Team (post, book, Field Guide)
• Silos, Politics and Turf Wars (post, book)
• Getting Naked (post, book)

Book Short – Another Must-Read by Lencioni

The Ideal Team Player: How to Recognize and Cultivate The Three Essential Virtues (hardcover,kindle is Patrick Lencioni’s latest and greatest.  It’s not my favorite of his, which is still The Advantage (post,buy ), but it’s pretty good and well worth a read.  It builds on his model for accountability in The Five Dysfunctions of a Team (post,buy)and brings it back to “how can you spot or develop and a good team player?”

The central thesis of the book is that great team players have three attributes – hungry, humble, and people-smart.  While I can’t disagree with those three things, as with all consultants’ frameworks, I sound two cautionary notes:  (1) they aren’t the absolute truth, just a truth, and (2) different organizations and different cultures sometimes thrive with different recipes.  That said, certainly for my company, this framework rings true, if not the only truth.

Some great nuggets from the book:

-The basketball coach who says he loves kids who want to come to practice and work as hard as they can at practice to avoid losing
-The concept of Addition by Addition and Addition by Subtraction in the same book – both are real and true.  The notion that three people can get more done than four if the fourth is a problem is VERY REAL
-When you’re desperate for people, you do stupid things – you bring people on who can get the job done but shouldn’t be in your environment.  I don’t know a single CEO who hasn’t made this mistake, even knowing sometimes that they’re in the process of making it

The framing of the “edge” people – people who have two of the three virtues, but not the third, is quite good:

-Hungry and Humble but not People-Smart – The Accidental Mess Maker
-Humble and People-Smart, but not Hungry – The Lovable Slacker
-Hungry and People-Smart, but not Humble – The Skillful Politician

In my experience, and Lencioni may say this in the book, too (I can’t remember and can’t find it), none of these is great…but the last one is by far the most problematic for a culture that values teamwork and collaboration.

Anyway, I realize this is a long summary for a short book, but it’s worth buying and reading and having on your (real or virtual) shelf.  In addition to the story, there are some REALLY GOOD interview guides/questions and team surveys in the back of the book.