Everything is Data, Part II – Get Those Expenses In

My friend and former colleague Angela Baldonero (used to run our People Team at Return Path, now is COO of super cool startup Procurify), used to say about her job as head of HR, “Everything is Data.”  She guest blogged about that principle on OnlyOnce years ago here , and she particularly cited this theory when talking about the recruiting and hiring process.

I’ve thought about this principle a lot over the years, and I’ve occasionally come up with other examples where I think peripheral data can inform whether or not an employee will succeed, at least in my world.  I don’t know how many of these can be caught in an interview process, but that’s worth thinking about.  Here’s one for today’s post:  I’ve noticed a very high correlation over the years between poor performance and being late turning in expenses.

I know, it sounds silly.  But think about it.  Most of the work we do involves some level of being organized, being on time, prioritizing work and working efficiently, and caring about money (whether the company’s money or our own money).  Someone who can’t bother to fill out a quick expense report following a business trip is demonstrating an absence of all of those traits.  The most glaring example of it we ever had here involved a fairly senior sales executive years ago who was delinquent in his expenses to the tune of over $40,000.  That’s right, $40,000.  It was so bad that our auditors made us footnote it in our annual audit.  We begged him to turn in his expenses.  We even offered to have him send a pile of all the receipts to us and have someone in Accounting help him out.  But he was always too busy, made too many excuses for why he couldn’t get them done.  I think it ended up taking us firing him for him to actually clean them up and get paid back.  Why did we fire him?  He was ineffective in his role, unresponsive to colleagues, unable to prioritize his work, and sloppy in his deliverables.

By the way, the opposite is not true – someone who is incredibly punctual about getting expenses in is not guaranteed to be a high performer, although they are usually guaranteed to at least be organized (which for some roles may be a critical success factor).

I suppose ultimately this is just another example of Broken Windows, which I blogged about in two different places, here and here.

A Community of Employees

One of the most memorable moments in a valedictorian speech that I’ve heard or read was at my sister-in-law’s graduation from Northwestern about 10 years ago. The speaker’s closing line was something like “Most of all, when you go out into the world, remember to be kind to other people.  It’s one of the best things you can do for the world.”

It’s not as if people are generally trained or predisposed to be UNkind to each other. But respecting other people and being kind to them is sometimes elusive in our busy lives. I think one of the things that makes Return Path more of a community and less of just a “place of work” is this one of our 13 core values:

We are obsessively kind to and respectful of each other

Kindness and respect in the workplace start with the seemingly trivial.  Holding doors open for colleagues, cleaning the coffee machine, helping someone lug a big jug of water and lift it onto the dispenser, and saying a simple “thank you” or “well done” here and there are all acts of kindness and respect. These might seem trivial, but don’t discount the trivial in life.  Being vigilant about the small things sets the right tone for the big things, sort of like the “broken windows” theory of policing says about crime. An atmosphere where people seek out opportunities to help with things like the coffee machine is likely an atmosphere where people seek out opportunities to collaborate on solving problems or cover for a vacationing colleague.

The small things lead to the big things.  We take fit incredibly seriously here.  Fit doesn’t mean that we all have to be the same type of person, or that we all have to like the same kinds of food.  But it means that you have to be kind.  You can be totally frank and direct and challenge authority (more about that in a future post) and still be kind and respectful.  Being a Bull in a China Shop doesn’t work here.

And that’s the difference between a pace to work and a community.

Pret a Manager

My friend James is the GM of the Pret a Manger (a chain of about 250 “everyday luxury” quick service restaurants in the UK and US) at 36th and 5th in Manhattan.  James recently won the President’s Award at Pret for doing an outstanding job opening up a new restaurant.  As part of my ongoing effort to learn and grow as a manager, I thought it would be interesting to spend a day shadowing James and seeing what his operation and management style looked like for a team of two dozen colleagues in a completely different environment than Return Path.  That day was today.  I’ll try to write up the day as combination of observations and learnings applied to our business.  This will be a much longer post than usual.  The title of this post is not a typo – James is “ready to manage.”

1. Team meeting.  The day started at 6:45 a.m. pre-opening with a “team brief” meeting.  The meeting only included half a dozen colleagues who were on hand for the opening, it was a mix of fun and serious, and it ended with three succinct points to remember for the day.  I haven’t done a daily huddle with my team in years, but we do daily stand-ups all across the company in different teams.  The interesting learning, though, is that James leaves the meeting and writes the three points on a whiteboard downstairs near the staff room.  All staff members who come in after the meeting are expected to read the board and internalize the three points (even though they missed the meeting) and are quizzed on them spontaneously during the day.  Key learning:  missing a meeting doesn’t have to mean missing the content of the meeting.

2. Individual 1:1 meeting.  I saw one of these, and it was a mix of a performance review and a development planning session.  It was a little more one-way in communication than ours are, but it did end up having a bunch of back-and-forth.  James’s approach to management is a lot of informal feedback “in the moment,” so this formal check-in contained no surprises for the employee.  The environment was a little challenging for the meeting, since it was in the restaurant (there’s no closed office, and all meetings are done on-site).  The centerpiece of the meeting was a “Start-Stop-Continue” form.  Key learning:  Start-Stop-Continue is a good succinct check-in format.

3. Importance of values.  There were two forms of this that I saw today.  One was a list of 13 key behaviors with an explanation next to each of specific good and bad examples of the behavior.  The behaviors were very clear and were “escalating,” meaning Team Members were expected to practice the first 5-6 of them, Team Leads the first 7-8, Managers the first 10, Head Office staff the first 12, Executives all 13 (roughly).  The second was this “Pret Recipe,” as posted on the public message board (see picture below).  Note – just like our values at Return Path, it all starts with the employee.  One interesting nugget I got from speaking to a relatively new employee who had just joined at the entry level after being recruited from a prominent fast food chain where he had been a store general manager was “Pret really believes this stuff — no lip service.”

I saw the values in action in two different ways.  The first was on the message board, where each element of the Pret Recipe was broken out with a list of supporting documents below it, per the below photo.  Very visual, very clear.

The second was that in James’s team meeting and in his 1:1 meeting, he consistently referenced the behaviors.  Key learning:  having values is great, making them come to life and be relevant for a team day-in, day-out is a lot harder but quite powerful when you get it right.

4. Managing by checklist.  I wrote about this topic a while ago here, but there is nothing like food service retail to demand this kind of attention to detail.  Wow.  They have checklists and standards for everything.  Adherence to standards is what keeps the place humming.  Key learning:  it feels like we have ~1% of the documentation of job processes that Pret does, and I’m thinking that as we get bigger and have people in more and more locations doing the same job, a little more documentation is probably in order to ensure consistency of delivery.

5. Extreme team-based and individual incentive compensation.  Team members start at $9/hour (22% above minimum wage that most competitors offer).  However, any week in which any individual store passes a Mystery Shopper test, the entire staff receives an incremental $2/hour for the whole week.  Any particular employee who is called out for outstanding service during a Mystery Shop receives a $100 bonus, or a $200 bonus if the store also passes the test.  The way the math works out, an entry level employee who gets the maximum bonus earns a 100% bonus for that week.  But the extra $2/hour per team member for a week seemed to be a powerful incentive across the board.  Key learning: team-based incentive comp is something we use here for executives, but maybe it’s worth considering for other teams as well.

6. Integrated systems.  Pret has basically one single software system that runs the whole business from inventory to labor scheduling to finances.  All data flows through it directly from point of sale or via manager single-entry.  All reports are available on demand.  The system is pretty slick.  There doesn’t seem to be much use of side systems and side spreadsheets, though I’m sure there are some.  Key learning: there’s a lot to be said for having a little more information standardized across the business, though the flip side is that this system is a single point of failure and also much less flexible than what we have.

7. Think time.  I’ve written a little about working “on the business, not in the business,” or what I call OTB time, once before, and I have another post queued up for later this summer about the same.  Brad Feld also very kindly wrote about it in reference to Return Path last week.  Working in retail means that time to work on IMPORTANT BUT NOT URGENT issues is extremely hard to come by and fragmented.  I suspect that it comes more at the end of the day for James, and it probably comes a lot more when he doesn’t have someone like me observing him and asking him questions.  But his “office” (below), exposed to the loud music and sounds and smells of the kitchen, certainly doesn’t lend itself to think time!  Key learning:  of course customers come first, but boy is it critical to make space to work OTB, not just ITB.  Oh, and James needs a new chair that’s more ergonomically compatible with his high countertop desk.

Years ago, I spent a few weekends working in my cousin Michael’s wine store in Hudson, NY, and I wrote up the experience in two different posts on this blog, the first one about the similarities between running a 2-person company and a 200-person company, and the second one about how in a small business, you have to wear one of every kind of hat there is.  My conclusion then was that there are more similarities than differences when it comes to running businesses of different types.  My conclusion from today is exactly the same, though the focus on management made for a very different experience.

Thanks to James, Gustavo, Orlanda, Shawona, and the rest of the team at the 36th & 5th Pret for putting up with the distraction of me for the bulk of the day today — I learned a lot (and particularly enjoyed the NYC Meatball Hot Wrap) and now have to figure out how to return the favor to you!

How to Get Laid Off – an Employee’s Perspective

One of my colleagues at Return Path  saw my post about How to Quit Your Job about 5 years ago and was inspired to share this story with me.  Don’t read anything into this post, team!  There is no other meaning behind my posting it at this time, or any time, other than thinking it’s a very good way of approaching a very difficult situation, especially coming from an employee.

In 2009 I was working at a software security start up in the Silicon Valley.  Times were exceedingly tough, there were several rounds of layoffs that year, and in May I was finally on the list. I was informed on a Tuesday that my last day was that Friday.  It was a horrible time to be without a job (and benefits), there was almost no hiring at all that year, one of the worst economic down turns on record.  While it was a hard message,  I knew that it was not personal, I was just caught up on a bad math problem.

After calling home to share the bad news, I went back to my desk and kept working. I had never been laid off and was not sure what to do, but I was pretty sure I would have plenty of free time in the short term, so I set about figuring out  how to wrap things up there.  Later that day the founder of the company came by, asked why I had not gone home, and I replied that I would be fine with working till the end of the week if he was okay with it.  He thanked me.

Later that week, in a meeting where we reviewed and prioritized the projects I was working on, we discussed who would take on the top three that were quite important to the future of the company.  A few names were mentioned of who could keep them alive, but they were people who I knew would not focus on them at all.  So I suggested they have me continue to work on them, that got an funny look but when he thought about it , it made sense, they could 1099 me one day a week.  The next day we set it up.  I made more money than I could of on unemployment, but even better I kept my laptop and work email, so I looked employed which paid off later. 

That one day later became two days and then three, however, I eventually found other full time work in 2010.  Layoffs are hard,  but it is not a time to burn bridges.   In fact  one of the execs of that company is a reference and has offered me other opportunities for employment.

Ratcheting Up Is Hard To Do (or Boiling the Frog, Part II)

I’ve had to ratchet down business several times over the years at Return Path.  Times were tough, revenues weren’t coming as fast as promised, my investors and I were growing weary, the dot com crash, etc. etc.  We had layoffs, consolidated jobs, cut salaries multiple times, made people wear 8 hats to get the job done.  It’s an awful process to go through.

In the last year or so, business has finally started going much better.  We’ve been fortunate in many ways that we’re still around, with products that work really well, with a good customer base, and with good and patient investors and employees, as the business climate has improved.  We’ve grown from 22 people (at our low point) up to almost 75.  But what that has meant for our organization is that we’ve had to quickly "ratchet back up," adding people, adding new functions that were previously one of many hats worn by a single person, operating at a different level.  While ratcheting down is a nightmare, it turns out that quickly ratcheting back up is in many ways just as hard on the organization.

Some examples:

– IT (internal email and servers) has been run by a part-time resource and "off the side of the desk" of our product development engineering department.  Now it is almost completely broken, and it turned out we hired a very talented IT manager, probably about three months too late.

– Staffing up is particularly tough without a dedicated HR function and with a legacy of missed budgets.  HR has been done off the side of the desk of me and my executive assistant, and we can’t keep pace any more with all the recruiting, hiring, training, and development planning.  Now that we feel like we need and can afford more staff, we need to hire an HR manager to handle it all, but we need someone in place and trained today, not three months from now.

– A 22 person company can function brilliantly as a network of Individual Contributors who loosely coordinate with each other.  But now what we need at 75 is a a few hardcore Managers that can build systems and processes so that the whole machine runs smoothly.  We don’t necessarily have those people in-house, and if we bring them in from the outside, I’m left wondering if the Individual Contributors will feel like their years of hard work aren’t appreciated if there’s a new layer of management surrounding them.

I hope we never have to ratchet down again…but part of the reason why now is that I never want to have to ratchet back up, either!

Thanks to my COO and business partner Jack Sinclair for his help with this posting.

New People Electrify the Organization

We had a good year in 2009, but it was tough.  Whose wasn’t?  Sales were harder to come by, more existing customers left or asked for price relief than usual, and bills were hard to collect.  Worse than that, internally a lot of people were in a funk all year.  Someone on our team started calling it “corporate ennui.”  Even though our business was strong overall and we didn’t do any layoffs or salary cuts, I think people had a hard time looking around them, seeing friends and relatives losing their jobs en masse, and feeling happy and secure.  And as a company, we were doing well and growing the top line, but we froze a lot of new projects and were in a bit of a defensive posture all year.

What a difference a year makes.  This year, still not perfect, is going much better for us.  Business conditions are loosening up, and many of our clients have turned the corner.  Financially, we’re stronger than ever.  And most important, the mood in the company is great.  I think there are a bunch of reasons for that – we’re investing more, we’re doing a ton of new innovation, people have travel budgets again, and people see our clients and their own friends in better financial positions.

But by far, I think the most impactful change to the organizational mood we’re seeing is a direct result of one thing:  hiring.  We are adding a lot of new people this year – probably 60 over the course of the year on top of the 150 we had at the beginning of the year.  And my observation, no matter which office of ours I visit, is that the new people are electrifying the organization.  Part of that is that new people come in fresh and excited (perhaps particularly excited to have a new job in this environment).  Part of it is that new people are often pleasantly surprised by our culture and working environment.  Part of it is that new people come in and add capacity to the team, which enables everyone to work on more new things.  And part of it is that every new person that comes in needs mentoring by the old timers, which gives the existing staff reminders and extra reason to be psyched about what they’re doing, and what the company’s all about.

Whether it’s one of these things or all of them, I’m not sure I care.  I’m just happy the last 18 months are over.  The world is a brighter place, and so is Return Path.  And to all of our new people (recent and future), welcome…thanks for reinvigorating the organization!

A Perfect Ten

Return Path turns 10 years old today.  We are in the midst of a fun week of internal celebrations, combined with our holiday parties in each office as well as year-end all-hands meetings.  I thought I would share some of my reflections on being 10 in the blog as I’ve shared them with our team. What being 10 means to me – and what’s enabled us to make it this long:

• It means we’ve beaten the odds.  Two major global economic meltdowns.  The fact that 90% of new small businesses fail before they get to this point.  Probably a higher percentage of venture backed startups fail before they get to 10 as well
• We’ve gotten here because we’ve been nimble and flexible.  Over our 10 years, we’ve seen lots of companies come and go, clinging to a model that doesn’t work.  We may have taken a while and a few iterations to get to this point, but as one of my Board members says, “we’re an overnight success, ten years in the making!”
• We’ve also made it this long because we have had an amazing track record with our three core constituencies – employees, clients, and investors – including navigating the sometimes difficult boundaries or conflicts between the three

What I’m most proud of from our first decade:

• We’ve built a great culture.  Yes, it’s still a job.  But for most of our team members most of the time, they like work, they like their colleagues, and they have a fun and engaging time at work.  That’s worth its weight in gold to me
• We’ve built a great brand and have been hawkish about protecting our reputation in the marketplace.  That’s also the kind of thing that can’t be bought
• We haven’t sacrificed our core principles.  We’ve always, going back to our founding and the ECOA business, had a consumer-first philosophy that runs deep.  This core principle continues to serve us well in deliverability (a non-consumer-facing business) and is clearly the right thing to do in the email ecosystem

What I most regret or would do differently if given the chance:

• We have not raised capital as efficiently as possible – mostly because our company has shifted business models a couple of times.  Investors who participated in multiple rounds of financing will do very well with their investments.  First or second round angel investors who didn’t or couldn’t invest in later rounds will lose money in the end
• I wish we were in one location, not five.  We are embracing our geographic diversity and using it to our advantage in the marketplace, but we pay a penalty for that in terms of travel and communication overhead
• We have at times spread ourselves a little too thin in pursuit of a fairly complex agenda out of a relatively small company.  I think we’re doing a good job of reigning that in now (or growing into it), but our eyes have historically been bigger than our stomachs

Thanks to all our investors and Board members, especially Greg Sands from Sutter Hill Ventures, Fred Wilson from Flatiron Partners and Union Square Ventures, Brad Feld from Mobius Venture Capital, and Scott Weiss for their unwavering support and for constantly challenging us to do better all these years.  Thanks to our many customers and partners for making our business work and for driving us to innovate and solve their problems.  Thanks to our many alumni for their past efforts, often with nothing more to show for it than a line item on their resume.  And most of all, thanks to our hardworking and loyal team of nearly 200 for a great 2009 and many more exciting years ahead!  

Why I joined the DMA Board, and what you can expect of me in that role

I don’t normally think of myself as a rebel. But one outcome of the DMA’s recent proxy fight with Board member Gerry Pike is that I’ve been appointed to the DMA’s Board and its Executive Committee and have been labeled “part of the reform movement” in the trade press. While I wasn’t actively leading the charge on DMA reform with Gerry, I am very enthusiastic about taking up my new role.

I gave Gerry my proxy and support for a number of reasons, and those reasons will form the basis of my agenda as a DMA Board member. As a DMA member, and one who used to be fairly active, I have grown increasingly frustrated with the DMA over the past few years.

1. The DMA could be stronger in fighting for consumers’ interests. Why? Because what’s good for consumers is great for direct marketers. Marketing is not what it used to be, the lines between good and bad actors have been blurred, and the consumer is now in charge. The DMA needs to more emphatically embrace that and lead change among its membership to do the same. The DMA’s ethics operation seems to work well, but the DMA can’t and shouldn’t become a police state and catch every violation of every member company. Its best practices and guidelines take too long to produce and usually end up too watered down to be meaningful in a world where the organization is promoting industry self-regulation. By aggressively fighting for consumers, the DMA can show the world that a real direct marketer is an honest marketer that consumers want to hear from and buy from.

2. Despite a number of very good ideas, the DMA’s execution around interactive marketing has been lacking. The DMA needs to accept that interactive marketing IS direct marketing – not a subset, not a weird little niche. It’s the heart and soul of the direct marketing industry. It’s our future. The acquisition of the EEC has been one bright spot, but the DMA could do much more to make the EEC more impactful, grow its membership, and replicate it to extend the DMA’s reach into other areas of interactive marketing, from search to display advertising to lead generation. The DMA’s staff still has extremely limited experience in interactive marketing, they haven’t had a thought leader around interactive on staff for several years, and their own interactive marketing efforts are far from best practice. Finally, the DMA’s government affairs group, perhaps its greatest strength, still seems disproportionately focused on direct mail issues. The DMA should maintain its staunch support of traditional direct marketers while investing in the future, making interactive marketing an equal or larger priority than traditional direct marketing. We have to invest in the future.

3. Finally, I think the DMA suffers from a lack of transparency that doesn’t serve it well in the hyper-connected world we live in here in 2009 – that’s a nice way of saying the organization has a big PR problem. The organization does a lot of great work that never gets adequately publicized. This whole proxy fight episode is another example, both in the weak response from the DMA and also in a lot of the complaints Gerry lodged against the organization, many of which the organization says are untrue or misleading. Senior DMA execs or Board members should be blogging. They should be active thought leaders in the community. They should be much more engaged with their members to both understand member needs and requirements and more aggressively promote their agenda.

In short, I will be an independent voice who advocates for progress and change in the areas that I consider to be most important, and I will be transparent and open about expressing my views. I’ve already been clear with the existing DMA Board and management that I do have this agenda, and that I hope the organization will embrace it. If they do, even if only in part, I think it will be to the DMA’s benefit as well as the benefit of its members. If they reject it wholesale, my interest in long-term involvement will be fairly low.

That’s the story. As I said up front, I am taking up this new role with enthusiasm and with the belief that the DMA is open to change and progress. We’ll see how it goes, and I will blog about it as often as I can.

Do you have thoughts on the future of the DMA? I’d love to hear from you. You can leave a comment below or email me directly at matt at returnpath dot net.

Less is More

I have a challenge for the email marketing community in 2009. Let’s make this the Year of “Less is More.”

Marketers are turning to email more and more in this down economy. There’s no question about that. My great fear is that just means they’re sending more and more and more emails out without being smart about their programs. That will have positive short term effects and drive revenues, but long term it will have a negative long term impact on inboxes everywhere. And these same marketers will find their short term positive results turning into poor deliverability faster than you can say “complaint rate spike.”

I heard a wonderful case study this week from Chip House at ExactTarget at the EEC Conference. One of his clients, a non-profit, took the bold and yet painful step of permissioning an opt-out list. Yikes. That word sends shivers down the spine of marketers everywhere. What are you saying? You want me to reduce the size of my prime asset? The results of a campaign done before and after the permission pass are very telling and should be a lesson to all of us. The list shrank from 34,000 to 4,500. Bounce rate decreased from 9% to under 1%. Spam complaints went from 27 to 0 (ZERO). Open rate spiked from 25% to 53%. Click-through from 7% to 22%. And clicks? 509 before the permissioning, 510 after. This client generated the same results, with better metrics along the way, by sending out 87% LESS EMAIL. Why? Because they only sent it to people who cared to receive it.

This is a great time for email. But marketers will kill the channel by just dumping more and more and more volume into it. Let’s all make Less Is More our mantra for the year together. Is everyone in? Repeat after me…Less Is More! Less Is More!

Book Short:  The Little Engine that Could

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

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

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

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

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.