Counter Cliche:  Connected at the Top

Fred hasn’t written an official VC Cliche of the Week for a while, but his post yesterday on Connectors is close enough — in it, he talks about how he likes to be a good Connector between people and thinks it’s a quality of great VCs.

First, we should give credit to Malcolm Gladwell for a great definition of Connectors in The Tipping Point.  Gladwell not only defines Connectors as Fred has but also defines two other types of people who are critical in the social networking/buzz building arena:  Mavens and Salesmen.  I’d argue that a great VC has to have a bit of all three!

But in terms of entrepreneurs (the point of the counter cliche series), is being a Connector a prerequisite for success?  I think the answer is nuanced, but it’s probably no.  I’ve met great CEOs who are fairly introverted and whose brains don’t work in the Connector kind of way.  And they can be great at developing product, even running operations.  But if you’re an entrepreneur and not a Connector, you’d better have one or more of them on your management team (think sales or business development or marketing) to make up for that missing piece of the equation to make sure your company is connecting the dots outside the corporate walls.  Otherwise, you’re sure to miss out on opportunities.

The one area where I would say that being a Connector is critical for an entrepreneur is internally within the company.  If you’re going to lead the troops effectively, you do need to be able to make Connections between people within the company, especially as the business grows.  And off-topic a bit (literally if not figuratively), you also need to be able to connect with your staff members on a personal level and make sure that people are connected to the company and its mission.  I’m not sure these are things that an entrepreneur can delegate as long as he or she is CEO.

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.

(Post 4 of 4 in the series on Scaling CBDO’s- other posts are, When to hire your first Chief Business Development Officer, What does Great look like in a Chief Business Development Officer and Signs your Chief Business Development Officer isn’t Scaling)

Other than the weekly executive meeting, your day as a CEO rarely has an entry of “meet the CBDO.” Because of the infrequency of deals it’s critical to engage with the CBDO with a regular cadence so that when something does come up you’re not getting to know each other again. Anyway, a few ways I’ve typically spent the most time or gotten the most value out of CBDOs over the years are:

One way to engage with the CBDO is to make ecosystem maps together. It’s important for you and the CBDO to understand exactly what ocean you’re swimming in, which other fish are swimming nearby, and which ones are sharks you need to watch out for. This understanding is what can make or break the CBDO role and it is vital that you, as CEO, engage with and help shape that understanding since you’ll have specialized knowledge of some of the other players, their CEOs, and their strategies. The ecosystem map is actually a fun thing to create and not only does it lead to better clarity about where you’re at and where you could go, it also aligns you and the CBDO on a deeper, strategic level.

While you can plan out the ecosystem mapping activity, a lot of the engagement I have with the CBDO is sporadic, unplanned, and spontaneous.  The deal world is intense and unpredictable.  When you’re working on a deal you may be talking to your CBDO 20 hours a day.  When it’s business as usual, you may go weeks without deep interaction. So unlike the other executives, the time you engage with your CBDO will be compressed into highly intense time frames.

A third way I engage with the CBDO is in-market and in-transit.  As with the CRO, I spend time extensively with the CBDO since we are likely going to the same place at the same time a few times a year.  Since the essence of the job as a CBDO is to be a trusted ambassador on all fronts, as Ken identified correctly in his section of Startup CXO, the CEO has to constantly be engaging the ambassador on the organization’s most current thinking, positioning, forward-looking strategy.  Over the life of Return Path (and currently at Bolster), there’s no question that I spent the majority of my “planes, trains, and automobiles work time” with Ken.

(You can find this post on the Bolster Blog here).

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.

What Gets Said vs. What Gets Heard

I’ve been on the edge of a few different situations lately at work where what seems like a very clear (even by objective standards) conversation ends up with two very different understandings down the road.  This is the problem I’d characterize as “What gets said isn’t necessarily what gets heard.”  More often than not, this is around delivering bad news, but there are other use cases as well.  Imagine these three fictitious examples:

• Edward was surprised he got fired, even though his manager said he gave him repeated warnings and performance feedback
• Jacob thought his assignment was to write a proposal and get it out the door before a deadline, but his manager thought the assignment was to schedule a brainstorming meeting with all internal stakeholders to get everyone on the same page before finalizing the proposal
• Bella gets an interim promotion – she still needs to prove herself for 90 days in the new job before the promotion is permanent and there is a comp adjustment – then gets upset when the “email to all” mentions that she is “acting”

Why does this happen?  There are probably two main causes, each with a solution or two.  The first is that What Gets Said isn’t 100% crystal clear.  Delivering difficult news is hard and not for the squeamish.  What can be done about it?  The first problem — the crystal clear one — can be fixed by brute force.  If you are giving someone their last warning before firing him, don’t mumble something about “not great performance” and “consequences.”  Look him in the eye and say “If you do not do x, y, and z in the next 30 days, you will be fired.” 

The second cause is that, even if the conversation is objectively clear, the person on the receiving end of the conversation may WANT to hear something else or believes something else, so that’s what “sticks” out of the conversation.  Solving this problem is more challenging.  Approaching it with a lengthy conversation process like the Action Design model or the Difficult Conversations model is one way; but we don’t always have the time to prepare for or engage in that level of conversation, and it’s not always appropriate.  I’d offer two shortcut tips to get around this issue.  First, ask the person to whom you’re speaking to “play back in your own words what you just heard.”  See it she gets it right.  Second, send a very clear follow-up email after the conversation recapping it and asking for email confirmation.

People are only human (for the most part, in my experience), and even when delivering good news or assignments, sometimes things get lost in translation.  But clarity of message, boldness of approach, and forcing playback and confirmation are a few ways to close the gap between What Gets Said and What Gets Heard.

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?

The Best Place to Work, Part 4: Be the Consummate Host

Besides Surrounding yourself with the best and brightest , Creating an environment of trust,  and Managing yourself very, very well, it’s important for you as a creator of The Best Place to Work to Be the Consummate Host.

What does that mean?  This is how I approach my job every day.  I think of the company as a party, where I’m the host.  I want everyone to have a good time.  To get along with the other guests.  To be excited to come back the next time I have a party (e.g., every day).

By the way, I always have co-hosts, as well – anyone who manages anyone in the company.  If I can’t do something specific below, someone on my executive team does it.  Sometimes, two of us do it!  Examples include:

• I interview people like I’m a bouncer at an exclusive club.  We do very personal new employee orientations.  We do personal check-ins after 30 and 90 days to make sure new employees are on track
• I attend every company function that I can and work the room as a host, even if it’s not “my” event – sometimes it means sacrificing long conversations and conversations with friends for smaller ones and meeting new people
• I call every employee (voicemail ok) and write a note and/or send a gift every anniversary of their employment with the company
• I write notes to people when they do something great or get a promotion

Full series of posts here.

Email Marketing Good and Bad:  Case Study Snippets

I had a good meeting this morning with one of our long-time multi-channel retailer clients who is in town for Shop.org’s Annual Summit.  Over the course of our conversation, she relayed two things going on in her world of email marketing at the moment that bear repeating (with her permission, of course).

First, the good.  In a recent study, our retailer hero determined that customers who receive their email newsletters and offers (not even open/click, just receive) spend on average 3x as much on in-store purchases than their non-email counterparts in any given week or for any given campaign.  Talk about deriving non-email or non-click value from your email marketing efforts!

Second, the bad (ok, well, it’s the ugly as well).  Our retailer hero was just nailed by Spamhaus because someone out there complained about a transactional email he or she received from the retailer.  She estimates that the poor Spamhaus listing is costing her millions of dollars a year in lost sales from regular customers.  The email was literally about a refund that the retailer owed the customer (why there was a complaint — who knows?).  What did Spamhaus suggest the retailer do?  Repermission their list around transactional messages — “or else.”  Seems to me that that’s a pretty tough stance to take on rather shaky evidence and with no appropriate dispute resolution mechanism (e.g., one that’s not just tuned to mailers’ interests, but one that’s fair in the broadest sense of the word).  No wonder Spamhaus is being sued, and no wonder the vigilante blacklist providers of the world are losing traction with ISPs and corporate system administrators.  Authentication and real, professionally run reputation systems with ample amounts of representative data, feedback loops, and dispute resolution mechanisms will ultimately win the day over the vigilantes of the world.  Folks like Spamhaus can get things right lots of the time and in fact do provide a valuable cog in the global world of spam fighting, but they’re less great at making amends when they don’t.

So email continues to have its challenges around filtering and deliverability…but how cool is it that marketers are really sinking their teeth into metrics that prove how effective the email channel is for driving sales, both online and offline?

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?

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?