Book Short:  Choose Voice!

I took a couple days off last week and decided to re-read two old favorites.  One –Ayn Rand’s The Fountainhead — my fourth reading — will take me a little longer to process and figure out if there’s a good intersection with the blog.  One would think so with entrepreneurship as the topic, but my head still hurts from all the objectivism.  The second — Exit, Voice, and Loyalty, by Albert O. Hirschman — is today’s topic.

I can’t remember when I first read Exit, Voice, and Loyalty.  It was either in senior year of high school Economics or Government; or in freshman year of college Political Philosophy.  Either way, it was a long time ago, and for some reason, some of the core messages of this quirkly little 125 page political/economic philosophy book have stayed with me over the years.  I remembered the book incorrectly as a book about political systems, and I think it was born consciously in the wake of Eugene McCarthy’s somewhat revolutionary challenge to a sitting President Johnson for the Democratic Party nomination in 1968.  But the book is actually about business; it’s just about businesses and their customers, not corporations as social structures (the latter being more of an interest to me).  Written by an academic economist (I think), the book has its share of gratuitous demonstrative graphs, 2×2 matrices, and SAT words.  But its central premise is a gem for anyone who runs an organization of any size.

The central premise is that there are really two paths by which one can express dissatisfaction with a temporary, curable lapse in an organization:  exit (bailing), or voice (trying to fix what’s wrong from within).  The third key element, Loyalty, is less a path in and of itself but more an agent that “holds exit at bay and activates voice.”

You need to read the book and apply it to your own circumstances to really get into it, but for me, it’s all about breeding loyalty as a means of making voice the path of least resistance, even when exit is a freely available option (few of us run totalitarian states or monopolies, after all).  That to me is the definition of a successful enterprise, both internally and externally.

With your customers:  make your product so irresistible, and make your customer service so deep, that your customers feel an obligation to help you fix what they perceive to be wrong with your product first, rather than simply complain about price or flee to a competitor.

With your employees:  make your company the best possible place you can think of to work so that even in as ridiculously fluid a job market as we live in, your employees will come to their manager, their department head, the head of HR, or you as leader to tell you when they’re unhappy instead of just leaving, or worse, sulking.

With your company (you as employee):  make yourself indispensible to the organization and do such a great job that if things go wrong with your performance or with your role, your manager’s loyalty to you leads him or her to give you open feedback and coach you to success rather than unceremoniously show you the door.

Ok, this wasn’t such a short book short — probably the longest I’ve ever written in this blog, and certainly the highest ratio of short:actual book.  But if you’re up for a serious academic framework (quasi-business but not exclusively) to apply to your management techniques, this short 1970 book is as valid today as when it was written.  Thanks to David Ramert (I am pretty sure I read it in high school) for introducing it to me way back when!

The Gift of Feedback, Part IV

I wrote a few weeks ago about my live 360 – the first time I’ve ever been in the room for my own review discussion.  I now have a development plan drafted coming out of the session, and having cycled it through the contributors to the review, I’m ready to go with it.  As I did in 2008, 2009, and 2011, I’m posting it here publicly.  This time around, there are three development items:

1. Continue to spend enough time in-market.  In particular, look for opportunities to spend more time with direct clients.  There was a lot of discussion about this at my review.  One director suggested I should spend at least 20% of my time in-market, thinking I was spending less than that.  We track my time to the minute each quarter, and I spend roughly 1/3 of my time in-market.  The problem is the definition of in-market.  We have a lot of large partners (ESPs, ISPs, etc.) with whom I spend a lot of time at senior levels.  Where I spend very little time is with direct clients, either as prospects or as existing clients.  Even though, given our ASP, there isn’t as much leverage in any individual client relationship, I will work harder to engage with both our sales team and a couple of larger accounts to more deeply understand our individual client experience.
2. Strengthen the Executive Committee as a team as well as using the EC as the primary platform for driving accountability throughout the organization.  On the surface, this sounds like “duh,” isn’t that the CEO’s job in the first place?  But there are some important tactical items underneath this, especially given that we’ve changed over half of our executive team in the last 12 months.  I need to keep my foot on the accelerator in a few specific ways:  using our new goals and metrics process and our system of record (7Geese) rigorously with each team member every week or two; being more authoritative about the goals that end up in the system in the first place to make sure my top priorities for the organization are being met; finishing our new team development plan, which will have an emphasis on organizational accountability; and finding the next opportiunity for our EC to go through a management training program as a team.
3. Help stakeholders connect with the inherent complexity of the business.  This is an interesting one.  It started out as “make the business less complex,” until I realized that much of the competitive advantage and inherent value from our business comes fom the fact that we’ve built a series of overlapping, complex, data machines that drive unique insights for clients.  So reducing complexity may not make sense.  But helping everyone in and around the business connect with, and understand the complexity, is key.  To execute this item, there are specifics for each major stakeholder.  For the Board, I am going to experiment with a radically simpler format of our Board Book.  For Investors, Customers, and Partners, we are hard at work revising our corporate positioning and messaging.  Internally, there are few things to work on — speaking at more team/department meetings, looking for other opportunities to streamline the organization, and contemplating a single theme or priority for 2015 instead of our usual 3-5 major priorities.

Again, I want to thank everyone who participated in my 360 this year – my board, my team, a few “lucky” skip-levels, and my coach Marc Maltz.  The feedback was rich, the experience of observing the conversation was very powerful, and I hope you like where the development plan came out!

Solving Problems Together

Last week, I started a series of new posts about our core values (a new tag in the tag cloud for this series) at Return Path.  Read the first one on Ownership here.

Another one of our core values is around problem solving, and ownership is intrinsically related.  We believe that all employees are responsible for owning solutions, not just surfacing problems.  The second core value I’ll write about in this series is written specifically as:

We solve problems together and always present problems with potential solutions or paths to solutions

In terms of how this value manifests itself in our daily existence, for one thing, I see people working across teams and departments regularly, at their own initiative, to solve problems here.  It happens in a very natural way.  Things don’t have to get escalated up and down management chains.  People at all levels seem to be very focused on solving problems, not just pointing them out, and they have good instincts for where, when, and how they can help on critical (and non-critical) items.

Another example, again relative to other workplaces I’ve either been at or seen, is that people complain a lot less here.  If they see something they don’t like, they do something about it, solve the problem themselves, or escalate quickly and professionally. The amount of finger pointing tends to be very low, and quite frankly, when fingers are pointed, they’re usually pointed inward to ask the question, “what could I have done differently?”

The danger of a highly collaborative culture like ours is teams getting stuck in consensus-seeking.  Beware!  The key is to balance collaboration on high value projects with authoritative leadership & direction.

A steady flow of problems are inherent in any business.  I’m thankful that my colleagues are generally quite strong at solving them!

I love me a good framework. And Geoffrey Moore is the kind of good product/marketing frameworks for technology companies. Moore’s Zone to Win: Organizing to Compete in an Age of Disruption is a must-read for anyone managing a larger technology organization (start reading it when you get to 200-250 people – it’s never too early to worry about disruption). More important, it’s really a companion book or coda to Escape Velocity: Free Your Company’s Future from the Pull of the Past, so if you haven’t read that one, start there and read both sequentially. Zone to Win is quite short and punchy, and it doesn’t disappoint.

I can’t believe is that I never blogged about Escape Velocity before since it was a very influential book in how we managed a bunch of things at Return Path in the later years when we got larger and were more in “disrupt or be disrupted” mode. I’ll start with the essence of that book before I move onto Zone to Win. Escape Velocity‘s principal framework is to divide the different product lines/lines of business you have into three planning horizons:

• Horizon 1 (H1): Current businesses that should be profitable and sustainable
• Horizon 3 (H3): Nascent R&D efforts with the potential to be disruptors or game changers
• Horizon 2 (H2): The bridge between H1 and H3 where an R&D effort that is taking off is scaled and hopefully achieves the eponymous Escape Velocity

The essence of the book is to talk about how larger companies become completely slavish to H1 businesses, their cash cows, and struggle to escape from their pull, whether that’s internal resource allocation or customer-driven demands. Failure to innovate properly beyond H1 businesses is why companies die. But the rest of the book is a lot less memorable, and it doesn’t quite prompt you into action.

That’s where Zone to Win comes in, and it helps me understand where we really got a couple things really wrong at Return Path (as an aside, Moore once met my Return Path cofounder George at a conference, and when George described our business to him, he said “Ah, a blue collar business. Those can work, too.” I think I understand what he meant by that, although it doesn’t sound like a compliment!)

In Zone to Win, Moore shows you how to put the three Horizons into action by creating an overlay framework to managing your company to help optimize all three zones simultaneously. The four zones are:

The key takeaways for me from this framework as well as the notes of where we got things wrong at Return Path, even while acknowledging that we had to play across H1, H2, and H3 simultaneously, were:

• Performance Zone: Managing your main H1 business in a way that drives growth and customer success for the long haul
• Productivity Zone: Managing your main H1 business for optimal profitability and scalability
• Incubation Zone: Starting new H3 businesses and hoping they work
• Transformation Zone: Getting your H3 business through H2 and into H1 to the point where it’s at least 10% of your overall revenue

What we got right at Return Path was first recognizing that we needed to incubate new businesses as the growth in our core business started to slow down, as well as recognizing that we needed to step up our game in managing the core business for performance. So, Moore would say something like “congratulations, you drew up the correct strategy.” But we fell down on implementation for reasons in three of the four zones. Our problem with the Performance Zone is that we discovered the three horizon model too late — there were several years where we were running R&D experiments in the middle of the core business, which created chaos. By the time we got religion around it, we were constantly playing catch up redesigning our management processes — like the teenager still wearing his kid clothes looking awkward and misfit. In the Productivity Zone, we did invest in productivity, but we weren’t aggressive enough about insisting on End of Life for some programs or products, and and we were bogged down by a convoluted legacy implementation of our CRM system that we never wholesale fixed. But the biggest problem we ran into was in the Transformation Zone, where we tried to jam two new businesses through that zone at the same time instead of focusing all our energies on one. I bet we could have pulled off even more of a transformational success with our security business (the one further along) if we hadn’t also been trying to get our consumer insights business through H2 at the same time. At least Moore notes that’s the hardest zone to get right, so I don’t feel quite so dumb.

There were probably other exogenous factors that caused us to fall down on implementation, too, but I think this had a lot to do with it. And don’t get me wrong, Return Path was a success in the end. It just could have been more successful if we had caught this book and adhered rigorously sooner. It was even published in time — somehow we just missed it. We were lured by customer traction and market pull into thinking we could do both. And it’s certainly possible that we were advised against this by one or more of our board members and plowed ahead anyway.

Moore is a masterful writer. If you haven’t read Crossing the Chasm or Inside the Tornado, for example, if you’re a GenZ founder and you think “wow those books came out before I was born, they can’t be relevant,” you should start by reading them. They’re still 100% applicable today, and Moore’s subsequent editions have updated some of the case studies, even if not totally contemporary — and these are worth reading even as a raw startup (in fact, especially as a raw startup). But once you finish those and your business gets larger, go straight into Escape Velocity and be sure to add on Zone to Win.

Understanding the Drivers of Success

Although generally business is great at Return Path  and by almost any standard in the world has been consistently strong over the years, as everyone internally knows, the second part of 2012 and most of 2013 were not our finest years/quarters.  We had a number of challenges scaling our business, many of which have since been addressed and improved significantly.

When I step back and reflect on “what went wrong” in the quarters where we came up short of our own expectations, I can come up with lots of specific answers around finer points of execution, and even a few abstracted ones around our industry, solutions, team, and processes.  But one interesting answer I came up with recently was that the reason we faltered a bit was that we didn’t clearly understand the drivers of success in our business in the 1-2 years prior to things getting tough.  And when I reflect back on our entire 14+ year history, I think that pattern has repeated itself a few times, so I’m going to conclude there’s something to it.

What does that mean?  Well, a rising tide — success in your company — papers over a lot of challenges in the business, things that probably aren’t working well that you ignore because the general trend, numbers, and success are there.  Similarly, a falling tide — when the going gets a little tough for you — quickly reveals the cracks in the foundation.

In our case, I think that while some of our success in 2010 and 2011 was due to our product, service, team, etc. — there were two other key drivers.  One was the massive growth in social media and daily deal sites (huge users of email), which led to more rapid customer acquisition and more rapid customer expansion coupled with less customer churn.  The second was the fact that the email filtering environment was undergoing a change, especially at Gmail and Yahoo, which caused more problems and disruption for our clients’ email programs than usual — the sweet spot of our solution.

While of course you always want to make hay while the sun shines, in both of these cases, a more careful analysis, even WHILE WE WERE MAKING HAY, would have led us to the conclusion that both of those trends were not only potentially short-term, but that the end of the trend could be a double negative — both the end of a specific positive (lots of new customers, lots more market need), and the beginning of a BROADER negative (more customer churn, reduced market need).

What are we going to do about this?  I am going to more consistently apply one of our learning principles, the Post-Mortem  –THE ART OF THE POST-MORTEM, to more general business performance issues instead of specific activities or incidents.  But more important, I am going to make sure we do that when things are going well…not just when the going gets tough.

What are the drivers of success in your business?  What would happen if they shifted tomorrow?

Book (Not So) Short:  Raise Your Hand If You’re Sure

I couldn’t get the catchy jingle from the 80’s commercial for Sure deodorant (you remember, the one with the Statue of Liberty at the end of it – thanks, YouTube) out of my head while I was reading the relatively new book, Confidence: How Winning Streaks and Losing Streaks Begin and End.  Written by HBS professor Rosabeth Moss Kantor, Confidence is one of the few business books I’ve read that’s both long and worth reading in full.

The book has scores of examples of both winning and losing streaks, from sports, business, politics, and other walks of life, and it does a great job of breaking down the core elements that go into creating a winning streak or turnaround (Accountability, Collaboration, Innovation).  Kantor also puts a very fine point on the “doom loop” of losing streaks and just how hard it is to turn them around.  The book also has a good crisp definition of why winning streaks end — arrogange, anyone? — and has consistent, but not preachy recipes for avoiding pitfalls and driving success.  All in all, very inspirational, even if many of the roots of success lie in well-documented leadership qualities like those expressed in Jim Collins’ Built to Last and Good to Great.  The book is good enough that Kantor can even be forgiven for lauding Verizon, probably the most consistently awful customer service company I’ve ever dealt with.

But even more of the roots of success and disappointment around streaks are psychological, and these examples really rang true for me as I reflected back on our acquisition of the troubled NetCreations in 2004.  That company was in the midst of a serious slump, a losing streak dating back to 2000, at the peak of the original Internet boom.  Year over year, the company had lost revenues, profits, customers, and key personnel.  Its parent company saw poor results and set it into the doom loop of starving it for resources and alternating between ignoring it and micromanaging it, and when we acquired the business, we found great assets and some fantastic people (many of whom I’m proud to say are still with us today), but a dispirited, blame-oriented, passive culture that was poised to continue wallowing in decline.

I can hardly claim that we’ve turned the business around in full, or that I personally made happen whatever turnaround there has been, but I do think we did a few things right as far as Kantor and Confidence would see it.  Her formula for a turnaround (Espouse the new message, Exemplify it with leadership actions, Establish programs to systematically drive it home throughout the organization) is right in line with our philosophy here at Return Path.

First, we accelerated the separation and autonomy of a fledgeling NetCreations spin-off unit, now our Authentic Response market research group, and let a culture of collaboration and innovation flourish under an exceptionally talented leader, Jeff Mattes.

But that was the easy part (for me anyway), because that part of the business was actually working well, and we just let it do its thing, with more support from HQ.  The turnaround of the core list rental and lead generation business of NetCreations, the original Postmaster Direct, was much tougher and is still a work in progress.  In the last six months, we’ve finally turned the corner, but it hasn’t been easy.  Even though we knew lots of what had to be done early on, actually doing it is much harder than b-school platitudes or even the best-written books make it seem.

The one thing that Kantor probably gives short shrift to, although she does mention it in passing a couple times, is that frequently turnarounds require massive major amounts of purging of personnel (not just management) to take hold.  As one of my former colleagues from Mercer Management Consulting used to say, “sometimes the only way to effect Change Management is to change management.”  Sometimes even very talented people are just bogged down with baggage — the “ghost of quarters past” — and nothing you do or say can break that psychological barrier.

Boy, have we learned that lesson here at Return Path the hard way.  I’m extremely grateful to our team at Return Path, from the old RP people who’ve seen it all happen, to the old NetCreations people who are thriving in the new environment, to the new blood we’ve brought in to help effect the turnaround, for playing such important roles in our own Confidence-building exercises here.  And I’m super Confident that 2007 will be the year that we officially turn the old NetCreations/Postmaster losing streak into a big, multi-year winning streak.

Anyway, I realize this may redefine the “short” in book short, but Confidence is without question a good general management and leadership read.

5 Ways to Get Your Staff on the Same Page

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.

To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:

1. Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
2. Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
3. Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
4. Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
5. Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.

Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.

It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.

Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.

The results of this system can be extraordinary:

• Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
• Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
• Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.

This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.

Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.

Book Short:  The Little Engine that Could

Authors Steven Woods and Alex Shootman would make Watty Piper proud.  Instead of bringing toys to the children on the other side of the mountain, though, this engine brings revenue into your company.  If you run a SaaS business, or really if you run any B2B business, Revenue Engine:  Why Revenue Performance Management is the Next Frontier of Competitive Advantage, will change the way you think about Sales and Marketing. The authors, who were CTO and CRO of Eloqua (the largest SaaS player in the demand management software space that recently got acquired by Oracle), are thought leaders in the field, and the wisdom of the book reflects that.

The book chronicles the contemporary corporate buying process and shows that it has become increasingly like the consumer buying process in recent years.  The Consumer Decision Journey, first published by McKinsey in 2009, chronicles this process and talks about how the traditional funnel has been transformed by the availability of information and social media on the Internet.  Revenue Engine moves this concept to a B2B setting and examines how Marketing and Sales are no longer two separate departments, but stewards of a combined process that requires holistic analysis, investment decisions, and management attention.

In particular, the book does a good job of highlighting new stages in the buying process and the imperatives and metrics associated with getting this “new funnel” right.  One that resonated particularly strongly with me was the importance of consistent and clean data, which is hard but critical!  As my colleague Matt Spielman pointed out when we were discussing the book, the one area of the consumer journey that Revenue Engine leaves is out is Advocacy, which is essential for influencing the purchase process in a B2B environment as well.

One thing I didn’t love about the book is that it’s a little more theoretical than practical. There aren’t nearly enough detailed examples.  In fact, the book itself says it’s “a framework, not an answer.”  So you’ll be left wanting a bit more and needing to do a bit more work on your own to translate the wisdom to your reality, but you’ll have a great jumping off point.

People First

I do not think it’s telling that my fourth post in this series of posts on Return Path’s core values (kickoff post, tag cloud) is something called People First.  Ok, it probably should have been the first post in the series.  To be fair, it is the first value on our list, but for whatever reason, the value about Ownership was top of mind when I decided to create this series.

Anyway, at Return Path,

We believe that people come first

And we aren’t shy about saying it publicly, either.  This came up in a lengthy interview I did with Inc. Magazine last year when we were profiled for winning an award as one of the top 20 small- and mid-sized businesses to work for in America.  After re-reading that article, I went back and tried to find the slide from our investor presentations that I referred to.  I have a few versions of this slide from different points in time, including one that’s simpler (it only has employees, clients, and shareholder on it) but here’s a sample of it:

That pretty much says it all.  We believe that if we have the best and most engaged workforce, we will do the best job at solving our clients’ problems, and if we do that well, our shareholders will win, too.

How does this “people first” mentality influence my/our day-to-day activities?  Here are a few examples:

• We treat all employees well, regardless of level or department.  All employees are important to us achieving our mission – otherwise, they wouldn’t be here.  So we don’t do a lot of things that other companies do like send our top performing sales reps on a boondogle together while the engineers and accountants slave away in the office as second-class citizens.  That would be something you might see in a “sales first” or “customer first” culture
• We fiercely defend the human capital of our organization.  There are two examples I can think of around this point.  First, we do not tolerate abusive clients. Fortunately, they are rare, but more than once over the years either I or a member of my senior team has had to get on the phone with a client and reprimand them, or even terminate their contract with us, for treating one of our employees poorly and unprofessionally. And along the same lines, when all economic hell broke loose in the fall of 2008, we immediately told employees that while we’d be in for a rough ride, our three top priorities were to keep everyone’s job, keep everyone’s compensation, and keep everyone’s health benefits. Fortunately, our business withstood the financial challenges and we were able to get through the financial crisis with those three things intact.
• We walk the walk with regard to employee feedback.  Everyone does employee satisfaction surveys, but we are very rigorous about understanding what areas are making people relatively unhappy (for us, even our poor ratings are pretty good, but they’re poor relative to other ratings), and where in the employee population (office, department, level) those issues lie.  We highlight them in an all-hands meeting or communication, we develop specific action plans around them, and we measure those same questions and responses the next time we do a survey to see how we’ve improved
• We invest in our people.  We pay them fairly well, but that’s not what I’m talking about.  We invest in their learning and growth, which is the lifeblood of knowledge workers.  We do an enormous amount of internal training.  We encourage, support, and pay for outside training and education.  We are very generous with the things that allow our employees to be happy and healthy, from food to fitness to insurance to time off to a flexible environment to allowing them to work from another office, or even remotely, if their lives require them to move somewhere else
• I spend as little time as I possibly can managing my shareholders and as much time as I can with employees and prospective employees.  That doesn’t mean I don’t interact with my Board members – I do that quite a bit.  But it does mean that when I do interact with them, it’s more about what they can do for Return Path and less about reporting information to them.  I do send them a lot of information, but the information flow works well for them and simultaneously minimizes my time commitment to the process:  (1) reporting comes in a very consistent format so that investors know WHAT to expect and what they’re looking at, (2) reporting comes out with a consistently long lead time prior to a meeting so investors know WHEN to expect the information, (3) the format of the information is co-developed with investors so they are getting the material they WANT, and (4) we automate as much of the information production as possible and delegate it out across the organization as much as possible so there’s not a heavy burden on any one employee to produce it
• When we do spend time with customers (which is hopefully a lot as well), we try to spread that time out across a broad base of employees, not just salespeople and account managers, so that as many of our employees can develop a deep enough understanding of what our customers’ lives are like and how we impact them

There are plenty of companies out there who have a “shareholder first” or “customer first” philosophy.  I’m not saying those are necessarily wrong – but at least in our industry, I’ll bet companies like that end up with significantly higher recruiting costs (we source almost half our new hires from existing employee referrals), higher employee churn, and therefore lower revenue and profit per employee metrics at a minimum.  Those things must lead to less happy customers, especially in this day and age of transparency.  And all of those things probably degrade shareholder value, at least over the long haul.

Half the Benefit is in the Preparation

This past week, we had what has become an annual tradition for us – a two-day Board meeting that’s Board and senior management (usually offsite, not this year to keep costs down) and geared to recapping the prior year and planning out 2009 together.  Since we are now two companies, we did two of them back-to-back, one for Authentic Response and the other for Return Path.

It’s a little exhausting to do these meetings, and it’s exhausting to attend them, but they’re well worth it.  The intensity of the sessions, discussion, and even social time in between meetings is great for everyone to get on the same page and remember what’s working, what’s not, and what the world around us looks like as we dive off the high dive for another year.

The most exhausting part is probably the preparation for the meetings.  We probably send out over 400 pages of material in advance – binders, tabs, the works.  It’s the only eco-unfriendly Board packet of the year.  It feels like the old days in management consulting.  It takes days of intense preparation — meetings, spreadsheets, powerpoints, occasionally even some soul searching — to get the books right.  And then, once those are out (the week before the meeting), we spend almost as much time getting the presentations down for the actual meeting, since presenting 400 pages of material that people have already read is completely useless.

By the end of the meetings, we’re in good shape for the next year.  But before the meetings have even started, we’ve gotten a huge percentage of the benefit out of the process.  Pulling materials together is one thing, but figuring out how to craft the overall story (then each piece of it in 10-15 minutes or less) for a semi-external audience is something entirely different.  That’s where the rubber meets the road and where good executives are able to step back; remember what the core drivers and critical success factors are; separate the laundry list of tactics from the kernel that includes strategy, development of competitive advantage, and value creation; and then articulate it quickly, crisply, and convincingly. 

I’m incredibly proud of how both management teams drove the process this year – and I’m charged up for a great 2009 (economy be damned!).