🔎
Mar 2 2017

Stamina

Stamina

A couple years ago I had breakfast with Nick Mehta, my friend who runs the incredibly exciting Gainsight.  I think at the time I had been running Return Path for 15 years, and he was probably 5 years into his journey.  He said he wanted to run his company forever, and he asked me how I had developed the stamina to keep running Return Path as long as I had.  My off the cuff answer had three points, although writing them down afterwards yielded a couple more.  For entrepreneurs who love what they do, love running and building companies for the long haul, this is an important topic.  CEOs have to change their thinking as their businesses scale, or they will self implode!  What are five things you need to get comfortable with as your business scales in order to be in it for the long haul?

Get more comfortable with not every employee being a rock star.  When you have 5, 10, or even 100 employees, you need everyone to be firing on all cylinders at all times.  More than that, you want to hire “rock stars,” people you can see growing rapidly with their jobs.  As organizations get larger, though, not only is it impossible to staff them that way, it’s not desirable either.  One of the most influential books I’ve read on hiring over the years, Topgrading (review, buy), talks about only hiring A players, but hiring three kinds of A players:  people who are excellent at the job you’re hiring them for and may never grow into a new role; people who are excellent at the job you’re hiring them for and who are likely promotable over time; and people who are excellent at the job you’re hiring them for and are executive material.  Startup CEOs tend to focus on the third kind of hire for everyone.  Scaling CEOs recognize that you need a balance of all three once you stop growing 100% year over year, or even 50%.

Get more comfortable with people quitting.  This has been a tough one for me over the years, although I developed it out of necessity first (there’s only so much you can take personally!), with a philosophy to follow.  I used to take every single employee departure personally.  You are leaving MY company?  What’s wrong with you?  What’s wrong with me or the company?  Can I make a diving catch to save you from leaving?  The reality here about why people leave companies may be 10% about how competitive the war for talent has gotten in technology.  But it’s also 40% from each of two other factors.  First, it’s 40% that, as your organization grows and scales, it may not be the right environment for any given employee any more. Our first employee resigned because we had “gotten too big” when we had about 25 employees.  That happens a bit more these days!  But different people find a sweet spot in different sizes of company.  Second, it’s 40% that sometimes the right next step for someone to take in their career isn’t on offer at your company.  You may not have the right job for the person’s career trajectory if it’s already filled, with the incumbent unlikely to leave.  You may not have the right job for the person’s career trajectory at all if it’s highly specialized.  Or for employees earlier in their careers, it may just be valuable for them to work at another company so they can see the differences between two different types of workplace.

Get more comfortable with a whole bunch of entry level, younger employees who may be great people but won’t necessarily be your friends.  I started Return Path in my late 20s, and I was right at our average age.  It felt like everyone in the company was a peer in that sense, and that I could be friends with all of them.  Now I’m in my (still) mid-40s and am well beyond our average age, despite my high level of energy and of course my youthful appearance.  There was a time several years ago where I’d say things to myself or to someone on my team like “how come no one wants to hang out with me after work any more,” or “wow do I feel out of place at this happy hour – it’s really loud here.”  That’s all ok and normal.  Participate in office social events whenever you want to and as much as you can, but don’t expect to be the last man or woman standing at the end of the evening, and don’t expect that everyone in the room will want to have a drink with you.  No matter how approachable and informal you are, you’re still the CEO, and that office and title are bound to intimidate some people.

Get more comfortable with shifts in culture and differentiate them in your mind from shifts in values.  I wrote a lot about this a couple years ago in The Difference Between Culture and Values . To paraphrase from that post, an organization’s values shouldn’t change over time, but its culture – the expression of those values – necessarily changes with the passage of time and the growth of the company.  The most clear example I can come up with is about the value of transparency and the use case of firing someone.  When you have 10 employees, you can probably just explain to everyone why you fired Joe.  When you have 100 employees, it’s not a great idea to tell everyone why you fired Joe, although you might be ok if everyone finds out.  When you have 1,000 employees, telling everyone why you fired Joe invites a lawsuit from Joe and an expensive settlement on your part, although it’s probably ok and important if Joe’s team or key stakeholders comes to understand what happened.  Does that evolution mean you aren’t being true to your value of transparency?  No.  It just means that WHERE and HOW you are transparent needs to evolve as the company evolves.

  • Get more comfortable with process.  This doesn’t mean you have to turn your nimble startup into a bureaucracy.  But a certain amount of process (more over time as the company scales) is a critical enabler of larger groups of people not only getting things done but getting the right things done, and it’s a critical enabler of the company’s financial health.  At some point, you and your CFO can’t go into a room for a day and do the annual budget by yourselves any more.  But you also can’t let each executive set a budget and just add them together.  At some point, you can’t approve every hire yourself.  But you also can’t let people hire whoever they want, and you can’t let some other single person approve all new hires either, since no one really has the cross-company view that you and maybe a couple of other senior executives has.  At some point, the expense policy of “use your best judgment and spend the company’s money as if it was your own” has to fit inside department T&E budgets, or it’s possible that everyone’s individual best judgments won’t be globally optimal and will cause you to miss your numbers.  Allow process to develop organically.  Be appropriately skeptical of things that smell like bureaucracy and challenge them, but don’t disallow them categorically.  Hire people who understand more sophisticated business process, but don’t let them run amok and make sure they are thoughtful about how and where they introduce process to the organization.

I bet there are 50 things that should be on this list, not 5.  Any others out there to share?

May 23 2013

Book Not-So-Short: Not Just for Women

Book Not-So-Short:  Not Just for Women

At the request of the women in our Professional Services team, I recently read Sheryl Sandberg’s Lean In:  Women, Work, and the Will to Lead, and while it may seem like dancing the meringue in a minefield for a male CEO to blog about it, I think it’s an important enough topic to give it a shot.  So here goes.

First, given the minefield potential, let me issue a few caveats up front.  These are deep, ages old, complex, societal issues and behaviors we’re talking about here.  There is no quick answer to anything.  There is no universal answer to anything.  Men don’t have the same perspective as women and can come across as observers (which in some respects, they are).  Working moms don’t have the same perspective as stay-at-home moms, or as single women.  We try to be good about all these issues at Return Path, but I’m sure we’ve only scratched the surface.  </caveats>

Perhaps most important, my overall take on the book is that it’s a very good business book that everyone should read – not just women.  I have a strong reaction to the reactions I’ve read and heard about the book – mostly from women dismissing the book because Sandberg has immense financial resources, so how could she possibly know the plight of the ordinary mom, and how could she understand what it is like to be a stay-at-home mom?  That reaction is to dismiss the dismissals!  I found the book to be very broadly applicable.  Of course things about life with a two-working parent family are easier if you have more money.  But that’s completely not the point of the book.  And Sandberg doesn’t once criticize stay-at-home moms for that choice – in fact, she acknowledges feelings of guilt and inferiority around them and admiration for the work they do that benefits all families and kids, not just their own.

Here are a few of the biggest areas of thinking, AHA, or questioning, that the book gave me:

  • One of Sandberg’s underlying points is that the world would be a better place with more women in leadership positions, so that’s an important goal.  It’s interesting that few enough of our leaders are women, that it’s hard for me to draw that same conclusion, but it makes sense to me on the surface, and there’s some research about management teams and boards to back it up.  As far as I can tell, the world has yet to see a brutal female dictator.  Or a fair share of political or corporate scandals caused by women.  There are definitely some horror stories of “tough boss” women, but probably no more than “tough boss” men.  It’s interesting to note that in our society, leadership roles seem to be prized for their power and monetary reward, so even if the world wouldn’t be a better place with more female leaders, it would certainly be a more fair place along those two dimensions
  • I felt that a bunch of Sandberg’s points about women were more generalizations about certain personality types which can be inherent in men and women.  Maybe they’re more prevalent in women, even much more, but some are issues for some men as well.  For example, her general point about women not speaking up even if they have something to say.  I have seen this trait in women as well as more introverted men.  As a leader, I work hard to draw comments out of people who look like they have something to say in a meeting but aren’t speaking up.  This is something that leaders need to pay close attention to across the board so that they hear all the voices around their tables.  Same goes for some of the fears she enumerates.  Many male leaders I know, myself included at times, have the “fear of being found out as a fraud” thought.  Same goes for the “desire to be liked by everyone” holding people back – that’s not gender specific, either.  All that said, if these traits are much more prevalent in women, and they are traits that drive attainment of leadership roles, well, you get the point
  • The fact that women earn 77 cents on the dollar in equivalent jobs for men is appalling.  I’ve asked our People Team to do a study of this by level, factoring in experience and tenure, to make sure we don’t have that bias at Return Path.  I know for sure we don’t at the leadership level.  And I sure as heck hope we don’t anywhere in the organization.  We are also about to launch an Unconscious Bias training program, which should be interesting
  • Sandberg made a really interesting point that most of the women who don’t work are either on the low end or high end of the income spectrum.  Her point about the low end really resonated with me – that women who don’t earn a lot stop working if their salaries only barely cover childcare costs.  However, she argues that that’s a very short term view, and that staying in the workforce means your salary will escalate over time, while childcare costs stay relatively flat.  This is compounded by the fact that women who lean back early in their careers simply because they are anticipating someday having children are earning less than they should be earning when they do finally have children.
  • The other end of the income spectrum also made sense once I parsed through it – why do women whose husbands make a lot of money (most of whom make a lot of money as well) decide to off-ramp?  Sandberg’s point about the “Leadership ambition gap” is interesting, and her example of running a marathon with the spectators screaming “you know you don’t have to do this” as opposed to “you’ve got this” is really vivid.  See two bullets down for more on this one.  But it might not be straight-up Leadership Ambition Gap so much as a recognition that some of the high-earning jobs out there are so demanding that having two of them in the household would be a nightmare (noting that Dave and Sheryl seem to have figured some of that out), or that moms don’t want to miss out on that much of their children’s lives.  They want to be there…and they can afford to.  Another related topic that I wish Sandberg had covered in more depth is the path of moms who off-ramp, then re-on-ramp once their youngest children are in school, whether into the career they left or a different one.  That would be an interesting topic on many fronts
  • Societal influences must matter.  The facts that, in 2011 – Gymboree manufactured onesies that say “smart like Daddy” and “pretty like Mommy,” and that JC Penney teenage girl t-shirts say “I’m too pretty to do homework so my brother has to do it for me” are more than a little troublesome on the surface (unless Gymboree also produces “handsome like Daddy” and “wicked smart like Mommy,” which somehow I doubt).  The fact that women do worse on math and science tests when they have to identify their gender at the top of the test is surprising and shocking
  • I am really fortunate that Mariquita only works part time, and it’s unclear to me how our lives would work if we both worked full time, especially given my extremely heavy travel schedule, though I am sure we’d figure it out.  And there’s no way that I carry 50% of the burden of household responsibilities.  Maybe 20-25% at best.  But I was struck by Sandberg’s comments (I am sure true) that in two-working-parent families, women still carry the preponderance of household responsibilities on their shoulders.  I totally don’t get this.  If you both work, how can you not be equal partners at home?  A quick mental survey of a couple of the two-working-parent families we know would indicate that the parents split household responsibilities somewhat evenly, though you can never know this from the outside.  This should be a no brainer.  Sandberg’s point that men need to “lean into their families” is spot on in these cases for sure
  • On a related note, Sandberg’s comment that “as women must be more empowered at work, men must be more empowered at home…moms can be controlling and critical…if he’s forced to do things her way, pretty soon she’ll be doing them herself” made me smile.  I have definitely seen this “learned helplessness” on the home front with dads quite a bit over the years
  • One really good point Sandberg makes is that younger employees who don’t have kids should be allowed to have a life outside of work just as much as women who do have kids.  And that she pays people for the quality and quantity of their output, not their hours.  These are principles that match our values and philosophy at Return Path 100%
  • Probably the most startling moment in the book for me – and I suspect many other men – was Sandberg’s vignette about the young woman at Facebook who was starting to “lean back” because she might someday have a family – before she was even dating anyone!  This really gave me a lot of pause.  If widespread (and I assume it is), there are clearly societal forces at work that we need to do more to help women early in their careers overcome, if they want to overcome them
  • Sandberg’s point that a rich and fulfilling career “is a Jungle Gym, not a Ladder” is spot on, but this is true for men as well as women.  It matches our philosophy of Scaling Horizontally perfectly
  • Another very poignant moment in the book was when Sandberg talked about how she herself had shown bias against women in terms of who she called on in meetings or lectures during Q&A.  Again, lots of pause for me.  If female leaders have the same societal bias against women, that’s a sign that we all have real work in front of us to help level the playing field around giving women air time.  Similarly, her example of the Heidi/Howard study was fascinating around how women with the same characteristics are perceived differently by both male and female co-workers gives me pause (for the record, I know the Heidi in question, and I like her!).  Likewise, the fact that female leaders are often given unflattering nicknames like “The Iron Lady” – you’d never see something like that for a man in the same position.  At least Thatcher wore the name as a badge of honor

I hope this post doesn’t end up as a no-win piece of writing where all I do is touch a few nerves and inspire no ongoing dialog.  “Let’s start talking about it,” the ending theme of the book, is a great way to end this post as well.  As with all tough issues, articulating the problem is the first step toward solving it.  Women need to allow men (as long as the men are open-minded, of course!) to think what they think, say what they think in a safe space, and blunder through their own learnings without feeling threatened.  And men need to be comfortable having conversations about topics like these if the paradigmatic relationship between women and leadership is going to continue to shift instead of avoiding the topic or just calling in HR.

Hopefully this blog post is one step towards that at my company.  Return Path colleagues – feel free to comment on the blog or via email and share stories of how we’ve either helped you or held you back!  But overall, I’m glad I read this book, and I’d encourage anyone and everyone to read it.

May 1 2013

Return Path’s Newest Board Member: Jeff Epstein

Return Path’s Newest Board Member: Jeff Epstein

I’ve written before about how much I love my Board. Well, I’m pleased to announce I have a new reason to love it – today, I’m officially welcoming Jeff Epstein to the Return Path Board of Directors. He is joining an all-star cast that includes Greg Sands, Fred Wilson, Brad Feld, Scott Weiss and Scott Petry.

I first met Jeff back in 2000 when, as CFO of DoubleClick, he and DoubleClick CEO Kevin Ryan agreed to invest in Return Path as our first institutional investor, along with Flatiron Partners.  He is one of the few people who have seen the company grow from its infancy to today.  Jeff has been a formal advisor to the company for more than a year, and he recently agreed to join as a director.

Jeff has all the qualities that make for an awesome board member and he’s already been an influential voice with uncommon insight and an impressive background that complements the rest of our board. As CFO of Oracle Jeff helped guide one of the world’s preeminent technology companies. He’s also served as CFO for large private and public companies including DoubleClick, King World Productions, and Neilsen’s Media Measurement and Information Group, and is a member of the boards of Priceline.com, Kaiser Permanente, Shutterstock, and the Management Board of the Stanford Graduate School of Business. Jeff is currently a partner at Bessemer Venture Partners and a senior advisor at Oak Hill Capital.

Building and managing a board of directors is one of the key functions of a CEO, and the entire Return Path team benefits from a close relationship with great industry leaders. Jeff’s appointment is a perfect example. He’s steered successful organizations through many of the same decisions and challenges that we’re facing. He evaluates issues from multiple points of view – as a senior executive, as a board member, as an investor. And he’s not quiet. On our board, that’s essential. We’re a group of strong personalities—we challenge ideas, we analyze everything, and our views don’t always have to agree.

I’ve said that one secret to running an effective board is to ask for members’ opinions only when you want them. In Jeff’s case I definitely want them. So, on behalf of the board and the entire team at Return Path, Jeff, welcome!

Nov 29 2012

The Value of Paying Down Technical Debt

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.

May 30 2013

Connecting the Dots

Connecting the Dots

Although I still maintain that the three primary roles of a CEO are to set Strategy and communicate it, develop Talent, and ensure that the business has proper Resources to run (see post here), I am increasingly finding that I play a fourth role in the organization that’s probably somewhat important, which is Connecting the Dots.

What do I mean by Connecting the Dots?  I mean helping others network internally, or helping others connect their work to the work of others, or helping others connect their work to the mission of the company, or even to the outside world.

Here are a few examples of how I’ve done this kind of work recently:

 –          I joined an Engineering all-hands and stood up after each segment to talk about the business impact of that team’s work during the prior quarter

–          I met with a new senior employee and connected him to someone internally that he wouldn’t have otherwise met with…but with whom he had a common outside interest

–          I helped a team that’s a classic “support team” understand why their work was directly, but not obviously, contributing to one of the company’s strategic initiatives

–          I connected someone in one of our international offices who had expressed an interest to me in a new role with an operational leader in the US who was thinking of adding someone to his team outside the US

–          I talked to our professional services team about a customer visit I’d recently done where we got really good feedback on the next release of a product but which also pointed out some needs for services that we hadn’t focused on yet

As a business leader, you are in a really good position to help Connect the Dots in a growing organization because you have a pretty unique view across the organization – and you tend to spend time with people internally across different functions and teams and offices.

I am not going to change my position that there are three primary roles, because I’m not sure that a CEO is required to Connect the Dots – hopefully that role can be delegated and replicated.  It’s something to think about, for sure.  But in the meantime, I like doing that and find it useful for me as well as the organization.

Jul 26 2012

The Best Place to Work, Part 1: Surround yourself with the best and brightest

First in my series of posts around creating the best place to work  is to Surround yourself with the best and brightest.  This one is simple.  Build the best team you can possibly build…as you need it.

As a founder, you may be the best person at doing everything in your company, especially if you are a technical founder.  But as my long-time Board member at Return Path Greg Sands always says, when the organism grows, cells start to specialize.  Eventually, you need a liver and a brain.  Just like companies need a head of sales and a CFO (not to imply that Anita likes the occasional cocktail or that Jack likes math – turns out both like both).

How does this come into play as a CEO?

-Don’t be afraid to hire people better than you at their specialty – older, wiser, more experienced, more expensive

– Check references carefully – don’t get suckered in by resume or rolodex – some successful big company people don’t actually know how to do work or build a business, so you have to dig and find back-channel references

– Don’t overhire before you’re ready, but especially as a start-up, better to hire 3 months before you need the position, not 6 months too late

-Remember that you are the CEO.  Even if you hire very experienced people in specific roles, you have the best global view of everything going on in the company.  And you need to pay attention to people on your team and actively manage them, even experts who are older or wiser than you are

Surrounding yourself with the best and brightest can be daunting and even threatening to some CEOs.  But you have to do it to grow your business.  And you have to keep doing it as you keep growing your business (and your staff has to do the same!).

May 3 2012

Skip-Level Meetings

I was talking to a CEO the other day who believed it was “wrong” (literally, his word) to meet directly 1:1 with people in the organization who did not report to him.  I’ve heard from other CEOs in the past that they’re casual or informal or sporadic about this practice, but I’ve never heard someone articulate before that they actively stayed away from it.  The CEO in question’s feeling was that these meetings, which I call Skip-Level Meetings, disempowers managers.

I couldn’t disagree more.  I have found Skip-Level Meetings to be an indispensable part of my management and leadership routine and have done them for years.  If your culture is set up such that you as CEO can’t interact directly and regularly with people in your organization other than the 5-8 people who report to you, you are missing out on great opportunities to learn from and have an impact on those around you.

That said, there is an art to doing these meetings right, in ways that don’t disempower people or encourage chaos.  Some of these themes will echo other things I’ve written in recent posts like Moments of Truth and Scaling Me.  My five rules for doing Skip-Level Meetings are:

  1. Make them predictable.  Have them on a regular schedule, whatever that is.  The schedule doesn’t have to be uniform across all these meetings.  I have some Skip-Levels that I do monthly, some quarterly, some once a year, some “whenever I am in town.”
  2. Use a consistent format.  I always have a few questions I ask people in these meetings – things about their key initiatives, their people, their roadblocks, what I can do to help, what their POV is about the company direction and performance, how they are feeling about their role and growth.  I also expect that people will come with questions or topics for me.  If I have more meaty ad hoc topics, I’ll let the person know ahead of time.
  3. Vary the location.  When I have regular Skip-Levels with a given person, I try to do the occasional one over a meal or drink to make it a little more social.  For remote check-ins, I now always do Skype or Videophone.
  4. Do groups.  Sometimes group skip-levels are fun and really enlightening, either with a full team, or with a cross-section of skip-levels from other teams.  Watching people relate to each other gives you a really different view into team dynamics.
  5. Close the loop.  I almost always check-in with the person’s manager BEFORE AND AFTER a Skip-Level.  Before, I ask what the issues are, if there is anything I should push on or ask.  After, I report back on the meeting, especially if there are things the person and I discussed that are out of scope for the person’s job or goals, so there are no surprises.

 I’m sure there are other things I do as well, but I can’t imagine running the company without this practice.  Doing it often and well EMPOWERS people in the company…I’d argue that managers who feel disempowered by it aren’t managers you necessarily want in your business unless you really run a command-and-control shop.

Aug 22 2013

Unknown Unknowns

Unknown Unknowns

There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.”   –Donald Rumsfeld

Say what you will about Rumsfeld or the Iraq war, but this is actually a great and extensible quote.  And more to the point, I’d say that one of the main informal jobs of a CEO, sort of like Connecting the Dots in that it’s not one of the three main roles of a CEO) is to understand and navigate known unknowns and unknown unknowns for your organization (hopefully you already understand and navigate the known knowns!).  Here’s what I mean:

  • An example of a known unknown is that a new competitor could pop up and disrupt your business from below (e.g., the low end) at any minute.  Or let’s say your biggest partner buys one of your competitors.  These are the kinds of things you and your team should be cognizant of as possibilities and always thinking about how to defeat
  • While I suppose unknown unknowns are by definition hard to pin down, an example of an unknown unknown is something like a foreign leader deciding to nationalize the industry you’re in including your local subsidiary, or a young and healthy leader in your organization dying unexpectedly, or September 11.  I suppose these are “black swan” events that Nassim Nicholas Taleb made famous in his book.

Helping your team identify potential known unknowns and think three steps ahead is critical.  But helping your team turn unknown unknowns into known unknowns is, while much harder, probably one of the best things you can do as CEO of your organization.  And there are probably two ways you can do this, noting that by definition, you’ll never be able to know all the unknowns.  As you might expect, the way to do that comes down to increasing your pool of close-at-hand knowledge.

First, you and your executive team can have as broad a view of your industry and corporate ecosystem, and of the economy at large, as possible.  It’s critical for business leaders to read diverse publications, to share insights with teammates, and to network with experts both inside and outside your space.
Second, you can design a culture so that information flows freely up, down, and sideways — so that people in your organization want to share information instead of hoard it.  That’s easier said than done, and there’s more than a blog post worth of what has to go into making that a reality.  But think about the CIA and all the flak they got about failure to connect the dots around September 11.  To close this post where I opened it, you can be the chief connector inside your organization…but you need to get your organization connecting the dots itself.
Sep 21 2017

Book Shorts: Summer Reading

I read a ton of books.  I usually blog about business books, at least the good ones.  I almost never blog about fiction or non-business/non-fiction books, but I had a good “what did you read this summer” conversation the other night with my CEO Forum, so I thought I’d post super quick snippets about my summer reading list, none of which was business-related.

If you have kids, don’t read Sheryl Sandberg and Adam Grant’s Option B:  Facing Adversity, Building Resilience, and Finding Joy unless you’re prepared to cry or at least be choked up.  A lot.  It is a tough story to read, even if you already know the story.  But it does have a number of VERY good themes and thoughts about what creates resilience (spoiler alert – my favorite key to resilience is having hope) that are wonderful for personal as well as professional lives.

Underground Airlines, by Ben Winters, is a member of a genre I love – alternative historical fiction.  This book is set in contemporary America – except that its version of America never had a Civil War and therefore still has four slave states.  It’s a solid caper in its own right, but it’s a chillingly realistic portrayal of what slavery and slave states would be like today and what America would be like with them.

Hillbilly Elegy, by J.D. Vance, is the story of Appalachia and white working class Americans as told by someone who “escaped” from there and became a marine, then a Yale-educated lawyer.  It explains a lot about the struggles of millions of Americans that are easy for so many of us to ignore or have a cartoonish view of.  It explains, indirectly, a lot about the 2016 presidential election.

Everybody Lies:  Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are, written by Seth Stephens-Davidowitz, was like a cross between Nate Silver’s The Signal and The Noise and Levitt & Dubner’s Freakonomics.  It’s full of interesting factoids derived from internet data.  Probably the most interesting thing about it is how even the most basic data (common search terms) are proving to be great grist for the big data mill.

P.J. O’Rourke’s How the Hell Did This Happen? was a lot like the rest of P.J. O’Rourke’s books, but this time his crusty sarcasm is pointed at the last election in a compilation of articles written at various points during the campaign and after.  It didn’t feel to me as funny as his older books.  But that could also be because the subject was so depressing.  The final chapter was much less funny and much more insightful, not that it provides us with a roadmap out of the mess we’re in.

Sapiens: A Brief History of Humankind, by Noah Harari, is a bit of a rambling history of our species.  It was a good read and lots of interesting nuggets about biology, evolution, and history, though it had a tendency to meander a bit.  It reminded me a bit of various Richard Dawkins books (I blogged a list of them and one related business topic here), so if you’re into that genre, this wouldn’t be bad to pick up…although it’s probably higher level and less scientific than Dawkins if that’s what you’re used to.

Finally, I finished up the fourth book in the massive Robert Caro quadrilogy biography of Lyndon Johnson (full series here).  I have written a couple times over the years about my long-term reading project on American presidential biographies, probably now in its 12th or 13th year.  I’m working my way forward from George Washington, and I usually read a couple on each president, as well as occasional other related books along the way.  I’ve probably read well over 100 meaty tomes as part of this journey, but none as meaty as what must have been 3000+ pages on LBJ.  The good news:  What a fascinating read.  LBJ was probably (with the possible exception of Jefferson) the most complex character to ever hold the office.  Also, I’d say that both Volumes 3 and 4 stand alone as interesting books on their own – Volume 3 as a braoder history of the Senate and Civil Rights; Volume 4 as a slice of time around Kennedy’s assassination and Johnson’s assumption of power.  The bad news:  I got to the end of Vol 4 and realized that there’s a Vol 5 that isn’t even published yet.

That’s it for summer reading…now back to school!

Feb 9 2017

Book Short: Why Wait?

A Sense of Urgency, by John Kotter, is a solid book – not his best, but worth a read and happily short, as most business books should be.  I originally was going to hold off on writing this post until I had more time, but the subject matter alone made me think that was a mistake and that I should write it while it’s fresh in my mind.  <g>

The three tools to fight complacency are the organizing framework for the book — bring the outside in, behave with urgency every day, and turn crises into opportunities — are all good thoughts, and good reminders of basic management principles.  But there were a couple other themes worth calling out even more.

First up, the notion that there is a vicious cycle at play in that urgency begets success which creates complacency which then requires but does not beget urgency.  The theme is really that success can drive arrogance, stability, and scale that requires inward focus — not that success itself is bad, just that it requires an extra level of vigilance to make sure it doesn’t lead to complacency.  I’ve seen this cycle at different times over the years in lots of organizations, and it’s one of the reasons that if you look at the original companies on the Dow Jones Industrials index when it was expanded from 12 to 30 around 100 years ago, only one of them (GE) still exists.

Second, that busy-ness can masquerade as urgency but actually undermines urgency.  A full calendar doesn’t mean you’re behaving with urgency.  Kotter’s example of an Indian manager is great:

If you watch the Indian manager’s behavior carefully and contrast it with the hospital executive’s, you find that the former relentlessly eliminates low-priority items from his appointment diary. He eliminates clutter on the agenda of the meetings that do make it into his diary. The space that is freed up allows him to move faster. It allows him to follow up quickly on the action items that come out of meetings. The time freed up allows him to hold impromptu interactions that push along important projects faster. The open space allows him to talk more about issues he thinks are crucial, about what is happening with customers and competitors, and about the technological change affecting his business.

Finally, Kotter’s theme of “Urgent patience” is a wonderful turn of phrase.  As he says,

It means acting each day with a sense of urgency but having a realistic view of time. It means recognizing that five years may be needed to attain important and ambitious goals, and yet coming to work each day committed to finding every opportunity to make progress toward those goals.

How true is that?  It’s not just that big ships take a long time to turn…it’s that big opportunities take a long time to pursue and get right.  If they didn’t…everyone would do them!  Urgent patience is what allows you to install a bias for action in your team without causing panic and frenzy, which is never productive.

Thanks to my friend Chad Dickerson for recommending this book, a great read as part of Operation Reboot Matt.

Aug 24 2023

What Does Great Look Like in a Chief People Officer?

This is the second post in the series…. the first one When to hire your first Chief People Officer is here).

While all CXOs are important to a company, the Chief People Officer is the one role you don’t want to get wrong because People Ops impacts every facet of a company. If you hire the wrong people—even one wrong person—you’ll regret it, and so will everyone else in your company. If you short-change the onboarding process you’ll create tons of work for others in the company to answer questions, teach people the systems, and help them get up to speed quickly—not to mention the frustration of the new hire. And of course, if you or your employees do anything illegal, discriminatory, or harassing, you’ll end up in legal trouble and you’ll lose—big time. So, it’s not enough, if you’re expanding rapidly, to “just get a Chief People Officer,” you need to hire a great Chief People Officer and I have found that great Chief People Officers do three things particularly well:

The most important characteristic or attribute of a great Chief People Officer is that they believe their function is strategic. In Startup CXO Chief People Officer Cathy Hawtrey wrote about the ways in which HR/People can be a strategic function and not just a tactical corporate function.  It’s true of most functions, but for whatever reason, (likely past experience), HR leaders frequently don’t view themselves or their functions as strategic, which is not only a huge missed opportunity but maybe says something more important about the confidence level of the Chief People Officer.  If that’s their frame of reference, then they will likely be tactical managers, they’ll keep the trains running on time, but you won’t be able to anticipate the changing talent landscape, much less be strategic about it.  If they believe they can move the needle on the business by improving engagement and productivity and efficiency, if they believe they can make the executive team more effective by helping you with team facilitation and coaching…they can do anything.

A second important characteristic of the Chief People Officer is courage—they have the courage to call you (you, the CEO) out on things directly and firmly when they see you doing or saying anything that is a bit off. It could be around language, inclusion, values, authenticity, or anything else, but they don’t let it slide or ignore it. The CPO, along with you, are the principal stewards of the company’s values and culture.  Even the best CEOs benefit from having a watchdog from time to time.

A third critical trait of a great Chief People Officer is that they think about investment in People in terms of ROI.  It’s one thing to run a killer recruiting function and fill seats efficiently, with high quality, as asked.  It’s an entirely different thing to start the recruiting process by asking if the role is needed, at that level and compensation band, or whether there are other people, fractional people, contractors, or shifts in lower value activities that could be put to work instead.  Only heads of People with deep understandings of the business can transform the function from a gatekeeper/”no” role into a business accelerator.

A great Chief People Officer is all of these things—strategic, courageous, and financially astute. Above all, great Chief people Officers know that they are the role model within a company and that their behavior, their language, their inclusiveness is setting the tone and providing a template for others to follow. 

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