Book Short:  A Must Read

Every once in a while, I read a book and think, “This is an important book.”  Microtrends, by Mark Penn, was just that kind of read.  Penn is the CEO of one of our largest clients in the market research business as well as CEO of Burson Marstellar and, more notably, the Clintons’ pollster and strategy director for much of the last 16 years.  He’s a smart guy, and more important than that, he’s awash in primary research data.

The premise of Microtrends is that America is no longer a melting pot, where lots of different people come together to try to be the same, but rather that it’s a big tent, where lots of small groups are now large enough to express their individuality powerfully.  The book is also perfect for the ADD-afflicted among us, with 75 chapters each of about 4 pages in length describing one new “microtrend” or small faction of American identity.  Penn not only describes the trend in a data-rich way but then goes on to postulate about the impact that trend will have on society at large and/or on the business opportunities that could come from serving those in the trend.

Just to give you a sample of the trends he covers:  Sex-ratio singles (explaining why there really are more single women than men), Extreme commuters (we certainly have a couple of those at Return Path),
Pro-Semites vs. Christian Zionists (they sound the same but are completely different), Newly-released Ex-cons (hint – there are a ton of them), and the rise of Chinese artists.

Whether you’re interested in marketing, entrepreneurship (you’ll get loads of ideas here), investing (more loads of ideas), or just trends in American and global society, Microtrends is a must must must read.  All 75 chapters were interesting to me, but even if you don’t love some…they’re only 4 pages each!

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:  Getting to MVP

Usually, when we hear the term MVP, we think Most Valuable Player.  But in my line of work, that acronym has come to mean something entirely different:  Minimum Viable Product.  Running Lean: Iterate from Plan A to a Plan That Works, by Ash Maurya, is an incredibly useful, practical how-to guide for any entrepreneur with an idea from concept through to MVP, or the smallest bit of functionality that you can get customers to pay for. This is one of the best books I’ve read that encapsulates most of the contemporary thinking and writing about product development in the early stages of a startup’s life from thought leaders like Steven Gary Blank and Eric Ries.

I read the book recently, as I was writing Startup CEO (original outline here), and I quoted liberally from it, including using his Lean Canvas graphic:

The basic principle behind the Lean Canvas is that the old way of doing a business plan was a ton of up front planning work, assuming you’re right, then building to spec.  The new way of doing a business plan is a really short series of hypotheses on a single page, then the time is spent de-risking the plan by systematically testing each element of it out.  The book includes several lists of checklists that walk you through how to test each box on the Lean Canvas.  As I’ve written about before, checklists are a really powerful management tool.

This is an essential read for entrepreneurs just starting a business.  But it’s also an excellent read for anyone running a growth company.  We have adopted more and more agile/lean methodologies over time at Return Path, and all of our product teams use the Lean Canvas with any major new features and projects.

(Side note – I’m writing this post on Friday, May 10, which is the 9th anniversary of my publishing this blog – 760 posts and one draft book later, it’s still an integral part of my business life!)

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

Book Short:  The Religion of Heresy

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

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

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

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

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

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

• Permission Marketing — the original

• Unleashing the Ideavirus — good follow up on viral marketing

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

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

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

• Free Prize Inside — on being buzzworthy

• Purple Cow — on being remarkable, a great book

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

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

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

• The Dip — haven’t read it

• Meatball Sundae — haven’t read it

• Tribes — see above

Book Short – 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:  Are You Topgraded?

I read a decent volume of business books (some of my favorites and more recent ones are listed in the left hand column of the blog).  I have two main pet peeves with business books as a rule:  the first is is that most business books have one central idea and a few good case examples and take way too many pages to get where they’re going; the other is that far too many of them are geared towards middle and upper management of 5,000+ person companies and are either not applicable or need to be adapted for startups.

Anyway, I thought I’d occasionally post quick synopses of some good ones I’ve read recently.  Topgrading, by Brad Smart was so good that this post will be longer than most.  It’s a must read for anyone who’s doing a lot of hiring (fellow entrepreneur blogger Terry Gold is a fan, as well).

The book is all about how to build an organization of A players and only A players, and it presents a great interviewing methodology.  It’s very long for a business book, but also very valuable.  Buy a copy for anyone in your company who’s doing a lot of hiring, not just for yourself or for your HR person.  I think the book falls down a little bit on startup adaptation, but it’s still worth a read.

There’s been much talk lately about “the importance of B players” in Harvard Business Review and other places.  I share the Topgrading perspective, which is a little different (although more semantically different than philosophically different).

The Topgrading perspective is that you should always hire A players — the definition of which is “one of the top 10% of the available people in the talent pool, for the job you have defined today, at the comp range you have specified.”  I absolutely buy into this.  Don’t like what you’re seeing while screening candidates?  Change one of the three variables (job definition, comp, or geography) and you’ll get there.

The corrolary to the A-player-only theory is that there are three types of A players — the author calls them A1, A2, and A3.  A1’s are capable of and interested in rapidly rising to be leaders of the organization.  A2s are promotable over time.  A3s are not capable of or interested in promotion.

I think what the HBR article on B players is talking about is really what Topgrading calls A3 players.  A3 players are absolutely essential to an organization, especially as it grows over time and develops more operational jobs that leverage the powerhouse A1s and A2s that make up such a big percentage of successful startups.  You just have to recognize (perhaps with them) that A3 players may not be interested in career growth and promotion and not try to push them into more advanced roles that they may not be interested in or capable of doing well.

I’m a huge believer in having a healthy balance of A1s, A2s, and A3s, but I will always want to hire A players per the above definition.  Why would you ever settle for less?

Years ago, I heard then General David Petraeus give a talk to a small group of us about leadership. He was literally coming to us live from his command center in Iraq or Afghanistan when he was running the whole theater of war over there. I realize he subsequently had some tarnish on his reputation after pleading guilty to a misdemeanor around handling classified information, but the main thrust of his talk, his Formula for Strategic Leadership, still stands as one of the more memorable talks on leadership I’ve ever heard and is no less relevant as a result.

Given that I still remember it vividly 14-15 years later, I thought I’d recreate it here with my own annotations after the four principles. It’s a simple 4-step formula:

1. Get the big ideas right. Obviously, you aren’t going to go down in history as a great leader if you consistently get the big picture wrong. That doesn’t mean you have to be right about everything and every detail. But if you pick the wrong market, bet on the wrong approach, happen to get your timing wrong by a few years…it’s hard to win.
2. Communicate them up and down the organization. Every mature leader knows that ideas and plans only go so far if they stay in your head or get filtered down through leadership teams. For your values to take root, for your strategy and strategic choices to make sense, and for people in the organization to be able to connect their daily execution to your company’s north star, you need to spend a lot of time communicating those things throughout the organization. Different groups, different meetings, different channels. And then, when you’re finally exhausted and sick of hearing yourself say those things over and over and over again…keep saying them.
3. Personally oversee their implementation. Leaders who throw things over the proverbial wall — “here’s what to do, now go do it while I move on to something else” — are not really strategic leaders. The devil is in the details. If you can’t bother to spend a few minutes overseeing the implementation of your strategy and carefully watching when and how it works and doesn’t (see next item), you may be a good visionary, but you’re not really a strategic leader.
4. Memorialize and institutionalize best and worst practices. This is where so many leaders fall down on the job. When something in your organization wraps up — a launch, a quarter, a project — you have to do a retrospective, curate learnings both good and bad, and publish them. That way your whole organization can have a growth mindset as a system.

There are about a zillion books on leadership out there. Most of them are probably between 200 and 400 pages long. While they may all have variations on this theme and colorful examples behind them, this still rings true for me as the essential formula for strategic leadership.

I love me a good framework. And Geoffrey Moore is the kind of good product/marketing frameworks for technology companies. Moore’s Zone to Win: Organizing to Compete in an Age of Disruption is a must-read for anyone managing a larger technology organization (start reading it when you get to 200-250 people – it’s never too early to worry about disruption). More important, it’s really a companion book or coda to Escape Velocity: Free Your Company’s Future from the Pull of the Past, so if you haven’t read that one, start there and read both sequentially. Zone to Win is quite short and punchy, and it doesn’t disappoint.

I can’t believe is that I never blogged about Escape Velocity before since it was a very influential book in how we managed a bunch of things at Return Path in the later years when we got larger and were more in “disrupt or be disrupted” mode. I’ll start with the essence of that book before I move onto Zone to Win. Escape Velocity‘s principal framework is to divide the different product lines/lines of business you have into three planning horizons:

• Horizon 1 (H1): Current businesses that should be profitable and sustainable
• Horizon 3 (H3): Nascent R&D efforts with the potential to be disruptors or game changers
• Horizon 2 (H2): The bridge between H1 and H3 where an R&D effort that is taking off is scaled and hopefully achieves the eponymous Escape Velocity

The essence of the book is to talk about how larger companies become completely slavish to H1 businesses, their cash cows, and struggle to escape from their pull, whether that’s internal resource allocation or customer-driven demands. Failure to innovate properly beyond H1 businesses is why companies die. But the rest of the book is a lot less memorable, and it doesn’t quite prompt you into action.

That’s where Zone to Win comes in, and it helps me understand where we really got a couple things really wrong at Return Path (as an aside, Moore once met my Return Path cofounder George at a conference, and when George described our business to him, he said “Ah, a blue collar business. Those can work, too.” I think I understand what he meant by that, although it doesn’t sound like a compliment!)

In Zone to Win, Moore shows you how to put the three Horizons into action by creating an overlay framework to managing your company to help optimize all three zones simultaneously. The four zones are:

The key takeaways for me from this framework as well as the notes of where we got things wrong at Return Path, even while acknowledging that we had to play across H1, H2, and H3 simultaneously, were:

• Performance Zone: Managing your main H1 business in a way that drives growth and customer success for the long haul
• Productivity Zone: Managing your main H1 business for optimal profitability and scalability
• Incubation Zone: Starting new H3 businesses and hoping they work
• Transformation Zone: Getting your H3 business through H2 and into H1 to the point where it’s at least 10% of your overall revenue

What we got right at Return Path was first recognizing that we needed to incubate new businesses as the growth in our core business started to slow down, as well as recognizing that we needed to step up our game in managing the core business for performance. So, Moore would say something like “congratulations, you drew up the correct strategy.” But we fell down on implementation for reasons in three of the four zones. Our problem with the Performance Zone is that we discovered the three horizon model too late — there were several years where we were running R&D experiments in the middle of the core business, which created chaos. By the time we got religion around it, we were constantly playing catch up redesigning our management processes — like the teenager still wearing his kid clothes looking awkward and misfit. In the Productivity Zone, we did invest in productivity, but we weren’t aggressive enough about insisting on End of Life for some programs or products, and and we were bogged down by a convoluted legacy implementation of our CRM system that we never wholesale fixed. But the biggest problem we ran into was in the Transformation Zone, where we tried to jam two new businesses through that zone at the same time instead of focusing all our energies on one. I bet we could have pulled off even more of a transformational success with our security business (the one further along) if we hadn’t also been trying to get our consumer insights business through H2 at the same time. At least Moore notes that’s the hardest zone to get right, so I don’t feel quite so dumb.

There were probably other exogenous factors that caused us to fall down on implementation, too, but I think this had a lot to do with it. And don’t get me wrong, Return Path was a success in the end. It just could have been more successful if we had caught this book and adhered rigorously sooner. It was even published in time — somehow we just missed it. We were lured by customer traction and market pull into thinking we could do both. And it’s certainly possible that we were advised against this by one or more of our board members and plowed ahead anyway.

Moore is a masterful writer. If you haven’t read Crossing the Chasm or Inside the Tornado, for example, if you’re a GenZ founder and you think “wow those books came out before I was born, they can’t be relevant,” you should start by reading them. They’re still 100% applicable today, and Moore’s subsequent editions have updated some of the case studies, even if not totally contemporary — and these are worth reading even as a raw startup (in fact, especially as a raw startup). But once you finish those and your business gets larger, go straight into Escape Velocity and be sure to add on Zone to Win.

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.