🔎
Oct 31 2005

Book Short: Reality Doesn’t have to Bite

Book Short:  Reality Doesn’t have to Bite

I just read Confronting Reality (book; audio), the sequel to Execution, by Larry Bossidy and Ram Charan.  Except I didn’t read it, I listened to it on Mariquita’s iPod Shuffle over the course of two or three long runs in the past week.  The book was good enough, but I also learned two valuable lessons.  Lesson 1:  Listening to audio books when running is difficult – it’s hard to focus enough, easy to lose one’s place, can’t refer back to anything or take notes.  Lesson 2:  If you sweat enough on your spouse’s Shuffle, you can end up owning a Shuffle of your own.

Anyway, I was able to focus on the book enough to know that it’s a good one.  It’s chock full of case studies from the last few years, including some “new economy” ones instead of just the industrial types covered in books like Built to Last and Good to Great.  Cisco, Sun, EMC, and Thomson are all among those covered.  The basic message is that you really have to dig into external market realities when crafting a strategic plan or business model and make sure they’re in alignment with your financial targets as well as people and processes.  But the devil’s in the details, and the case studies here are great.

Apr 26 2005

Book Short: Are You Topgraded?

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?

Sep 26 2005

Book Short: The Most Rapacious Guys in the Room

Book Short: The Most Rapacious Guys in the Room

I just finished The Smartest Guys in the Room, by journalists Bethany McLean and Peter Elkind. This is the story of Enron, and what a tale it is! The book is a good quick business novel read. It reminded me a lot of Barbarians at the Gate, except that it made me far angrier. I’m not sure if that’s because I’m at a different place in my career now than I was 10 years ago and therefore have a different appreciation for what goes on in companies, or if the Enron guys were just far worse than anyone surrounding RJR Nabisco. But in any case, as my Grandpa Bill would have said, this one certainly raised my hackles.

Anyway, I can’t even get into the details without working myself into a frenzy about these crooks, but suffice to say there are lots of “what not to do” lessons in this book, starting with CEO Ken Lay’s wuss-like, disconnected approach to leading the company and ending with CFO Andy Fastow’s insane rationalizations for using the company as his own piggy bank. Anyway, I thought it would just be easier to just list out a few simple things to look for in your own company if you’re concerned you might be having some financial scandals within.  You know you have a problem if…

– Your company has 3,000 off-balance sheet special purpose entities, including 800 in the Caymans

– Your CEO has waived your company code of ethics twice so that the CFO could negotiate deals for his own profit against the company

– Your President combatively calls an analyst an asshole on an earnings call when asked why the company couldn’t produce a balance sheet and cash flow statement with its income statement and earnings release

– Your staffers meet someone from your auditor and say “oh, you’re the guy that won’t let us do something”

– Your accounting department becomes viewed as a major profit center because of its treatment of revenue

It’s truly astonishing what these bozos thought they could get away with. Thank God they’re going to jail. Thanks to my colleague Patty Mah (a friend of the author) for this book.

Jul 25 2005

Book Short: Why Not Both?

Book Short:  Why Not Both?

Craig Hickman’s Mind of a Manager, Soul of a Leader talks about how tapping the natural tension between managers and leaders allows an organization to achieve its best.  It covers dozens of topical areas and for each compares how a prototypical manager handles the area (practical, reasonable, decisive) vs. how a prototypical leader handles it (visionary, empathetic, and flexible).  Of course, the book describes the ideal organization as “balanced an integrated” between the two extremes.

My take for startups, a topic not addressed in the book, is that the job of the entrepreneur CEO is to be both manager and leader, and try to do both roles effectively without driving the team nuts.  The book says that “managers wield authority, leaders apply influence.”  Entrepreneurs have to be comfortable with both styles.  Thanks to my colleague Stephanie Miller for giving me a copy of this one.

Dec 27 2010

Book Short: Beyond 10,000 Hours

Book Short: Beyond 10,000 Hours

In Outliers: The Story of Success, by Malcolm Gladwell (post, buy), we are taught, among other things, that it takes 10,000 hours of practice to become an expert at something, as well as a dash of luck and timing, as opposed to huge amounts of innate and unique talent.  In Talent is Overrated, by Geoff Colvin, this theory comes to life, with a very clear differentiating point – it’s not just logging the 10,000 hours, it’s HOW the hours are spent.

Colvin’s main point is that the hours need to be spent in what he calls “deliberate practice.”  The elements of deliberate practice are best explained with his example of Jerry Rice, although you can apply these to any discipline:

  • He spent very little time playing football (e.g., most of his practice was building specific skills, not playing the game)
  • He designed his practice to work on specific needs
  • While supported by others, he did much of the work on his own (e.g., it can be repeated a lot, and there are built-in feedback loops)
  • It wasn’t fun
  • He defied the conventional limits of age

If you’re the kind of person who cares deeply about your own performance, let alone the performance of people around you, it doesn’t take long to be completely riveted by Colvin’s points.  They ring true, and his examples are great and cross a lot of disciplines (though not a ton about business in particular).  I wasn’t 50% done with the book before I had made my list of three key things that I need to Deliberately Practice.

There are some other great aspects to the book as well — including a section on Making Organizations Innovative, from creating a culture of innovation to allowing people the freedom to think, to a section on where passion and drive come from, but hopefully this post conveys the gist of it all.  Want to be a better CEO?  Or a better anything?  This is a good place to start the process.

Thanks to Greg Sands for sending me this excellent book.  I’m going to work it into my rotation for Return Path anniversary presents.

Feb 19 2006

Book Short: Which Runs Faster, You or Your Company?

Book Short:  Which Runs Faster, You or Your Company?

Leading at the Speed of Growth, by Katherine Catlin at the Kauffman Center for Entrepreneurial Leadership is a must read for any entrepreneur or CEO of a growth company.  It’s one of the best books I’ve ever read targeted to that audience – its content is great, its format is a page-turner, and it’s concise and to the point.

The authors take you through three stages of a growth company’s lifestyle (Initial Growth, Rapid Growth, and Continuous Growth) and describe the “how to’s” of the transition into each stage:  how you know it’s coming, how to behave in the new stage, how to leave the old stage behind.

I didn’t realize it when I started reading the book, but Brad had one of the quotes on the back cover that says it all:  “There are business books about starting a company, but they tend to deal with the mechanics of business plans and financing.  Then there are books about ‘how to be the CEO of a Fortune 500 company.’  This is the first book I’ve seen that details the role of the CEO of a small but growing company.”  Thanks to my colleague George Bilbrey for pointing this one out to me.

UPDATE:  Brad corrects me and says that I should mention Jana Matthews, who co-wrote the book with Katherine Catlin and is actually the Kauffman Center person of the duo.

Feb 18 2008

Book Short: Tech Founder? Varsity Basketball Captain? Both! At the Same Time!

Book Short: Tech Founder? Varsity Basketball Captain? Both!  At the Same Time!

Ben Casnocha’s My Startup Life has some of the same appeal as The Mousedriver Chronicles (which I reviewed years go here) in its tale of a startup, its successes, failures, and lessons learned. If you like that kind of book or are starting a company and are looking for kindred spirits, it’s a good book for you.

Ben’s story is more remarkable in some ways because he started his eGovernment software (SaaS of course) company Comcate at the age of 13. That’s right, 13. When I was learning how to shave, having a bar mitzvah, and dealing with acne and a voice dropping at terminal velocity. Starting a business was the furthest thing from my mind. Though to be fair, teenage entrepreneurs are a featured new demographic in Mark Penn’s Microtrends (also worth a read). Perhaps if I were Ben’s age today, I would be a startup junkie, too.

I’ve had the pleasure of meeting Ben a couple times via Brad — I think Brad MUST have been a lot like him 20ish years ago. The advice in the book is good and relevant and incredibly mature for a 20-year old, and Ben, I mean that in an impressed way, not a patronizing one. It’s not necessarily revolutionary, but it’s a very quick and light read if you like the genre/premise.

Dec 22 2007

Book Short: a Corporate Team of Rivals

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.

Apr 22 2009

Book Short: Wither the Team

Book Short:  Wither the Team

I keep expecting one of his books to be repetitive or boring, but Patrick Lencioni’s The Five Dysfunctions of a Team held my interest all the way through, as did his others.  It builds nicely on the last one I read, Death by Meeting (post, link).

I’d say that over the 9 1/2 years we’ve been in business at Return Path, we’ve systematically improved the quality of our management team.  Sometimes that’s because we’ve added or changed people, but mostly it’s because we’ve been deliberate about improving the way in which we work together.  This particular book has a nice framework for spotting troubles on a team, and it both reassured me that we have done a nice job stamping out at least three of the dysfunctions in the model and fired me up that we still have some work to do to completely stamp out the final two (we’ve identified them and made progress, but we’re not quite there yet.

The dysfunctions make much more sense in context, but they are (in descending order of importance):

  • Absence of trust
  • Fear of conflict (everyone plays politically nice)
  • Lack of commitment (decisions don’t stick)
  • Avoidance of accountability
  • Inattention to results (individual ego vs. team success)

For those who are wondering, the two we’re still working on at the exec team level here are conflict and commitment.  And the two are related.  If you don’t produce engaged discussion about an issue and allow everyone to air their opinions, they will invariably be less bought into a decision (especially one they don’t agree with).  But we’re getting there and will continue to work aggressively on it until we’ve rooted it out.

There’s one other interesting takeaway from the book that’s not part of the framework directly, which is that an executive has to be first and foremost a member of his/her team of peers, not the head of his/her department.  That’s how successful teams get built.  AND (this is key) this must trickle down in the organization as well.  Everyone who manages a team of group heads or managers needs to make those people function well as a team first, then as managers of their own groups second.

At any rate, another quick gem of a book.  I’m kind of sorry there’s only one left in the series.

So far the series includes:

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

Feb 1 2007

Book Short: Finishing First

Book Short:  Finishing First

The Power of Nice:  How to Conquer the Business World with Kindness, by Linda Kaplan Thaler and Robin Koval, is one of those “airport books” that takes about an hour to read.  I had an ear-to-ear grin reading the book, in part because, well, it’s just a happy book, filled with anecdotes about how a smile here or a gesture of kindness there made a difference in someone’s life — both personally and professionally.

But part of my interest in the book was also driven by a long-standing debate we have at Return Path over whether we’re “too nice” as a company and whether we should have “sharper elbows.”  I was struck by a few comments the authors made, things you would expect like “nice doesn’t mean naïve” as well as things you wouldn’t like “help your enemies.”  To me, that says it all about success in business:  you can be a fierce competitor externally and demand accountability internally and still be a warm and kind person, and that’s the best (and most rewarding) place to be.

Feb 5 2015

Book Short: Internet Fiction, part II

Book Short:  Internet Fiction, part II

I hate to write a lame post, but here’s what I wrote earlier in the year about Eliot Peper’s first Internet thriller, Uncommon Stock:

Eliot Pepper’s brand new startup thriller, Uncommon Stock, was a breezy and quick read that I enjoyed tremendously. It’s got just the right mix of reality and fantasy in it. For anyone in the tech startup world, it’s a must read. But it would be equally fun and enjoyable for anyone who likes a good juicy thriller.

Like my memory of Hackoff, the book has all kinds of startup details in it, like co-founder struggles and a great presentation of the angel investor vs. VC dilemma. But it also has a great crime/murder intrigue that is interrupted with the book’s untimely ending.  I eagerly await the second installment, promised for early 2015.

Having just finished that second installment, called Uncommon Stock: Power Play, basically I want to say “ditto.”  Power Play was just as good as the first book, and now I can’t wait for the third. Where the first installment’s startup focus was around funding and founder dynamics, this one’s startup focus was around shipping product and customers. The thriller part was just as juicy.

It’s also kind of fun reading about the Boulder startup scene, especially from a writer who doesn’t and who has never spent a ton of time there. He gets some things remarkably accurate with crisp descriptions. I was kind of hoping for a cameo by Brad, at least in the form of a throw-away comment about the “long haired homeless-looking investor in the corner of Frasca.”