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.

Fig Wasp #879

I have 7 categories of books in my somewhat regular reading rotation:  Business (the only one I usually blog about), American History with a focus on the founding period, Humor, Fiction with a focus on trash, Classics I’ve Missed, Architecture and Urban Planning (my major), and Evolutionary Biology.  I’m sure that statement says a lot about me, though I am happy to not figure it out until later in life.  Anyway, I just finished another fascinating Richard Dawkins book about evolution, and while I usually don’t blog about non-business books, this one had an incredibly rich metaphor with several business lessons stemming from it, plus, evolution is running rampant in our household this week, so I figured, what the heck?

The Dawkins books I’ve read are The Selfish Gene (the shortest, most succinct, and best one to start with), The Blind Watchmaker (more detail than the first), Climbing Mount Improbable (more detail than the second, including a fascinating explanation of how the eye evolved “in an evolutionary instant”), The Ancestor’s Tale (very different style – and a great journey back in time to see each fork in the evolutionary road on the journey from bacteria to humanity), and The God Delusion (a very different book expounding on Dawkins’ theory of atheism).  All are great and fairly easy to read, given the topic.  I’d start with either The Selfish Gene or maybe The Ancestor’s Tale if you’re interested in taking him for a spin.

So on to the tale of Fig Wasp #879, from this week’s read, Climbing Mount Improbable.  Here’s the thing.  There are over 900 kinds of fig trees in the world.  Who knew?  I was dimly aware there was such a thing as a fig tree, although quite frankly I’m most familiar with the fig in its Newton format.  Some species reproduce wildly inefficiently — like wild grasses, whose pollen get spread through the air, and with a lot of luck, 1 in 1 billion (with a “b”) land in the right place at the right time to propagate.  At the opposite end of the spectrum stands the fig tree.  Not only do fig trees reproduce by relying on the collaboration of fig wasps to transport their pollen from one to the next, but it turns out that not only are there over 900 different kinds of fig trees on earth, there are over 900 different kinds of fig wasps — one per tree species.  The two have evolved together over thousands of millenia, and while we humans might take the callous and uninformed view that a fig tree is a fig tree, clearly the fig wasps have figured out how to swiftly and instinctively differentiate one speices from another.

So what the heck does this have to do with business?  Three quick lessons come mind.  I’m sure there are scores more.

1. Collboration only works when each party benefits selfishly from it.  Fig wasps don’t cross-pollenate fig trees bcause the fig trees ask nicely or will fire them if they don’t.  They do their job because their job is independently fulfilling.  If they don’t — they probably die of starvation.  They’re just programmed with a very specific type of fig pollen as their primary input and output.  We should all think about collaboration this way at work.  I wrote a series of posts a couple years back on the topic of Collboration Being Hard, and while all the points I make in those posts are valid, I think this one trumps all.  Quite frankly, it calls on the core principle from the Harvard Project on Negotiation, which is that collaboration requires a rethinking of the pie, so that you can expand the pie.  That’s what the fig trees and fig wasps have done, unwittingly.  Each one gets what it needs far more so than if it had ever consulted directly with the other.  The lesson:  Be selfish, but do it in a way that benefits your company.

2. Incredibly similar companies can have incredibly distinct cultures.  900+ types of fig tree, each one attracting one and only one type of fig wasp.  Could there be anything less obvious to the untrained human eye?  I assume that not only would most of us not be able to discern one tree or wasp type from another, but that we wouldn’t be able to disdcern discern any of the 900+ types of trees or wasps from thousands or hundreds of thousands or millions (in the case or urbanites) types of trees or bugs in general!  But here’s the thing.  I know hundreds of internet companies.  Heck, I know dozens of email companies.  And I can tell you within 5 minutes of walking around the place or meeting an executive which ones I’d be able to work for, and which ones I wouldn’t.  And the older/bigger the company, the more distinct and deeply rooted its culture becomes.  The lessons:  don’t go to work for a company where you’d even remotely uncomfortable in the interview environment; cultivate your company’s culture with same level of care and attention to detail that you would your family — regardless of your role or level in the company!

3. Leadership is irrelevant when the operating system is tight.  You think fig wasps have a CEO?  Or a division president who reports into the CEO that oversees both fig wasps and fig trees, making sure they all cross-pollenate before the end of the quarter?  Bah.  While as a CEO, you may be the most important person in the organization sometimes, or in some ways, I can easily construct the argument that you’re the least important person in the shop as well.  If you do your job and create an organization where everyone knows the mission, the agenda, the goal, the values, the BHAG, whatever you want to call it — withoutit needing to be spelled out every day — you’ve done your job, because you’ve made a company where people rock ‘n’ roll all night and every day without you needing to be in the middle of what they’re doing. 

I’m sure there are other business lessons from evolutionary biology…send them along if you have good thoughts to share!

Think Global, Act Local

At Return Path, we have always had a commitment to community service and helping make the world around us a better place.  We ratcheted that up a lot in the last year, which is why we added the following statement in as one of our 14 Core Values:

Think Global, Act Local.  We commit our time and energy to support our local communities.  

We feel strongly that companies can and should make the world a better place in several different ways.  Certainly, many companies’ core businesses do that — just look at all the breakthroughs in medicine and social services over the years brought to market by private enterprises, including my friend Raj Vinnakota, who I blogged about here years ago. 

But many companies, including Return Path, aren’t inherently “save the world” in nature, and those companies can still make a difference in the world in a few ways:

1.  Allow employees to take a limited amount of paid time off for community service work
2. Organize projects in the local community for their employees to help out/work at
3. Provide matching gift programs so employees’ donations are enhanced by the company
4. Donate money or services to charitable organizations they believe in

As a relatively small company, we have had to pick our battles here.  When we were smaller, we had a policy for #1 above that allowed employees 5 days per year of paid time off for community service work in addition to vacation.  We organized projects here and there for employees, including various walks and races and drives, and multiple Habitat for Humanity projects, including one that our employees blogged extensively about after Hurricane Katrina in New Orleans (see Tom Bartel’s final blog post of 7 here.  We never had a specific policy around matching donations, but we were always quick to support one-off employee requests.  And we did have comprehensive program for #4 above to donate cash and in-kind services to one particular charitable organization that fought Multiple Sclerosis, which was inspired by a long-time employee who was diagnosed with MS. 

Over the years, our approach has evolved around service.  When we moved to an Open Vacation policy a few years back, we effectively eliminated the Community Service time off benefit since people can just go do that now under the umbrella time-off policy.  We do still organize some projects for employees from time-to-time, but those are done on an office-by-office basis.  The biggest change in our approach was to stop doing company-run projects, stop responding to one-off requests from employees, and stop supporting a single organization.  We felt that those things, while good, were diffusing the impact that we could potentially have.

So this year we launched something called the Dream Fund.  Once each quarter, we invite self-forming teams of employees to submit applications for a $10,000 grant to help make some corner of their community a better place.  There are some loose guidelines around the use of funds (e.g., they can’t be a straight donation, they have to include some hands-on work), and we have a panel select each quarter’s winner.  So far, we have had two projects run very successfully: 

• Sistas Against Cancer which supports the Avan Walk for Breast Cancer.
• Tennyson Center for Children. This charity supports kids suffering from abuse, neglect, emotional crises and other traumatic experiences will get the help they need while finding healing and HOPE in a safe and caring environment

There’s no right way to do community service as a company.  Bu t we feel strongly that part of our “mission” (an overused word if there ever was one) was to have an impact on the world around us – not just on our customers and fellow employees, but by using our time and money to help those who need it most in the many communities where we operate around the world.

(The following post was written by one of Return Path’s long-time senior managers, Chris Borgia, who runs one of our data science teams and has run other support organizations in the past, both at Return Path and at AOL.  I don’t usually run guest posts, but I loved the topic with Chris suggested it, and it’s a topic that I’d only have a limited perspective on!)

Managing Up in a Growing, Global Workplace

For many years, I thought “managing up” was a cheap way of getting ahead. I thought someone who managed up was skilled at deceiving their boss into thinking they were more accomplished than they really were.

I have since learned that managing up, or managing your boss, is not devious, but is actually a valuable discipline. When you learn to manage up successfully, you empower your boss to better represent your interests to influencers in the organization.

If you are a manager, you should realize that in addition to managing your boss, you can help your employees effectively manage you. When our employees help us to be successful, we are further enabled to invest in their success. This symbiosis is seen in any relationship – the more you help the other person, the more they will be able to – and want to – help you. If you are a manager, it’s important to realize that your employees should be managing up, and you can encourage them to do so by being vulnerable, admitting ignorance, and asking for support.

There are many books and articles on managing up or managing one’s boss. The essentials are fairly consistent:

• Understand your boss’s goals, priorities, and needs
• Know your boss’s strengths and weaknesses
• Set mutual expectations to build trust
• Communicate and keep your boss informed

You’ll need to be intentional about the essentials no matter where you work, but there are additional challenges of managing up in a growing, global workplace like Return Path. In a growing company, you’re likely to work for a boss who is new to their role, the company or the industry. In a global company, you may report to a boss who works in another office, or even in another country. The fundamental aspects of managing up are the same, but these situations can require a tailored approach.

When your boss is new to their role, the company, or the industry

In a growing company, you’re likely to report to someone who is new to their role in the company, new to the company itself, or even new to the industry. You can be invaluable to your boss in closing the knowledge gap and enabling them to make the best decisions for you and your team.

• Process Help your boss understand how the department operates. How are goals and priorities determined? How do people communicate? What does the team expect from the boss?
• People If your boss doesn’t know the people, they may lack the appropriate empathy in a given situation. Help them understand your team’s needs and how their decisions impact the people.
• Decision Making Your boss will likely need additional data to help them make decisions. Providing your boss with this data up front, saving them from admitting ignorance, will go a long way to developing a strong relationship.
• Context Sometimes your boss won’t know what they don’t know, so providing your boss the context around issues, decisions, and goals will enable them to make the best decisions for your team.

When your boss works in another office or country

In a global workplace, it’s likely that at some point you will have a boss who works in another office or even in another country. Having a remote boss offers many opportunities for managing up.

• Visibility Your boss doesn’t see you – or possibly others on the team – every day, so you might want to communicate more about the day-to-day operations of the team. At times, it will feel like you are sharing minutia, but it’s likely your boss will find this valuable in developing a complete understanding of what is going on.
• Insight If you work in a core office, you have a tremendous opportunity to be your boss’s eyes and ears.  What are you seeing or hearing locally that might change your boss’s plans or perspective? What are people worried about? Are there any rumors your boss should be aware of?
• Culture If your boss is in a different country, you will need to develop a relationship that considers any cultural differences. Cultural differences are seen in office attire, working hours, email habits, vacation schedules, and more. Bosses in some cultures may expect more deference, while in others they may expect more direct honesty. Understanding your boss’s culture, and helping her understand yours, will develop mutual respect and expectations to make each other successful.

Your relationship with your boss is a symbiotic one. Your boss can’t be successful unless you are, so they are your champion.  Learning to effectively manage up, especially in a growing, global workplace, is not nefarious business. Your boss will represent and support you to the best of their abilities. The more you enable your boss, the better they can support you, and everybody wins.

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).

(This is the sixth post in a series documenting the work I did in Colorado on the Governor’s COVID-19 Innovation Response Team – IRT.  Other posts in order are 1, 2, 3, 4, and 5.)

As these posts have been running, a few people have asked me to quickly compare this experience to the experience of being a Startup CEO.  And that’s an interesting way to think about it. In a lot of ways, the couple of weeks of getting the IRT up and running felt like starting up a new business, only a lot more intense.  Following the outline of sections in Startup CEO:  a field guide to scaling up your business…

Part One: Storytelling.  The whole timeframe was super compressed.  It took us 2 days to be able to spend 4 hours writing our initial pitch deck defining scope, structure, and staffing request – and that was while we were working hard on our first two workstreams.  In a startup environment, that process would have taken much longer, involved more customer discovery and product/market fit research and spending 100% of our time on that. But then we got our “approval and funding” in about 45 minutes – that would have taken weeks and involved dozens of pitch meetings.  In terms of creating the organization’s Mission, Vision, and Values, we didn’t even bother, although I think it helped that the three of us were generally on the same page with how to work and that urgency was the essence of our job. The larger emergency operations team that we were more or less embedded in also had a very clear set of values and operating principles on display…although we didn’t actually go read them, I think they were in sync with our view of our team’s mission and principles.  In terms of “bringing our story to life,” that was wholly unnecessary!

Part Two: Building The Company’s Human Capital.  Like a startup, getting it right with the first handful of employees means everything.  In this case, the first two deputies on the team, handpicked by the Governor’s staff, were awesome and critical.  Bringing someone in from the private sector to run a public sector team only works when the rest of the team is incredibly knowledgeable about how the machinery of state government works.  And in the end, I think Sarah will be a better leader for the team than I was because she had a combination of private and public sector experience (and within her public sector experience, she had a lot of emergency response experience).  In general, the recruiting process was soooo different than private sector and public sector normally are. The first two team members handpicked the best people they knew in other relevant parts of the government. People were brought onto the team after one short phone call.  Other state departments heads loaned their people willingly. No such thing as a comp negotiation or a reference check. There were a bunch of other things under the “Human Capital” heading that are interesting notes/comparables as well. First, feedback in a compressed-timeframe emergency is something that you absolutely can’t skip – and you can’t wait for a formal process either.  Our team was pretty good about giving feedback at least daily in a semi-structured way as well as in the moment. We didn’t really have time to get into things like career pathing and compensation and firing. We did, after about 6 days at the suggestion of Kacey, our Chief of Staff, move the team to almost entirely remote (other than leadership and occasional critical meetings). This worked surprisingly well for a workforce probably unaccustomed to remote work.  The rest of the world is also learning how to do a lot of that now, too.

Part Three: Execution.  This whole experience was 97% execution.  In fact, we had a hard time finding time for things like strategy and planning because there was a crushing amount of work to do (welcome to emergency response), and a small team to do it.  We didn’t have to worry about raising money, budgeting, forecasting, reporting, and some of the other major execution steps in the private sector. We did do a good job of creating goals and milestones for our workstreams, but even that took a couple of weeks, and in retrospect, I wish we’d been able to do some of those sooner.  In terms of how our work got done, we were very conscious of creating daily meeting routines to structure our day and work – but there was no such thing as even a weekly meeting (let alone monthly strategics or quarterly offsites!), only daily meetings, multiple times per day. One thing that was interesting – I talk in the book about being deliberate and consistent with your platforms, especially around communication.  Channel proliferation is a real issue today (much more so than when I wrote the book), but we had an interesting mismatch at the beginning. The public sector team was used to email, text, and Google hangouts for comms. Nothing else. The private sector team used those things but was a lot more comfortable with Trello, Zoom, and Slack. Thank goodness both teams used G-Suite and not a mix of that and LiveOffice. But getting everyone on the team to converge on a couple systems is a work in progress and was messy, as evidenced in this great moment where Kacey was holding a laptop up to an actual whiteboard to show one of our private sector teams how she was thinking about something. 

Part Four: Building and Leading a Board of Directors.  This is kind of N/A, although the proxy for it in our case on the IRT was the leadership structure of the Emergency Operations Center and then the Governor and the part of his cabinet that was keyed into the emergency response.  In this regard, the main differences between the private sector and public sector were speed/formality (no room for formality when you’re meeting daily or at a moment’s notice!), and, interesting, the need for integration. A company reports to its board on how it’s doing.  This team had to use its “board” to make sure it was integrating with other state agencies and initiatives. In this way, the team functioned more like a business unit within a company than an actual company.

Part Five: Managing Yourself So You can Manage Others.  This was obviously critical…and obviously quite difficult.  And within the overall Emergency Operations Center (outside of our team, the real emergency professionals), there were people, including leaders, who were working 7 days/week for multiple weeks on end, and long days, too.  At one point, the EOC leader posted this note on the wall, and he frequently took time in daily briefings to encourage everyone to take a day or two off and take care of themselves physically.  He role-modeled that behavior as well. You can only run a sprint for so long. Once it becomes clear it’s a marathon, well, you know.

Stay tuned for the final post in the series tomorrow…

How Deliverability is Like SEO and SEM for Email

I admit this is an imperfect analogy, and I’m sure many of my colleagues in the email industry are going to blanch at a comparison to search, but the reality is that email deliverability is still not well understood — and search engines are.  I hope that I can make a comparison here that will help you better understand what it really means to work on deliverability – they same way you understand what it means to work on search.

But before we get to that, let’s start with the language around deliverability which is still muddled.  I’d like to encourage everyone in the email industry to rally around more precise meanings.  Specifically I’d like propose that we start to use the term “inbox placement rate” or IPR, for short.  I think this better explains what marketers mean when they say “delivered” – because anywhere other than the inbox is not going to generate the kind of response that marketers need.  The problem with the term “delivered” is that it is usually used to mean “didn’t bounce.”  While that is a good metric to track, it does not tell you where the email lands.  Inbox placement rate, by contrast, is pretty straightforward: how much of the email you sent landed in the inbox of our customers and prospects?

Now let’s come back to how achieving a high inbox placement rate is like search.  If you run a web site, you certainly understand what SEO and SEM are, you care deeply about both, and you spend money on both to get them right.  Whether “organic” or “paid,” you want your site to show up as high as possible on the page at Google, Yahoo, Bing, whatever.  Both SEO and SEM drive success in your business, though in different ways.

The inbox is different and a far more fragmented place than search engines, but if you run an email program, you need to worry both about your “organic” inbox placement and your “paid” inbox placement.  If you are prone to loving acronyms you could call them OIP and PIP.

What’s the difference between the two?

With organic inbox placement, you are using technology and analytics to manage your email reputation, the underpinning of deliverability.  You are testing, tracking, and monitoring your outbound email.  Seeing where it lands – in the inbox, in the junk mail folder, or nowhere?  You are doing all this to optimize your inbox placement rate (IPR) — just as you work to optimize your page rank on search engines.  One of the ways you do this is by monitoring your email reputation (Sender Score) as a proxy for how likely you are to have your email filtered or blocked.  The more you manage all of these factors, the greater likelihood you will be placed in inboxes everywhere.

With paid inbox placement, you first have to qualify by having a strong email reputation.  Then you use payment to ensure inbox placement, and frequently other benefits like functioning images and links or access to rich media.  With this paid model, there’s no guarantee to inbox placement (don’t let anyone tell you otherwise), just like there’s no guarantee that you’ll be in the #1 position via paid search if someone outbids you.  But by paying, you are radically increasing the odds of inbox placement as well as adding other benefits.  There is one critical difference from search here, which is that you need good organic inbox placement in order to gain access to PIP.  You can’t just pay to play.

Like SEO, some organic deliverability work can and must be done in-house, but frequently it’s better to outsource to companies like Return Path to save costs and time, and to gain specific expertise.  Like SEM, paid deliverability inherently means you are working with third parties like our Return Path Certification program. 

As I said, it’s an imperfect analogy, but hopefully can help you better understand the strategies and services that are available to help you make the most of every email you send.

I’ve always been a big believer in the Operating Framework and the Operating System as two of the management underpinnings behind every well run company.

The Operating Framework is the company’s Mission, Vision, Values, Strategic Objectives, and Key Metrics. Companies have all sorts of different labels for this, from Balanced Scorecard to Salesforce’s V2MOM to Patrick Lencioni’s 6 Questions. It’s what you have to define up front, refresh annually, and tweak quarterly so that people in the company are aligned and know where you’re going.

The Operating System, as I wrote extensively about in Startup CEO, is the collection of practices, meetings, mailing lists, routines/rhythms, and behaviors that your company and team use and depend on to run the business on a day to day basis. It’s what you have to put in place and tweak as needed so work gets done efficiently – the thing that turns the sprint of a raw startup into the marathon of a scaling business.

But there’s a third leg to the stool of company management underpinnings that’s often overlooked and underappreciated – the company’s Operating Philosophy. The Operating Philosophy is the intellectual underpinning of how you want to run and lead the business. It’s related to, but different from, your company’s values. Think of it as the essence of how you want to work and shape the work of others…what defines your form of company.

You can run a company perfectly well without a clear Operating Philosophy, especially with a tight Operating Framework and Operating System in place. But my guess is that you have one, you just haven’t articulated it yet, and you might benefit from doing so. At least that was our experience where we had an undefined but real one at Return Path and have now tried to define one front and center at Bolster.

A useful way to think about these three legs of the stool is the analogy of government (bear with me on this and pretend like our government in the US isn’t quite as dysfunctional as it is at the moment). Our Operating Framework is the Constitution – it lays out the broad contours of what our government does. Our mission, vision, and values. Our Operating System is the collection of policies, practices, and programs that run the country, from the timing and cadence of elections, to the ways the three branches of government enact and execute policy, to the ways state and local governments fit in. Our Operating Philosophy is the Declaration of Independence. It’s our essence. It is what separates our form of government from other forms of government. We are a Representative Democracy, a Constitutional Federal Republic. We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are Life, Liberty and the pursuit of Happiness. That to secure these rights, Governments are instituted among Men, deriving their just powers from the consent of the governed.

Some examples? Zappos is a Holocracy – defined as a system of corporate governance whereby members of a team or business form distinct, autonomous, yet symbiotic, teams to accomplish tasks and company goals. The concept of a corporate hierarchy is discarded in favor of a flat organizational structure where all workers have an equal voice while simultaneously answering to the direction of shared authority. Patagonia (and lots of other companies) is a Delaware Public Benefit Corporation (PBC or often called a B Corporation), which must by law follow Stakeholder Capitalism and not Shareholder Capitalism. Plenty of crypto organizations are set up as DAOs (Decentralized Autonomous Organizations), which is a group of people who come together without a central leader or company dictating any of the decisions, built on a blockchain using smart contracts and a currency of tokens that give them the ability to vote on decisions that are made around how the pool of money is spent and managed.

Hopefully that makes sense. Next week, I’ll talk about our Operating Philosophy at Bolster.

No Recession at Return Path

I know, I know.  I shouldn’t jinx us.  But we’re growing like mad at the moment, so much so that we have well almost 50 open positions now across all divisions of the company.  If you want to come join one of the fastest growing, most innovative, and just plain coolest places to work in the industry, we’d love to talk to you.

What’s driving the growth? 

• All our operating units have open positions.  Sender Score (deliverability/whitelisting) has the most openings and is growing explosively.  But Authentic Response (market research) and Postmaster (lead generation) both have openings as well
• Geographic expansion.  We have a bunch of openings in Europe as well as in the U.S.  Other parts of the world…stay tuned for later in the year (or let us know now that you are interested once we get to your corner of the globe)
• The power of email.  Parts of the economy may be a bit choppy now, but online marketing, and email in particular, are going strong.  Clients are finding the e-channels to be more and more effective and efficient ways of driving sales and customer loyalty

Visit the careers page at our web site to have a look — all the new jobs probably aren’t posted yet, but many are, and the rest are on the way shortly.  This is a fun and exciting and rewarding place to work.  Trust me.  I’m completely unbiased.  No, really.  Come join the team, or refer others!

Two Ears, One Mouth

Brace yourself for a post full of pithy quotes from others.  I’m not sure how we missed this one when drafted our original values statements at Return Path years ago, because it’s always been central to the way we operate.  We aren’t just the world’s biggest data-driven email intelligence company – we are a data-driven organization.  So another one of our newly written Core Values is:

Two Ears, One Mouth:  We ask, listen, learn, and collect data.  We engage in constructive debate to reach conclusions and move forward together.

I’m not sure which of my colleagues first said this to me, but I’m going to give credit to Anita, our long-time head of sales (almost a decade!), for saying “There’s a reason God gave you two ears and one mouth.”  The meaning?  Listen (and look, I suppose) more than you speak.

This value really has two distinct components to it, though they’re closely related.  First, we always look to collect data when we need to understand a situation or make a decision.  To quote our long-time investor, Board member, and friend Brad Feld, “the plural of anecdote is not data.”  That means we are always looking far and wide for facts, numbers, and multiple perspectives.  Some of us are better than others at relying on second-hand data and observations from trusted colleagues, which means often times, many of us are collecting data ourselves to inform a situation.  But regardless, we always start with the data.

Second, we use data as the foundation of our decision-making process.  I heard another great quote about this once, which is something like, “If we are going to make a decision based on data, the data will make the decision for us.  If we’re going to use opinion, let’s use mine.”  And while I’m at it, I’ll throw in another great quote from Winston Churchill who famously said “Facts are stubborn things.”  While we do have constructive debates all across our organization, those debates are driven by facts, not emotion.

Finally, when this value says that “we move forward together,” that is the combination of the points in the two prior paragraphs.  People may have different opinions entering a debate.  Even with a lot of data behind a decision, they may still have different opinions after a decision has been made.  But we work very deliberately to all support a decision, even one we may disagree with, and we are able to do that, move forward together, and explain the decision to the organization, because the decision is data-driven.

Book Short:  Is CX the new UX?

Outside In: The Power of Putting Customers at the Center of Your Business, by Harley Manning and Kerry Bodine from Forrester Research, was a good read that kept crossing back and forth between good on the subject at hand, and good business advice in general.  The Customer Experience (CX) movement is gaining more and more steam these days, especially in B2B companies like Return Path.  The authors define Customer Experience as “how your customers perceive their interactions with your company,” and who doesn’t care about that?

A few years ago, people started talking a lot more about User Experience (UX) as a new crossover discipline between design and engineering, and our experience at Return Path has been that UX is an incredibly powerful tool in our arsenal to build great technical products via lean/agile methods.  The recurring thought I had reading this book, especially for companies like ours, was “Is CX the new UX?”

In other words, should we just be taking the same kind of lean/agile approach to CX that we do with technical product development and UX — but basically do it more holistically across every customer touchpoint, from marketing to invoice?  It’s hard to see the answer being “no” to that question, although as with all things, the devil is in the implementation details.  And that’s true at the high level (the authors talk about making sure you align CX strategy with corporate strategy and brand attributes and values) as well as a more granular level (what metrics get tracked for CX, and how do those align with the rest of the companies KPIs).

The book’s framework for CX is six high-level disciplines: strategy, customer understanding, design, measurement, governance, and culture — but you really have to read the book to get at the specifics.

Some other thoughts and quotes from the book:

• the book contains some good advice on how to handle management of cross-functional project teams in general (which is always difficult), including a good discussion of various governance models
• “to achieve the full potential of customer experience as a business strategy, you have to change the way you run your business. You must manage from the perspective of your customers, and you must do it in a systematic, repeatable, and disciplined way.”
• one suggestion the book had for weaving the customer experience into your culture (if it’s not there already) is to invite customers to speak all-hands meetings
• another suggestion the book had for weaving the customer experience into everyone’s objectives was one company’s tactic of linking compensation (in this case, 401k match) to customer experience metrics
• “Customer Experience is a journey, not a project. It has a beginning but it doesn’t have an end.”

Thanks to my colleague Jeremy Goldsmith for recommending this book.