The Value (and Limitations) of Benchmarking

I think I am starting to drive my team nuts a little bit. I have suggested, prodded, and executed a ton of external benchmarking projects this year, all of which have different leaders inside Return Path doing both systematic and ad hoc phone calls and meetings with peer companies and aspirational peer companies to understand how we compare to them in terms of specific metrics, practices, and structures.  It’s some combination of the former management consultant in me rearing its head, and me just trying to make sure that we stay ahead of the curve as we rapidly scale our business this year.

Why go through an exercise like this?  One answer is that you don’t want to reinvent the wheel.  If a non-competitive comparable company has solved a problem or done some good creative thinking, then I say “plagiarize with pride,” especially if you’re sharing your best practices with them.  The reality of scaling a business is that things change when you go from 50 to 100 people, or 150 to 300, or 300 to 1,000 — and unless you and your entire executive team have “been there, done that” at all levels, or unless you are constantly replacing execs, there’s not exactly an instruction manual for the work you have to do.

But a second, equally valuable answer, is that benchmarking can uncover both problems and opportunities that you didn’t know you had, or at least validate theories about problems and opportunities that you suspect you have.  Learning that comparable companies convert 50% better on their marketing funnel than you do, or that they systematically raise prices 5-7% per year regardless of new feature introduction (I’m just making these examples up) can help you steer the ship in ways you might not have thought you needed to.

What are the limitations of benchmarking?  As our CTO Andy said to me the other day, sometimes no one else has the answer, either.  We do run into this regularly – for example, a tough technical problem where literally no one else does it well like disaster recovery.  Or in how to solve channel conflict problems or streamline commission plans.

Also, sometimes you find out that you are actually best in class at a particular function.  In those cases, while one could just chalk up the exercise to a waste of time, I still think there is learning to be had from studying others.  And if there are a couple other companies who are also best in class, I always encourage group brainstorming among the top peers about how to push the envelope further and be even better.  This can even take the form of a regular peer group meeting/forum.

On the whole, I find benchmarking a good management practice and in particular a good use of time.  But like everything, it’s situational, and you have to understand what you’re looking for when you start your questioning.  You also have to be prepared to find nothing – and go back to your own drawing board.  Good entrepreneurs have to be great at both inventing and, as I noted above, plagiarizing with pride.

The Value of Ownership

We believe in ownership at Return Path.  One of our 13 core values, as I noted in my prior post, which kicks off a series of 13 posts, is:

We are all owners in the business and think of our employment at the company as a two-way street

We give stock options to every employee, and we regularly give additional grants to employees as well, as their initial grants vest, as they get promoted into more senior roles, and as they earn them through outstanding performance.  But beyond giving those grants out, we regularly remind people that they are part owners of the business, and we encourage them to act that way.  Among other mechanisms for this is an award we allow employees to give out to one another (through a regular mechanism we have for this, which I’ve written about in the past here), the Think Like an Owner award.

One great example of how this value appears in the workplace is that, more often than not, our people think about how to invest money rather than how to spend it.  I wish this happened 100% of the time, and we’re working towards that, but for the most part, people here don’t talk about things like “budget,” “headcount,” and “spend” the way they do at other companies.

Another example is around the “two-way street” concept written into the value statement.  We trust our employees to make every effort to do right by the company, and we make every effort to right by employees in return.  Among other things, we don’t have a formal vacation policy. People are encouraged to take as much vacation as they can, at least 3-4 weeks per year.  We track the days just to make sure people are in fact taking time off, but we don’t have a limit, and we also don’t let people accumulate compensation if they don’t take the time off.  We decided at some point – we don’t count how many hours people work, why should we count the hours they don’t?  We trust that people will get their jobs done, and if they don’t, they will suffer other consequences.  The result of this policy is that people are basically taking the same amount of vacation time they took before, maybe slightly more, but they are liberated from fretting over their time if they want or need extra days or half days here or there.

Two other examples are things we started more recently.  One is called OTB Day, which stands for “On The Business.”  Having a full day set aside each month that is meeting-free and travel-free is a way of carving time out for people to take a step back from their day-to-day jobs of working IN the business so every single employee can spend a relatively distraction-free day being thoughtful about working ON the business and figuring out how we can reinvent and reimagine things as opposed to just doing them.  The other is the concept of a Hack-a-thon.  A lot has been written about this topic on lots of other blogs, but fundamentally, this is about trusting that our whole employee population (these are open to everyone, not just engineers) can figure out how to spend two days’ time wisely working on “outside” projects.

The dividends just keep accumulating as we get larger and as the culture of ownership becomes more and more ingrained.  How owner-like do your employees feel about your company?

To Err is Human, To Admit it is Divine

Forget about forgiveness.  Admitting mistakes is much harder.  The second-to-last value that I’m writing up of our 13 core values at Return Path is

We don’t want you to be embarrassed if you make a mistake; communicate about it and learn from it

People don’t like to feel vulnerable.  And there’s no more vulnerable feeling in business than publicly acknowledging that you goofed, whether to your peers, your boss, or your team (hard to say which is worse — eating crow never tastes good no matter who is serving it). But wow is it a valuable trait for an organization to have. Here are the benefits that come from being good at admitting mistakes:

• You’re not afraid to MAKE mistakes in the first place.  Taking risks, which is one of the things that vaults businesses forward with great speed, inherently involves making mistakes. If you’re afraid to shoot…you can’t score
• You teach yourself not to make the same mistake twice.  Being public about mistakes you make really reinforces your leanings.  It’s sort of like taking notes in class.  If you write it down, you’re more likely to remember it, even if you’re a good listener to the teacher
• You teach others not to make the same mistake you made.  Not everyone learns from the mistakes of others as opposed to the mistakes of self, but being public about mistakes and learnings at least gives other people a shot at learning

We’ve gotten good over the years at doing post-mortems (which I wrote about here) when a major snafu happens, which is institutional (large scale) admission and learning. But smaller scale post-mortems within a team and with less formal process around them are just as important if not more so, to make them commonplace.

We have also baked this thinking into our entire product development process.  We are as lean and agile as possible given that we are closing in on 300 employees now in 11 offices in 8 countries.  Our entire product development process is now geared around the concept of “fail fast” and killing projects or sending them back to the drawing board when they’re not meeting marketplace demand.  Embracing this posture has been one of the hallmarks of our success as we’ve scaled the business these past few years.

One trick here:  If this is something you are trying to institutionalize in your company — make sure you celebrate the admission of a mistake and the learnings from it, rather than the mistake itself. You do still value successful execution more than most things!

I was talking to a CEO the other day who believed it was “wrong” (literally, his word) to meet directly 1:1 with people in the organization who did not report to him.  I’ve heard from other CEOs in the past that they’re casual or informal or sporadic about this practice, but I’ve never heard someone articulate before that they actively stayed away from it.  The CEO in question’s feeling was that these meetings, which I call Skip-Level Meetings, disempowers managers.

I couldn’t disagree more.  I have found Skip-Level Meetings to be an indispensable part of my management and leadership routine and have done them for years.  If your culture is set up such that you as CEO can’t interact directly and regularly with people in your organization other than the 5-8 people who report to you, you are missing out on great opportunities to learn from and have an impact on those around you.

That said, there is an art to doing these meetings right, in ways that don’t disempower people or encourage chaos.  Some of these themes will echo other things I’ve written in recent posts like Moments of Truth and Scaling Me.  My five rules for doing Skip-Level Meetings are:

1. Make them predictable.  Have them on a regular schedule, whatever that is.  The schedule doesn’t have to be uniform across all these meetings.  I have some Skip-Levels that I do monthly, some quarterly, some once a year, some “whenever I am in town.”
   
2. Use a consistent format.  I always have a few questions I ask people in these meetings – things about their key initiatives, their people, their roadblocks, what I can do to help, what their POV is about the company direction and performance, how they are feeling about their role and growth.  I also expect that people will come with questions or topics for me.  If I have more meaty ad hoc topics, I’ll let the person know ahead of time.
   
3. Vary the location.  When I have regular Skip-Levels with a given person, I try to do the occasional one over a meal or drink to make it a little more social.  For remote check-ins, I now always do Skype or Videophone.
   
4. Do groups.  Sometimes group skip-levels are fun and really enlightening, either with a full team, or with a cross-section of skip-levels from other teams.  Watching people relate to each other gives you a really different view into team dynamics.
   
5. Close the loop.  I almost always check-in with the person’s manager BEFORE AND AFTER a Skip-Level.  Before, I ask what the issues are, if there is anything I should push on or ask.  After, I report back on the meeting, especially if there are things the person and I discussed that are out of scope for the person’s job or goals, so there are no surprises.

 I’m sure there are other things I do as well, but I can’t imagine running the company without this practice.  Doing it often and well EMPOWERS people in the company…I’d argue that managers who feel disempowered by it aren’t managers you necessarily want in your business unless you really run a command-and-control shop.

Half Your Waking Hours

I just came back from our annual Board/Management ski trip (and Board meeting) — we had about half of both groups join, which is typical given the time commitment.  We had a great time, and the conversation for the three days was a nice blend of business and personal. 

The thing that struck me during the weekend — and I am reminded of this regularly in the office and at other work events as well — is how much I genuinely enjoy the company of the people with whom I work.  Whether it’s my senior staff, my Board, or anyone I can think of in other roles within Return Path, we can manage to have a good time together and have fun as well as be productively thinking about and discussing work.

With generic assumptions of 8 hours of sleep a night and 8 hours of work a day (neither one being true of course, but canceling each other somewhat out here), we spend half our waking hours on the job.  So we might as well choose to work with people that we get along with!  That doesn’t mean everyone we hire at Return Path has to be like-minded or have the same sense of humor.  But it does mean that we look for people who have that spark in their eye that says "I get it"; it means we want to find people who are articulate and have strong convictions and are not afraid to speak their mind; and it means we screen for people who can be light-hearted and don’t take themselves too too too seriously when we recruit, interview, and hire.

Think about that "half your waking hours" thing the next time you’re hiring someone.  Which candidate (of the technically qualified ones who are in the right zone in terms of compensation) would you rather spend your day with?  In my former career in management consulting, we used to call this the "Cleveland Airport test" — as in, if you were stuck in the Cleveland Airport with this candidate, would you be happy or sad about it?

Who Are Your CPO and COO?

Every senior management team needs a CPO and a COO.  No, I’m not talking about Privacy and Operations.  I’m talking about Paranoia and Optimism.  On my leadership team at Return Path, many of us are Paranoid and many of us are Optimistic, and many of us can play both roles.  But I’m fortunate to have two business partners who are the Chiefs – George Bilbrey is our Chief Paranoia Officer, and Anita Absey is our Chief Optimism Officer.  Those monikers fit their respective roles (product and sales) as well as their personalities.

My view is simple – both traits are critical to have around the management table, and they’re best when they’re in some kind of equilibrium.  Optimism keeps you running forward in a straight line.  The belief that you can successfully execute on your plan, with a spring in your step and a smile on your face, is very motivating.  Paranoia keeps you looking around corners.  It may also keep you awake at night, but it’s the driving force for seeing potential threats to the business that aren’t necessarily obvious and keeping you on your toes.  I wrote about the benefits and limits of paranoia (with an extreme example) years ago here.

Too much of either trait would be a disaster for a team’s psyche.  But both are critical points of view that need a loud voice in any management discussion.  It’s a little bit like making sure your management team knows its actual and target location along the Fear/Greed Continuum.

Feature Requests

Here are two new features I’d like to see in life:

1. Any time you hit “reply to all” when you are in the BCC line – a giant red alert should pop up and say “are you really sure you want to let all these people know that you were BCCd on this thread?”
2. Any time you place a call to a cell phone that’s outside of the person’s normal time zone – a giant red alert should pop up and say “are you sure you want to call this person at 3 a.m. in Singapore?” before completing the call

I’m not sure to whom these requests should be addressed, so I’ll just start with the open web.

It’s a Sad Day When the Lawyers Take Over

With all due respect to lawyers, of course, Google’s recent decision to start making a legal fuss when people in the media use the word “Google” as a verb is NUTS.  Someone, get Marketing on Line 1 — and make it snappy.  Steve Rubel wrote about it, as did Jeff Jarvis, and the source material is here.

For the record, anyone who wants to use any of the following words or phrases as a verb, noun, or any other part of speech, may do so at any time:  Return Path, Sender Score, Authentic Response, Postmaster Direct.  Oh, and then there’s ECOA, the service we pioneered in 2000 that *is* occasionally (in some very small circles) used as a verb!

Spam is Dead.  Long Live Spam!

As pointed out in The Register yesterday (and picked up by Whit in his feed), it’s now been exactly two years since Bill Gates declared that Microsoft would eliminate spam in two years.

Hmmm.  Let’s think about that.  Filters do keep getting better, which Gates predicted.  But challenge/response filtering seems to be dead in the water, and the notion that we’re all going to pay for email stamps seems to be toast as well.

So where are we?  Spam is certainly more of a nuisance than a true crisis these days, which is even more true than when I wrote about here 15 months ago.  But it still consumes massive amounts of time, bandwidth, computing power, and mental energy to deal with the problem and reduce its visible impact on end users.  And even then, the problems of too much spam and too many false positives (emails which aren’t spam that get filtered by mistake) are still very real.  Bottom line — it’s still a business problem with a real, growing market and sub-markets and after-markets for solutions.

With apologies to my many friends and business partners at Microsoft, maybe as is the case with the occasional piece of software, Gates needs to release version 3.0 of his comment before it sticks.

Counter Cliche:  Failure Is Not an Orphan

I haven’t written one of these for a while, but this week, Fred’s VC Cliche of the Week, Success Has a Thousand Fathers, definitely merits an entrepreneurial point of view.  Fred’s main point is right — it’s very easy when something goes right, whether a company/venture deal or even something inside the company like a good quarter or a big new client win, for lots of people to take credit, many of whom don’t deserve it.

But what separates A companies from B and C companies is the ability to recognize and process failures as well as successes.  Failure is not orphan.  It usually has as many real fathers as success.  Although it’s true that Sometimes, There is No Lesson to Be Learned, failure rarely emerges spontaneously. 

Companies that have a culture of blame and denial eventually go down in flames.  They are scary places to work.  They foster in-fighting between departments and back-stabbing among friends.  Most important, companies like that are never able to learn from their mistakes and failures to make sure those things don’t happen again.

Finger-pointing and looking the other way as things go south have no place in a well-run organization.  While companies don’t necessarily need to celebrate failures, they can create a culture where failures are treated as learning experiences and where claiming responsibility for a mistake is a sign of maturity and leadership.  And all of this starts at the top.  If the boss (CEO, department head, line manager) is willing to step up and acknowledge a mistake, do a real post-mortem, and process the learnings with his or her team without fear of retribution, it sets an example that everyone in the organization can follow.

Blog on for Swerdloff

My colleague Craig Swerdloff, who runs our Postmaster Network lead generation business and is one of the smartest people in the online advertising business, has started blogging.  Of particular note is this post, in which he talks about the concept of explicit vs. implicit consent in advertising.

His thinking is a lot like some of the things I’ve written about in the past, like the New Media Deal and the We Media Deal.  The bottom line is that advertising has to be valuable and relevant for end users — and properly/carefully delivered.  Welcome to the blogosphere, Craig!