Sep 112014

The 2×4

The 2×4

I took a Freshman Seminar in my first semester at Princeton in 1988 with a world-renowned professor of classical literature, Bob Hollander.  My good friend and next-door neighbor Peggy was in the seminar with me.  It was a small group — maybe a dozen of us — meeting for three hours each week for a roundtable with Professor Hollander, and then writing the occasional paper.  Peggy and I both thought we were pretty smart.  We had both been high school salutatorians from good private schools and had both gotten into Princeton, right?

Then the first paper came due, and we were both a bit cavalier about it.  We wrote them in full and delivered them on time, but we probably could have taken the exercise more seriously and upped our game.  This became evident when we got our grades back.  One of us got a C-, and the other got either a D or an F.  I can’t remember exactly, and I can’t remember which was which.  All I remember is that we were both stunned and furious.  So we dropped by to see Professor Hollander during his office hours, and he said the same thing to each of us:  “Matt, sometimes you need a 2×4 between the eyes.  This paper is adequate, but I can tell it’s not your best work, it’s decent for high school but not for college, and almost all the others in the class were much more thoughtful.”

Ouch.

Ever since then, Peggy and I have talked about the 2×4, and how it helped us snap out of our own reality and into a new one with a significantly higher bar for quality.  That phrase made it into Return Path‘s lexicon years ago, and it means an equivalent thing — sometimes we have to have hard conversations with employees about performance issues.  The hardest ones are with people who think they are doing really well, when in reality they’re failing or in danger of failing.  That disconnect requires a big wakeup call — the 2×4 between the eyes — before things spiral into a performance plan or a termination.

Delivering a 2×4 between the eyes to an employee can feel horrible.  But it’s the best gift you can give that employee if you want to shake them back onto a successful trajectory.

Aug 142014

How to Manage Your Career

I gave a presentation to a few hundred Return Path employees in January at an all-hands conference we did called “How to Manager Your Career.”

The presentation has three sections — The Three Phases of a Career, How to Get Promoted, and How to Wow Your Manager.

While it’s not as good without the voiceover and interactivity, I thought I’d post it here…see the presentation on Slideshare.

As I said to my audience, if there’s one thing to take away from the topic, it’s this:

Managing your career is up to one, and only one person – you. 

It doesn’t matter how great a corporate culture you have, or how supportive your manager is.  You’re the only person who cares 100% of the time about your career, and you’re the only person with a longitudinal view of what you love, what you’re great at, where you’ve been, and where you want to go.

Jul 172014

The Gift of Feedback, Part IV

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!

Jun 052014

Book short: Life Isn’t Just a Wiki

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.

May 222014

The 90-Day Reverse Review

The 90-Day Reverse Review

Like a lot of companies, Return Path does a 90-day review on all new employees to make sure they’re performing well, on track, and a good fit.  Sometimes those reviews are one-way from the manager, sometimes they are 360s.

But we have also done something for years now called the 90-Day Reverse Review, which is equally valuable.  Around the same 90-day mark, and unrelated to the regular review process, every new employee gets 30 minutes with a member of the Executive Committee (my direct reports, or me if the person is reporting to someone on my team) where the employee has a chance to give US feedback on how WE are doing.

These meetings are meant to be pretty informal, though the exec running the meeting takes notes and circulates them afterwards.  We have a series of questions we typically ask, and we send them out ahead of time so the employee can prepare.  They are things like:

-Was this a good career move?  Are you happy you’re here?

-How was your onboarding experience?

-How do you explain your job to people outside the company?

-What is the company’s mission, and how does your role contribute to it?

-How do you like your manager?  Your team?

-Do you feel connected to the company?  How is the company’s information flow?

-What has been your proudest moment/accomplishment so far?

-What do you like best about the company?

-If you could wave a wand and change something here, what would it be?

We do these for a few reasons:

-At the 90-day mark, new employees know enough about the company to give good input, and they are still fresh enough to see the company through the lens of other places they’ve worked

-These are a great opportunity for executives to have a “Moment of Truth” with new employees

-They give employees a chance to productively reflect on their time so far and potentially learn something or make some course correction coming out of it

-We always learn things, large or small, that are helpful for us as a management team, whether something needs to be modified with our Onboarding program, or whether we have a problem with a manager or a team or a process, or whether there’s something great we can steal from an employee’s past experiences

This is a great part of our Operating System at Return Path!

Apr 242014

Breaking New Ground on Transparency

Breaking New Ground on Transparency

I’ve written a lot over time about our Live 360 process for senior leaders in the business.  (This post is a good one, and it links to a couple earlier ones that are good, as well.)  We take a lot of pride in feedback and in transparency at Return Path, and after 15 years, even for an innovative business, it’s unusual that we do something big for the first time around people.  But we did today.

This image is of something never seen before at our company.  It’s my own handwritten notes about my own Live 360.

360 notes

It’s never been seen before, because no one has ever been physically present for his or her own review before.  In previous reviews, my Board, my exec team, and a few skip-levels gather in a room for 90 minutes with a facilitator to discuss my performance and behaviors.  Then the facilitator would go away and write up notes, and discuss them with me, then I’d produce a development plan.

Today, we decided to experiment with having me sit in my own review to add to the transparency and directness of the feedback.  My only role was to listen, ask (non-judgmental) clarifying questions, and take notes.  I left the room at the end in case someone wanted to say something without me hearing it directly, but although the conversation about the business continued, it didn’t sound like there was anything material about me that surfaced.

It was a little awkward at first, and it was interesting that some people addressed me directly while others spoke of me in the third person.  But once we got past that, the experience was incredibly powerful for me.  The first part — the “what do you appreciate about Matt” part — was humbling and embarrassing and gratifying all at the same time.

The meat of the review, though — the “how can we coach Matt on areas where he needs development” — was amazing.  I got great insights into a couple of major areas of work that I need to do, and that we need to do as a business.  I’m guessing I would have gotten them out of reading a summary of the review conversation, but hearing the texture of the conversation was much, much richer than reading a sanitized version of it on paper.  As always with reviews, there was the odd comment or two that annoyed me, but I felt like I handled them well without any defensive body language or facial expressions.

I will, as I’ve always done, post my development plan to my blog after I formulate it over the course of the next few weeks.  But for now, I just want to thank my Board and team for their awesomely constructive feedback and for helping us usher in a new era of increased transparency here.

Apr 102014

Understanding the Drivers of Success

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?

Filed under: Business, Return Path

Tags: ,

Mar 062014

Open Vacation

At Return Path, we’ve had an “open vacation” policy for years, meaning that we don’t regulate the amount of time off people take, and we don’t accrue for it or pay out “unused” vacation if someone leaves the company.  I get asked about this all the time, so I thought I’d post our policy here and also answer a couple follow-up questions I usually get about it.

First, here’s the language of our policy:

Paid Time Off

You’re encouraged to take as much time off as you can while maintaining high performance and achieving your goals. We don’t count the hours you work, so why should we count the hours you don’t? (Unless you’re a non-exempt employee, and only then because we have to!) Take what you need, when you can, and make sure to arrange coverage with your team. If you haven’t had a vacation in a while, you can expect to get a friendly nudge from your manager to get away from the office!

Use your Paid Time Off (PTO) for planned vacations, days off for appointments, religious, or personal holidays that are not offered in your country, community service days, or if you need an unanticipated, last-minute day off to care for a sick child or family member. Statutory or legally protected leaves of absence, such as medical leave, maternity/parental leave, family medical leave or unpaid leave, are governed by separate regulations that will not be affected by our PTO policy. See the Regional section for a list of statutory leaves of absence in your country.

Paid Time Off scheduling is subject to approval by your manager, who has sole discretion to approve or deny requests under this policy. Requests of greater than two consecutive weeks or more than two weeks in one three-month period require approval of your Executive Committee member.

The first question I always get is, “Wow – does that really work?  What issues have you had with it?  My response:

No issues with it at all, other than it’s a little weird to apply internationally, where we have 50 people across 7 countries, since most of those countries have significantly more generous vacation policies/customs than the US.  But we generally make it work.

The second question I get is whether people abuse it or not:

In all the years we’ve done it, we only ever had one person attempt to abuse the policy, one time.  People do still have to ask their managers if it’s ok to take time off, and they do still have to get their jobs done.

Finally, people ask me for general advice on implementing this kind of policy:

Continue to track days off and generate reports for managers every quarter so they at least know whether their people are taking not enough or too much – generally people will take not enough, and you will need to encourage them to take more.  Also, our managers were *really* worried about launching this, so we had to do some hand-holding along the way. 

The results of this policy for us have generally been great.  People take about the same amount of true vacation they used to take, maybe a little more.  They definitely take more half-days and quarter-days where they probably still get a full day worth of work done, without worrying about counting the hours.  Best of all, there’s a strong signal sent and received with this kind of policy that we trust our team members to do what they need to do in order to live their lives AND get their jobs done.

Jan 302014

New New Employee Training

Years ago, my co-founder Jack and I developed a training presentation to give to new employees who were not just new to Return Path but also new to the workforce.  This is another one of those things, like my last post on our sabbatical policy, that people ask me for all the time.

Bringing new people into the workforce is different from just bringing new people into an organization.  I know I got a huge amount of value in my first job in management consulting from just learning how to go to work every day and how to be successful professionally.  The process you need to go through is like Onboarding, but on steroids.

Not everyone has parents or older siblings or role models who work in business — or for that matter, who focus on any kind of workplace mentoring.  It may sound dumb, but even things like showing up on time for work, what to wear, and how to meet with your manager aren’t necessarily obvious even to smart and well-intentioned 21-year olds.

So with the caveats that it’s a little dated as is, and that it’s more relevant to the kind of company we are at Return Path (e.g., we serve business clients), here’s a SlideShare version of the presentation.



Feel free to plagiarize, customize, and share it from here if you’re interested.

Jan 022014

Sabbaticals

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!

css.php