Book Short:  Tales of Two Cities

Return Path is basically dual-headquartered in New York City and Broomfield, Colorado, so two recently published books which provide history and insights into the tech industry in those two cities were both of interest to me.

Startup Communities: Building an Entrepreneurial Ecosystem in Your City, by Brad Feld (book, kindle) came out a few months ago and is part of Brad’s Startup Revolution series which will also include my upcoming book Startup CEO, to be published this fall.  In the book, Brad uses the example of the Boulder/Denver area and a few different sectors to demonstrate a blueprint to creating an entrepreneurial ecosystem – the kind that are popping up all over the world of late.

Tech and the City: The Making of New York’s Startup Community, by Alessandro Piol (kindle only) hits on many of the same themes and topics as they relate to New York City, although the book is more of a history of the New York tech scene than a framework with examples.  The book draws heavily on quotes from Fred Wilson, like Brad, a long time friend and Board member.  One of the things the book left me thinking about was what the New York tech scene will look like in 30 years after the new Cornell-Technion campus is up and running.  That plus the current momentum of the tech industry in New York, plus the sheer commercial scale of the city, could really produce an interesting environment down the road that actually starts to rival Silicon Valley, though rival probably isn’t the right word.

All in, these two books do a good job of chronicling the industry I work in, in the two cities where I work, but they also abstract nicely to broader principles about public-private collaboration as well as sector development.

Book Short:  Entrepreneurial Lessons

The Startup Playbook: Secrets of the Fastest-Growing Startups from 42 Founders, by David Kidder, is the ultimate coffee table book for entrepreneurs and people who are interested in how they think about running their businesses.

David is the author of the Intellectual Devotional series (here’s a link to one of the five or six books in the series), he’s a good friend of mine and a member of a CEO Forum that I’m in, and my major disclosure about this blog post is that I’m one of the 42 entrepreneurs David interviewed for and profiles in the book.

The Startup Playbook is very different from my own book (in progress) on being a Startup CEO.  Where my book is going to go deep on different topics – think of it as a bit of a field guide – David’s book is extremely broad in its coverage of different entrepreneurs and their stories.  Taken together, the book paints a great picture of how CEOs think about the most important parts of the job.  It’s also a nice change of pace (for me, anyway) that David profiles some entrepreneurs who aren’t in the Internet/tech space.

It was an honor to be included in The Startup Playbook next to entrepreneurs like Reid Hoffman and Elon Musk.

Book Short:  Unsung Heroes

If you like “entrepreneurship by analogy” books, you’ll like The Innovators:  The Engineering Pioneers Who Made America Modern, by David Billington.  I have to admit some bias here — Professor Billington was my favorite teacher and senior thesis advisor at Princeton (I almost majored in civil engineering because of him), and this book is one of a number he’s written that are outgrowths of his most popular courses at Princeton.  And while there’s no substitute for the length or energy of his lectures, the book works.

The book is basically a person-focused engineering history of America from 1776-1883.  Billington talks about four classes of engineering product:  public structures (mostly bridges), machines that produced power, networks like the railroads and telegraphs, and processes like steel manufacturing.

His approach is to acknowledge that the Americans innovators couldn’t do much without the right context:  learnings from their counterparts in Britain, a supportive government here at home, and abundant raw materials and capital.  But with that backdrop in place, Billington tells the tale of a number of the inventions that built our modern society with a focus on the engineers who got things right.  While some of them are familiar names (Morse, Edison), many are not (Thomas Telford, J. Edgar Thomson, Joseph Henry).

Sound familiar?  It feels at many point in the book that you could insert some different names and dates and be reading a history of the Internet or information age.  And as with the Industrial Revolution, while many of the innovators in our world today are known (Bezos, Yang, Brin/Page), there are probably an equal number who are unsung heroes — either software engineers or even buisness model pioneers who haven’t sought or won’t end up in the spotlight even though their contributions to society or to their companies are giant.  I know there are a number of unsung heroes in our own engineering department at Return Path — people who aren’t market facing and who never get quoted in press releases, but who really make a difference in how the company works and how competitive we are.  This book celebrates those people as much as it does the entrepreneurs you’ve heard of.

Warning, there are lots of pages which are full of mathematical formulas, which may or may not be interesting to you, but the book still holds together 100% if you skip over them.

People First

I do not think it’s telling that my fourth post in this series of posts on Return Path’s core values (kickoff post, tag cloud) is something called People First.  Ok, it probably should have been the first post in the series.  To be fair, it is the first value on our list, but for whatever reason, the value about Ownership was top of mind when I decided to create this series.

Anyway, at Return Path,

We believe that people come first

And we aren’t shy about saying it publicly, either.  This came up in a lengthy interview I did with Inc. Magazine last year when we were profiled for winning an award as one of the top 20 small- and mid-sized businesses to work for in America.  After re-reading that article, I went back and tried to find the slide from our investor presentations that I referred to.  I have a few versions of this slide from different points in time, including one that’s simpler (it only has employees, clients, and shareholder on it) but here’s a sample of it:

That pretty much says it all.  We believe that if we have the best and most engaged workforce, we will do the best job at solving our clients’ problems, and if we do that well, our shareholders will win, too.

How does this “people first” mentality influence my/our day-to-day activities?  Here are a few examples:

• We treat all employees well, regardless of level or department.  All employees are important to us achieving our mission – otherwise, they wouldn’t be here.  So we don’t do a lot of things that other companies do like send our top performing sales reps on a boondogle together while the engineers and accountants slave away in the office as second-class citizens.  That would be something you might see in a “sales first” or “customer first” culture
• We fiercely defend the human capital of our organization.  There are two examples I can think of around this point.  First, we do not tolerate abusive clients. Fortunately, they are rare, but more than once over the years either I or a member of my senior team has had to get on the phone with a client and reprimand them, or even terminate their contract with us, for treating one of our employees poorly and unprofessionally. And along the same lines, when all economic hell broke loose in the fall of 2008, we immediately told employees that while we’d be in for a rough ride, our three top priorities were to keep everyone’s job, keep everyone’s compensation, and keep everyone’s health benefits. Fortunately, our business withstood the financial challenges and we were able to get through the financial crisis with those three things intact.
• We walk the walk with regard to employee feedback.  Everyone does employee satisfaction surveys, but we are very rigorous about understanding what areas are making people relatively unhappy (for us, even our poor ratings are pretty good, but they’re poor relative to other ratings), and where in the employee population (office, department, level) those issues lie.  We highlight them in an all-hands meeting or communication, we develop specific action plans around them, and we measure those same questions and responses the next time we do a survey to see how we’ve improved
• We invest in our people.  We pay them fairly well, but that’s not what I’m talking about.  We invest in their learning and growth, which is the lifeblood of knowledge workers.  We do an enormous amount of internal training.  We encourage, support, and pay for outside training and education.  We are very generous with the things that allow our employees to be happy and healthy, from food to fitness to insurance to time off to a flexible environment to allowing them to work from another office, or even remotely, if their lives require them to move somewhere else
• I spend as little time as I possibly can managing my shareholders and as much time as I can with employees and prospective employees.  That doesn’t mean I don’t interact with my Board members – I do that quite a bit.  But it does mean that when I do interact with them, it’s more about what they can do for Return Path and less about reporting information to them.  I do send them a lot of information, but the information flow works well for them and simultaneously minimizes my time commitment to the process:  (1) reporting comes in a very consistent format so that investors know WHAT to expect and what they’re looking at, (2) reporting comes out with a consistently long lead time prior to a meeting so investors know WHEN to expect the information, (3) the format of the information is co-developed with investors so they are getting the material they WANT, and (4) we automate as much of the information production as possible and delegate it out across the organization as much as possible so there’s not a heavy burden on any one employee to produce it
• When we do spend time with customers (which is hopefully a lot as well), we try to spread that time out across a broad base of employees, not just salespeople and account managers, so that as many of our employees can develop a deep enough understanding of what our customers’ lives are like and how we impact them

There are plenty of companies out there who have a “shareholder first” or “customer first” philosophy.  I’m not saying those are necessarily wrong – but at least in our industry, I’ll bet companies like that end up with significantly higher recruiting costs (we source almost half our new hires from existing employee referrals), higher employee churn, and therefore lower revenue and profit per employee metrics at a minimum.  Those things must lead to less happy customers, especially in this day and age of transparency.  And all of those things probably degrade shareholder value, at least over the long haul.

Return Path Core Values, Part II

As I said at the beginning of this series, I was excited to share the values that have made us successful with the world and to also articulate more for the company some of the thinking behind the statements.

You can click on the tag for all the posts on the 13 Return Path’s core values, but the full list of the values is below, with links to each individual post, for reference:

1. We believe that people come first
2. We believe in doing the right thing
3. We solve problems together and always present problems with potential solutions or paths to solutions
4. We believe in keeping the commitments we make, and communicate obsessively when we can’t
5. We don’t want you to be embarrassed if you make a mistake; communicate about it and learn from it
6. We believe in being transparent and direct
7. We challenge complacency, mediocrity, and decisions that don’t make sense
8. We believe that results and effort are both critical components of execution
9. We are serious and passionate about our job and positive and light-hearted about our day
10. We are obsessively kind to and respectful of each other
11. We realize that people work to live, not live to work
12. We are all owners in the business and think of our employment at the company as a two-way street
13. We believe inboxes should only contain messages that are relevant, trusted, and safe

As I noted in my initial post, every employee as of August 2008 was involved in the drafting of these statements.  That’s a long post for another time, but it’s an important part of the equation here.  These were not top-down statements written by me or other executives or by our People team.  Some are more aspirational than others, but they are the aspirations of the company, not of management!

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.

I haven’t done short book summaries in a LONG time, but I’ll try to start adding that back into the mix as I read interesting and relevant books. Here’s one to add to your list: One Life to Lead, by Russell Benaroya. I was recently connected to Russell by a mutual friend, TA McCann at Pioneer Square Labs. TA had a sense Russell and I would hit it off, and we did. Russell is a multi-time founder/CEO, a Coach, and an author, so we have a lot in common.

One Life to Lead is an excellent book. First, it is short and easy to get through. Unlike a lot of business books, it doesn’t go on too long or contain anything extraneous. It’s to the point!

Second, the book is a business book that’s not really about business. It’s about life and what Russell calls Life Design, which is a great framing of how to be intentional about leading your life. While I have become less and less of a life planner as I’ve gotten older under the headline of “man plans, God laughs,” I am a huge believer in being intentional about everything, which I talk about in Startup CEO quite a bit in the nuts and bolts context of building your business.

Finally, Russell’s framework is easy to understand and full of concrete exercises you can to. Here are his five steps, but you’ll have to read the book to get the details:

• Ground stories with facts. This reminds me a lot of the principles we have taught team members over the years in our Action/Design (and related) trainings. First, start with absolute concrete facts that everyone will agree are facts.
• Establish your principles. This is brilliant. Your company has documented values or operating principles. Why don’t you?
• Harness energy from the environment. Figuring out what makes you tick, and what drains your energy, is so important.
• Get in and stay in your genius zone. Shouldn’t we all focus our time on the things we do best and love the most?
• Take action. How to put it together and make it all happen.

If you don’t get out in front of life, it will happen to you, and Russell’s framework is about how to make sure you are in the driver’s seat of your own life. Here’s to that.

Book Short:  The Religion of Heresy

At the end of Tribes: We Need You to Lead Us, Seth Godin’s new book, Seth says this:

I’m going to get a lot of flak from people about what you just read. People might say that it’s too disorganized or not practical enough or that I require you to do too much work to actually accomplsh anything. That’s ok.

He’s kind of right. The book is a little breezy and meanders around, just like riffing with Seth. It’s not practical in the sense that if the entire world operated this way in the extreme, we’d have serious problems. But the fact that he requires you to do “too much work to actually accomplish anything” is part of the brilliance of his message.

This was Seth’s best book in years, mostly because it is fresh. It is not a rant about marketing; it is a wonderfully succinct look at how we as a society are rallying and organizing around causes, campaigns, companies, and collective beliefs. It’s not about the Internet, though its principles are easily implemented and amplified using online tools. It’s not a how-to guide to being a fancy corporate leader, but it’s one of the most pointed descriptions of the ethos of a certain type of leader (the upstart, or as Seth says, the heretic). It’s not about a particular revolution; it’s about how mini-revolutions are becoming the norm these days.

Tribes is short, inspirational, and pure Seth. Though quite different in its nature and mission, it really evoked for me Mark Penn’s Microtrends (post, link) — a study of larger tribes and heretics in contemporary America.

A listing of Seth’s books over the years follows:

• Permission Marketing — the original

• Unleashing the Ideavirus — good follow up on viral marketing

• Really Bad Powerpoint (ebook) — the standard for not being boring when you present

• The Big Red Fez — the standard on designing great web sites

• Survival Is Not Enough — motivating about being a nimble company

• Free Prize Inside — on being buzzworthy

• Purple Cow — on being remarkable, a great book

• The Big Moo — good follow-up with remarkable examples

• Small Is the New Big — not worth it if you read his blog

• All Marketers Are Liars — fine, a little “more of the same”

• The Dip — haven’t read it

• Meatball Sundae — haven’t read it

• Tribes — see above

Email Deliverability Data

We just published our 2004 year-end email deliverability report.  Feel free to download the pdf, but I’ll summarize here.  First, this report is very different from the reports you see published by Email Service Providers like Digital Impact and DoubleClick, because (a) it measures deliverability across a broad cross-section of mailers, not just a single ESP’s clients, and (b) it is a true measure of deliverability — what made it to the inbox — as opposed to the way some ESPs measure and report on deliverability, which is usually just the percentage of email that didn’t bounce or get outright blocked as spam.

Headline number one:  the “false positive” problem (non-spam ending up in the junk mailbox) is getting worse, not better.  Here’s the trend:

Full year 2004:  22%
Second half 2003:  18.7%
First half 2003:   17%
Second half 2002:  15%

Headline number two:  mailers who work on the problem can have a huge impact on their deliverability.  Obviously, I’m biased to Return Path’s own solution for mailers, but I think you can extrapolate our data to the broader universe:  companies that work on understanding, measuring, and solving the root causes of weak deliverablility can raise their inbox rate dramatically in a short time — in our study, the average improvement was a decrease in false positives from 22% to about 9% over the first three months.  But we have a number of mailers who are now closer to the 2% false positive level on a regular basis.

Book Short: What’s For Dinner Tonight, Honey?

The Paradox of Choice: Why More is Less, by Barry Schwartz, presents an enlightening, if somewhat distressing perspective on the proliferation of options and choices facing the average American today. The central thesis of the book is that some choice is better than no choice (I’d rather be able to pick blue jeans or black jeans), but that limited choice may be better in the end than too much choice (how do I know that the jeans I really want are relaxed cut, tapered leg, button fly, etc.?). We have this somewhat astonishing, recurring conversation at home every night, with the two of us sitting around paralyzed about where to eat dinner.

The author’s arguments and examples are very interesting throughout, and his “Laffer curve” type argument about choice vs. too much choice rings true. While there’s obviously no conclusive proof about this, the fact that our society is more rife with depression than ever before at least feels like it has a correlation with the fact that most of us now face a proliferation of choices and decisions to make exponentially more than we used to. The results of this involve ever-mounting levels of regret, or fear of regret, as well as internal struggles with control and expectations. Perhaps the best part of the book is the final chapter, which ties a lot of the material of the book together with 11 simple suggestions to cope better with all the choices and options in life — summed up in the last few words of the book suggestions that “choice within constraints, freedom within limits” is the way to go. Amen to that. We all need some basic structure and frameworks governing our lives, even if we create those constructs ourselves. The absence of them is chaos.

Overall, this is a good social science kind of read, not overwhelming, but definitely interesting for those who are students of human psychology, marketing, and decision making. It’s squarely in the genre of Gladwell’s The Tipping Point and Blink, and Robert Cialdini’s Influence, most of which I’ve written about recently, and though not as engaging as Gladwell, worth a read on balance if you like the genre.

Thanks to my friend Jonathan Shapiro for this book.

Book Short:  Culture is King

Joy, Inc.:  How We Built a Workplace People Love, by Richard Sheridan, CEO of Menlo Innovations, was a really good read. Like Remote  which I reviewed a few weeks ago, Joy, Inc. is ostensibly a book about one thing — culture — but is also full of good general advice for CEOs and senior managers.

Also like Remote, the book was written by the founder and CEO of a relatively small firm that is predominately software engineers, so there are some limitations to its specific lessons unless you adapt them to your own environment. Unlike Remote, though, it’s neither preachy nor ranty, so it’s a more pleasant read.  And I suppose fitting of its title, a more joyful read as well. (Interestingly on this comparison, Sheridan has a simple and elegant argument against working remotely in the middle of the book around innovation and collaboration.)

Some of the people-related practices at Sheridan’s company are fascinating and great to read about. In particular, the way the company interviews candidates for development roles is really interesting — more of an audition than an interview, with candidates actually writing code with a development partner, the way the company writes code. Different teams at Return Path interview in different ways, including me for both the exec team and the Board, but one thing I know is that when an interview includes something that is audition-like, the result is much stronger. There are half a dozen more rich examples in the book.

Some of the other quotable lines or concepts in the book include:

• the linkage between scalability with human sustainability (you can’t grow by brute force, you can only grow when people are rested and ready to bring their brain to work)
• “Showcasing your work is accountability in action” (for a million reasons, starting with pride and ending with pride)
• “Trust, accountability, and results — these get you to joy” (whether or not you are a Myers-Briggs J, people do get a bit of a rush out of a job well done)
• “…the fun and frivolity of our whimsically irreverent workplace…” (who doesn’t want to work for THAT company?)
• “When even your vendors want to align with your culture, you know you’re on the right path” (how you treat people is how you treat PEOPLE, not just clients, not just colleagues)
• “One of the key elements of a joyful culture is having team members who trust one another enough to argue” (if you and I agree on everything, one of us is not needed)
• “The reward is in the attempt” (do you encourage people to fail fast often enough?)
• “Good problems are good problems for the first five minutes. Then they just feel like regular problems until you solve them” (Amen, Brother Sheridan)

The benefits of a joyful culture (at Return Path, we call it a People-First culture) have long been clear to me. As Sheridan says, we try to “create a culture where people want to come to work every day.” Cultures like ours look soft and squishy from the outside, or to people who have grown up in tough, more traditional corporate environments. And to be fair, the challenge with a culture like ours is keeping the right balance of freedom and flexibility on one side and high performance and accountability on the other. But the reality is that most companies struggle with most of the same issues — the new hire that isn’t working out or the long-time employee who isn’t cutting it any more, the critical path project that doesn’t get done on time, the missed quarter or lost client.  As Sheridan notes though, one key benefit of working at a joyful company is that problems get surfaced earlier when they are smaller…and they get solved collaboratively, which produces better results. Another key benefit, of course, is that if you’re going to have the same problems as everyone else, you might as well have fun while you’re dealing with them.

If you don’t love where you work and wish you did, read Joy, Inc. If you love where you work but see your company’s faults and want to improve them, read Joy, Inc. If you are not in either of the above camps, go find another job!