The Value (and Limitations) of Benchmarking
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.
I Don’t Want to Be Your Friend (Today), part III
I Don’t Want to Be Your Friend (Today), part III
My first thought when my colleague Jen Goldman forwarded me a SlideShare presentation that was 224 pages long was, “really?” But a short 10 minutes and 224 clicks later, I am glad I spent the time on it.
Paul Adams, a Senior User Experience Researcher at Google, put the presentation up called The Real Life Social Network. Paul describes the problem I discuss in Part I and Part II of this series much more eloquently than I have, with great real world examples and thoughts for web designers at the end.
If you’re involved in social media and want to start breaking away from the “one size of friend fits all” mentality – this is a great use of time.
Agile Marketing, Part II
Agile Marketing, Part II
I wrote about this years ago when I was temporarily running Marketing and was noting a lot of the similarities between running contemporary Product Development and Marketing efforts.
Nick Van Weerdenburg just put up a great post called Why Marketing is Becoming Like Software Development which you should read if you run or work in, or work closely with, a marketing department.
Feature Requests
Feature Requests
Here are two new features I’d like to see in life:
- 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?”
- 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.
Mental Maps
Mental Maps
I recently went grocery shopping at a store I’d never been to before, Stew Leonard’s, and, no offense to Stew, I am unlikely to be a repeat customer. While there were some things about the store that were better than most grocery stores, the experience drove me nuts. Here’s why.
The store is laid out completely differently from standard grocery stores. Most stores, even unusual ones like Whole Foods or Trader Joe’s, have a nearly identical layout. One side is produce, frozen foods in the middle, meats in the back, dairy around the other side, standard aisles have bread, baking stuff, cans, cereals, drinks and snacks, etc. Go shopping enough, and you can generally find your way around any store in your sleep.
Stew Leonard’s decided to break the model. The store has no aisles and is linear – you just keep walking in one direction/flow and hit every single section of the store before you reach the end of the maze at the cashiers. One bonus is that they merchandise some things well and put logical items next to each other (burgers next to buns). But you can’t really go back if you missed something, you have no idea what’s coming up next, you can’t tell if you’ve seen all of a given class of item yet since different elements of every category keep popping up.
Sometimes that kind of a risk can pay off in a breakthrough new product design. Maybe people buy more items at Stew’s because things are set up differently. But the experience was very disorienting, the shop took twice as long as usual, and I couldn’t find a bunch of things so I still had to go to A&P afterwards – basically, the costs outweighed the benefits.
The obvious comparison here to our professional world is UI design. Breakthrough redesigns are always risky. They can produce better user experiences, but they can also confuse new visitors or less sophisticated users, and they risk an immediate reaction of “I can’t figure this site out, goodbye.”
UPDATE: Comments aren’t working today on the new blog, but my friend Pete Warden just emailed me a great comment about this post:
Your post reminded me of an incident at Apple that I wanted to share…One of the engineers was advocating for a UI change to an existing product. It clearly made the interface more elegant and logical, but our designer was pushing back hard. Finally the designer said “If you put that change in, I’m going to sneak into your house tonight and move all your furniture to different positions”. That analogy stuck with me; familiarity is what enables us to use a tool without having to stop and think, and so you need a really strong reason to change the structure of an interface.
Book Short: Multiplying Your Team’s Productivity
Book Short: Multiplying Your Team’s Productivity
No matter how frustrated a kids’ soccer coach gets, he never, ever runs onto the field in the middle of a game to step in and play. It’s not just against the rules, it isn’t his or her role.
Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman and Greg McKeown (book, Kindle) takes this concept and drives it home. The book was a great read, one of the better business books I’ve read in a long time. I read a preview of it via an article in a recent Harvard Business Review (walled garden alert – you can only get the first page of the article without buying it), then my colleague George Bilbrey got the book and suggested I read it. George also has a good post up on his blog about it.
One of the things I love about the book is that unlike a lot of business books, it applies to big companies and small companies with equal relevance. The book echoes a lot of other contemporary literature on leadership (Collins, Charan, Welch) but pulls it into a more accessible framework based on a more direct form of impact: not long-term shareholder value, but staff productivity and intelligence. The book’s thesis is that the best managers get more than 2x out of their people than the average – some of that comes from having people more motivated and stretching, but some comes from literally making people more intelligent by challenging them, investing in them, and leaving them room to grow and learn.
The thesis has similar roots to many successful sales philosophies – that asking value-based questions is more effective than presenting features and benefits (that’s probably a good subject for a whole other post sometime). The method of selling we use at Return Path which I’ve written about before, SPIN Selling, based on the book by Neil Rackham, gets into that in good detail. One colorful quote in the book around this came from someone who met two famous 19th century British Prime Ministers and noted that when he came back from a meeting with Gladstone, he was convinced that Gladstone was the smartest person in the world, but when he came back from a meeting with Disraeli, he was convinced that he (not Disraeli) was the smartest person in the world.
Anyway, the book creates archetypal good and bad leaders, called Multipliers and Diminishers, and discusses five traits of both:
- Talent Magnet vs. Empire Builder (find people’s native genius and amplify it)
- Liberator vs. Tyrant (create space, demand the best work, delineate your “hard opinions” from your “soft opinions”)
- Challenger vs. Know-It-All (lay down challenges, ask hard questions)
- Debate Maker vs. Decision Maker (ask for data, ask each person, limit your own participation in debates)
- Investor vs. Micromanager (delegate, teach and coach, practice public accountability)
This was a great read. Any manager who is trying to get more done with less (and who isn’t these days) can benefit from figuring out how to multiply the performance of his or her team by more than 2x.
OnlyOnce, Part II
OnlyOnce, Part II
After more than six years, my blog starting looking like, well, a six-year old blog on an off-the-shelf template. Thanks to my friends at Slice of Lime, OnlyOnce has a new design as of today as well as some new navigation and other features like a tag cloud and Twitter feed (and a new platform, WordPress rather than Typepad). I know many people only read my posts via feed or email (those won’t change), but if you have a minute, feel free to take a look. The site also has its own URL now – https://onlyonceblog.wpengine.com.
With my shiny new template, I may add some other features or areas of content over time, as well. There are still a couple things that are only 95% baked, but I love the new look and wanted to make if “official” today. Thanks to Kevin, Jeff, Mike, Lindsay, and everyone at Slice of Lime for their excellent design work, and for my colleague Andrea for helping do the heavy lifting of porting everything over to the new platform.
Automated Love
Automated Love
Return Path is launching a new mini feature sometime this week to our clients. Normally I wouldn’t blog about this — I think this is mini enough that we’re probably not even saying much about it publicly at the company. But it’s an interesting concept that I thought I’d riff on a little bit.
I forget what we’re calling the program officially — probably something like “Client Status Emails” or “Performance Summary Alerts” — but a bunch of us have been calling it by the more colorful term “Automated Love” for a while now.
The art of account management or client services for an on-demand software company is complex and has evolved significantly from the old days of relationship management. Great account management now means a whole slew of new things, like Being The Subject Matter Expert, and Training the Client. It’s less about the “hey, how are things going?” phone call and more about driving usage and value for clients.
As web services have taken off, particularly for small businesses or “prosumers,” most have built in this concept of Automated Love. The weekly email from the service to its user with charts, stats, benchmarks, and links to the web site, occasionally with some content or blog posts. It’s relatively easy (most of the content is database driven), it reminds customers that you’re there, working on their behalf in the background, it tells them what happened on their account or how they’re doing, it alerts them to current or looming problems, and it drives usage of your service. As a bonus for you internally, usually the same database queries that produce a good bit of Automated Love can also alert your account management team when a client’s usage pattern of your service changes or stops entirely.
While some businesses with low values of any single customer value can probably get away with having a client service function based ENTIRELY on Automated Love, I think any business with a web service MUST have Automated Love as a component of its client service effort.
The Greatest Minds in Email
I recently returned from a six-week sabbatical. It was fantastic. I blogged about it here if you’re curious about the experience. It turned out that, while I was gone, we had probably the most successful, least dramatic six weeks in our 10 year history. I had assumed that’s because the team buckled down while I was out, and so did our Board.
Little did we know what really happened during that six week stretch. It’s often said that when the cat’s away, the mice play. The short video below is what greeted me today at an all-hands meeting. If the team can crank out such great work and have this much fun while I’m out, well, I guess I should take more time off!
I Don’t Want to Be Your Friend (Today), part II
I think Facebook is starting to get out of control from a usability perspective. This doesn’t mean it’s not a great platform and that it doesn’t have utility. But if the platform continues on its current path, the core system runs the risk of going sideways like its various predecessors: GeoCities, MySpace, etc. Maybe I’ll go in there to look for something or someone, but it won’t be a place I scroll through as part of a daily or semi-daily routine.
I wrote about this a year ago now, and while the site has some better tools to assign friends to groups, it doesn’t do any better job than it did a year ago about segregating information flow, either by group or by some kind of intelligence.
I don’t know why my home page, news feed, RSS feed, and iPhone app can’t easily show me posts from people I care about, but if it can’t do that soon enough, I will almost entirely stop using it. Can’t Facebook measure the strength of my connections? Can’t it at least put my wife’s posts at the top? My usage is already way down, and the trend is clear.
And I won’t really comment on Facebook COO Sheryl Sandberg’s inane remark last week that “email is dead because young people don’t use it” other than to paraphrase two things I read on a discussion list I’m on: “Just checked, and you still need an email address to sign-up for a Facebook account,” and “Most teens don’t buy stocks so Wall Street has no future.” More entertaining analogies from Loren McDonald of Silverpop are listed here.
Why I Love Our New Product
Why I Love Our New Product
Return Path officially announced a new product today called Domain Assurance, which I blogged a little bit about here. It’s a very exciting product that will help reduce and ultimately eliminate phishing emails – spam’s even more evil cousin that leads to identity theft, malware, further propagation of spam through botnets, and all sorts of other goodies. The product is in beta now with a bunch of top ISPs and brands.
Those are a lot of reasons to love our new product. But for me, there’s more.
For starters, this is the first new product (entirely new product, not just a feature or extension) that we’ve launched in years. While we’ve made some acquisitions and done a ton of product development, they’ve always been right in our strike zone of deliverability. This is a nice, deeply interrelated adjacency. It’s fun to branch out a little bit and do something new.
Second, this product is a great example of operating leverage. Many of the necessary ingredients for it were already in house – most notably customers and partners, but also a lot of data. That’s what adjacencies should be about. Building it, while a significant effort (and one that’s not completely done yet) was significantly easier than building, say, the original deliverability tool set or reputation database. Let’s hear it for scale!
Finally, the product showcases Return Path’s commitment to open standards, which is fundamental to the Internet’s success. We hope our new Domain Assurance product encourages more and more mailers to authenticate all of their outbound mail, and we hope the product also encourages the use of ADSP and ultimately some productive enhancements to both ADSP and DKIM. Authentication does not equal reputation, but we’ve said for years it’s the fundamental underpinning of it.