A couple weeks ago, I blogged about some innovations we’d made in People practices around basic benefits. But that post raised questions for me like “Why do you spend money on things like that when all people care about is their salary? When they get poached by another company, all they think of it the headline number of their base compensation, unless they’re in sales and think about their OTE.”

While that is hard to entirely argue against, one thing you can do as you layer in more and more benefits on top of base salary, you can, without too much trouble, produce annual “Total Rewards Statements” for everyone on your team. We did this at Return Path for several years when we got larger, and it was very effective.

The concept of the Total Rewards Statement is simple. At the beginning/end of the year, produce a single document for each employee – a spreadsheet, or a spreadsheet merged into a doc, that lists out all forms of cash compensation the employee received in the prior year and also has a summary of their equity holdings.

For cash compensation, start with base salary and any cash incentive comp plans. Add in all other classic benefits like the portion of the employee’s health insurance covered by the company, any transit benefits, gym memberships or wellness benefits, 401k match, etc. Add in any direct training and development expenses you tracked – specific stipends, training courses, conferences, education benefits, subscriptions, or professional memberships you sponsored the employee attending. All of that adds up to a much larger total than base salary.

If you have some other program like extensive universally available and universally consumed food in the office (or a chef, if you’re Google), you could even consider adding that to the mix, or perhaps having a separate section for things like that called “indirect benefits” so employees can see the expenses associated with perks and investment in their environment.

Finally, put together a summary of each employee’s equity. How many options are vested? Unvested and on what schedule? What’s the strike price? What’s the value of the equity as of the most recent financing? What’s the value of the equity at 3 other reasonable exit values? Paint the picture of what the equity is actually likely to be worth some day.

Yes, you could do these things and still lose an employee to Google or whoever offers them $50k more in base salary. It happens. But if you’re doing a great job with your culture and your business and people’s roles and engagement in general, having a Total Rewards Statement at least makes it easy for you to remind employees how much they *really* earn every year.

(Excerpted from Chapter 12 of Startup CEO)

As a CEO, one of the most important things you can do is solicit feedback about your own performance. Of course, this will work only if you’re ready to receive that feedback! What does that mean? It means you need to be really, really good at doing four things:

1. Asking for feedback
2. Accepting feedback gracefully
3. Acting on feedback
4. Asking for follow‐up feedback on the same topic to see how you did

In some respects, asking for it is the easy part, although it may be unnatural. You’re the boss, right? Why do you need feedback? The reality is that all of us can always benefit from feedback. That’s particularly true if you’re a first‐time CEO. Even more experienced CEOs change over time and with changing circumstances. Understanding how the board and your team experience your behavior and performance is one of the only ways to improve over time. It’s easier to ask for feedback if you’re specific. I routinely solicit feedback in the major areas of my job (which mirror the structure of this book):

Strategy. Do you think we’re on target with what we’re doing? Am I doing a good enough job managing to our goals while also being nimble enough to respond to the market?

Staff management/leadership. How effective am I at building and maintaining a strong, focused, cohesive team? Do I have the right people in the right roles at the senior staff level?

Resource allocation. Do I do a good enough job balancing among competing priorities internally? Are costs adequately managed?

Execution. How do the team and I execute versus our plans? What do you think I could be doing to make sure the organization executes better?

Board management/investor relations. Do you think our board is effective and engaged? Have I played enough of a role in leading the group? Do you as a director feel like you’re contributing all you can? Do I strike the right balance between asking and telling? Are communications clear enough and regular enough?

Accepting feedback gracefully is even harder than the asking part. You may or may not agree with a given piece of feedback, but the ability to hear it and take it in without being defensive is the only way to make sure that the feedback keeps coming. Sitting with your arms crossed and being argumentative sends the message that you’re right, they’re wrong, and you’re not interested. If you disagree with something that’s being said, ask questions. Get specifics. Understand the impact of your actions rather than explaining your intent.

The same logic applies to internalizing and acting on the feedback. If you fail to act on feedback, people will stop giving it to you. Needless to say, you won’t improve as a CEO. Fundamentally, why ask for it if you’re not going to use it? And that leads right into the fourth point, closing the loop with the person who gave you feedback on whether or not your actions achieved the desired change.

Living With Less…For Good?

Like all companies, Return Path is battening down the hatches a bit on expenses these days.  Our business is very strong and still growing nicely, but in this environment, the specter of disaster looms large, so there's no reason not to be more cautious and more profitable.

We weren't an extravagant company before this, and we never have been. But there is almost always room to save. Less travel, leaner budgets for office cafeterias, no more pilates classes in the Colorado office.  We've been very clear internally that our three priorities are protecting everyone's job, everyone's salary, and everyone's health benefits.  Hopefully things continue to go well and those can remain sacrosanct.

We are now a few months into our various cost savings plans, and it's great to see the results on the income statement and balance sheet.  More than that, it's great to see how everyone in the company is rallying around the common cause and looking for other ways to save money as well.  We've made it chic to be cheap.  And so far, there's no impact on the business. 

It will be interesting to me to see what happens on the far end of this economic badness.  It's often said the companies that make it through times like these emerge stronger on the other side, and I think I now understand why:  it's clear to me that some of the changes will work long term and some will only work short term, which means that we'll learn during this period that we can live with less. 

That doesn't mean we were profligate in the past; but it does mean that I think we are going to retrain ourselves.  We don't have to send 10 people to a big trade show to have an impact and drive the business forward.  We don't have to be the vendor who picks up the tab at the end of the night.  We don't need to pay for half the company to have cell phones (a very 1999 policy) to retain top talent.  I bet we will learn those things — and a bunch of others to come — in the next few months.

(This is going to be an interesting week.  I expect in a couple days, a group of friends and former Return Path colleagues and I are going to officially start a new company once initial funding closes.  I will write about that down the road, but first, this message brought to you by COVID-19.)

I just returned from spending an intense two weeks in Denver.  On March 15, my long-time friend and Board member Brad Feld called me with an interesting idea.  His friend, Colorado Governor Jared Polis (who I’d met a briefly couple times over the years), had an idea of starting and rapidly scaling up a task force in the state government and wanted to tap a private sector entrepreneur to lead the effort.  After some back and forth over 36 hours, and strong encouragement from Mariquita to go help despite the pending lockdown at home in New York, I decided to jump on a plane and go do it. Here’s the description of the group, called the Innovation Response Team (IRT) that I wrote up on LinkedIn:

Governor Jared Polis established the state of Colorado’s COVID-19 Innovation Response Team (IRT), and I was its initial leader to get it off the ground. The team is responsible for pulling together rapid-response creative programs as part of the state’s response to the pandemic that require entrepreneurial, out-of-the-box thinking and deep connections to the private sector (as well as cross-agency within various levels of government), integrated with the state’s Emergency Operations Center. Along with two key deputies from state government, I was responsible for starting the group, both the public sector and private sector sides; recruiting the state team, a leader for the private sector side, and a long-term replacement for myself; and leading the development of the group’s structure, workstreams, and initial plans along with the rest of the team. In the first two weeks, the team grew from 0 to over 200 people (including an army of private sector volunteers) and started to make a significant impact on the state’s response to the crisis.

At Brad’s suggestion out of the gate, I took daily notes as the project unfolded.  I thought the most interesting way to present the experience here on OnlyOnce (because you *definitely* Only lead a COVID-19 state emergency task force Once) would be to share the daily chronicle, a few days at a time, along with a couple photos I took along the way.  So I’ll do that here, then at the end, I’ll do a wrap-up post that compares the work to running a private sector company.  Because the pace of news around COVID-19 is moving so fast, I’ll post a few days’ worth of daily notes at a time.

Sunday, March 15 – Day -1

• Brad text/call to ask me if I’m interested in doing this
• Lukewarm – not excited about leaving home for 2-4 weeks
• Mariquita encourages me to do it – “when else are you going to get an opportunity to have an impact like this?”
• Jared (Governor) called (spoke a mile a minute), outlined his vision and a couple potential workstreams and discussion ends with “talk tomorrow”
• Can’t sleep – started a Google doc in bed with notes on the first workstreams

Monday, March 16, Day 0

• More back and forth with Jared and his team – Lisa (Chief of Staff) and Stan (supervising cabinet member)
• Officially invited to come at 3 pm
• Kids bummed but supportive
• By 6 pm, packed, cleaned up odds and ends at home and was in a car to Kennedy
• 8 pm flight and airport both still ⅔ full 
• Feeling full of purpose
• Worked on more reading and enhanced doc and Day 1 goals
• Texted Brad:  “Thank you. Wish me luck. I don’t know what the fuck I’m doing. Fortunately I never have and that’s usually been ok.”  Brad LOL.
• Notified parents…a bit shocked
• Good to see and surprise Khalid, the driver we used for years at Return Path
• Crashed in extended stay hotel

Stay tuned for more tomorrow! Apologies if any of these notes or posts aren’t quite right…anyone who was there doing the work with me, please send me any corrections you’d like me to post!

The Value of Paying Down Technical Debt

Our Engineering team has a great term called Technical Debt, which is the accumulation of coding shortcuts and operational inefficiencies over the years in the name of getting product out the door faster that weighs on the company’s code base like debt weighs on a balance sheet.  Like debt, it’s there, you can live with it, but it is a drag on the health of the technology organization and has hard servicing costs.  It’s never fun to pay down technical debt, which takes time away from developing new products and new features and is not really appreciated by anyone outside the engineering organization.

That last point is a mistake, and I can’t encourage CEOs or any leaders within a business strongly enough to view it the opposite way.  Debt may not be fun to pay off, but boy do you feel better after it’s done.  I attended an Engineering all-hands recently where one team presented its work for the past quarter.  For one of our more debt-laden features, this team quietly worked away at code revisions for a few months and drove down operational alerts by over 50% — and more important, drove down application support costs by almost 90%, and all this at a time when usage probably doubled.  Wow. 

I’m not sure how you can successfully scale a company rapidly without inefficiencies in technology.  But on the other side of this particular project, I’m not sure how you can afford NOT to work those ineffiencies out of your system as you grow.  Just as most Americans (political affiliation aside) are wringing their hands over the size and growth of our national debt now because they’re worried about the impact on future generations, engineering organizations of high growth companies need to pay attention to their technical debt and keep it in check relative to the size of their business and code base.

And for CEOs, celebrate the payment of technical debt as if Congress did the unthinkable and put our country back on a sustainable fiscal path, one way or another!

As a long Post Script to this, I asked our CTO Andy and VP Engineering David what they thought of this post before I put it up.  David’s answer was very thoughtful and worth reprinting in full:

 I’d like to share a couple of additional insight as to how Andy and I manage Tech Debt in the org: we insist that it be intentional. What do I mean by “intentional”

•  There is evidence that we should pay it
• There is a pay off at the end

 What are examples of “evidence?”

•  Capacity plans show that we’ll run out of capacity for increased users/usage of a system in a quarter or two
• Performance/stability trends are steadily (or rapidly) moving in the wrong direction
• Alerts/warnings coming off of systems are steadily or rapidly increasing

 What are examples of “pay off?”

•  Increased system capacity
• Improved performance/stability
• Decreased support due to a reduction in alerts/warnings

 We ask the engineers to apply “engineering rigor” to show evidence and pay-offs (i.e. measure, analyze, forecast).

 I bring this up because some engineers like to include “refactoring code” under the umbrella of Tech Debt solely because they don’t like the way the code is written even though there is no evidence that it’s running out of capacity, performance/stability is moving in the wrong direction, etc. This is a “job satisfaction” issue for some engineers. So, it’s important for morale reasons, and the Engineering Directors allocate _some_ time for engineers to do this type of refactoring.  But, it’s also important to help the engineer distinguish between “real” Tech Debt and refactoring for job satisfaction.

Challenging Authority

My dad told me a joke once about a kid who as a teenager thought his father was the dumbest person he’d ever met. But then, as the punchline goes, “By the time I’d graduated college, it was amazing how much the old man had learned.”

The older we get as humans, the more we realize how little we know — and how fallible we are. One of our 13 core values at Return Path gets right to the heart of this one:

We challenge complacency, mediocrity, and decisions that don’t make sense

I will note up front that this particular value statement is probably not as widely practiced as most of the others I’m writing about in this series of posts, but it’s as important as any of the others.

Very few things make me happier at work than when an employee challenges me or another leader — and quite frankly, the more junior and less well I know the employee, the better. No matter what the role, we hire smart, ambitious, and intellectually curious people to work at Return Path. Why let all that raw brainpower go to waste?  We thrive as a company in part because we are all trying to do a better job, and because we work with our eyes open to the things happening around us.

I have no doubt that some real percentage of the decisions that I or other leaders of the company make don’t make sense, either in full or in part. And I’m sure that from time to time we become complacent with things that are running smoothly or quietly, even if they’re not optimal or even moderately destructive.  That’s why I’m particularly grateful when someone calls me out on something. We have made great strides in and changes to the business over the years because someone on the team has challenged something. We’ve terminated employees who were poisonous to the organization, we’ve reversed course on strategic plans, we’ve even sold a business unit.

One of the things we do well is blend this value with one I wrote about a few weeks ago about being kind and respectful to each other.  The two play together very nicely in our culture.  People are generally constructive when they have feedback to give or are challenging authority, and people who receive feedback or challenges assume positive intent and nothing personal.  We specifically train people around these delicate balances both via the Action/Design framework and a specific course we teach called Giving and Receiving Feedback.

It takes courage to challenge authority. But then again, nothing great is ever accomplished in life without courage (and enthusiasm, so the old adage goes).

Fred beat me to it. I wasn’t at a computer to post this yesterday on the actual 4th of July, so today will have to do. I’ve read lots of books on the American revolution and the founding fathers over the years. It’s absolutely my favorite historical period, probably because it appeals to the entrepreneur in me. Think about what our founding fathers accomplished:

– Articulated a compelling vision for a better future with home democratic rule and capitalist principles. Life, liberty, and the pursuit of happiness is really the ultimate tag line when you think about it.

– Raised strategic debt financing from, and built critical strategic alliances with France, the Netherlands, and Spain.

– Assembled a team of A players to lead the effort in Washington, Adams, Jefferson, Franklin, Hamilton, and numerous others who haven’t been afforded the same level of historical stature.

– Built early prototypes to prove the model of democratic home rule in the form of most of the 13 colonial assemblies, the Committees of Correspondence, and the Articles of Confederation.

– Relentlessly executed their plans until they were successful, changing tactics several times over the years of 1774-1783 but never wavering from their commitment to the ultimate vision.

– Followed through on their commitments by establishing a new nation along the principles to which they publicly committed early on, and taking it to the next level with the Constitution and our current form of government in 1789.

And let’s not forget, these guys accomplished all of this at a time when it took several days to get a letter from Virginia to Boston on horseback and six weeks to get a message across the Atlantic on a sailboat. Can you imagine what Washington would have been able to accomplish if he could have IMd with Adams in Paris?

So happy 4th to all, with a big thanks to this country’s founding fathers for pulling off the greatest spin-off of all time.

Promiscuity

I figure the title will entice someone new to read this (although he or she might be sorely disappointed with the actual content).  Fred’s posting today about VCs’ conflicts of interest, besides giving me fodder for my weekly counter-cliche posting, brings up another interesting point, one about entrepreneurs and their levels of confidentiality or secrecy about their business plans.

I heard a quote once from Vinod Khosla of Kleiner Perkins that has stayed with me for years:  that “to be successful in the new economy you must be open to the point of promiscuity.”  I think Khosla is right.  As Fred says, VCs are notorious for meeting lots of companies before making an investment, and as an entrepreneur on the other side of the table, it’s impossible to completely protect your ideas and thoughts if you want to attract outside capital.  You just have to trust that the VCs are going to be as honest as possible in how they use the information you share with them.  Same goes for potential partnerships and even M&A as well.  You simply can’t have productive conversations on those topics without opening the proverbial kimono at least a little bit.

But being promiscuous with the state secrets of your business carries certain risks as well.  If the partnership or M&A conversation goes awry, you could easily find yourself with a competitor that knows part of your game plan.  We’ve had this happen at least once at Return Path, and to this day, it still irritates the heck out of us.  But we still think we made the right decision at the time to share that information — and now at least we know that our new competitor isn’t creative enough to come up with his own ideas!

On a completely side note, anyone who’s not using desktop search like Google or the Lookout plugin for Outlook is missing out.  I couldn’t remember the exact quote from Vinod Khosla, but I remembered that it was emailed to me years ago by my colleague Mary Lynn McGrath.  It took Lookout 0.06 seconds to find the exact email from September of 2000 using keywords McGrath and Vinod.  Amazing (and thanks again, Mary Lynn!).

Winds of Change at the DMA

I’ve been an active member of the Direct Marketing Association (DMA) for almost seven years now.  It’s kind of the Mac Daddy of trade associations in and around our business.  The DMA has taken its lumps of late, mostly deservedly so, and I think made some terrible moves, misjudgments, and decisions a few years back.

But I’ve continued to be an active member, mostly convinced by new DMA CEO John Greco and COO Ramesh Ratan that there was a new sheriff in town who was going to restore peace and order to the village.  John and Ramesh have a deep understanding and deeply held convictions about consumer experience and permission — and about the centrality of interactive marketing to direct marketing, and to marketing departments in general.

And they’re starting to make lots of changes at the DMA, from who is on the staff, to the staff’s mindset, to their goals, budgets, and plans — all to the benefit of interactive marketers.

One thing they’ve done is revitalized the Interactive Marketing Advisory Board (IMAB), which we created after AIM was dissolved last year, of which I’m the Chairman.  The IMAB has a star-studded list of member companies and individuals (see coverage in DMNews here) and is working diligently and in great partnership with the senior staff of the DMA to really bring interactive marketing principles to the core of the DMA’s offerings and ethos.  We still have a long way to go, as you probably noticed at this week’s DMA 06 show in San Francisco (great interactive programming, very weak interactive trade show floor and critical mass of key attendees), but I think the IMAB initiative has us off to a great start.

Stay tuned for more developments on this front over the coming weeks.

Taking Stock

Every year around this time, I take a few minutes to reflect on how the business is doing, on my goals and development plans, and on what I want to accomplish in the coming year.  Although most of that work is focused on how to move the business forward, I also make sure to take stock of my own career trajectory.  I always ask myself three questions when I do this:

1. Am I having fun at work?
2. Am I learning and growing as a professional?
3. Is my work financially rewarding enough, either in the short term or in the long term?

Of course, I always shoot for 3 YES responses.  Then I know my career is on track.  But as long as I get 2 YESses, then I feel like I’m in good shape, and I know which one to work on in the coming year.  I’m not sure I’ve ever had a situation in the dozen years of running Return Path where I’ve had 0 or 1 YESses.  If I did, I’d probably spend more time thinking about whether I was still in the right job for me.

I think these three questions can work for anyone, not just a CEO.  Hopefully everyone takes the time to take stock like this at least once a year.  It’s healthy for everyone’s career development.

Last week, I wrote about the concept of the Operating Philosophy, and how it fits with a company’s Operating Framework and Operating System and defines the essence of who you are as a company…what form of company you are.

While we had a loose Operating Philosophy at Return Path, we never really crisply articulated it, and that caused some hand-wringing at various points over the years, as different people interpreted our “People First” mantra in different ways. So this time around at Bolster, we’re trying to be more intentional about this up front. We have labeled our company a “Mostly Self Managed Organization” or MSMO (pronounced Miz-Moh). We made those up.

Our Operating Philosophy – we are a Mostly Self-Managed Organization, or MSMO (pronounced Miz-Mo, a term we just made up). The MSMO is the product of years of work, research, practical learning, and thinking on our part.  Self-Management has been important to me my whole career as a manager and leader.  Over the last 15 years, the team and I have studied various forms of self-management with interviews and onsite meetings at Netflix, Gore, Nucor, Morningstar, and Zappos.  While we implemented some aspects of it at Return Path, we are trying to take the implementation a step further here at Bolster from the beginning.

Of all those companies, what we’re doing is probably closest to the Operating Philosophy of W.L. Gore & Associates, which you can find written out online without a name but with the description that “individuals don’t need close supervision; what they need is mentoring and support.” The embodiments of the Operating Philosophy at Gore may be different from those we create at Bolster, but the essence of the philosophies is pretty similar.

Why a MSMO?  We employ smart people, and smart people crave autonomy, purpose, and mastery (according to Daniel Pink) and do their best work when they have those things in alignment.  

So, how do we define self-management at Bolster?  We aren’t going to be a DAO.  I don’t think that model works for a for-profit multifaceted corporation – complete Self-Management is too chaotic.  Leadership and mentorship matter and make a difference in guiding strategy, critical decisions, and careers. Holocracies or other unnamed structures like that of Morningstar are ok, but they are so rigidly ideological that they require an immense amount of work-around, or scaffolding, to be practical.

But we aren’t a traditional fixed top-down hierarchy, either.  We are going to run the business in a way that lets people co-create their work and be responsible for driving their own feedback and development with a support structure.  That’s the ideology we have. Letting talented people loose to do their best work is critical; but leadership, judgment, and experience matter, too. If not, why bother having a CEO, or a VP of anything? Why not just pay everyone the same thing and hope they can all figure out the complexities of the business together?

We believe the MSMO is the best operating philosophy to allow high performers to do their best work. 

At Bolster, we are leaning into things like social contracts, peer feedback, career mentorship, individuals translating our Operating Framework into priorities and work, flexible work streams and team leadership, instead of fixed permanent hierarchies, rotating chairs of key company meetings, and market-level-based compensation.  

What we are steering away from are things like traditional titles, micromanaging or overmanaging, traditional performance reviews linked to compensation and complex incentive compensation structures, and fixed organization boundaries and structure.

We’ll see if our MSMO Operating Philosophy works. If not, we’ll iterate on it. That’s the good thing about adherence to an ideology of philosophy as opposed to an ideology of practices. Who knows – maybe the MSMO concept and even its quirky name will catch on!