Only Once

• Share
• 2 comments

Firsts, Still

Firsts, Still

After more than 13 years in the job, I run into “firsts” less and less often these days.  But in the past week, I’ve had three of them. They’re incredibly different, and it’s awkward to write about them in the same post, but the “firsts” theme holds them together.

One was incredibly tragic — one of our colleagues at Return Path died suddenly and unexpectedly.  Even though we’ve lost two other employees in the last 18 months to cancer, there was something different about this one.  While there’s no good way to die, the suddenness of Joel’s passing was a real shock to me and to the organization, and of course more importantly, to his wife.

The second was that I came face to face with a judge in the state of Delaware for the first time around some litigation we’re in the middle of now.  While I can’t comment on this for obvious reasons, you never think when you decide to incorporate in Delaware that a trip to a courthouse in Wilmington is in your future.

The third, which can only be described as bittersweet, is that we had our first long-time employee retire!  Now THAT’S something you never think about when you run a startup.  But Sophie Miller Audette, one of our first 20 employees going back to 2000 and the sixth longest tenured person at the company today, has decided to retire and move on to other adventures in her already rich life.  A quick search on my blog reveals that I’ve blogged about Sophie three times since I started OnlyOnce 9 years ago (as of next week).  The first time was in 2004 when I quoted her memorable line, “In my next life, I want to come back as a client.”  The second and third times were in 2005 and were about the company’s commitment to helping to find a cure for Multiple Sclerosis, which Sophie was diagnosed with almost 10 years ago now.  Sophie has been an inspiration to many of us for a long time, and while we’ll miss her day-to-day, she’ll always be part of the Return Path family.  Picture of her, me, and Anita at her “retirement dinner” earlier this week below.

I always say that one of the best parts about being in this job for this long is that there are always new challenges and new opportunities to learn and grow.  The last couple weeks, full of firsts, proved the point!

• Share
• 0 comments

The People Who Go to the Trainer the Most Are the Ones Who Were in the Best Shape to Begin With

The People Who Go the the Trainer the Most Are the Onese Who Were int eh Best Shape to Begin With

Have you ever noticed this?  That the people working out with trainers in the gym are usually in great shape?  So why do they keep working with the trainer?  So they maintain their awesome level of fitness, of course!

The lesson for business is the same.  Just because you have a strong suit doesn’t mean you can afford to ignore it and rest on your laurels (at least not for very long).  This is true in good times, and in bad times. 

When things are going well, it can feel like it’s the right time to turn your focus to new things, or to fixing broken things.  And that is true to some extent, but it can’t come at the expense of continuing to develop what’s working.

And the temptation to “cut and coast” in the areas of the business that are working well is especially strong when times get tough and resources are stretched.  In fact, the situation is the opposite.  When times get tough and resources are stretched, it’s even more important to double down on the parts of the business that work well. 

Why is all of this true? 

-Your strong suits have a disproportionate impact on business results.  Are you a product-first organization?  Then great product is what makes your organization successful.  Keep producing more of it.  Are you a sales-dominant organization?  Sell more.   Are you a people-first organization?  Your people don’t become less important over time.  Why would you – in any business environment – do less of what makes you successful?

- Your strong suits are bellwethers for employee insight into the organization.  The things that your company does that are best in class are the things that employees take their cues from, and that employees have the most pride in.  Let those things go – and you risk alienating your most enthusiastic employees.  This isn’t to say that companies should have “third rails,” things that are the equivalent of Social Security or the Pentagon, where the minute someone talks about a budget cut, hysteria ensues.  And it’s not about silly perks (you can be a people-first organization whether or not you have “bring your pet to work day”).  But whatever is important to you one day can’t suddenly be unimportant the next day without risking a high degree of employee whiplash.

- Your strong suits compensate for your weaknesses.  The last two points are all about strong suits being out in front.  But I’d argue that your strong suits do more than that.  They protect you from your weaknesses.  Think about it metaphorically, and relating back to the title of this post, think about the body.  When you have a broken leg, your arms get stronger because you need to use them to crutch yourself around.  If you also broke your arms, you’d have a real problem!  In business, it’s the same.  Strong sales teams tend to compensate for weak marketing teams – invest less in sales, it actually hurts marketing, too.  Strong product can compensate for weak sales teams – so more stagnant product hits twice as hard.

All this may sound obvious.  There are other comparable axioms like “put your best people on your biggest opportunities,” and “manage to your strengths and compensate for your weaknesses.”  And yet, the temptations to coast are real.  So get going to that gym and see your trainer for your weekly appointment.  Even if you’re in great shape.

• Share
• 2 comments

The Nachos Don’t Have Enough Beef in Them

The Nachos Don’t Have Enough Beef in Them

Short story, two powerful lessons.

Story:  I’m sitting at the bar of Sam Snead’s Tavern in Port St. Lucie, Florida, having dinner solo while I wait for my friend to arrive.  I ask the bartender where he’s from, since he has a slight accent.  Nice conversation about how life is rough in Belfast and thank goodness for the American dream.  I ask him what to order for dinner and tell him a couple menu items I’m contemplating.  He says, “I don’t know why they don’t listen to me.  I keep telling them that all the people here say that the nachos aren’t good because they don’t have enough beef in them.”  I order something else.  Five minutes later, someone else pounds his hand on the bar and barks out “Give me a Heineken and a plate of nachos.”  The bartender enters the order into the point-of-sale system.

Lesson 1:  Listen to your front-line employees – in fact, make them your customer research team.  I’ve seen and heard this time and again.  Employees deal with unhappy customers, then roll their eyes, knowing full well about all the problems the customers are encountering, and also believing that management either knows already or doesn’t care.  Or both.  There’s no reason for this!  At a minimum, you should always listen to your customer-facing employees, internalize the feedback, and act on it.  They hear and see it all.  Next best prize – ask them questions.  Better yet – get them to actively solicit customer feedback.

Lesson 2:  Always remember another person’s person-ness, especially if he or she is in a service role.  The old story about the waiter spitting and coughing in the obnoxious customer’s soup would dictate that self-preservation, if nothing else, should inspire civility towards people who are serving you, be it a B2B account manager or a waiter in a diner.  Next best prize – self-interest to get a higher level of service.  Better yet – engagement and kindness like you’d want people to show you.  Chances are, they’re trying to make your day a bit better.  Shouldn’t you try to do the same for theirs?

(Lesson 3:  Always listen to your bartender!)

• Share
• 2 comments

Book Short: Plain Talk

Book Short: Plain Talk

An HR rock star I met with recently told me that “You can say anything you want to your people, as long as it’s true,” which of course is great advice.  Plain Talk: Lessons from a Business Maverick (book, kindle), by Ken Iverson, the long-time CEO of Nucor, pretty much embodies that.  If you’re not familiar with Nucor, it’s a steel company – right, steel – and the most successful one of the last 50-75 years, at that.  You may think an industrial company like this offers no lessons for you.  If so, you are wrong.

The reason Nucor has been so successful, if you believe their long time leader, is that they run the people side of their business differently than most companies like them.  Reading this book from the perspective of a knowledge worker business CEO was particularly interesting, since I had to transform my frame of reference a bit (and do a little mental time travel as well) in order to understand just how revolutionary Nucor’s practices were at the time.

But then I realized – they’re still revolutionary today.  How many companies – even the most progressive ones – don’t have performance reviews because they don’t need them in order to create a high performing environment?  Companies that spend a good percentage of their time and energies thinking about how to get their employees to do their best work, as opposed to focusing only on the goals of the business, do better than those who don’t.  It doesn’t matter what industry you’re in.  As Patrick Lencioni would say, you can outbehave the competition.

Plain Talk is a really short book, and a good, authentic read if you’re a leader who cares about your people and wants to learn a few nuggets here and there from one of the 20^th century masters of that discipline.  Anyone that can link a high degree of delegation to authority has a story worth telling.

• Share
• 1 comment

Articulating the Problem is the First Step Toward Solving It

Articulating the Problem is the First Step Toward Solving It

A while back, we were having some specific challenges at Return Path that were *really* hard to diagnose.  It was like peeling the proverbial onion.  Every time we thought we had the answer to what was going on, we realized all we had was another symptom, not a root cause.  We’re a pretty analytical bunch, so we kept looking for more and more data to give us answers.  And we kept coming up with, well, not all that much, besides a lot of hand-wringing.

It wasn’t until I went into a bit of a cave (e.g., took half a day’s quiet time to myself) and started writing things down for myself that I started to get some clarity around the problem and potential solutions.  I literally opened up a blank Word document and started writing, and writing, and writing.  At first, the thoughts were random.  Then they started taking on some organization.  Eventually, I moved from descriptions of the problem to patterns, to reasons, to thoughts about solutions. 

But what really put me on a track to solutions (as opposed to just understanding the problem better) was starting to *talk* through the problems and potential solutions.  It didn’t take more than a couple conversations with trusted colleagues/advisors before I realized how dumb half of my thoughts were, both about the problems and the solutions, which helped narrow down and consolidate my options considerably.

Even better than solving the problems, or at least a driver of being able to solve them, is feeling more in control of a tough situation.  That’s probably the best thing I’ve learned over the years about the value of articulating problems and solutions.  For a leader, there is no worse feeling than being out of control…and no better feeling than the opposite.  Some level of control or confidence is required to get through tough times.

I suppose this post is not all that different from any 12-step program.  First, admit you have a problem.  Then you can go on to solve it.  But the point I am trying to make is more than that – it’s not just admitting you have a problem.  It’s actually diving in deep to the potential causes of the problem, and writing them down and (better) speaking them out loud a few times, that puts you on the road to solving those problems.

• Share
• 2 comments

A New VC Ready to Go!

A New VC Ready to Go!

One of the interesting things about being in business for 13 years (as of last week!) at Return Path is that we have been around longer than two of our Venture Capital funds.  Fortunately for us, Fred led an investment in the company with his new fund, Union Square Ventures, even though his initial investment was via his first fund, Flatiron Partners.  And even though Brad hasn’t invested out of his new fund, Foundry Group, he remains a really active member of our group as a Board Advisory through his Mobius Venture Capital investment.

Although our third and largest VC shareholder, Sutter Hill Ventures, is very much still in business, our Board member Greg Sands just announced today that he has left Sutter and started his own firm, Costanoa Venture Capital, sponsored in part by Sutter.  The firm was able to buy portions of some of Greg’s portfolio companies from Sutter as part of its founding capital commitment, so Return Path is now part of both funds, and Greg, like Fred, will continue to serve as a director for us and manage both firms’ stakes in Return Path.

The descriptions of the firm in Greg’s first blog post are great – and they point to companies like Return Path being in his sweet spot:  cloud-based services solving real world problems for businesses, Applied Big Data, consumer interfaces and distribution strategies for Enterprise companies.

I give Greg a lot of credit for going out on his own with a strong vision, something that’s unusual in the VC world.  We’re proud to be part of his new portfolio, and I’m sure he’ll be incredibly successful.  Like Fred and Brad and their new firms, Greg understands the value of being able to write smaller initial checks and back them up over time, he is a disciplined investor, and he is a fantastic Board member and mentor.

• Share
• 0 comments

Book Short: Culture is King

Book Short:  Culture is King

Tony Hsieh’s story, Delivering Happiness (book, Kindle), is more than just the story of his life or the story of Zappos. It’s a great window into the soul of a very successful company and one that in many ways has become a model for great culture and a great customer service model.  It’s a relatively quick and breezy read, and it contains a handful of legendary anecdotes from Zappos’ history to demonstrate those two things — culture and customer service — in action.

As Hsieh himself says in the book, you can’t copy this stuff and believe it will work in your company’s environment as it does in Zappos’.  You have to come up with these things on your own, or better yet, you have to create an environment where the company develops its own culture and operating system along the broad lines you lay out.  I think Return Path has many similarities with Zappos in how we seek out WOW experiences and in our Core Values, as well as the evolutionary path we took to get to those places.  But as much as I enjoyed reading about a like-minded company, I also recognized the specific things that were different and had a good visceral understanding as to WHY the differences exist.

It is the rare company that gets to $1 billion in revenue ever – let alone within a decade.  For that reason alone, this is a worthwhile read.  But if you are a student of organizational culture and believe in the power of values-driven organizations, this is good affirmation and full of good examples.  And if you’re a doubter of the power of those things, this might just convince you to think twice about that!

• Share
• 4 comments

The Value of Paying Down Technical Debt

The Value of Paying Down Technical Debt

Our Engineering team has a great term called Technical Debt, which is the accumulation of coding shortcuts and operational inefficiencies over the years in the name of getting product out the door faster that weighs on the company’s code base like debt weighs on a balance sheet.  Like debt, it’s there, you can live with it, but it is a drag on the health of the technology organization and has hard servicing costs.  It’s never fun to pay down technical debt, which takes time away from developing new products and new features and is not really appreciated by anyone outside the engineering organization.

That last point is a mistake, and I can’t encourage CEOs or any leaders within a business strongly enough to view it the opposite way.  Debt may not be fun to pay off, but boy do you feel better after it’s done.  I attended an Engineering all-hands recently where one team presented its work for the past quarter.  For one of our more debt-laden features, this team quietly worked away at code revisions for a few months and drove down operational alerts by over 50% — and more important, drove down application support costs by almost 90%, and all this at a time when usage probably doubled.  Wow. 

I’m not sure how you can successfully scale a company rapidly without inefficiencies in technology.  But on the other side of this particular project, I’m not sure how you can afford NOT to work those ineffiencies out of your system as you grow.  Just as most Americans (political affiliation aside) are wringing their hands over the size and growth of our national debt now because they’re worried about the impact on future generations, engineering organizations of high growth companies need to pay attention to their technical debt and keep it in check relative to the size of their business and code base.

And for CEOs, celebrate the payment of technical debt as if Congress did the unthinkable and put our country back on a sustainable fiscal path, one way or another!

As a long Post Script to this, I asked our CTO Andy and VP Engineering David what they thought of this post before I put it up.  David’s answer was very thoughtful and worth reprinting in full:

 I’d like to share a couple of additional insight as to how Andy and I manage Tech Debt in the org: we insist that it be intentional. What do I mean by “intentional”

•  There is evidence that we should pay it
• There is a pay off at the end

 What are examples of “evidence?”

•  Capacity plans show that we’ll run out of capacity for increased users/usage of a system in a quarter or two
• Performance/stability trends are steadily (or rapidly) moving in the wrong direction
• Alerts/warnings coming off of systems are steadily or rapidly increasing

 What are examples of “pay off?”

•  Increased system capacity
• Improved performance/stability
• Decreased support due to a reduction in alerts/warnings

 We ask the engineers to apply “engineering rigor” to show evidence and pay-offs (i.e. measure, analyze, forecast).

 I bring this up because some engineers like to include “refactoring code” under the umbrella of Tech Debt solely because they don’t like the way the code is written even though there is no evidence that it’s running out of capacity, performance/stability is moving in the wrong direction, etc. This is a “job satisfaction” issue for some engineers. So, it’s important for morale reasons, and the Engineering Directors allocate _some_ time for engineers to do this type of refactoring.  But, it’s also important to help the engineer distinguish between “real” Tech Debt and refactoring for job satisfaction.

• Share
• 0 comments

Not Just About Us

Not Just About Us

When we updated our values this year, we felt there were a couple critical business elements missing from this otherwise “how” series of statements.  One thing missing was our clients and users!  So we added this value to our list:

Not Just About Us:  We know we’re successful when our clients are successful and our users are happy.

This may be one of the most straightforward statements of all our values, so this will be a short post.  We serve lots of constituencies at Return Path.  And we always talk about how we’re a “People First” organization and what that means.  I suppose that inherently means we are a “Client Second” organization, though I’m not sure we’d ever come out and say that.  We do believe that by being People First, we will ultimately do the best job for our customers. 

 That said, we aren’t in business just to build a great company or to have an impact on our community.  Or even our shareholders.  We are also in it for our customers.  Whether we are producing a product for mailers, for ESPs, for ISPs, for security companies, for agencies, or for end users, we can’t forget that as an important element of our success every day.

• Share
• 2 comments

Two Ears, One Mouth

Two Ears, One Mouth

Brace yourself for a post full of pithy quotes from others.  I’m not sure how we missed this one when drafted our original values statements at Return Path years ago, because it’s always been central to the way we operate.  We aren’t just the world’s biggest data-driven email intelligence company – we are a data-driven organization.  So another one of our newly written Core Values is:

Two Ears, One Mouth:  We ask, listen, learn, and collect data.  We engage in constructive debate to reach conclusions and move forward together.

I’m not sure which of my colleagues first said this to me, but I’m going to give credit to Anita, our long-time head of sales (almost a decade!), for saying “There’s a reason God gave you two ears and one mouth.”  The meaning?  Listen (and look, I suppose) more than you speak.

This value really has two distinct components to it, though they’re closely related.  First, we always look to collect data when we need to understand a situation or make a decision.  To quote our long-time investor, Board member, and friend Brad Feld, “the plural of anecdote is not data.”  That means we are always looking far and wide for facts, numbers, and multiple perspectives.  Some of us are better than others at relying on second-hand data and observations from trusted colleagues, which means often times, many of us are collecting data ourselves to inform a situation.  But regardless, we always start with the data.

Second, we use data as the foundation of our decision-making process.  I heard another great quote about this once, which is something like, “If we are going to make a decision based on data, the data will make the decision for us.  If we’re going to use opinion, let’s use mine.”  And while I’m at it, I’ll throw in another great quote from Winston Churchill who famously said “Facts are stubborn things.”  While we do have constructive debates all across our organization, those debates are driven by facts, not emotion.

Finally, when this value says that “we move forward together,” that is the combination of the points in the two prior paragraphs.  People may have different opinions entering a debate.  Even with a lot of data behind a decision, they may still have different opinions after a decision has been made.  But we work very deliberately to all support a decision, even one we may disagree with, and we are able to do that, move forward together, and explain the decision to the organization, because the decision is data-driven.