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.

Book Short:  Gladwell Lite

What the Dog Saw, And Other Adventures (book, Kindle) is Malcolm Gladwell’s latest book.  Unlike his three other books, which I quite enjoyed:

• The Tipping Point (about how trends and social movements start and spread)
• Blink (about how the mind makes judgments)
• Outliers: The Story of Success (about how talents are genetic, situational, and cultivated)

this was not a complete book, but rather a compendium of his New Yorker articles loosely grouped into three themes.

If you love Gladwell and don’t read The New Yorker, it’s not a bad read. He’s a fantastic writer, and his vignettes are interesting.  There are many “hmmm” moments as we learn why ketchup always tastes the same but mustard doesn’t; why Ron Popeil is a great salesman of kitchen gadgets; or why the inventor of the birth control pill thought the Pope would endorse it.  But it falls far short of his three books, which go deep into topics and leave a much more lasting impression/impact.

Book Short:  Next, Write a Sequel

Written by Rodd Wagner and James K. Harter and billed as “the long awaited sequel to First, Break All the Rules” (one of the best management books I’ve ever read), I thought 12: The Elements of Great Managing, was good, but not great.  12…, along with the original book First… and Now, Discover Your Strengths, the latter two both by Marcus Buckingham, are all based on an extensive database of research done on corporate America by the Gallup organization over many years.  All three are valuable reads in one way or another, although I found this to be the weakest of the three.  (Note that Now… is different from the other two in that it’s not about management, it’s about self-management — very different, though based on the same research.)

Anyway, the elements of great managing, so say the authors, is all about creating employee engagement.  I totally buy into that.  And since no book short on 12… would be complete if it didn’t list out the 12…

1. Do I know what is expected of me at work?
2. Do I have the materials and equipment I need to do my work right?
3. At work, do I have the opportunity to do what I do best every day?
4. In the last seven days, have I received recognition or praise for doing good work?
5. Does my supervisor, or someone at work, seem to care about me as a person?
6. Is there someone at work who encourages my development?
7. At work, do my opinions seem to count?
8. Does the mission/purpose of my company make me feel my job is important?
9. Are my co-workers committed to doing quality work?
10. Do I have a best friend at work?
11. In the last six months, has someone at work talked to me about my progress?
12. This last year, have I had the opportunities at work to learn and grow?

The book fleshes out each of the 12, gives examples (some of which are better/clearer than others), and then addresses compensation in a very interesting chapter at the end.  Key takeaways on comp:

– Higher pay doesn’t guarantee greater engagement
– Good and bad employees are equally likely to think they deserve a raise
– Money without meaning isn’t enough
– Most employees, most of the time, feel undercompensated
– Individual pay can/should be private, but comp criteria should be very public
– People who feel well-compensated generally work harder

The book also cites a very provocative article suggesting that organizations would handle comp better if they made everyone’s comp public (in contrast to the final bullet above, yes).  I’m going to write more about compensation in future postings, so I’ll leave this section on those notes.

Finally, the book’s two closing thoughts are perhaps its most prescient:  one critical element of BEING a great manager is HAVING a great manager; and the managers who put the most into their people, get the most out of their people.

Half the Benefit is in the Preparation

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

It’s a little exhausting to do these meetings, and it’s exhausting to attend them, but they’re well worth it.  The intensity of the sessions, discussion, and even social time in between meetings is great for everyone to get on the same page and remember what’s working, what’s not, and what the world around us looks like as we dive off the high dive for another year.

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

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

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

Book Short – Blink part III – Undo?

I just finished reading Michael Lewis’s The Undoing Project: A Friendship That Changed Our Minds, and honestly, I wish I could hit Life’s Undo button and reclaim those hours.  I love Michael Lewis, and he’s one of those authors where if he writes it, I will read it.  But this one wasn’t really worth it for me.

Having said that, I think if you haven’t already read both Malcolm Gladwell’s Blink (review, buy) and Daniel Kahneman’s Thinking, Fast and Slow (review, buy), then it might be worth it.  But having read those two books, The Undoing Project had too much overlap and not enough “underlap” (to quote my friend Tom Bartel) – that is, not enough new stuff of substance for me.  The book mostly went into the personal relationship between two academic thinkers, Daniel Kahneman and Amos Tversky.  It also touched on some of the highlights of their work, which, while coming out of the field of psychology, won them a Nobel prize in Economics for illuminating some of the underlying mechanics of how we make decisions.

The two most interesting pieces of their work to me, which are related in the book, are:

First, that human decision-making is incredibly nuanced and complex, and that at least 25% of the time, the transitive property doesn’t apply.  For example, I may prefer coffee to tea, and I may prefer tea to hot chocolate, but that doesn’t necessarily mean I prefer coffee to hot chocolate.

From the book, “When faced with complex multidimensional alternatives, such as job offers, gambles or [political] candidates, it is extremely difficult to utilize properly all the available information.” It wasn’t that people actually preferred A to B and B to C and then turned around and preferred C to A. It was that it was sometimes very hard to understand the differences. Amos didn’t think that the real world was as likely to fool people into contradicting themselves as were the experiments he had designed.  And the choice created its own context: Different features might assume greater prominence in the mind when the coffee was being compared to tea (caffeine) than when it was being compared to hot chocolate (sugar). And what was true of drinks might also be true of people, and ideas, and emotions. The idea was interesting: When people make decisions, they are also making judgments about similarity, between some object in the real world and what they ideally want. They make these judgments by, in effect, counting up the features they notice. And as the noticeability of features can be manipulated by the way they are highlighted, the sense of how similar two things are might also be manipulated.”

Second, what Kahneman and Tversky called Prospect Theory, which is basically that humans are more motivated by the fear of loss as opposed to the greed of gain.  I’ve written about the “Fear/Greed Continuum” of my former boss from many years ago before.  I’m not sure he knew about Kahneman and Tversky’s work when he came up with that construct, and I certainly didn’t know about it when I first blogged about it years ago.  Do this experiment – ask someone both of these questions:  Would you rather be handed $500 or have a 50% chance of winning $1,000 and a 50% of getting nothing?  Then, Would you rather hand me $500 or have a 50% chance of owing me $1,000 and a 50% chance of owing me nothing?  Most of the time, the answers are not the same.

For fun, I tried this out on my kids and re-proved Prospect Theory, just in case anyone was worried about it.

Anyway, bottom line on this book – read it if you haven’t ready those other two books, skip it if you have, maybe skim it if you’ve read one of them!

Book Short:  Unsung Heroes

If you like “entrepreneurship by analogy” books, you’ll like The Innovators:  The Engineering Pioneers Who Made America Modern, by David Billington.  I have to admit some bias here — Professor Billington was my favorite teacher and senior thesis advisor at Princeton (I almost majored in civil engineering because of him), and this book is one of a number he’s written that are outgrowths of his most popular courses at Princeton.  And while there’s no substitute for the length or energy of his lectures, the book works.

The book is basically a person-focused engineering history of America from 1776-1883.  Billington talks about four classes of engineering product:  public structures (mostly bridges), machines that produced power, networks like the railroads and telegraphs, and processes like steel manufacturing.

His approach is to acknowledge that the Americans innovators couldn’t do much without the right context:  learnings from their counterparts in Britain, a supportive government here at home, and abundant raw materials and capital.  But with that backdrop in place, Billington tells the tale of a number of the inventions that built our modern society with a focus on the engineers who got things right.  While some of them are familiar names (Morse, Edison), many are not (Thomas Telford, J. Edgar Thomson, Joseph Henry).

Sound familiar?  It feels at many point in the book that you could insert some different names and dates and be reading a history of the Internet or information age.  And as with the Industrial Revolution, while many of the innovators in our world today are known (Bezos, Yang, Brin/Page), there are probably an equal number who are unsung heroes — either software engineers or even buisness model pioneers who haven’t sought or won’t end up in the spotlight even though their contributions to society or to their companies are giant.  I know there are a number of unsung heroes in our own engineering department at Return Path — people who aren’t market facing and who never get quoted in press releases, but who really make a difference in how the company works and how competitive we are.  This book celebrates those people as much as it does the entrepreneurs you’ve heard of.

Warning, there are lots of pages which are full of mathematical formulas, which may or may not be interesting to you, but the book still holds together 100% if you skip over them.

Book Short:  Entrepreneurial Lessons

The Startup Playbook: Secrets of the Fastest-Growing Startups from 42 Founders, by David Kidder, is the ultimate coffee table book for entrepreneurs and people who are interested in how they think about running their businesses.

David is the author of the Intellectual Devotional series (here’s a link to one of the five or six books in the series), he’s a good friend of mine and a member of a CEO Forum that I’m in, and my major disclosure about this blog post is that I’m one of the 42 entrepreneurs David interviewed for and profiles in the book.

The Startup Playbook is very different from my own book (in progress) on being a Startup CEO.  Where my book is going to go deep on different topics – think of it as a bit of a field guide – David’s book is extremely broad in its coverage of different entrepreneurs and their stories.  Taken together, the book paints a great picture of how CEOs think about the most important parts of the job.  It’s also a nice change of pace (for me, anyway) that David profiles some entrepreneurs who aren’t in the Internet/tech space.

It was an honor to be included in The Startup Playbook next to entrepreneurs like Reid Hoffman and Elon Musk.

Book Short:  Deep Dive on Customer Development

I continue to be on a tear reading books about startups as I finish and get ready for the publication of Startup CEO (now available for pre-ordering at Amazon).   This week’s selection was The Startup Owners Manual:  A Step-by-Step Guide for Building a Great Company, by Steve Blank and Bon Dorf.  This book is a significantly more detailed version of Blank’s first book, The Four Steps to the Epiphany, which was a revolutionary book a few years ago that helped spawn the Lean Startup movement.

And when I say significantly, I mean it!  The Startup Owners Manual is 600 pages of really detailed how-to around the first two steps of Blank’s four steps, Customer Discovery and Customer Validation.  It doesn’t get into the last two steps at all, Customer Creation and Company Building.  It has a lot of overlap with Ash Maurya’s Running Lean (post, book), although it’s significantly more detailed.  And essentially, especially around the topic of “Company Building,” my book starts where this one stops.

One of Blank’s great lines in the book is that a “A startup is a temporary organization in search of a scalable, repeatable, profitable business model.”  That frames the whole Lean Startup movement really, really well.  The whole concept of Customer Discovery and Validation, of testing hypotheses, is critical to getting product-marketing fit right in a capital-efficient manner.  If I were starting Return Path today, we’d be using these methods from the get-go.

But Lean principles are wholly compatible with larger companies, as well, and in fact we use all of these principles in our product development organization today.  We adapt them for our size and scale and the fact that often we are selling either new or enhanced versions of existing product into existing customers, but our product teams have all embraced the Lean principles and the vocabulary around them, and our goal is that we should never bring a product to market that isn’t already being bought.

Book Short – A Smattering of Good Ideas that further my Reboot path

Ram Charan’s The Attacker’s Advantage was not his best work, but it was worth the read.  It had a cohesive thesis and a smattering of good ideas in it, but it felt much more like the work of a management consultant than some of his better books like Know How (review, buy), Confronting Reality (review, buy), Execution (review, buy), What the CEO Wants You to Know ( buy), and my favorite of his that I refer people to all the time, The Leadership Pipeline (review, buy).

Charan’s framework for success in a crazy world full of digital and other disruption is this:

Perceptual acuity (I am still not 100% sure what this means)

1. A mindset to see opportunity in uncertainty
2. The ability to see a new path forward and commit to it
3. Adeptness in managing the transition to the new path
4. Skill in making the organization steerable and agile

The framework is basically about institutionalizing the ability to spot pending changes in the future landscape based on blips and early trends going on today and then about how to seize opportunity once you’ve spotted the future.  I like that theme.  It matches what I wrote about when I read Mark Penn’s Microtrends (review, buy) years ago.

Charan’s four points are important, but some of the suggestions for structuring an organization around them are very company-specific, and others are too generic (yes, you have to set clear priorities).  His conception of something he calls a Joint Practice Session is a lot like the practices involved in Agile that contemporary startups are more likely to just do in their sleep but which are probably helpful for larger companies.

I read the book over a year ago, and am finally getting around to blogging about it.  That time and distance were helpful in distilling my thinking about Charan’s words.  Probably my biggest series of takeaways from the book – and they fit into my Reboot theme this quarter/year, is to spend a little more time “flying at higher altitude,” as Charan puts it:  talking to people outside the company and asking them what they see and observe from the world around them; reading more and synthesizing takeaways and applicability to work more; expanding my information networks beyond industry and country; creating more routine mechanisms for my team to pool observations about the external landscape and potential impacts on the company; and developing a methodology for reviewing and improving predictions over time.

Bottom line:  like many business books, great to skim and pause for a deep dive at interesting sections, but not the author’s best work.

Book Short:  Is CX the new UX?

Outside In: The Power of Putting Customers at the Center of Your Business, by Harley Manning and Kerry Bodine from Forrester Research, was a good read that kept crossing back and forth between good on the subject at hand, and good business advice in general.  The Customer Experience (CX) movement is gaining more and more steam these days, especially in B2B companies like Return Path.  The authors define Customer Experience as “how your customers perceive their interactions with your company,” and who doesn’t care about that?

A few years ago, people started talking a lot more about User Experience (UX) as a new crossover discipline between design and engineering, and our experience at Return Path has been that UX is an incredibly powerful tool in our arsenal to build great technical products via lean/agile methods.  The recurring thought I had reading this book, especially for companies like ours, was “Is CX the new UX?”

In other words, should we just be taking the same kind of lean/agile approach to CX that we do with technical product development and UX — but basically do it more holistically across every customer touchpoint, from marketing to invoice?  It’s hard to see the answer being “no” to that question, although as with all things, the devil is in the implementation details.  And that’s true at the high level (the authors talk about making sure you align CX strategy with corporate strategy and brand attributes and values) as well as a more granular level (what metrics get tracked for CX, and how do those align with the rest of the companies KPIs).

The book’s framework for CX is six high-level disciplines: strategy, customer understanding, design, measurement, governance, and culture — but you really have to read the book to get at the specifics.

Some other thoughts and quotes from the book:

• the book contains some good advice on how to handle management of cross-functional project teams in general (which is always difficult), including a good discussion of various governance models
• “to achieve the full potential of customer experience as a business strategy, you have to change the way you run your business. You must manage from the perspective of your customers, and you must do it in a systematic, repeatable, and disciplined way.”
• one suggestion the book had for weaving the customer experience into your culture (if it’s not there already) is to invite customers to speak all-hands meetings
• another suggestion the book had for weaving the customer experience into everyone’s objectives was one company’s tactic of linking compensation (in this case, 401k match) to customer experience metrics
• “Customer Experience is a journey, not a project. It has a beginning but it doesn’t have an end.”

Thanks to my colleague Jeremy Goldsmith for recommending this book.

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.