I’ve written a few times over the years about our Sabbatical policy at Return Path, including this post and this post about my experience as CEO when one of my direct reports was on his sabbatical, and this post about my own sabbatical.

People ask me this all the time, so I thought I’d write the policy out here.  This is the language in our employee handbook about them:

You have big dreams. We know. This is your chance to cross something off your life list. Whether it’s climbing Mt. Everest, learning Russian or taking your kids across the country in a Winnebago, we believe in rewarding longevity at Return Path and know that a good long break will leave you refreshed and energized!  As such, you are eligible for a sabbatical after your first seven (7) years of employment; then again after every five (5) years incremental employment. The sabbatical provides you with up to six (6) weeks of consecutive time off provided you have that time off approved by your manager at least two months prior to the start of your sabbatical.

You will be requested to sign an Agreement before your sabbatical: if you do not return to work after your sabbatical or if you leave employment within twelve (12) months of returning to work, you will be required to reimburse all amounts received while on sabbatical.  If a holiday occurs on any of of the days of absence, you will not receive holiday pay in addition to your sabbatical pay.  During your sabbatical, your benefits will continue and you will be responsible for making payments for the employee portion of insurance costs if applicable. The period you are on leave will be counted as employment for the purposes of determining your applicable level of benefits.  If you are eligible and have not taken your sabbatical and your employment with Return Path ends (for any reason), you will not be paid out for sabbatical time not taken.

I also wrote an email recently to someone internally that is worth reprinting here, which is How to Prepare for Your Sabbatical, which is aimed at both the person taking the sabbatical, and the person’s manager:

As the employee:

–          Prepare your team

• Make sure their goals and metrics for your time out are super clear
• Make sure they know who to go to for what
• Set their expectations of management coverage (see below). 
• Remember that your manager has a day job so you should look to see how your team members can take over some of the responsibilities.
• Give them stretch goals while you’re out

–          Prepare your individual contributor work

• Hand off all loose ends with extra details. 
• Make introductions via email if your manager/team member  is going to have to work with external parties
• Can be to your team, to your manager, to someone else

–          Prepare your manager

• Brief your manager thoroughly on everything going on with your team, its work, your individual contributor work
• Good topics to cover with your manager:Discuss specifics of team and 1:1 check-ins and agree on a plan for coverage.
  • What are the big initiatives that you’ll need coverage on
  • Which team members would you like the manager to spend a little extra time with?  Are there any work you would like the manager to help a particular EE with?

–          Prepare yourself

• Plan any personal travel early so you get good rates!
• Figure out how to keep your work and personal communications separate – your email (autoresponder, routing, disabling from your smartphone), your voicemail if you use Google Voice or Simulscribe, etc.
• Block out two full days immediately when you return to catch up on email and catch up with your manager and team

As the manager:

–          Prepare your team

• Make sure the rest of your team knows your time will be compromised while you’re covering
• Figure out what kind of coverage you need (either internal or external) while you’re covering

–          Rearrange your calendar/travel

• Add new team meetings or 1:1s as it makes sense.  You don’t have to do exactly what your employee did, but some portions of it will make sense to pick up
• If your employee works in another office with members of his/her team, you might want to plan some travel there to cover in person
• It’s ok to cut back on some other things a bit while you’re covering – just remember to undo everything when the employee’s sabbatical is over

–          While you’re in charge

• Surprise your employee with how much you were able to keep things running in his/her absence!
• Learn as much as you can by doing bits and pieces of his/her job.  This is a great opportunity of the employee to get some value from a fresh perspective.

–          Prepare for your employee’s return

• Keep a running tab of everything that goes on at the company, critical industry news (if appropriate), and with your employee’s function or team and prepare a well-organized briefing document so your employee can hit the ground running when he/she returns
• Block out an hour or two each of the employee’s first two days back to review your briefing document

My main takeaway from this post?  I am overdue my second sabbatical, and it’s time to start thinking about that!

Exciting News for Return Path

If you’ll indulge me in a quick moment of company self-promotion, we are so excited at Return Path to announce that we have been included in Fortune Magazine’s annual list of the Best Places to Work — we are ranked #11 in the Medium Size Company category!  Our official blog post/press release are here.

This is really exciting and a testament to all 360+ of our talented team members at the company.  When we talk about one of our core values as being Job 1 — a shared responsibility for championing and extending our unique culture as a competitive advantage — this is one of those examples of where the theory becomes reality!

Of the many things I may have had in mind for the Return Path of the future on December 6, 1999, winning what is probably the most prestigious “employer of choice” award in the world certainly wasn’t one of them, but it was wonderful to receive the acknowledgment.  Congratulations to the whole team here on this great achievement!

A friend who is a newly promoted CEO just wrote me and asked me this:

I’m having a sort of guilt complex.  Let me explain.

I’ve set up a bunch of positions, which people are grooving into.  We just completed our budget for our new fiscal year, probably faster and easier than ever before.  Sales are going really, really well.

BUT, despite all of this, I feel more relaxed than I have in years.  And I am struggling with that.

I’m relaxed because we seem out in front of stuff, I’ve reduced my span of control from a dozen direct reports to four.  Things are progressing in good ways.  I also have time now that I’ve not had in ages to pop my head up and out and do some long-term thinking and planning.

I still have a bunch of management to do with the senior team, some key problem areas to work on … but I’m not racing breathlessly feeling like I’d rather shoot myself than do my job.

Of course, we are doing well.  That helps. 

Is this honeymoon?  Should I feel guilty?  Should I figure out ways to race breathlessly?

My gut tells me I should feel good and not guilty but this is a sense-check request.

 My response:

I have gone through many stretches here over the years of not being overly busy.  Just means you have a great team and have delegated well.  And that the business has a nice tailwind behind it.

You should feel good.  And not guilty.  But you should also feel a bit paranoid about what you might be missing.

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.

Post on Return Path and People

For those readers of OnlyOnce who aren’t also readers of Fred’s AVC blog, Fred invited our SVP People, Angela, to guest post on his site this week as part of his series on HR/People.  Her post is here, and it’s a great encapsulation of a lot of what we do at Return Path from a People perspective.

The Best Place to Work, Part 6: Let People Be People

Last week, in this continuing series on creating the best place to work, I talked about being a great enabler of people, meaning you do your best to let people do their best work.  This week, I want to talk about Letting People Be People.

I wrote about topic a bit this last year when I wrote my series on Return Path’s Core Values, in particular the post on our value People Work to Live, Not Live to Work .

Work-life balance is critical.  I’ve worked in a grind-it-out 100-hour/week environment as an analyst before.  Quite frankly, it sucks.  One week I actually filled in 121 on my hourly time sheet as a consultant.  If you’ve never calculated the denominator, it’s only 168.  Even being well paid as a first-year analyst out of college, the hourly rate sucked.  Thinking about 121 gives me the shivers today…and it certainly puts into perspective that whether you work 40, 45, 50, 55, or 60 hours in a given week can pale by comparison, and all still let you have a life.  An average week of 40 hours probably doesn’t make sense for a high-growth company of relatively well-paid knowledge workers.  But at 121 you barely get to shower and sleep.

While you may get a lot done working like a dog, you don’t get a lot more done hour for hour relative to productive people do in a 50-week environment.  Certainly not 2x.  People who say they thrive on that kind of pressure are simply lying – or to be fair, they’re not lying, but they are pretending they wouldn’t prefer a different environment, which is likely disingenuous and a result of rationalizing their time spent at work.  Your productivity simply diminishes after some number of hours.  So as a CEO, even a hard-charging one, I think it’s better to focus on creating a productive environment than an environment of sustained long hours.

Work has ebbs and flows just like life has ebbs and flows.  As long as the work generally gets done well and when you need it, you have to assume that sometimes, people will work long hours in bursts and sometimes, people will work fewer hours.  Work-life balance is not measured in days or even weeks, but over the long term.  So to that end, We Let People Be People as a means of trading off freedom and flexibility for high levels of performance and accountability.  At Return Path, we create an environment where people can be people by:

• Giving generous maternity leave and even paternity leave, at least relative to norms in the US
• Having a flexible “work from home” policy, as people do have personal things to do during the business day from time to time
• Allowing even more flexible work conditions for anyone (especially new parents) – 3 or 4 days/week if we can make it work
• Letting people take a 6-week paid sabbatical after 7 years, then after every 5 years after that
• Having an “open vacation” policy where people can take as much vacation as they want, as long as they get their jobs done

As with all the posts in this series, this is meant to be general, not specific.  But these are a few of the things we’ve done to Let People Be People, which has created an incredibly productive environment here where people have fun, lead their lives, and still get their jobs done well and on time.

What Kind of Entrepreneur Are You?

I think there are two kinds of entrepreneurs, and sometimes, you can be both.  There is the kind that starts businesses, and there is the kind that builds businesses.

The kind of entrepreneur who starts businesses but usually doesn’t like running or building them are typically serial entrepreneurs.  How can you spot one?  They:

• Have an idea a minute and a bit of ADD – they are attracted to bright shiny objects – they can’t focus
  • Would rather generate 1 good and idea and 19 bad ones than just 1 good one
  • Are always thinking about the next thing, only excited by the possibility of what could be, not by what is
  • Are more philosophical and theoretical than practical
  • Probably shouldn’t run businesses for more than a few months
  • Are likely to frustrate everyone around them and get bored themselves
  • Are really fun at cocktail parties
  • Say things like “I thought of auctions online way before eBay!”

The second kind of entrepreneur is the kind of person who can run businesses but may or may not come up with the idea.  Typically, these people:

• Care about success, not about having the idea
• Love to make things work
• Would rather generate 1 idea and execute it well than 2 ideas
• Are problem solvers
• Are great with people
• May be less fun at cocktail parties, but you’d want them on your team in a game of paintball or laser tag

It’s the rare one who can do both of these things well.  But you know them when you see them.  Think Dell or Microsoft…or even Apple in a roundabout way if you consider the fact that Jobs hired Cook (and others) to partner with them to run the business.

The Best Laid Plans, Part I

One of my readers asked me if I have a formula that I use to develop strategic plans.  While every year and every situation is different, I do have a general outline that I’ve followed that has been pretty successful over the years at Return Path.  There are three phases — input, analysis, and output.  I’ll break this up into three postings over the next three weeks.

The Input Phase goes something like this:

Conduct stakeholder interviews with a few top clients, resellers, suppliers; Board of directors; and junior staff roundtables.  Formal interviews set up in advance, with questions given ahead.  Goal for customers: find out their view of the business today, how we’re serving them, what they’d like to see us do differently, what other products we could provide them.  Goal for Board/staff: get their general take on the business and the market, current and future.

Conduct non-stakeholder interviews with a few industry experts who know the company at least a little bit.  Goal: learn what they think about how we were doing today…and what they would do if they were CEO to grow the business in the future.

Re-skim a handful of classic business books and articles.  Perennial favorite include Good to Great, Contrarian Thinking, and Crossing the Chasm.

Hold a solo visioning exercise.  Take a day off, wander around Central Park.  No phone, no email.  Nothing but thinking about business, your career, where you want everything to head from a high level.

Hold senior staff brainstorming.  Two-day off-site strategy session with senior team and maybe Board.

Next up:  the Analysis Phase.

Counter Cliche:  Who’s The Dog in this Scenario?

Fred’s VC cliche of the week is a good one — “If you lie down with dogs, you’ll come up with fleas.” His point is a good and simple one, that VCs shouldn’t take people risks in deals and shouldn’t try to back management teams they have serious concerns about (ethical or otherwise) in the hopes of trying to change the team or change management.

The obvious counter cliche is that entrepreneurs run that same risk in accepting capital from less-than-savory venture investors.  An ethically-challenged investor can wreak havoc on a young company, potentially tying the company up with peripheral legal problems or even damaging the company’s attempts at raising future rounds of capital.  So, VCs can be the dog in the scenario as well.

But I think there’s a broader counter cliche here, which is that one’s reputation in business is always tied, to some extent, to the company one keeps.  This applies to investors, and also to clients, vendors, and partners.  The appearance of a connection to an unsavory character, even if it’s just an appearance, and even if “unsavory” is in the grey area instead of black-and-white, is almost as problematic as a real connection.

Our business at Return Path is a good illustration of this principle, as is the case with many companies in email marketing, since email marketing has some very visible bad guys (spammers), good guys (think eBay and Expedia), and lots of companies that operate in shades of grey in between.  One of our lines of business, Delivery Assurance Solutions (email deliverability), is particularly critical in terms of us having a great reputation in the industry, since we work on behalf of email marketers to get their mail accepted (not blocked/filtered) at major ISPs.  No matter how you cut it, this business invariably involves making some judgment calls from time to time on who’s a “good guy” vs. a “bad guy” in the email marketing world.

We try to be as clear as possible with our prospects and clients about what kinds of behavior we wil or will not accept from clients, since our reputation in this business is everything to us.  We won’t, for example, help a client with ISP relations or monitoring tools if they don’t sign reps and warrantees in our contract about their email practices that go well beyond CAN-SPAM in terms of compliance with industry best practices.  We can’t accept clients into the Bonded Sender whitelist program unless they jump through all kinds of hoops with our third-party watchdog partner, TRUSTe.  And as painful as it is from a revenue perspective, we do fire clients periodically who we discover to be either not in compliance with their reps and warrantees to us, or who we discover to have a particularly poor reputation in the industry.  All of these things are designed to make sure we stay flea-free.

One area that’s particularly tricky for us is what to do with a “bad guy” who comes to us asking for help to become a “good guy.”  While it’s hard to be completely objective about this type of situation, we have an emerging policy around it.  We WILL work with clients who the world perceives as a “bad guy,” but only on a consulting basis to teach them email best practices and how to become a “good guy” (one of my Board members, Scott Weiss from IronPort Systems, calls this Return Path’s 12-step program).  If those clients take our advice and make meaningful and measurable changes to their email programs, we will continue to work with them and will slowly allow them to use our other services over time.  If those clients resist our advice or are too slow to change their ways, we will stop working with them immediately.

I guess the point of the counter cliche is that sometimes it’s hard to tell, as Sally told Harry in the movie, who is supposed to be the dog in a particular scenario.

• Seth’s Blog: Nine things marketers ought to know about salespeople (and two bonuses)
  Great blog posting from Seth Godin on things the rest of us need to remember about how challenging it is to sell…and a couple pointers for the sales team about how to handle the rest of us!
  (tags: Sales Marketing Management selling)

Highs and Lows

I was reminded recently of one of my favorite entrepreneur sayings.  What drives me nuts isn’t the inevitable presence of highs and lows of running a new company, it’s when they happen at the same time.

It’s one thing to get used to the roller coaster ride of running a startup.  That’s part of the fun and the challenge of it all.  There are great moments when everything’s working beautifully.  Your strategy is proving to be spot-on.  Your team is executing brilliantly.  Your biggest client renews and gives you a testimonial.  Then there are the dark moments of despair.  You’re running out of cash.  The new product release is behind schedule.  A competitor steals a top client.  No one lives for the lows, but you at least grow to anticipate them and realize that "this, too, shall pass."

But the thing I can never get used to is when those highs and lows occur simultaneously.  It just seems unfair.  Let me enjoy the good news — whatever it is — for at least a day or two before clocking me with something terrible!  But perhaps that’s just another, even more poignant part of the humbling process that comes with running a startup.