The Beginning of the DMA’s Next Chapter

As I wrote a few months back, I recently joined the DMA’s Board of Directors and its Executive Committee to try to help the association – one of the largest and highest profile groups representing marketers – advance its agenda in a few specific ways.  At the time, I noted that my interests would be on consumer advocacy and engagement, execution around interactive marketing issues and the internet community, and transparency around the organization itself.

Yesterday, John Greco, the association’s CEO, announced he is stepping down to make way for the next generation of leadership.  John has done some great work the past five years running the DMA and has advanced it materially from where the association was when he took over in terms of interactive marketing, but he recognized (the hallmark of a good leader) that it was time for a change.

There are all sorts of questions people have about this announcement, and I’ve already gotten a number of calls and emails from people trying to read between the lines and get some inside scoop.  Some of the questions have answers – others don’t at this stage or can’t given confidentiality agreements. 

That said, as a new Board member helping the DMA build some bridges to the interactive marketing community, I thought I would share a few perspectives on this situation:

–          There is not a final search committee yet, nor are there final search criteria.  That said, there is a strong commitment to find a leader for the DMA who is not only capable of running a broad-based $30mm+ trade association and running a world class advocacy operating in Washington, but who also has deep roots in the Internet

–          There are many, many initiatives in the works – some of which have been underway for quite some time now – for the DMA to evolve as an association to more effectively execute its mission in the interactive marketing arena.  These will start to unfold relatively quickly

–          The DMA’s Board and Executive Committee are fantastic groups with very progressive, committed volunteers who understand the things that need to happen.  “Reform,” which probably isn’t quite the right word anyway, isn’t being pushed on the association – it is coming from within

–          The DMA is committed in its search process, and in its new “operating system” going forward, to embrace not just its membership but the broader interactive and direct marketing community as it evolves its strategy, broadens its mission, and looks for a new leader

So the bottom line is – this announcement of one change is the first of many.  Stay tuned, and look for much more open and transparent communication from the DMA, including a lot more community-oriented dialog as opposed to just one-way statements, than you’ve ever seen before in the coming weeks and months.

Post 4 of 4 in the series of Scaling CMO’s- the other posts are, When to Hire your First Chief Customer Officer, What does Great Look like in a Chief Customer Officer and Signs your Chief Customer Officer isn’t Scaling.

You can engage with each person on the executive team one-on-one to understand what their issues and challenges are, but I’ve found that engaging with the CCO offsite with customers is far more productive and leads to a better understanding of the service organization than any other meeting time. I have typically spent the most time with or gotten the most value out of CCOs over the years doing the following.

In person at “Canary in the Coal Mine” customers. They don’t use canaries any more in coal mines, but the principle applies to companies: What are the early warning signs that you’ve got big problems looming? The earlier you discover those problems the better, and the CCO is usually the first person to figure out that something isn’t right with your product or service. I always find that the largest clients, the most demanding ones, the ones who push you around, the ones who are highly critical or you, are the ones who make your company a better company.  At Return Path, we had those types of clients over the years, from eBay, to DoubleClick, to Microsoft, to Groupon, to Facebook, to Bank of America—and that’s just the short list off the top of my mind.  The demanding customer is the one who breaks things and forces you to own up to your lack of scalability.  They also either take you to task or threaten to pull their business if you don’t clean up your act.  As painful as some of those meetings are, they are also ones I always wanted to attend in person with my CCO, both so I could eat whatever form of crow needed to be eaten as the Chief Crow Eater (which sends a very powerful message to the customer), and also because the CCO and I could experience the chirping of the canary in the coal mine and learn from the experience together.

While it’s important to engage with the CCO in the critical meetings with demanding customers, it’s also important to understand the base.  There’s an old saying from the hardware world that goes, “God was able to create the world in only 7 days because God didn’t have an installed base.”  The new world of Internet technologies, SaaS, and agile development is one where your installed base of customers is your biggest asset, not a millstone around your neck.  Some of the most meaningful experiences I had over the years with our CCOs was to be in market, spending time with all kinds of customers together in small groups and large, deeply understanding their needs and use of our product.

The CCO role is one that is easy to ignore or put on the back burner if things are going smoothly at your company, but as CEO I feel that it is best to stay close to the market and engaging with the CCO with demanding customers and with the base is a good way to understand your company and CCO better.

(You can find this post on the Bolster Blog here)

I recently returned from a six-week sabbatical. It was fantastic. I blogged about it here if you’re curious about the experience. It turned out that, while I was gone, we had probably the most successful, least dramatic six weeks in our 10 year history. I had assumed that’s because the team buckled down while I was out, and so did our Board.

Little did we know what really happened during that six week stretch. It’s often said that when the cat’s away, the mice play. The short video below is what greeted me today at an all-hands meeting. If the team can crank out such great work and have this much fun while I’m out, well, I guess I should take more time off!

Agile Development

Sometime last year, our engineering and product teams embraced the Agile Software Development framework.  Without going into too much detail (here’s the Wikipedia entry for those who want it), the concept of Agile Development is to run software development in small pieces with a focus on more communication between product and development teams resulting in collaborative requirements development.  This leads to a “release early and often” environment where there are continual improvements.  For us, we group development projects now into a “release” that consists of a series of usually six, two-week “iterations.”

The release planning and iteration planning meetings are reasonably long meetings that involve the major stakeholders, product management and engineering.  The process also includes a very short, 10-minute Daily Stand-Up meeting with everyone on the team to review progress and identify roadblocks to completing the two-week iteration.  Requirements are not heavily documented and discussed more or less on the spot during the iteration meetings.  Because there’s a major pull-up every two weeks and a minor one every day, it’s easy to be light on requirements and for product management to constantly be in the loop with engineering to see progress, test functionality, and make mid-course corrections.

This methodology isn’t for everyone, but it’s particularly well suited to the kind of work we do at Return Path — small team, multiple internal and external stakeholders, very dynamic market, and web services as opposed to packaged software.

Our efforts have been bolstered by some limited consulting and more important, a fantastic web-based workflow management tool geared towards Agile Development run by a company called Rally Development in Boulder.  Think of it as Salesforce.com for your engineering and product team.

We’ve had great success with this methodology to date.  Engineering productivity is way up, product management visibility and input into development is way up, the level of friction/noise between product management and engineering is way down, and we have a much tighter grip on our development milestones than we ever have in the past.

Agile and Rally have worked so well for us, in fact, that we’re starting to extend the concept to other parts of our business, which I’ll write about separately.

The Nachos Don’t Have Enough Beef in Them

Short story, two powerful lessons.

Story:  I’m sitting at the bar of Sam Snead’s Tavern in Port St. Lucie, Florida, having dinner solo while I wait for my friend to arrive.  I ask the bartender where he’s from, since he has a slight accent.  Nice conversation about how life is rough in Belfast and thank goodness for the American dream.  I ask him what to order for dinner and tell him a couple menu items I’m contemplating.  He says, “I don’t know why they don’t listen to me.  I keep telling them that all the people here say that the nachos aren’t good because they don’t have enough beef in them.”  I order something else.  Five minutes later, someone else pounds his hand on the bar and barks out “Give me a Heineken and a plate of nachos.”  The bartender enters the order into the point-of-sale system.

Lesson 1:  Listen to your front-line employees – in fact, make them your customer research team.  I’ve seen and heard this time and again.  Employees deal with unhappy customers, then roll their eyes, knowing full well about all the problems the customers are encountering, and also believing that management either knows already or doesn’t care.  Or both.  There’s no reason for this!  At a minimum, you should always listen to your customer-facing employees, internalize the feedback, and act on it.  They hear and see it all.  Next best prize – ask them questions.  Better yet – get them to actively solicit customer feedback.

Lesson 2:  Always remember another person’s person-ness, especially if he or she is in a service role.  The old story about the waiter spitting and coughing in the obnoxious customer’s soup would dictate that self-preservation, if nothing else, should inspire civility towards people who are serving you, be it a B2B account manager or a waiter in a diner.  Next best prize – self-interest to get a higher level of service.  Better yet – engagement and kindness like you’d want people to show you.  Chances are, they’re trying to make your day a bit better.  Shouldn’t you try to do the same for theirs?

(Lesson 3:  Always listen to your bartender!)

The old carpenter’s axiom of being extra careful to plan before executing is something not enough executives take to heart in business. Just like cutting a piece of wood a little too long, sometimes you execute in ways that can be modified on the fly; but other times, just like the cases where you cut a piece of wood too short, you can’t. And of course, in business, sometimes it’s somewhere in between. Some examples:

• One example that’s a little more literal is around cutting staff or planning a layoff. Layoffs are traumatic for everyone involved – mostly those impacted, but for you as CEO and for your remaining organization as well. Being thoughtful about how much you cut and (unlike the case of a piece of wood) erring on the side of cutting more than you think you need to can prevent you from having to do a second set of even more traumatic layoffs down the road
  
• Getting a lease on a new office? Plan, plan, and plan again – you can end up spending too much if you get too much space and can’t sublet it…you have a real headache if you don’t get enough space and need to scramble for more
  
• Planning a major investment in a new product? You don’t want to spin up a whole new effort internally and hire people before you’ve done enough discovery and planning to know it’s worth it

It’s an interesting question as to whether or not this axiom conflicts with the startup mentality of moving quickly and with agility. I don’t think it does, although in the startup ecosystem, a lot of fixed decisioning has moved to variable, which means you may be faced with fewer times where you need to measure twice. For example, a lot of SaaS licenses you have to buy are per-seat, or AWS costs are fluid. All that is much easier than perpetual license software models or standing up servers in a data center.

I’m a big fan of Eisenhower’s line that “plans are nothing but planning is everything.” That’s why I like to measure twice, cut once when I’m working on something big. It just raises the odds of getting it right, whatever it is.

Almost a year into my second journey as a startup CEO at Bolster, and I’m getting more and more questions from other CEOs about what it’s like doing a second startup after almost 20 years at the first one…and achieving pretty good scale by the end.  The short answer is, it’s the same, only it’s way better.  Here’s why.

I’m more confident.  So is our whole founding team.  When Jack and I started Return Path, we were 29.  This time, we were 49 — and the average age of the founders was probably 46 or 47.  The bottom line is that we don’t know everything about the business we’re building, but we know what we’re doing in terms of building a business, a startup, a software company, a service-oriented business, leading a team, planning, executing, and on and on.  Confidence in all of those areas means large portions of our day and brain space are freed up to focus on the actual construction of the business without worrying if we’re doing things right or wrong.

It’s much easier to build a startup today.  1999 wasn’t the dark ages, but it feels like a different millennium in terms of what it’s like to start a technology company from scratch.  The cloud and micro services/APIs mean that we are able to build our platform much more quickly at much lower cost than in the past.  And in terms of tooling the business, we got up and running with about 20 different DIY cloud/SaaS solutions in about 6 weeks for a cost of less than $10k/year.

We are sharper on execution and impatient for success.  Your first startup in your 20s is a lot about “enjoying the startup journey.”  This time around, our team is significantly more focused on critical stage-gate success metrics.  In both cases of course, the objective was to win, but this time around, we are much more focused on getting to that point sooner and with less waste.

We are a lot more productive.  Ok, fine, we’re cheating because of COVID and working from home.  No train commutes.  No plane trips.  No water cooler chatter.  No fluff.  It’s not sustainable, and I’ll write about that more in a future post.  But it’s leading to a surge of productivity like I’ve never experienced or seen before in my career.  I do like to think at least some of it comes from professional maturity — we’ll see when life returns to something more closely approximating normal.

I am having a blast being on the front lines.  I went from running a 500-person company, where I’d honed my job and skill set around communication, people issues, and mobilizing the army to go do things…to spending less than 5% of my time running the company and managing people.  Now depending on the moment, I’m an SDR, a customer success manager, a product manager, and a marketing copywriter.  And probably some other things, too.  And I love every minute of it.  It’s a lot more fun to see the direct impact of my actions on the business as opposed to only really seeing the direct impact of my actions on the people in the business (and occasionally then on some aspect of the business as an individual contributor).

Maybe I’m not having a typical second startup experience.  I know some friends who had successful first exits and hated going back to square one, or failed at a second business and were really disappointed about it, only to shift careers.  But my experience so far is a much better second verse, even though it’s a bit like the first.

I wrote part I of this post in 2011, and I feel even more strongly about it today. I generally keep this blog away from politics (don’t we have enough of that running around?), but periodically, I find some common sense, centrist piece of information worth sharing. In this case, I just read a great and very short book, Six Amendments: How and Why We Should Change the Constitution, by former Supreme Court Justice John Paul Stevens, that, if you care about the polarization and fractiousness going on in our country now, you’d appreciate.

If nothing else, the shattered norms and customs of the last several years should point people to the fact that our Constitution needs some revision. Not a massive structural overhaul, but some changes on the margin to keep it fresh, as we approach its 250th anniversary in the next couple decades.

You, Too, Can Take Six Weeks Off

Note:  I have been really quite on OnlyOnce for a few months, I realize.  It’s been a busy stretch at work and at home.  I keep a steady backlog of blog topics to write about, and finally today I’ve grabbed a couple minutes on a flight to knock one out.  We’ll see if this starts me back on a more steady diet of blogging – I miss it!

I’ve written in the past about our sabbatical policy at Return Path, from what it is (here) to how much I enjoyed my own (here), to how great it is when my direct reports have been on Sabbatical so I can walk a few miles in their shoes (here and here).

But recently, a fellow CEO asked me if there was a special set of rules or advice on taking a sabbatical as a CEO.  My quick answer to his specific question was:

Well, first, you and your co-founder can’t take them at the same time. 🙂

But I have a longer list of thoughts as well.  It’s not easy, but as I’ve said many times, it’s important and wonderful.  Some tips:

• You have to make sure your balance sheet is strong and you’re not raising a round of financing
• You’re best off doing it a week or two after a Board meeting (and obviously, don’t miss one)
• You need everyone on your team to know about it and get excited for you!  They will rally/rise to the occasion more than you think
• You have to do a total disconnect, otherwise it doesn’t count.  Literally turn off email.  But make sure the team knows they can call you if there’s a true emergency
• Put someone in charge of keeping a running list of things that happened and be in charge of your “re-boarding”
• Put one person clearly in charge while you’re out, or tell your senior team that they’re responsible for collectively being in charge – either can work as long as you’re clear about it
• Be prepared to cancel or shift your plans if an emergency comes up before you leave

This last one is important.  I’ve postponed sabbaticals twice, and while it’s been a little tumultuous both at work and at home, it’s been better than going on a sabbatical and interrupting it with work, which I’ve also done.

Speaking of which…I’m coming up on my 17^th anniversary, which in our book means it’s time for another one!

The 90-Day Reverse Review

Like a lot of companies, Return Path does a 90-day review on all new employees to make sure they’re performing well, on track, and a good fit.  Sometimes those reviews are one-way from the manager, sometimes they are 360s.

But we have also done something for years now called the 90-Day Reverse Review, which is equally valuable.  Around the same 90-day mark, and unrelated to the regular review process, every new employee gets 30 minutes with a member of the Executive Committee (my direct reports, or me if the person is reporting to someone on my team) where the employee has a chance to give US feedback on how WE are doing.

These meetings are meant to be pretty informal, though the exec running the meeting takes notes and circulates them afterwards.  We have a series of questions we typically ask, and we send them out ahead of time so the employee can prepare.  They are things like:

-Was this a good career move?  Are you happy you’re here?

-How was your onboarding experience?

-How do you explain your job to people outside the company?

-What is the company’s mission, and how does your role contribute to it?

-How do you like your manager?  Your team?

-Do you feel connected to the company?  How is the company’s information flow?

-What has been your proudest moment/accomplishment so far?

-What do you like best about the company?

-If you could wave a wand and change something here, what would it be?

We do these for a few reasons:

-At the 90-day mark, new employees know enough about the company to give good input, and they are still fresh enough to see the company through the lens of other places they’ve worked

-These are a great opportunity for executives to have a “Moment of Truth” with new employees

-They give employees a chance to productively reflect on their time so far and potentially learn something or make some course correction coming out of it

-We always learn things, large or small, that are helpful for us as a management team, whether something needs to be modified with our Onboarding program, or whether we have a problem with a manager or a team or a process, or whether there’s something great we can steal from an employee’s past experiences

This is a great part of our Operating System at Return Path!

Child Prodigies, or Misspent Youths?

I just got an email from a reader of this blog with a subject line of "15 year-old entrepreneur" and a series of engaging questions around starting a business (and actually, quite a good idea for one as well).  It got me thinking about being a kid and being an entrepreneur at the same time.  The author of this email is impressively savvy and focused on the world of business and startups.

Ben Casnocha is another one.  Ben is 19, has already started two companies, and has written and published a book called My Startup Life. 

When I was 15, I actually did have an inkling that I was going to go into business someday, and probably even that I wanted to start a business someday.  After all, it’s what my dad did, and what both of my grandfathers did.  But the key words in that sentence are INKLING and SOMEDAY.  I’m not sure it would have occurred to me in a million years to actually start a real business.  I suppose I could have figured out how.  But I wasn’t interested in doing it, or I didn’t have a good peer network of business-minded teens, or something.

It’s interesting to think about whether or not I’d be a better entrepreneur or CEO today if I’d started entrepreneurial pursuits at age 15 instead of age ~25.  Certainly, one makes a huge number of mistakes the first time one does anything, so perhaps better to get those out of the way early.  But I have to imagine that there are some things that one learns with age about dealing with other people that can’t be hurried up just because one starts businesses early.

Anyway, my hat is off to guys like Ben and the even younger guy who wrote into me…I just hope they’re making enough time for more standard teenage fun with their friends as well!