Book Short:  Fixing America

I usually only blog about business books, but since I occasionally comment on politics, I thought I would also post on That Used to be Us:  How America Fell Behind in the World It Invented and How We Can Come Back, by Tom Friedman and Michael Mandelbaum (book, Kindle), which I just finished.

There is much that is good about America.  And yet, there is much that is broken and in need of serious repair.  I wrote about some thought on fixing our political system last year in The Beginnings of a Roadmap to Fix America’s Badly Broken Political System?, but fixing our political system can only do so much.  Tom Friedman, with whom I usually agree a lot, but only in part, nailed it in his latest book.  Instead of blaming one party or the other (he points the finger at both!), he blames our overall system, and our will as a people, for the country’s current problems.

The authors talk about the four challenges facing America today – globalization, the IT revolution, deficits and debt, and rising energy demand and climate change, and about how the interplay of those four challenges are more long term and less obvious than challenges we’ve faced as a country in the past, like World Wars or The Great Depression, or even The Great Recession.  The reason, according to the authors, that we have lost our way a bit in the last 20-40 years, is that we have strayed from the five-point formula that has made us successful for the bulk of our history:

• Providing excellent public education for more and more Americans
• Building and continually modernizing our infrastructure
• Keeping America’s doors to immigration open
• Government support for basic research and development
• Implementation of necessary regulations on private economic activity

It’s hard not to be in violent agreement with the book as a normal person with common sense.  Even the last point of the five-point formula, which can rankle those on the right, makes sense when you read the specifics.  And the authors rail against excessive regulation enough in the book to give them credibility on this point.

The authors’ description of the labor market of the future and how we as a country can be competitive in it is quite well thought through.  And they have some other great arguments to make – for example, about how the prior decade of wars was, for the first time in American history, not accompanied by tax increases and non-essential program cuts; or about how we can’t let ourselves be held hostage to AARP and have “funding old age” trump “funding youth” at every turn.

The one thing I disagree with a bit is the authors’ assertion that “we cannot simply cut our way to fiscal sanity.”  I saw a table in the Wall Street Journal the same day I was reading this book that noted the federal budget has grown from $2.6T in 2007 to $3.6T today – 40% in four years!  Sure sounds to me like mostly a spending program, though I do support closing loopholes, eliminating subsidies, and potentially some kind of energy tax for other reasons.

I’ll save their solution for those who read the book.  It’s not as good as the meat of the book itself, but it’s solid, and it actually mirrors something my dad has been talking about for a while now.  If you care about where we are as a country and how we can do better, read this book!

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:  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!

Book Short:  Multiplying Your Team’s Productivity

No matter how frustrated a kids’ soccer coach gets, he never, ever runs onto the field in the middle of a game to step in and play.  It’s not just against the rules, it isn’t his or her role.

Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman and Greg McKeown (book, Kindle) takes this concept and drives it home.  The book was a great read, one of the better business books I’ve read in a long time.  I read a preview of it via an article in a recent Harvard Business Review (walled garden alert – you can only get the first page of the article without buying it), then my colleague George Bilbrey got the book and suggested I read it.  George also has a good post up on his blog about it.

One of the things I love about the book is that unlike a lot of business books, it applies to big companies and small companies with equal relevance.  The book echoes a lot of other contemporary literature on leadership (Collins, Charan, Welch) but pulls it into a more accessible framework based on a more direct form of impact:  not long-term shareholder value, but staff productivity and intelligence.  The book’s thesis is that the best managers get more than 2x out of their people than the average – some of that comes from having people more motivated and stretching, but some comes from literally making people more intelligent by challenging them, investing in them, and leaving them room to grow and learn.

The thesis has similar roots to many successful sales philosophies – that asking value-based questions is more effective than presenting features and benefits (that’s probably a good subject for a whole other post sometime).  The method of selling we use at Return Path which I’ve written about before, SPIN Selling, based on the book by Neil Rackham, gets into that in good detail.  One colorful quote in the book around this came from someone who met two famous 19th century British Prime Ministers and noted that when he came back from a meeting with Gladstone, he was convinced that Gladstone was the smartest person in the world, but when he came back from a meeting with Disraeli, he was convinced that he (not Disraeli) was the smartest person in the world.

Anyway, the book creates archetypal good and bad leaders, called Multipliers and Diminishers, and discusses five traits of both:

• Talent Magnet vs. Empire Builder (find people’s native genius and amplify it)
• Liberator vs. Tyrant (create space, demand the best work, delineate your “hard opinions” from your “soft opinions”)
• Challenger vs. Know-It-All (lay down challenges, ask hard questions)
• Debate Maker vs. Decision Maker (ask for data, ask each person, limit your own participation in debates)
• Investor vs. Micromanager (delegate, teach and coach, practice public accountability)

This was a great read.  Any manager who is trying to get more done with less (and who isn’t these days) can benefit from figuring out how to multiply the performance of his or her team by more than 2x.

Book Short:  The Little Engine that Could

Authors Steven Woods and Alex Shootman would make Watty Piper proud.  Instead of bringing toys to the children on the other side of the mountain, though, this engine brings revenue into your company.  If you run a SaaS business, or really if you run any B2B business, Revenue Engine:  Why Revenue Performance Management is the Next Frontier of Competitive Advantage, will change the way you think about Sales and Marketing. The authors, who were CTO and CRO of Eloqua (the largest SaaS player in the demand management software space that recently got acquired by Oracle), are thought leaders in the field, and the wisdom of the book reflects that.

The book chronicles the contemporary corporate buying process and shows that it has become increasingly like the consumer buying process in recent years.  The Consumer Decision Journey, first published by McKinsey in 2009, chronicles this process and talks about how the traditional funnel has been transformed by the availability of information and social media on the Internet.  Revenue Engine moves this concept to a B2B setting and examines how Marketing and Sales are no longer two separate departments, but stewards of a combined process that requires holistic analysis, investment decisions, and management attention.

In particular, the book does a good job of highlighting new stages in the buying process and the imperatives and metrics associated with getting this “new funnel” right.  One that resonated particularly strongly with me was the importance of consistent and clean data, which is hard but critical!  As my colleague Matt Spielman pointed out when we were discussing the book, the one area of the consumer journey that Revenue Engine leaves is out is Advocacy, which is essential for influencing the purchase process in a B2B environment as well.

One thing I didn’t love about the book is that it’s a little more theoretical than practical. There aren’t nearly enough detailed examples.  In fact, the book itself says it’s “a framework, not an answer.”  So you’ll be left wanting a bit more and needing to do a bit more work on your own to translate the wisdom to your reality, but you’ll have a great jumping off point.

Book Short:  Required Reading, Part II

Every once in a while, a business book nails it from all levels.  Well written, practical, broadly applicable to any size or type of organization, full of good examples, full of practical tables and checklists.   The Leadership Pipeline, which I wrote about here over six years ago, is one of those books — it lays out in great and clear detail a framework for understanding the transition from one level to another in an organization and how work behaviors must change in order for a person to succeed during and on the other side of that transition.  In an organization like Return Path‘s which is rapidly expanding and promoting people regularly, this is critical.  We liked the book so much that we have adopted a lot of its language and have built training courses around it.

The book’s sequel, The Performance Pipeline (book, Kindle), also by Stephen Drotter but without the co-authors of the original book, is now out — and it’s just as fantastic.  The book looks at the same six level types in an organization (Enterprise Manager, Group Manager, Business Manager, Functional Manager, Manager of Managers, Manager of Others, and Self Managers/Individual Contributors) and focuses on what competencies people at each level must have in order to do their jobs at maximum effectiveness — and more important, in order to enable the levels below them to operate in an optimal way.

This book is as close to a handbook as I’ve ever seen for “how to be a CEO” or “how to be a manager.”  Coupled with its prequel, it covers the transition into the role as well as the role itself, so “how to become a CEO and be a great one.”  As with the prequel, the author also takes good care to note how to apply the book to a smaller organization (from the below list, usually the top three levels are combined in the CEO, and often the next two are combined as well).  No synopsis can do justice to this book, but here’s a bit of a sense of what the book is about:

• Enterprise Manager:  role is to Perpetuate the Enterprise and develop an Enterprise-wide strategic framework – what should we look like in 15-20 years, and how will we get the resources we need to get there?
• Group Manager:  role is to manage a portfolio of businesses and develop people to run them
• Business Manager:  role is to optimize short- and long-term profit and develop business-specific strategies around creating customer and stakeholder value
• Functional Manager:  role is to drive competitive advantage and functional excellence
• Manager of Managers:  role is to drive productivity across a multi-year horizon, and focus
• Manager of Others:  role is to enable delivery through motivation, context setting, and talent acquisition
• Self Managers/Individual Contributors:  role is to deliver and to be a good corporate citizen

I could write more, but there’s too much good stuff in this book to make excerpts particularly useful.  The Performance Pipeline is another one of those rare – “run, don’t walk, to buy” books.  Enjoy.  For many of my colleagues at RP – look out – this one is coming!

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)

5 Ways to Get Your Staff on the Same Page

[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]

When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.

To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:

1. Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
2. Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
3. Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
4. Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
5. Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.

Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.

It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.

Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.

The results of this system can be extraordinary:

• Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
• Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
• Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.

This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.

Book Short:  Best Book Ever

The Hard Thing About Hard Things, by Ben Horowitz, is the best business book I’ve ever read.  Or at least the best book on management and leadership that I’ve ever read.  Period.

It’s certainly the best CEO book on the market.  It’s about 1000 times better than my book although my book is intended to be different in several ways.  I suppose they’re complementary, but if you only had time left on this planet for one book, read Ben’s first.

I’m not even going to get into specifics on it, other than that Ben does a great job of telling the LoudCloud/Opsware story in a way that shows the grit, psychology, and pain of being an entrepreneur in a way that, for me, has previously only existed in my head.

Just go buy and read the book.

Book Short:  Like a Prequel to My Book

How to Start a Business, by Jason Nazar, CEO of our client Docstoc, is a great and quick (and free) eBook that feels a lot like a prequel to my book Startup CEO:  A Field Guide to Scaling Up Your Business (original outline here). My book is about scaling a business once you’ve started it.  Jason’s book is a really practical guide to starting it in the first place.

The thing that’s particularly good about this book is that it’s as much a resource guide as it is a book.  At the end of each of its 24 chapters (and within them as well), Jason adds a series of external links to other resources, from videos to checklists to templates.  The book answers a lot of really practical questions that are easy for product-focused entrepreneurs to gloss over or ignore, from corporate structures to insurance, from trademark registration to pitching VCs, from payroll to tax planning.

It’s great to see so much more being written for entrepreneurs these days.  Ash Maurya’s Running Lean: Iterate from Plan A to a Plan That Works (which I blogged about last week) is another related book that focuses on how to bring a new product to market.  But Jason’s eBook is a must read for anyone in TechStars or any accelerator program, or anyone contemplating starting a business.

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)