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.

Alter Ego

A couple people have asked me recently how I work with an Executive Assistant, what value that person provides, and even questioned the value of having that position in the company in an era where almost everything can be done in self-service, lightweight ways. At my old company (in the 90s), each VP-level person and up had a dedicated assistant – the world certainly doesn’t require that level of support any more.  In our case, Andrea has other tasks for the company that take up about half of her time.

I happen to have the absolute best, world class role model assistant in Andrea, who I’ve had the pleasure of working with for almost seven years now (which is a reminder to me that she has a sabbatical coming up soon!).

This is an important topic.  It’s tempting for CEOs of startups, and even companies that are just out of the startup phase, to want to do it all themselves…or feel like they don’t need help on small tasks.  My argument against those viewpoints is that your time is your scarcest resource as the leader of an organization, and anything you can do to create more of it for yourself is worthwhile.  And a good assistant does just that – literally creates time for you by offloading hundreds of small things from your plate that sure, you could do, but now you don’t have to.

I asked Andrea to write up for me a list of the major things she does for me (although she didn’t realize it was going to turn into a blog post at the time).  I’ll add my notes after each bullet point in italics on the value this creates for me.

• Updates and maintains calendar, schedules meetings and greets visitors – My calendar is like a game of sudoku sometimes.  I can and do schedule my own things, but Andrea handles a lot of it.  She also has access to all my staff’s calendars so she can just move things around to optimize for all of us.  Finally, she and I review my calendar carefully, proactively, to make sure I’m spending my time where I want to spend it (see another item below)
• Answers and screens direct phone line – The bigger we get, the more vendors call me. I can’t possibly take another call from a wealth management person or a real estate broker.  Screening is key for this!
• Plans and coordinates company-wide meetings and events – This is an extension of managing my calendar and accessing other executives’ calendars…and a pretty key centralized function.
• Plans and coordinates Executive Committee offsite’s – Same, plus as part of my theme of “act like you’re the host of a big party,” I like this to be planned flawlessly, every detail attended to.  I do a lot of that work with Andrea, but I need a partner to drive it.
• Collects and maintains confidential data – Every assistant I’ve ever had starts by swearing an oath around confidentiality.
• Prepares materials for Board Meetings and Executive Committee meetings – Building Board Books is time consuming and great to be able to offload.  We put together the table of contents, then everyone pours materials into Andrea, and poof!  We have a book.  For staff meetings, she manages the standing agenda, changes to it, and the flow of information and materials so everyone has what they need when they need it to make these meetings productive from start to finish.  In our case, Andrea is part of the Executive Committee and joins all of our meetings so she is completely up to speed on what’s going on in the company – this really enables her to add value to our work.  She’s also not just a passive participant – some great ideas have come from her over the years!
• Coordinates and books travel (domestic and international) – Painful and time consuming, not because Expedia is hard to use but because there is a lot of change, complexity, and tight calendars to manage and coordinate for certain trips.  And while it takes a while to get an assistant up to speed on how you like to travel or how you think about travel, this is a big time saver.
• Prepares expense reports – Same thing – you CAN do it, but easier not to.
• Manages staff gifts and Anniversary presents for all employees – This is a big one for me.  I send every employee an anniversary gift each year and call them.  Once a month, a stack of things to sign magically appears on my desk…and then gets distributed.  Andrea manages the schedule, the inventory of gifts, the distribution of gifts to managers.
• Manages investor database – I assume someday we’ll have a system for this, but for now, IR is a function that Andrea coordinates for me and Jack, my CFO.
• Assist Executive Committee with project as needed – The person in this role for you ends up being really valuable to help anyone on your staff with major projects.  Good use of time.
• Prepares Quarterly Time Analysis for CEO – This is a big one for me.  Every quarter, Andrea downloads my calendar and classifies all of my time, then produces an analysis showing me where I’m spending time my classifications are – Internal, External, non-RP, free, travel, Board/Investor.  This really helps us plan out the next quarter so I’m intentional about where I put my hours, and then it helps her manage my calendar and balance incoming requests.
• Help with communications – This one was not on Andrea’s list, but I’m adding it.  She ends up drafting some things for me (sometimes as small as an email, sometimes as large as a presentation, though with a lot more guidance), which is helpful…it’s always easier to edit something than create it.  I also usually ask Andrea to read any emails I send to ALL ahead of time to make sure they make sense from someone’s perspective other than my own, and she’s very helpful in shaping things that way.

This may not be true of all companies at all sizes and stages, but for companies like ours, I’d classify a great assistant as a bit of an alter ego, one definition of which is “second self” – literally an extension of you as CEO.  That means the person is acting AS YOU, not just doing things FOR YOU.  Think about the transitive property here.  Everything you do as CEO is (in theory) to propel the whole company forward.  So everything your alter ego does is the same.  A great assistant isn’t just your administrative assistant.  A great assistant is an overall enabler of company success and productivity.  You do have to invest a lot of time in getting someone up to speed in this role for them to be effective, and you have to pay well for performance, but a great assistant can literally double your productivity as CEO.

Marketers have blinders on when it comes to some aspects of data. We‘re so focused on using it to build relationships and businesses, that we don’t pay enough attention to data’s inherent risks. Those risks are real, though. Our brands are constantly under attack, and even trivial oversights in data handling can leave us—and our customers—unacceptably vulnerable. We need to better understand the risks. We need to know more.

If marketers don’t develop industrywide expertise in all aspects of data use, if we can’t demonstrate that we can be trusted stewards of information, we risk losing our rights to use it. The DMA is taking the lead to make sure that we, as an industry, gain the knowledge we need: It’s Institute for Data Governance and Certification  is a badly needed program that can make a real difference.

The Institute is a three-day intensive for marketers to learn how to protect their customers and their brands while using the power of data to connect with consumers—and ultimately to grow. The first course begins on July 18^th in New York, with more scheduled across the country over the next year.

As many of you know, I chair the DMA’s board, so I’m not a neutral third party when I urge you to attend the Institute and get certified in marketing data governance. But if I’m biased it’s because I’m a passionate industry advocate and I believe that marketers should lead the global effort to champion intelligent, responsible data use. Before we can start, we all need to know what that means.

Please click here to learn more about how you can register for the DMA’s Institute for Data Governance and Certification.

Closer to the Front Lines

When we started Return Path, we added a little clause to our employee handbook that entitled people to a sabbatical after 7 years of service (and then after every 5 incremental years).  Six weeks off, 3/4 pay.  Full pay if you do something “work related.”  Sure, we thought.  That’s an easy thing to give.  We’ll never be 7 years old as a company. 

Now, 8 1/2 years later, of course, the first wave of people are reaching their sabbatical date.  A couple have already gone (one trip around the world, one quality time with the kids).  A couple others are pending.  Four of us at the exec level are overdue to take ours, and we all committed to take them this year, planning them out so we can back each other up.  My colleague George Bilbrey is in the middle of his 6 weeks off now, and I’m his backup.  And wow – is it a great experience.  Busy, but great.

The reason it’s great is that I am one step closer to the action.  Usually when someone on my team goes on vacation, we just let things run for that week or two.  The people who report into that exec know I’m around if they need something, but I don’t take over actively working with them.  Not so this time.  Six weeks is too long for that.  I’m actively subbing for George.  I’m sitting in his office in Colorado every other week for the sabbatical.  I have weekly meetings with his staff.  I’m working with them on their Q2 goals (for added fun, we’re even working on George’s Q2 goals!).  I’m attending meetings that George usually attends but that I’m not invited to.

The insight I’m getting into things in George’s area of the business is great.  I’m learning more about the ins and outs of everyone’s work, more about the team dynamic, and more about how the team works with other groups in the company.  Most important, I’m learning more about how George and I interact, and how I can manage that interaction better in the future.  And I’m making or suggesting some small changes here and there on the margin.  Hopefully I’m not messing things up too badly.  Otherwise, I will hear about it in 3 1/2 weeks!

I strongly encourage everyone who is a Manager of Managers or higher in their company (especially if that company’s name rhymes with Geturn Fath) to use any vacation of someone on their team as an excuse to really substitute and get closer to the front lines.

Closure

This past weekend was a weekend of closure for me. As I prepare to leave the city after almost 17 years and the apartment I’ve lived in for almost 15, we had my two original roommates from this apartment in town for the weekend with their families for a bit of a farewell party. Times certainly have changed – from three single guys to three families and 7, almost 8 kids between us. Sitting around and noting that all three couples had either gotten engaged or first started dating within the confines of Apartment 35B, then saying goodbye as everyone left the apartment for the last time, was a little surreal. But overall, having everyone around was great fun and was a fitting way to mark the occasion.

If that wasn’t enough to drive the point home, we were lucky enough to get tickets to the Yankees game last night, which was the last home game the Yanks will play in their 85-year old stadium before moving across the street next season to their fancy new home. The ceremony before the game, which featured a bunch of prominent Yankee greats and their progeny (Babe Ruth’s daughter threw out the opening pitch!), was similarly surreal, but a fitting ending to a long-standing tradition.

Why is closure important? I’m not a psychologist, but for me and my brain anyway, celebrating or formally noting the END of something helps move on to the BEGINNING of the next thing. It helps compartmentalize and define an experience. It provides time to reflect on a change and WHY it’s (inevitably) both good and bad. And I suppose it appeals to the sentimentalist in me.

I think it’s important to create these moments in business as well as in one’s personal life. We and I have done them sporadically at Return Path over the years. Moving offices as we expand. Post-mortems on projects gone well or badly. Retrospectives with employees who didn’t work out, sometimes months after the fact. Whether the moment is an event, a speech at an all-hands meeting, or even just an email to ALL, one of the main jobs of a leader in building and driving a corporate culture is to identify them and mark them.

Reverse Engineering Venture Economics

An Execution Problem

My biggest takeaway from the TED Conference this week is that we — that is to say, all of us in the world — have an execution problem.  This is a common phrase in business, right?  You’ve done the work of market research, positioning, and strategy and feel good about it.  Perhaps as a bigger company you splurge and hire McKinsey or the like to validate your assumptions or develop some new ones.  And now all you have to do is execute — make it happen.  And yet so many businesses can’t make the right things happen so that it all comes together.  I’d guess, completely unscientifically, that far, far more businesses have execution problems than strategic ones.  Turns out, it’s tough to get things to happen as planned BUT with enough flexibility to change course as needed.  Getting things done is hard.

So what do I mean when I say that humanity has an execution problem?  If nothing else, the intellectual potpourri that is TED showed me this week that we know a lot about the world’s problems, and we don’t lack for vision and data on how to solve them.  A few of the things we heard about this week are the knowledge — and in many cases, even real experiences — about how to:

– Steer the evolution of deadly disease-causing bacteria to make them more benign within a decade

– Build world class urban transportation systems and growth plans to improve urban living and control pollution

– Drive down the cost of critical pharmaceuticals to developing nations by 95%

– Dramatically curb CO2 emissions

We have the knowledge, and yet the problems remain unsolved.  Why is that?  Unlike the organized and controlled and confined boundaries of a company, these kinds of problems are thornier to solve, even if the majority of humans agree they need to be solved.  Whether the roadblock is political, financial, social — or (d) all of the above — we seem to be stuck in a series of execution problems.

The bright spot out of all of this (at least from this week’s discussions) is that, perhaps more than ever before in the history of mankind, many of our most talented leaders AND our wealthiest citizens are taking more of a personal stake in not just defining the problems and solutions, but making them happen.  They’re giving more money, buiding more organizations, and spending more time personally influencing society and telling and showing the stories.  It will take years to see if these efforts can solve our execution problems, but in the meantime, the extraordinary efforts are things we can all be proud of.

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.

It’s a Little Weird When Your Best Customer Experience of the Week is with the Government

Mariquita has been doing a lot of personal admin lately for us.  This week had a little surprise in it.

Verizon continues to be one of the most awful, painful vendors in the history of the universe.
At least their phone network is solid, since any interaction with the people at the company is so bad.  We came to the conclusion this week that they actually do some things which aren’t just the usual bad customer service or outrageous pricing — they have some policies in place that are literally designed to systematically rip off their customers.  The one we ran into was (after 45 minutes on and off hold, of course) that the data plans for Treos are prepaid for a month, but when you go to cancel your data plan, they tell you they HAVE TO cancel it the day you call, even if you have days or weeks left on your plan, and they CAN’T issue a refund for unused days.  But if you complain loudly enough, a supervisor can keep your service active through the end of your pre-pay, or can issue you a refund.  So in fact, they are telling their customer service reps to lie to their customers in the hope that their customers don’t push back so they can keep your money while not delivering your service.

She had a similarly bad experience dealing with our insurance company about car insurance.  State Farm just has a ridiculous set of procedures in place around changing car insurance that cause their customers to jump through hoops several times over for no apparent reason at all.  There have been several stupid things, but this week was needing to take a brand new car to get inspected before insuring it within three days of buying it.  But we had to take it to a specific mechanic on the “approved list” to get it inspected.  That place required an appointment (which meant two trips).  It couldn’t be done at the dealer.  Then the actual inspection lasted about 30 seconds.  Maybe they were just making sure there was an actual car, not a pretend car.  Harry Potter, beware.

And then came the surprise — Mariquita’s trip to the DMV to trade in our old license plates.  She was in and out in under 5 minutes with a prompt, efficient, friendly person handling the transaction with a smile.  Wonders never cease.

It doesn’t take a lot to be great at customer service, just the right mindset and culture.  It’s amazing that Albany (or at least a small pocket therein) seems to have figured that out before some of the biggest companies around.

I read a ton of books.  I usually blog about business books, at least the good ones.  I almost never blog about fiction or non-business/non-fiction books, but I had a good “what did you read this summer” conversation the other night with my CEO Forum, so I thought I’d post super quick snippets about my summer reading list, none of which was business-related.

If you have kids, don’t read Sheryl Sandberg and Adam Grant’s Option B:  Facing Adversity, Building Resilience, and Finding Joy unless you’re prepared to cry or at least be choked up.  A lot.  It is a tough story to read, even if you already know the story.  But it does have a number of VERY good themes and thoughts about what creates resilience (spoiler alert – my favorite key to resilience is having hope) that are wonderful for personal as well as professional lives.

Underground Airlines, by Ben Winters, is a member of a genre I love – alternative historical fiction.  This book is set in contemporary America – except that its version of America never had a Civil War and therefore still has four slave states.  It’s a solid caper in its own right, but it’s a chillingly realistic portrayal of what slavery and slave states would be like today and what America would be like with them.

Hillbilly Elegy, by J.D. Vance, is the story of Appalachia and white working class Americans as told by someone who “escaped” from there and became a marine, then a Yale-educated lawyer.  It explains a lot about the struggles of millions of Americans that are easy for so many of us to ignore or have a cartoonish view of.  It explains, indirectly, a lot about the 2016 presidential election.

Everybody Lies:  Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are, written by Seth Stephens-Davidowitz, was like a cross between Nate Silver’s The Signal and The Noise and Levitt & Dubner’s Freakonomics.  It’s full of interesting factoids derived from internet data.  Probably the most interesting thing about it is how even the most basic data (common search terms) are proving to be great grist for the big data mill.

P.J. O’Rourke’s How the Hell Did This Happen? was a lot like the rest of P.J. O’Rourke’s books, but this time his crusty sarcasm is pointed at the last election in a compilation of articles written at various points during the campaign and after.  It didn’t feel to me as funny as his older books.  But that could also be because the subject was so depressing.  The final chapter was much less funny and much more insightful, not that it provides us with a roadmap out of the mess we’re in.

Sapiens: A Brief History of Humankind, by Noah Harari, is a bit of a rambling history of our species.  It was a good read and lots of interesting nuggets about biology, evolution, and history, though it had a tendency to meander a bit.  It reminded me a bit of various Richard Dawkins books (I blogged a list of them and one related business topic here), so if you’re into that genre, this wouldn’t be bad to pick up…although it’s probably higher level and less scientific than Dawkins if that’s what you’re used to.

Finally, I finished up the fourth book in the massive Robert Caro quadrilogy biography of Lyndon Johnson (full series here).  I have written a couple times over the years about my long-term reading project on American presidential biographies, probably now in its 12th or 13th year.  I’m working my way forward from George Washington, and I usually read a couple on each president, as well as occasional other related books along the way.  I’ve probably read well over 100 meaty tomes as part of this journey, but none as meaty as what must have been 3000+ pages on LBJ.  The good news:  What a fascinating read.  LBJ was probably (with the possible exception of Jefferson) the most complex character to ever hold the office.  Also, I’d say that both Volumes 3 and 4 stand alone as interesting books on their own – Volume 3 as a braoder history of the Senate and Civil Rights; Volume 4 as a slice of time around Kennedy’s assassination and Johnson’s assumption of power.  The bad news:  I got to the end of Vol 4 and realized that there’s a Vol 5 that isn’t even published yet.

That’s it for summer reading…now back to school!

Patience and Impatience are both critical tools in the founder toolbelt. That sounds kind of funny since they’re at odds with each other. Let me explain.

Patience is hard, but there are some things that require it. As they say metaphorically about Product, nine women can’t make a baby in a month. Products needs to be built, tested in the wild, marinate with clients. GTM motions take time to figure out. Brands take time to build unless you have billions to throw at the problem. Bread takes time to rise.  Patience is a really useful tool when people on your team or board get itchy for success and you need to calm them down and keep them focused.

Impatience, on the other hand, is easy, and you have to moderate it. Once we have a vision…don’t we want it to become reality yesterday? Why is that roadmap item taking so damn long? Where’s the blog post? We already agreed to terms on the financing, why do the lawyers need to take 60 days and $50,000 to paper it?

How do you know when to use which tool?

Be patient with the seemingly impossible – changing the world, changing people’s habits, changing thoughts and perceptions all take time. But be impatient with those eminently possible and important items – the things someone on the team or you need to knock off a to do list to advance the business.

Most of all, be impatient for success and tangible signs of progress. Turning your vision into a viable business requires that kind of fire within you.