🔎
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?

Feb 13 2009

Book Short: Hire Great

Book Short: Hire Great

It’s certainly not hiring season for most of America The World The Universe, but we are still making some limited hires here at Return Path, and I thought – what better time to retool our interviewing and hiring process than in a relatively slow period?

So I just read Who: The A Method for Hiring, by Geoff Smart and Randy Street.  It’s a bit of a sequel, or I guess more of a successor book, to the best book I’ve ever read about hiring and interviewing, Topgrading, by Geoff Smart and his father Brad (post, link to buy).  This one wasn’t bad, and it was much shorter and crisper.

I’m not sure I believe the oft-quoted stat that a bad hire costs a company $1.5mm.  Maybe sometimes (say, if the person embezzles $1.4mm), but certainly the point that bad hires are a nightmare for an organization in any number of ways is well taken.   The book does a good job of explaining the linkage from strategy and execution straight to recruiting, with good examples and tips for how to create the linkage.  That alone makes it a worthwhile read.

The method they describe may seem like common sense, but I bet 95 out of 100 companies don’t come close.  We are very good and quite deliberate about the hiring process and have a good success average, but even we have a lot of room to improve.  The book is divided into four main sections:

  • Scorecard: creating job descriptions that are linked to company strategy and that are outcome and competency based, not task based
  • Sourcing: going beyond internal and external recruiters to make your entire company a talent seeker and magnet
  • Selection: the meat of the book – good detail on how to conduct lots of different kinds of interviews, from screening to topgrading (a must) to focused to reference
  • Sell:  how to reel ’em in once they’re on the line (for us anyway, the least useful section as we rarely lose a candidate once we have an offer out)

One of the most poignant examples in the book centered around hiring someone who had been fired from his previous job.  The hiring method in the book uncovered it (that’s hard enough to do sometimes) but then dug deep enough to understand the context and reasons why, and, matching up what they then knew about the candidate to their required competencies and outcomes for the job, decided the firing wasn’t a show-stopper and went ahead and made the hire.

I’d think of these two books the way I think about the Covey books.  If you have never read The 7 Habits of Highly Effective People, you could just get away with reading Stephen Covey’s newer book, The 8th Habit:  From Effectiveness to Greatness, though the original is much richer.

Jan 6 2005

Sometimes, There Is No Lesson To Be Learned

Sometimes, There Is No Lesson To Be Learned

We had a very unusual employee situation this week at Return Path.  A brand new senior executive we brought in to the company to be our first ever head of HR and Organization Development resigned very abruptly after only a few weeks on the job, citing a complete change of heart about her career direction and moving on to a government position in economic and community development.  Unfortunately, the person gave no notice and provided no assistance with transition, and resigned by cell phone.  What a disappointment, especially coming from an HR professional!

After getting over my disbelief/irritation/rage (not easy, not a small amount), after communicating this difficult message to the company, and after sending a thoughtful-yet-cathartic note to the person, I sat down to think a little bit about how I could have prevented or at least spotted the situation in advance.

We interviewed the person thoroughly — 10 people internally conducted interviews, and I interviewed the person for almost four hours myself, conducting one of the most rigorous interviews I’ve ever conducted given how critical this position was to our organization at this time.  (The interview followed the Chronological In-Depth Structured interview format from Brad Smart’s book Topgrading — more on that in a future posting.)  I also checked five references on the person, all of which were sterling.  I had one outside person, an executive coach with whom I work, interview the person.  Everything checked out, and the person’s attitude and enthusiasm about the position couldn’t have been better.

My conclusion on the lesson learned here?  It’s “Sometimes, there is no lesson to be learned.”  There may be ancillary lessons around handling the situation once it became apparent, but I think the core lesson I’d hope to get out of this — that we could have done something different in the interview process or orientation or first few weeks to prevent or at least spot this ahead of time — appears to be nonexistent.  Hmmmph!

Nov 14 2013

Startup CEO “Bibliography”

Startup CEO “Bibliography”

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

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

Mar 2 2017

Stamina

Stamina

A couple years ago I had breakfast with Nick Mehta, my friend who runs the incredibly exciting Gainsight.  I think at the time I had been running Return Path for 15 years, and he was probably 5 years into his journey.  He said he wanted to run his company forever, and he asked me how I had developed the stamina to keep running Return Path as long as I had.  My off the cuff answer had three points, although writing them down afterwards yielded a couple more.  For entrepreneurs who love what they do, love running and building companies for the long haul, this is an important topic.  CEOs have to change their thinking as their businesses scale, or they will self implode!  What are five things you need to get comfortable with as your business scales in order to be in it for the long haul?

Get more comfortable with not every employee being a rock star.  When you have 5, 10, or even 100 employees, you need everyone to be firing on all cylinders at all times.  More than that, you want to hire “rock stars,” people you can see growing rapidly with their jobs.  As organizations get larger, though, not only is it impossible to staff them that way, it’s not desirable either.  One of the most influential books I’ve read on hiring over the years, Topgrading (review, buy), talks about only hiring A players, but hiring three kinds of A players:  people who are excellent at the job you’re hiring them for and may never grow into a new role; people who are excellent at the job you’re hiring them for and who are likely promotable over time; and people who are excellent at the job you’re hiring them for and are executive material.  Startup CEOs tend to focus on the third kind of hire for everyone.  Scaling CEOs recognize that you need a balance of all three once you stop growing 100% year over year, or even 50%.

Get more comfortable with people quitting.  This has been a tough one for me over the years, although I developed it out of necessity first (there’s only so much you can take personally!), with a philosophy to follow.  I used to take every single employee departure personally.  You are leaving MY company?  What’s wrong with you?  What’s wrong with me or the company?  Can I make a diving catch to save you from leaving?  The reality here about why people leave companies may be 10% about how competitive the war for talent has gotten in technology.  But it’s also 40% from each of two other factors.  First, it’s 40% that, as your organization grows and scales, it may not be the right environment for any given employee any more. Our first employee resigned because we had “gotten too big” when we had about 25 employees.  That happens a bit more these days!  But different people find a sweet spot in different sizes of company.  Second, it’s 40% that sometimes the right next step for someone to take in their career isn’t on offer at your company.  You may not have the right job for the person’s career trajectory if it’s already filled, with the incumbent unlikely to leave.  You may not have the right job for the person’s career trajectory at all if it’s highly specialized.  Or for employees earlier in their careers, it may just be valuable for them to work at another company so they can see the differences between two different types of workplace.

Get more comfortable with a whole bunch of entry level, younger employees who may be great people but won’t necessarily be your friends.  I started Return Path in my late 20s, and I was right at our average age.  It felt like everyone in the company was a peer in that sense, and that I could be friends with all of them.  Now I’m in my (still) mid-40s and am well beyond our average age, despite my high level of energy and of course my youthful appearance.  There was a time several years ago where I’d say things to myself or to someone on my team like “how come no one wants to hang out with me after work any more,” or “wow do I feel out of place at this happy hour – it’s really loud here.”  That’s all ok and normal.  Participate in office social events whenever you want to and as much as you can, but don’t expect to be the last man or woman standing at the end of the evening, and don’t expect that everyone in the room will want to have a drink with you.  No matter how approachable and informal you are, you’re still the CEO, and that office and title are bound to intimidate some people.

Get more comfortable with shifts in culture and differentiate them in your mind from shifts in values.  I wrote a lot about this a couple years ago in The Difference Between Culture and Values . To paraphrase from that post, an organization’s values shouldn’t change over time, but its culture – the expression of those values – necessarily changes with the passage of time and the growth of the company.  The most clear example I can come up with is about the value of transparency and the use case of firing someone.  When you have 10 employees, you can probably just explain to everyone why you fired Joe.  When you have 100 employees, it’s not a great idea to tell everyone why you fired Joe, although you might be ok if everyone finds out.  When you have 1,000 employees, telling everyone why you fired Joe invites a lawsuit from Joe and an expensive settlement on your part, although it’s probably ok and important if Joe’s team or key stakeholders comes to understand what happened.  Does that evolution mean you aren’t being true to your value of transparency?  No.  It just means that WHERE and HOW you are transparent needs to evolve as the company evolves.

  • Get more comfortable with process.  This doesn’t mean you have to turn your nimble startup into a bureaucracy.  But a certain amount of process (more over time as the company scales) is a critical enabler of larger groups of people not only getting things done but getting the right things done, and it’s a critical enabler of the company’s financial health.  At some point, you and your CFO can’t go into a room for a day and do the annual budget by yourselves any more.  But you also can’t let each executive set a budget and just add them together.  At some point, you can’t approve every hire yourself.  But you also can’t let people hire whoever they want, and you can’t let some other single person approve all new hires either, since no one really has the cross-company view that you and maybe a couple of other senior executives has.  At some point, the expense policy of “use your best judgment and spend the company’s money as if it was your own” has to fit inside department T&E budgets, or it’s possible that everyone’s individual best judgments won’t be globally optimal and will cause you to miss your numbers.  Allow process to develop organically.  Be appropriately skeptical of things that smell like bureaucracy and challenge them, but don’t disallow them categorically.  Hire people who understand more sophisticated business process, but don’t let them run amok and make sure they are thoughtful about how and where they introduce process to the organization.

I bet there are 50 things that should be on this list, not 5.  Any others out there to share?