How Much Marketing Is Too Much Marketing?

It seems like a busy holiday season is already underway for marketers, and hopefully for the economy, shoppers as well.  Just for kicks, I thought I’d take a rough count of how many marketing messages I was exposed to in a given day.  Here’s what the day looked like:

5:30 a.m. – alarm clock goes off with 1010 WINS news radio in the middle of an ad cycle – 2 ads total.  Nice start to the day.

5:45-6:30 – in the gym, watching Today In New York News on NBC for 30 minutes, approximately 6 ad pods, 6 ads per pod – 36 ads total.  So we’re at 38, and it’s still dark out.

7:00 – walk to subway and take train to work, then walk to office from subway.  Probably see 6 outdoor ads of various kinds on either walk, then about 8 more on the subway within clear eyeshot – 20 ads total.

7:30 – quick scan of My Yahoo – 2 ads total.

7:32 – read Wall St. Journal online, 15 page views, 3 ads per page – 45 ads total.

7:40 – Catch up on RSS feeds and blogs, probably about 100 pages total, only 50% have ads – 50 ads total (plus another 25 during the rest of the day).

7:50 – Sift through email – even forgetting the spam and other crap I delete – 10 ads total (plus another 10 during the rest of the day).

8:00-noon – basically an ad free work zone, but some incidental online page views are generated in the course of work – 25 ads total, plus a ton of Google paid search ads along the way.

Noon-1 p.m. – walk out to get lunch and come back to office, so some outdoor ads along the path – 12 ads total.

1-7 p.m. – same work zone as before – 25 ads total, plus lots of Google.

7 p.m. – walk to Madison Square Garden to see the Knicks get clobbered by Milwaukee, see lots of outdoor ads along the way – 20 ads total.

7:30-9:30 – at the Garden for the Knicks game, bombarded by ads on the scoreboards, courtside, sponsorship announcements, etc.  Approximately 100 ads total (and that’s probably being exceptionally generous).

9:30 – subway ride and walk home – 14 ads total.

10:00 – blitz through episodes of The Daily Show and West Wing in TiVo.  8 minutes of :30 advertising per half hour, or 48 ads total, fortunately can skip most of them with TiVo.

11:00 – flip through issue of The New Yorker before bed – 50 ads total.

Total: 492 ads.

I’m sure I missed some along the way, and to be fair, I am counting the ads I skipped with TiVo — but hey, I’m also not counting all the ads I saw on Google, so those two should wash each other out.  On the other hand, if I drove to and from work in California, I’d have seen an extra 100 billboards, and if I read the New York Times print edition, I’d have seen an extra 100 print ads.

Approximate cost paid to reach me as a consumer today (assuming an average CPM of $10): just under $5.  Sanity check on that — $5/day*200 million Americans who are “ad seers”*365 days is a $365 billion advertising industry, which is probably in the right ballpark.

What are the two ads I consciously acted on?  An offer from LL Bean through email (I’m on their list) for a new fleece I’ve been meaning to get, and a click on one of the Google paid search results.  No doubt, I subconsciously logged some good feelings or future purchase intentions for any number of the other ads.  Or at least so hope all of the advertisers who tried to reach me.

What’s the message here?  A very Seth Godin-like one.  Nearly all of the marketing thrown at me during the day (Seth would call it interrupt marketing) — on the subway, at the Garden, on the sidebar of web pages — is just noise to me.  The ones I paid attention to were the ones I WANTED to see:  the email newsletter I signed up for from a merchant I know and love; and a relevant ad that came up when I did a search on Google.

Brand advertising certainly has a role in life, but permission and relevance rule the day for marketers.  Always.

Exciting News for Return Path

If you’ll indulge me in a quick moment of company self-promotion, we are so excited at Return Path to announce that we have been included in Fortune Magazine’s annual list of the Best Places to Work — we are ranked #11 in the Medium Size Company category!  Our official blog post/press release are here.

This is really exciting and a testament to all 360+ of our talented team members at the company.  When we talk about one of our core values as being Job 1 — a shared responsibility for championing and extending our unique culture as a competitive advantage — this is one of those examples of where the theory becomes reality!

Of the many things I may have had in mind for the Return Path of the future on December 6, 1999, winning what is probably the most prestigious “employer of choice” award in the world certainly wasn’t one of them, but it was wonderful to receive the acknowledgment.  Congratulations to the whole team here on this great achievement!

Someone asked me the other day how things are going at Bolster, the new company I started along with a bunch of long-time colleagues from Return Path last year. My visceral answer was “I’m having a blast!”  I thought about it more after and came up with five reasons why. 

First, I am working with a hand-picked group of people. My co-founders, I’ve worked with for an average of 15 years – we know and trust each other tremendously. And for the most part, the same is true about our cap table. Almost everyone else at the company is also someone multiple of us have known or worked with for years. That may not last forever, but it makes things so much easier and almost friction-free out of the gate here. 

Second, this is the “second lap around the track” for a few of us on the founding team in terms of starting something from scratch, and even those at the company who haven’t done a raw startup before are super experienced professionals and many have worked in and around early stage businesses a lot. All this combines to cut down our error rate, reduce anxiety, and speed up the pace of work. More friction-free or at least low-friction work.

Third, after a 20-year run at Return Path, it’s great to start with a clean slate. No mountains of tech debt and legacy code bases. No installed base of customers with contracts or pricing we no longer like or offer. No institutional debt like a messy cap table, legacy people issues, leases for offices we don’t want or need any more.  This also points to low friction as part of what’s going on…and while that’s a theme, the next two areas are different. 

The fourth reason I’m having a blast at Bolster is that I love — and really live in — the problem space we are working in.  When we started Return Path, I was deeply familiar with email marketing and the challenges faced by our client set and had a good vision for the early product.  But as the years went on, the product got geekier and nicher — and even when it wasn’t, I was never a USER of the product since I’m not an email marketer.  In fact, at our peak of 500 people, the company employed one email marketer and therefore had one user of our own product.  At Bolster, we have three user personas — Member, Client, and Partner.  And I’m all three of them.  I’m constantly in the product, multiple times a day.  I’m deeply familiar with all angles of the executive search and board building process.  It’s MUCH better to be this close to the product, and the same is true for many of our team members.

Finally, the thing I was really worried about with starting another company from scratch — moving from a leadership role into an individual contributor role — has been nothing short of fantastic.  I love working with clients.  I love talking to members.  I love advising and coaching CEOs. I love being a pretend product manager.  I love writing marketing copy.  It’s just great to be on the front lines. (I still love working on strategy and leading the board and engaging with people internally — but those are things that never stopped being part of my day to day.)

I was trying to think if there’s some priority to this list. Almost all of these items are or can be made to be true in your second+ startup. But while four of the five can theoretically be true in your first startup as well, I don’t think it’s quite the same. So I’d have to weight “second lap around the track” a bit higher and also note that during your second lap around the track, hand-picking your team and cap table, appreciating a clean slate, and appreciating individual contributor work are that much easier and things you can appreciate a lot more as a repeat entrepreneur.

Why I Love Our New Product

Return Path officially announced a new product today called Domain Assurance, which I blogged a little bit about here.  It’s a very exciting product that will help reduce and ultimately eliminate phishing emails – spam’s even more evil cousin that leads to identity theft, malware, further propagation of spam through botnets, and all sorts of other goodies.  The product is in beta now with a bunch of top ISPs and brands.

Those are a lot of reasons to love our new product.  But for me, there’s more.

For starters, this is the first new product (entirely new product, not just a feature or extension) that we’ve launched in years.  While we’ve made some acquisitions and done a ton of product development, they’ve always been right in our strike zone of deliverability.  This is a nice, deeply interrelated adjacency.  It’s fun to branch out a little bit and do something new.

Second, this product is a great example of operating leverage.  Many of the necessary ingredients for it were already in house – most notably customers and partners, but also a lot of data.  That’s what adjacencies should be about.  Building it, while a significant effort (and one that’s not completely done yet) was significantly easier than building, say, the original deliverability tool set or reputation database.  Let’s hear it for scale!

Finally, the product showcases Return Path’s commitment to open standards, which is fundamental to the Internet’s success.  We hope our new Domain Assurance product encourages more and more mailers to authenticate all of their outbound mail, and we hope the product also encourages the use of ADSP and ultimately some productive enhancements to both ADSP and DKIM.  Authentication does not equal reputation, but we’ve said for years it’s the fundamental underpinning of it.

Book Short:  Steve Jobs and Lessons for CEOs and Founders

First, if you work in the internet, grew up during the rise of the PC, or are an avid consumer of Apple products, read the Walter Isaacson biography of Steve Jobs (book, kindle).  It’s long but well worth it.

I know much has been written about the subject and the book, so I won’t be long or formal, but here are the things that struck me from my perspective as a founder and CEO, many taken from specific passages from the book:

• In the annals of innovation, new ideas are only part of the equation. Execution is just as important.  Man is that ever true.  I’ve come up with some ideas over the years at Return Path, but hardly a majority or even a plurality of them.  But I think of myself as innovative because I’ve led the organization to execute them.  I also think innovation has as much to do with how work gets done as it does what work gets done.

• There were some upsides to Jobs’s demanding and wounding behavior. People who were not crushed ended up being stronger. They did better work, out of both fear and an eagerness to please.  I guess that’s an upside.  But only in a dysfunctional sort of way.

• When one reporter asked him immediately afterward why the (NeXT) machine was going to be so late, Jobs replied, “It’s not late. It’s five years ahead of its time.”  Amen to that.  Sometimes product deadlines are artificial and silly.  There’s another great related quote (I forget where it’s from) that goes something like “The future is here…it’s just not evenly distributed yet.”  New releases can be about delivering the future for the first time…or about distributing it more broadly.

• People who know what they’re talking about don’t need PowerPoint.”  Amen.  See Powerpointless.

• The mark of an innovative company is not only that it comes up with new ideas first, but also that it knows how to leapfrog when it finds itself behind.  This is critical.  You can’t always be first in everything.  But ultimately, if you’re a good company, you can figure out how to recover when you’re not first.  Exhibit A:  Microsoft.

• In order to institutionalize the lessons that he and his team were learning, Jobs started an in-house center called Apple University. He hired Joel Podolny, who was dean of the Yale School of Management, to compile a series of case studies analyzing important decisions the company had made, including the switch to the Intel microprocessor and the decision to open the Apple Stores. Top executives spent time teaching the cases to new employees, so that the Apple style of decision making would be embedded in the culture.  This is one of the most emotionally intelligent things Jobs did, if you just read his actions in the book and know nothing else.  Love the style or hate it – teaching it to the company reinforces a strong and consistent culture.

• Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!’” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.  There’s always a tension between listening TO customers and innovating FOR them.  Great companies have to do both, and know when to do which.

• What drove me? I think most creative people want to express appreciation for being able to take advantage of the work that’s been done by others before us. I didn’t invent the language or mathematics I use. I make little of my own food, none of my own clothes. Everything I do depends on other members of our species and the shoulders that we stand on. And a lot of us want to contribute something back to our species and to add something to the flow. It’s about trying to express something in the only way that most of us know how—because we can’t write Bob Dylan songs or Tom Stoppard plays. We try to use the talents we do have to express our deep feelings, to show our appreciation of all the contributions that came before us, and to add something to that flow. That’s what has driven me.  This is perhaps one of the best explanations I’ve ever heard of how creativity can be applied to non-creative (e.g., most business) jobs.  I love this.

My board member Scott Weiss wrote a great post about the book as well and drew his own CEO lessons from it – also worth a read here.

Appropos of that, both Scott and I found out about Steve Jobs’ death at a Return Path Board dinner.  Fred broke the news when he saw it on his phone, and we had a moment of silence.  It was about as good a group as you can expect to be with upon hearing the news that an industry pioneer and icon has left us.  Here’s to you, Steve.  You may or may not have been a management role model, but your pursuit of perfection worked out well for your customers, and most important, you certainly had as much of an impact on society as just about anyone in business (or maybe all walks of life) that I can think of.

Why I Love My Board, Part III

My prophesy is starting to come true.  In Part I of this series four years ago, I asserted that

Fred may be the only one of my directors who has done something this dorky, this publicly, but quite frankly, I could see any of us in the same position.

Now, Brad Feld is no shrinking violet.  As far as I’m concerned, he made his film debut in the memorable “Munch on Your Bones” video (short, worth a watch if you’re a Feld groupie) something like 6 or 7 years ago for an all-hands meeting I ran.  But his newest short feature film, “I’m a VC,” made with his three partners, Jason, Ryan, and Seth, is a must-see for anyone in the entrepreneur-VC set and puts him up there with Fred in the pantheon of “this dorky, this publicly.”

Why We Love Email Authentication, But Why It Won’t Stop Spam

Microsoft made a big announcement today that they’re taking email authentication, in the form of Sender ID, very seriously.  They’re using a stick, not a carrot.  Emailers who do not publish a proper Sender ID record are now going to (a) find themselves in the bulk mail folder at Hotmail and MSN, and (b) have a big fat disclaimer thrown on top of their emails from Microsoft warning users that the email’s source can’t be authenticated.

At Return Path, we’re big fans of authentication, and we’re sponsoring the upcoming Email Authentication Summit in a couple of weeks in New York as one way of supporting the effort — encouraging our clients to get on the ball with authentication is another one.  Here’s what we think it will (and won’t) do:

– It WILL make a big dent in spoofing, phishing, and fraud, right away.  Why?  Because those particular elements of the Internet Axis of Evil are identity-based…therefore, identity authentication will either stop those things, make it easier for consumers to steer clear of them, or make it easier for law enforcement to go after them.

– It WILL NOT make a big dent in spam right away.  Why?  Because spam is much more nuanced than fraud.  If I’m Microsoft, and I know that you are the particular sender of an email into my network, that’s all good and well, but I might not have any idea if I want to accept that mail or not.  Another way of saying this is that spammers can publish Sender ID records, too.

– It WILL lay the foundation for longer-term spam solutions.  Why?  Because it’s important to understand exactly who is sending mail into a network in order to answer that next question of “do I want to accept your mail or not?”  We think the answers to that question lie with accreditation and reputation services.

Obviously, I have my biases.  Return Path owns Bonded Sender, the leading accreditation service, which answers that question by saying “yes – you want to accept this mail, because Return Path and TRUSTe have examined me thoroughly and are vouching for my integrity, they’re measuring how many people are complaining about my mail, and if I get too many complaints, they fine me and kick me out of the program.”

Look for another announcement from us soon about what we’re up to in the reputation space, which is a more complex cousin to accreditation in answering that same question.

Why I Love My Board

Fred may be the only one of my directors who has done something this dorky, this publicly, but quite frankly, I could see any of us in the same position.  Guys, next meeting, we’re having nerd olympics.

Why I Love My Board, Part II

I’ve written a few things about my Board of Directors over the years, some of which I note below.  Part I of this series isn’t particularly useful, though there’s an entertaining link in it to a video of Fred that’s worth looking at if you know or follow him.

Today, we are happy to announce that we are adding a new independent director, Scott Petry, the founder of Postini and now a senior email product leader at Google (read the official press release [here]).  Scott’s a fantastic addition to our already strong Board, and the process of recruiting and adding him has made me reflect a bit on my Board and its strengths and weaknesses, so I thought I’d share a couple of those thoughts here.

I think Return Path has cultivated a very high functioning Board over the years, and I feel very fortunate to have the group that we have.  Here are the top five things I think make our Board special, in no particular order.

1. We have great individuals on the Board.  Each of our individual Board members — Fred Wilson, Greg Sands, Scott Weiss, Scott Petry, and Brad Feld (now officially an observer), (in addition to me) — could anchor a super strong Board in his own right and have all served on multiple Boards of related companies.  And not only do these guys know their stuff…they do their homework.  They all come to every meeting very well prepared.
2. The individual Board members are different but have different experiences and personalities that complement each other nicely.  Among the three VCs on the Board, two have operating experience, one as a founder and one in product management.  Among the two industry CEOs, one has more of a business development focus, and the other has deep technical expertise.  Some directors are excitable and a bit knee-jerk, others are more reflective; some are aggressive and others are more conservative; some have extremely colorful metaphors, others are a bit more steeped in traditional pattern recognition.
3. We have built a great team dynamic that encourages productive conflict.  I assume a lot of rooms full of great directors of different types are so ego-laden that people just talk over each other.  Our group, for whatever reason, doesn’t function that way.  We are engaged and in each others’ faces during meetings, no one is afraid to voice an opinion, and we listen to each other.  Some of this may be the way we spend time together outside of Board rooms, which I wrote about in The Social Aspects of Running a Board. Some is about just making sure to have fun, which I wrote about in The Good, The Board, and The Ugly (Part I, Part II, Part III), I talk about other aspects of running a good Board, including making sure to have fun – that post includes an entertaining picture of now-Twitter CEO Dick Costolo and a few of his friends from his FeedBurner days.
4. We are deliberate about connecting the Board and the Executive team, and the rest of the company.  We encourage every director to have a direct relationship with every one of my direct reports.  They connect both during and outside of meetings, and they have gotten to know each other well over the years.  This is much more helpful to us than a more traditional “hourglass” structure where all connections go through the CEO.
5. We run great meetings.  We send out a single, well-organized document several days before the meeting.  Board members do their homework.  We focus on current and future issues more than reporting on historical numbers, and we no longer do any presentations — it’s all discussion (I also wrote about a lot of this here in PowerPointLess).

Welcome to the Return Path family, Scott P – we are delighted to have you on board our Board!

What Gets Said vs. What Gets Heard

I’ve been on the edge of a few different situations lately at work where what seems like a very clear (even by objective standards) conversation ends up with two very different understandings down the road.  This is the problem I’d characterize as “What gets said isn’t necessarily what gets heard.”  More often than not, this is around delivering bad news, but there are other use cases as well.  Imagine these three fictitious examples:

• Edward was surprised he got fired, even though his manager said he gave him repeated warnings and performance feedback
• Jacob thought his assignment was to write a proposal and get it out the door before a deadline, but his manager thought the assignment was to schedule a brainstorming meeting with all internal stakeholders to get everyone on the same page before finalizing the proposal
• Bella gets an interim promotion – she still needs to prove herself for 90 days in the new job before the promotion is permanent and there is a comp adjustment – then gets upset when the “email to all” mentions that she is “acting”

Why does this happen?  There are probably two main causes, each with a solution or two.  The first is that What Gets Said isn’t 100% crystal clear.  Delivering difficult news is hard and not for the squeamish.  What can be done about it?  The first problem — the crystal clear one — can be fixed by brute force.  If you are giving someone their last warning before firing him, don’t mumble something about “not great performance” and “consequences.”  Look him in the eye and say “If you do not do x, y, and z in the next 30 days, you will be fired.” 

The second cause is that, even if the conversation is objectively clear, the person on the receiving end of the conversation may WANT to hear something else or believes something else, so that’s what “sticks” out of the conversation.  Solving this problem is more challenging.  Approaching it with a lengthy conversation process like the Action Design model or the Difficult Conversations model is one way; but we don’t always have the time to prepare for or engage in that level of conversation, and it’s not always appropriate.  I’d offer two shortcut tips to get around this issue.  First, ask the person to whom you’re speaking to “play back in your own words what you just heard.”  See it she gets it right.  Second, send a very clear follow-up email after the conversation recapping it and asking for email confirmation.

People are only human (for the most part, in my experience), and even when delivering good news or assignments, sometimes things get lost in translation.  But clarity of message, boldness of approach, and forcing playback and confirmation are a few ways to close the gap between What Gets Said and What Gets Heard.

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.