Response to the Journal
(This post is running concurrently on the Return Path blog.)
It is now widely understood that the Internet runs on data. I first blogged about this in 2004—14 years ago!— here.  People have come to expect a robust—and free!—online experience. Whether it’s a shopping app or a social media platform like Instagram, these free experiences provide a valuable service. And like most businesses, the companies that provide these experiences need to make money somehow. Consumers are coming to understand and appreciate that the real cost of a “free” internet lies in advertising and data collection.
Today, the Wall Street Journal ran an article exploring the data privacy practices of Google and some of the third party developers who utilize their G Suite ecosystem. Return Path was among the companies mentioned in this article. We worked closely with the journalist on this piece and shared a great deal of information about the inner workings of Return Path, because we feel it’s important to be completely transparent when it comes to matters of privacy.  Unfortunately, the reporter was extremely and somewhat carelessly selective in terms of what information he chose to use from us — as well as listing a number of vague sources who claimed to be “in the know” about the inner workings of Return Path. We know that he reached out to dozens of former employees via LinkedIn, for example, many of whom haven’t worked here in years.
While the article does not uncover any wrongdoings on our part (in fact, it does mention that we have first-party relationships with and consent from our consumers), it does raise a larger privacy and security concern against Google for allowing developer access to Gmail’s API to create email apps. The article goes on to explain that computers scan this data, and in some rare cases, the data is reviewed by actual people. The article mentions a specific incident at Return Path where approximately 8,000 emails were manually reviewed for classification. As anyone who knows anything about software knows, humans program software – artificial intelligence comes directly from human intelligence.  Any time our engineers or data scientists personally review emails in our panel (which again, is completely consistent with our policies), we take great care to limit who has access to the data, supervise all access to the data, deploying a Virtual Safety Room, where data cannot leave this VSR and all data is destroyed after the work is completed.
I want to reaffirm that Return Path is absolutely committed to data security and consumer data privacy. Since our founding in 1999, we’ve kept consumer choice, permission, and transparency at the center of our business. To this end, we go above and beyond what’s legally required and take abundant care to make sure that:
- Our privacy policy is prominently displayed and written in plain English;
- The user must actively agree to its terms (no pre-checked boxes); and
- A summary of its main points is shown to every user at signup without the need to click a link
While a privacy expert quoted in the article (and someone we’ve known and respected for years) says that he believes consumers would want to know that humans, not only computers, might have access to data, we understand that unfortunately, most consumers don’t pay attention to privacy policies and statements, which is precisely why we developed succinct and plain-English “just-in-time” policies years before GDPR required them. When filling out a form people may not think about the impact that providing the information will have at a later date. Just-in-time notices work by appearing on the individual’s screen at the point where they input personal data, providing a brief message explaining how the information they are about to provide will be used, for example:
It’s disappointing to say the least that the reporter called this a “dirty secret.”  It looks pretty much the opposite of a secret to me.
In addition to our own policies and practices, Return Path is deeply involved in ongoing industry work related to privacy. We lead many of these efforts, and maintain long-term trusted relationships with numerous privacy associations. Our business runs on data, and keeping that data secure is our top priority.
Further, I want to address the scare tactics employed by this journalist, and many others, in addressing the topics of data collection, data security, and who has access to data. It’s common these days to see articles that highlight the dangers that can accompany everyday online activities like downloading an app or browsing a retail website. And while consumers certainly have a responsibility to protect themselves through education, it’s also important to understand the importance of data sharing, open ecosystems, and third party developers.  And more than that, it’s important to draw distinctions between companies who have direct relationships with and consent from consumers and ones who do not.
While they may not be top of mind, open ecosystems that allow for third-party innovation are an essential part of how the internet functions. Big players like Facebook and Google provide core platforms, but without APIs and independent developers, innovation and usability would be limited to big companies with significant market power and budgets—to the detriment of consumers. Think about it—would Facebook have become as wildly popular without the in-app phenomenon that was Farmville? Probably, but you get the point: third party applications add a new level of value and usefulness that a platform alone can’t provide.
Consumers often fall into the trap of believing that the solution to all of their online worries is to deny access to their data. But the reality is that, if they take steps like opting out of online tracking, the quality of their online experience will deteriorate dramatically. Rather than being served relevant ads and content that relates to their browsing behaviors and online preferences, they’ll see random ads from the highest bidder. Unfortunately some companies take personalization to an extreme, but an online experience devoid of personalization would feel oddly generic to the average consumer.
There’s been a lot of attention in the media lately—and rightfully so—about privacy policies and data privacy practices, specifically as they relate to data collection and access by third parties. The new GDPR regulations in the EU have driven much of this discussion, as has the potential misuse of private information about millions of Facebook users.
One of Return Path’s core values is transparency, including how we collect, access and use data.  Our situation and relationship with consumers is different from those of other companies. If anyone has additional questions, please reach out.
You Have to Throw a Stone to Get the Pond to Ripple
You Have to Throw a Stone to Get the Pond to Ripple
This is a post about productive disruption. The title comes from one of my favorite lines from a song by Squeeze, Slap & Tickle. But the concept is an important one for leaders at all levels, especially as businesses mature.
Founders and CEOs of early stage companies don’t disrupt the flow of the business. Most of the time, they ARE the flow of the business. They dominate the way everything works by definition — product development, major prospect calls, client dialog, strategy, and changes in strategy. But as businesses get out of the startup phase and into the “growth” phase (I’m still trying to figure out what to call the phase Return Path is in right now), the founders and CEO should become less dominant. The best way to scale a business is by not being Command Central any longer – to build an organization capable of running without you in many cases.
Organizations that get larger seek stability, and to some extent, they thrive on it. The kinds of people you hire into a larger company aren’t accustomed to or prepared for the radical swings you get in startups. And the business itself has needs specifically around a lack of change. Core systems have to work flawlessly. Changes to those systems have to go off without a hitch. Clients need to be served and prospects need to be sold on existing products. The world needs to understand your company’s positioning and value proposition clearly — and that can’t be the case if it’s changing all of the time. Of course innovation is required, both within the core and outside of it, but the tensions there can be balanced out with the strengths of having a stable and profitable core (see my colleague George Bilbrey’s guest post on OnlyOnce a couple months back for more discussion on this point).
Despite all of this required stability, I think the art of being a leader in a growth organization is knowing when and how to throw that stone and get the pond to ripple — that is, when to be not just disruptive, but productively disruptive.
If done the right way, disruption from the top can be incredibly helpful and energizing to a company. If done the wrong way, it can be distracting and demotivating. I’ve been in environments where the latter is true, and it’s not fun. I think the trick is to figure out how to blaze a new trail without torching what’s in place, which means forcing yourself to exercise a lot of judgment about who you disrupt, and when, and how (specifically, how you communicate what it is you’re doing and saying — see this recent post entitled “Try It On For Size” for a series of related thoughts).
Here are a few ideas for things that I’d consider productive disruption. We’ve done some or shades of some of them at Return Path over the years.
- Challenge everyone in the organization or everyone on your team to make a “stop doing” list, which forces people to critically evaluate all their ordinary processes and tasks and meetings and understand which ones are outdated, and therefore a waste of time
- With the knowledge and buy-in of the group head, kick off an offsite meeting for a team other than the executive team by presenting them with your vision for the company three years down the road and ask them to come back to you in a week with four ideas of how they can help achieve that vision over time
- If you see something going on in the organization that rubs you the wrong way, stop it and challenge it. Do it politely (e.g., pull key people aside if need be), but ask why it’s going on, how it relates to the company’s mission or values as the case may be. It’s ok to put people on the defensive periodically, as long as you’re asking them questions more than advocating your own position
I’m not saying we have it all figured out. I have no doubt that my disruption is a major annoyance sometimes to people in the organization, and especially to people to report to me. And I’ll try to perfect the art of being productive in my disruption. But I won’t stop doing it — I believe it’s one of the engines of forward progress in the organization.
A Lighter, Yet Darker, Note
A Lighter, Yet Darker, Note
I’ve been meaning to post about this for some time now since my colleague Tami Forman introduced me to this company. It’s a riot.
You know all those well-intentioned, but slightly cheesy motivational posters you see in places like dentists’ offices? The kind that talk about “Perseverence” and “Commitment” and “Dare to Dream” and have some beautiful or unique, usually nature-centric image to go with them and their tag line?
For the sarcastic among us, you must visit Despair, Inc.’s web site, in particular any of the “Individual Designs” sections featured on the left side navigation. The posters are brilliant spoofs on the above, with such gems as “Agony” and “Strife” and “Despair” (whose tag line is “It’s always darkest just before it goes pitch black”). E.L. Kersten is one funny, albeit strange dude.
Worth a look, and everything is for sale there, too, in case you need to have these posted in a back room somewhere.
Book Short: How, Now
Book Short: How, Now
Every once in a while, I read a book that has me jump up and down saying “Yes! That’s so right!” How: Why How We Do Anything Means Everything in Business (and in Life), by Dov Seidman, was one of those books. But beyond just agreeing with the things Seidman says, the book had some really valuable examples and two killer frameworks, one around culture, and one around leadership.
It’s a book about the way the world we now live in — a world of transparency and hyper-connectedness — is no longer about WHAT you do, but HOW you do it. It’s about how you can have a great brand and great advertising, but if your customers find out via a blog and YouTube clip that you run a low quality sweatshop in Malaysia, you are toast. It’s about you can…not outwork the competition, not outsmart the competition, but how you can out-behave the competition.
The book, which talks about principles like mutual gain, and thriving on the collaborative, reminds me a lot of a basic tenet of negotiation I learned years ago at the Harvard Program on Negotiation about finding a “third way” beyond a “me vs. you” negotiation by expanding the pie so both parties get more out of a deal.
Here are a few snippets from the book to inspire a purchase:
– How encouraging doctors to say “I’m sorry” radically reduces lawsuits
– How “micro-inequities” can subtly leech productivity from an organization
– How the majority of workers expect from their workplaces: equity, achievement, camaraderie
– How companies whose employees understand and embrace their mission, goals, and values see a 29% greater return than companies whose employees don’t
– How reputation is the new competitive advantage
– How people will do the right thing because in self-governing cultures, not doing the right thing no longer betrays just the company; it betrays individuals’ own values
– How increasing self-governance means moving values to the center of your efforts and making it clear — in how you reward, celebrate, communicate, and pursue — that those values form the guiding spirit of the enterprise
What type of organization do you run? One based on Anarchy & Lawlessness, one based on Blind Obedience, one based on Informed Acquiescence, or one of Values-Based Self-Governance? (Hint, it’s most likely the third category.) Read the book to find out more.
Pret a Manager
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!
Selling a Line of Business
Selling a Line of Business
It’s been a couple of years since Return Path decided to focus on our deliverability business by divesting and spinning out our other legacy businesses. That link tells some of the story, and the rest is that subsequently, Authentic Response divested part of the Postmaster Direct business to Q Interactive. Those three transactions, plus a number of experiences over the years on the buy side of similar transactions (Bonded Sender, Habeas, NetCreations), plus my learnings from talking to a number of other CEOs who have done similar things over the years, form the basis of this post. The Authentic Response spin-out was also partially chronicled by Inc. Magazine in this article earlier this year.
It’s an important topic — as entrepreneurs build businesses, they frequently end up creating new revenue opportunities and go off on productive tangents. Those new lines of business might or might not take off; but sometimes they can take off and still, down the road, end up being non-core to the overall mission of the company and therefore candidates for divestiture. Even if they are good businesses, the overall enterprise might benefit from the focus or cash provided by a sale. Look at the example of Occipital building the Red Laser app, then selling it to eBay to finance the rest of their business.
Here are some of the signs of a successful divestiture:
- Business is truly non-core or relies on starkly different competencies for success (e.g., one is B2B, the other is B2C)
- Business is growing rapidly and requires assistance to scale properly (either technology, or sales)
- Business has its own culture and operations and “a life of its own”
Conversely, here are some of the reasons why a divestitures of a business unit might stall or fail:
- Lack of a very compelling story as to why you’re selling the business unit
- Stand-alone financials of the unit are too hard for the buyer to determine with confidence
- Operations of the unit too tethered to the mothership
- There is some problem with the leadership of the unit (there is no stand-alone leader, the leader isn’t involved in the divestiture, the leader isn’t squarely behind the divestiture)
- Business performance weakens during the process
I have a couple points of advice to entrepreneurs in this situation. The first is to clarify for yourself up front: are you selling a true line of business, or are you selling assets? If you are selling assets, you need to clearly define what they are, and what they aren’t, and you need to make sure all legal details (contracts, IP, etc.) are buttoned up before the process starts.
If you are selling a true line of business, beware that buyers will not be interested in doing any hard work, or if they feel like they have to do hard work, the price they pay for the business will reflect that in the form of a steep, steep discount. The financials must be understandable and credible on a stand-alone basis. The business must be completely separated from the core already. The business must have its own management team, completely aligned with the decision to sell.
You also have to be extremely cognizant of the human aspects of what you’re doing. Every culture is different, and I’m not advocating one style over another, but selling or spinning out a business is very different than selling a company. There’s going to be a big difference in reactions, perceptions, hopes, and fears between the people in the core who are staying, and the people in the business unit that’s going. Having a heightened awareness of those differences and factoring them into your communications plan is critical to success, as a poorly managed effort can end up harming both sides.
In terms of valuation expectations, don’t expect to get any credit for synergies. You have to present them and sell them, and they may make the different between getting a deal done and not, but they will most likely not impact the price you get for the divestiture.
Finally, remember that buyers understand your psychology as well. They know you’re selling the business for a reason (you need to raise cash, you’re concerned about its future performance, it’s become a distraction or has the potential to suck scarce resources out of your core, etc.). They will completely understand the costs you carry, whether financial, opportunity, or mental, in continuing to own the business. And they will factor that into the price they’re willing to offer. Of course, as with all deals, the best thing you can do to maximize price is have multiple interested parties bidding on the deal!
Stamina
Stamina
A couple years ago I had breakfast with Nick Mehta, my friend who runs the incredibly exciting Gainsight.  I think at the time I had been running Return Path for 15 years, and he was probably 5 years into his journey. He said he wanted to run his company forever, and he asked me how I had developed the stamina to keep running Return Path as long as I had. My off the cuff answer had three points, although writing them down afterwards yielded a couple more. For entrepreneurs who love what they do, love running and building companies for the long haul, this is an important topic. CEOs have to change their thinking as their businesses scale, or they will self implode! What are five things you need to get comfortable with as your business scales in order to be in it for the long haul?
Get more comfortable with not every employee being a rock star. When you have 5, 10, or even 100 employees, you need everyone to be firing on all cylinders at all times. More than that, you want to hire “rock stars,” people you can see growing rapidly with their jobs. As organizations get larger, though, not only is it impossible to staff them that way, it’s not desirable either. One of the most influential books I’ve read on hiring over the years, Topgrading (review, buy), talks about only hiring A players, but hiring three kinds of A players: people who are excellent at the job you’re hiring them for and may never grow into a new role; people who are excellent at the job you’re hiring them for and who are likely promotable over time; and people who are excellent at the job you’re hiring them for and are executive material. Startup CEOs tend to focus on the third kind of hire for everyone. Scaling CEOs recognize that you need a balance of all three once you stop growing 100% year over year, or even 50%.
Get more comfortable with people quitting. This has been a tough one for me over the years, although I developed it out of necessity first (there’s only so much you can take personally!), with a philosophy to follow. I used to take every single employee departure personally. You are leaving MY company? What’s wrong with you? What’s wrong with me or the company? Can I make a diving catch to save you from leaving? The reality here about why people leave companies may be 10% about how competitive the war for talent has gotten in technology. But it’s also 40% from each of two other factors. First, it’s 40% that, as your organization grows and scales, it may not be the right environment for any given employee any more. Our first employee resigned because we had “gotten too big” when we had about 25 employees. That happens a bit more these days! But different people find a sweet spot in different sizes of company. Second, it’s 40% that sometimes the right next step for someone to take in their career isn’t on offer at your company. You may not have the right job for the person’s career trajectory if it’s already filled, with the incumbent unlikely to leave. You may not have the right job for the person’s career trajectory at all if it’s highly specialized. Or for employees earlier in their careers, it may just be valuable for them to work at another company so they can see the differences between two different types of workplace.
Get more comfortable with a whole bunch of entry level, younger employees who may be great people but won’t necessarily be your friends. I started Return Path in my late 20s, and I was right at our average age. It felt like everyone in the company was a peer in that sense, and that I could be friends with all of them. Now I’m in my (still) mid-40s and am well beyond our average age, despite my high level of energy and of course my youthful appearance. There was a time several years ago where I’d say things to myself or to someone on my team like “how come no one wants to hang out with me after work any more,” or “wow do I feel out of place at this happy hour – it’s really loud here.” That’s all ok and normal. Participate in office social events whenever you want to and as much as you can, but don’t expect to be the last man or woman standing at the end of the evening, and don’t expect that everyone in the room will want to have a drink with you. No matter how approachable and informal you are, you’re still the CEO, and that office and title are bound to intimidate some people.
Get more comfortable with shifts in culture and differentiate them in your mind from shifts in values. I wrote a lot about this a couple years ago in The Difference Between Culture and Values . To paraphrase from that post, an organization’s values shouldn’t change over time, but its culture – the expression of those values – necessarily changes with the passage of time and the growth of the company. The most clear example I can come up with is about the value of transparency and the use case of firing someone. When you have 10 employees, you can probably just explain to everyone why you fired Joe. When you have 100 employees, it’s not a great idea to tell everyone why you fired Joe, although you might be ok if everyone finds out. When you have 1,000 employees, telling everyone why you fired Joe invites a lawsuit from Joe and an expensive settlement on your part, although it’s probably ok and important if Joe’s team or key stakeholders comes to understand what happened. Does that evolution mean you aren’t being true to your value of transparency? No. It just means that WHERE and HOW you are transparent needs to evolve as the company evolves.
- Get more comfortable with process. This doesn’t mean you have to turn your nimble startup into a bureaucracy. But a certain amount of process (more over time as the company scales) is a critical enabler of larger groups of people not only getting things done but getting the right things done, and it’s a critical enabler of the company’s financial health. At some point, you and your CFO can’t go into a room for a day and do the annual budget by yourselves any more. But you also can’t let each executive set a budget and just add them together. At some point, you can’t approve every hire yourself. But you also can’t let people hire whoever they want, and you can’t let some other single person approve all new hires either, since no one really has the cross-company view that you and maybe a couple of other senior executives has. At some point, the expense policy of “use your best judgment and spend the company’s money as if it was your own” has to fit inside department T&E budgets, or it’s possible that everyone’s individual best judgments won’t be globally optimal and will cause you to miss your numbers. Allow process to develop organically. Be appropriately skeptical of things that smell like bureaucracy and challenge them, but don’t disallow them categorically. Hire people who understand more sophisticated business process, but don’t let them run amok and make sure they are thoughtful about how and where they introduce process to the organization.
I bet there are 50 things that should be on this list, not 5. Any others out there to share?
Keeping Commitments
Keeping Commitments
Today’s post is another in the series about our 13 core values at Return Path, about making commitments. The language of our value specifically is:
We believe in keeping the commitments we make, and we communicate obsessively when we can’t
Making and keeping commitments is not a new value – it’s one of Covey’s core principles if nothing else. I’m sure it has deeper roots throughout the history of mankind. But for us, this is one of those things that is hard wired into the social contract of working here. The value is more complicated than some of the other ones we have, and although it is short, it has three components that worth breaking down:
- Making commitments:Â Goal setting, whether big company-wide goals, or smaller “I’ll have it to you by Tuesday” goals, is the foundation for a well-run, aligned, and fast-paced organization
- Keeping commitments:Â If you can’t keep the overwhelming majority of your commitments, you erode the trust of your clients or colleagues and ultimately are unable to succeed
- Communicating when commitments can’t be met: Nobody is perfect. Sometimes circumstances change, and sometimes external dependencies prevent meeting a goal. The prior two parts of this value statement are, in my mind, pay to play. What separates the good from the great is this third piece — owning up loud and clear when you’re in danger of blowing a goal so that those who are counting on you know how to reset their own work and expectations accordingly
It’s worth noting on this one that the goal is as relevant EXTERNALLY as it is INTERNALLY. Internal commitments are key around building an organization that knows how to collaborate and hand work off from group to group. External commitments — from meeting investor expectations to client deliverables — keep the wheels of commerce flowing.
I’m enjoying articulating these values and hope they’re helpful for both my Return Path audience and my much larger non-Return Path audience. More to come over time.
Wasde believe in keeping the commitments we make, and communicate obsessively when we can’t |
Double Book Short: Framework of Frameworks
I love me a good framework. And Geoffrey Moore is the kind of good product/marketing frameworks for technology companies. Moore’s Zone to Win: Organizing to Compete in an Age of Disruption is a must-read for anyone managing a larger technology organization (start reading it when you get to 200-250 people – it’s never too early to worry about disruption). More important, it’s really a companion book or coda to Escape Velocity: Free Your Company’s Future from the Pull of the Past, so if you haven’t read that one, start there and read both sequentially. Zone to Win is quite short and punchy, and it doesn’t disappoint.
I can’t believe is that I never blogged about Escape Velocity before since it was a very influential book in how we managed a bunch of things at Return Path in the later years when we got larger and were more in “disrupt or be disrupted” mode. I’ll start with the essence of that book before I move onto Zone to Win. Escape Velocity‘s principal framework is to divide the different product lines/lines of business you have into three planning horizons:
- Horizon 1 (H1): Current businesses that should be profitable and sustainable
- Horizon 3 (H3): Nascent R&D efforts with the potential to be disruptors or game changers
- Horizon 2 (H2): The bridge between H1 and H3 where an R&D effort that is taking off is scaled and hopefully achieves the eponymous Escape Velocity
The essence of the book is to talk about how larger companies become completely slavish to H1 businesses, their cash cows, and struggle to escape from their pull, whether that’s internal resource allocation or customer-driven demands. Failure to innovate properly beyond H1 businesses is why companies die. But the rest of the book is a lot less memorable, and it doesn’t quite prompt you into action.
That’s where Zone to Win comes in, and it helps me understand where we really got a couple things really wrong at Return Path (as an aside, Moore once met my Return Path cofounder George at a conference, and when George described our business to him, he said “Ah, a blue collar business. Those can work, too.” I think I understand what he meant by that, although it doesn’t sound like a compliment!)
In Zone to Win, Moore shows you how to put the three Horizons into action by creating an overlay framework to managing your company to help optimize all three zones simultaneously. The four zones are:

The key takeaways for me from this framework as well as the notes of where we got things wrong at Return Path, even while acknowledging that we had to play across H1, H2, and H3 simultaneously, were:
- Performance Zone: Managing your main H1 business in a way that drives growth and customer success for the long haul
- Productivity Zone: Managing your main H1 business for optimal profitability and scalability
- Incubation Zone: Starting new H3 businesses and hoping they work
- Transformation Zone: Getting your H3 business through H2 and into H1 to the point where it’s at least 10% of your overall revenue
What we got right at Return Path was first recognizing that we needed to incubate new businesses as the growth in our core business started to slow down, as well as recognizing that we needed to step up our game in managing the core business for performance. So, Moore would say something like “congratulations, you drew up the correct strategy.” But we fell down on implementation for reasons in three of the four zones. Our problem with the Performance Zone is that we discovered the three horizon model too late — there were several years where we were running R&D experiments in the middle of the core business, which created chaos. By the time we got religion around it, we were constantly playing catch up redesigning our management processes — like the teenager still wearing his kid clothes looking awkward and misfit. In the Productivity Zone, we did invest in productivity, but we weren’t aggressive enough about insisting on End of Life for some programs or products, and and we were bogged down by a convoluted legacy implementation of our CRM system that we never wholesale fixed. But the biggest problem we ran into was in the Transformation Zone, where we tried to jam two new businesses through that zone at the same time instead of focusing all our energies on one. I bet we could have pulled off even more of a transformational success with our security business (the one further along) if we hadn’t also been trying to get our consumer insights business through H2 at the same time. At least Moore notes that’s the hardest zone to get right, so I don’t feel quite so dumb.
There were probably other exogenous factors that caused us to fall down on implementation, too, but I think this had a lot to do with it. And don’t get me wrong, Return Path was a success in the end. It just could have been more successful if we had caught this book and adhered rigorously sooner. It was even published in time — somehow we just missed it. We were lured by customer traction and market pull into thinking we could do both. And it’s certainly possible that we were advised against this by one or more of our board members and plowed ahead anyway.
Moore is a masterful writer. If you haven’t read Crossing the Chasm or Inside the Tornado, for example, if you’re a GenZ founder and you think “wow those books came out before I was born, they can’t be relevant,” you should start by reading them. They’re still 100% applicable today, and Moore’s subsequent editions have updated some of the case studies, even if not totally contemporary — and these are worth reading even as a raw startup (in fact, especially as a raw startup). But once you finish those and your business gets larger, go straight into Escape Velocity and be sure to add on Zone to Win.
Reboot – The Fountainhead
Reboot – The Fountainhead
Happy New Year! Every few years or so, especially after a challenging stretch at work, I’ve needed to reboot myself. This is one of those times, and I will try to write a handful of blog posts on different aspects of that.
The first one is about a great book. I just read Ayn Rand’s The Fountainhead for (I think) the 5th time. It’s far and away my favorite book and has been extremely influential on my life. I think of it (and any of my favorite books) as an old friend that I can turn to in order to help center myself when needed as an entrepreneur and as a human. The last time I read it was over 10 years ago, which is too long to go without seeing one of your oldest friends, isn’t it? While the characters in the book by definition are somewhat extreme, the book’s guiding principles are great. I’ve always enjoyed this book far more than Atlas Shrugged, Rand’s more popular novel, which I think is too heavy-handed, and her much shorter works, Anthem and We The Living, which are both good but clearly not as evolved in her thinking.
As an entrepreneur, how does The Fountainhead influence me? Here are a few examples.
- When I think about The Fountainhead, the first phrase that pops into my head is “the courage of your convictions.” Well, there’s no such thing as being a successful entrepreneur without having the courage of your convictions. If entrepreneurs took “no” for an answer the first 25 times they heard it, there would be no Apple, no Facebook, no Google, but there’d also be no Ford, no GE, and no AT&T
- One great line from the book is that “the essence of man is his creative capacity.” Our whole culture at Return Path, and one that I’m intensely proud of, is founded on trust and transparency. We believe that if we trust employees with their time and resources, and they know everything going on in the company, that they will unleash their immense creative capacity on the problems to be solved for the business and for customers
- Another central point of influence for me from the book is that while learning from others is important, conventional wisdom only gets you far in entrepreneurship.  A poignant moment in the book is when the main character, Howard Roark, responds to a question from another character along the lines of “What do you think of me?” The response is “I don’t think of you.” Leading a values-driven life, and running a values-driven existence, where the objective isn’t to pander to the opinion of others but to fill my life (and hopefully the company’s life) with things that make me/us happy and successful is more important to me than simply following conventional wisdom at every turn. Simply put, we like to do our work, our way, noting that there are many basics where reinventing the wheel is just dumb
- Related, the book talks about the struggle between first-handers and second-handers. “First-handers use their own minds. They do not copy or obey, although they do learn from others.” All innovators, inventors, and discoverers of new knowledge are first-handers. Roark’s speech at the Cortland Homes trial is a pivotal moment in the book, when he says, “Throughout the centuries, there were men who took first steps down new roads armed with nothing but their own vision. The great creators — the thinkers, the artists, the scientists, the inventors — stood alone against the men of their time. Every great new thought was opposed.” In other words, first-handers, critical thinkers, are responsible for human progress. Second-handers abdicate the responsibility of independent judgment, allowing the thinking of others to dominate their lives. They are not thinkers, they are not focused on reality, they cannot and do not build
- The “virtue of selfishness” is probably the essence of Rand’s philosophy. And it sounds horrible. Who likes to be around selfish people? The definition of selfish is key, though. It doesn’t inherently mean that one is self-centered or lacks empathy for others. It just means one stays true to one’s values and purpose and potentially that one’s actions start with oneself. I’d argue that selfishness on its own has nothing to do with whether someone is a good person or a good friend. For example, most of us like to receive gifts. But people give gifts for many different reasons – some people like to give gifts because they like to curry favor with others, other people like to give gifts because it makes them feel good. That’s inherently selfish. But it’s not a bad thing at all
- Finally, I’d say another area where The Fountainhead inspires me as a CEO is in making me want to be closer to the action. Howard Roark isn’t an ivory tower designer of an architect. He’s an architect who wants to create structures that suit their purpose, their location, and their materials. He only achieves that purpose by having as much primary data on all three of those things as possible. He has skills in many of the basic construction trades that are involved in the realization of his designs – that makes him a better designer. Similarly, the more time I spend on the front lines of our business and closer to customers, the better job I can do steering the ship
One area where I struggle a little bit to reconcile the brilliance of The Fountainhead with the practice of running a company is around collaboration. It’s one thing to talk about artistic design being the product of one man’s creativity, and that such creativity can’t come from collaboration or compromise. It’s another thing to talk about that in the context of work that inherently requires many people working on the same thing at the same time in a generalized way. Someday, I hope to really understand how to apply this point not to entrepreneurship, but to the collaborative work of a larger organization. I know firsthand and have also read that many, many entrepreneurs have cited Ayn Rand as a major influence on them over the years, so I’m happy to have other entrepreneurs comment here and let me know how they think about this particular point.
It feels a little shallow to try to apply a brilliant 700 page book to my life’s work in 1,000 words. But if I have to pick one small point to illustrate the connection at the end, it’s this. I realize I haven’t blogged much of late, and part of my current reboot is that I want to start back on a steady diet of blogging weekly. Why? I get a lot out of writing blog posts, and I do them much more for myself than for those who reads them. That’s a small example of the virtue of selfishness at work.
More Good Inc.
More Good Inc.
Last year I was pleased and proud to write about our debut on the Inc. 500 list of America’s fastest growing companies. At that time I wrote that “Now our challenge, of course, is STAYING on the list, and hopefully upping our ranking next year!” Well, I am again please and proud to announce that we, in fact, stayed on the list. (You can read all the Inc. coverage here and see our press release about the ranking here.)
Unfortunately, we didn’t make the second part of our goal to up our rank. But, we did up our growth – our three-year revenue growth rate was 18% higher than last year. This is a testament to the hard work of our team (now 150 strong!) and wouldn’t be possible without the support of our many great clients (now 1,500 strong!). Most importantly, we see no end in sight. In fact, 2008 promises to be an even bigger year for us as we poise for continued growth. By the way, would you like to be part of a team that has now ranked as one of America’s fastest growing companies two years in a row? Check out our Careers page and join the team that is advancing email marketing, one company at a time.