Book Short – Blink part III – Undo?

I just finished reading Michael Lewis’s The Undoing Project: A Friendship That Changed Our Minds, and honestly, I wish I could hit Life’s Undo button and reclaim those hours.  I love Michael Lewis, and he’s one of those authors where if he writes it, I will read it.  But this one wasn’t really worth it for me.

Having said that, I think if you haven’t already read both Malcolm Gladwell’s Blink (review, buy) and Daniel Kahneman’s Thinking, Fast and Slow (review, buy), then it might be worth it.  But having read those two books, The Undoing Project had too much overlap and not enough “underlap” (to quote my friend Tom Bartel) – that is, not enough new stuff of substance for me.  The book mostly went into the personal relationship between two academic thinkers, Daniel Kahneman and Amos Tversky.  It also touched on some of the highlights of their work, which, while coming out of the field of psychology, won them a Nobel prize in Economics for illuminating some of the underlying mechanics of how we make decisions.

The two most interesting pieces of their work to me, which are related in the book, are:

First, that human decision-making is incredibly nuanced and complex, and that at least 25% of the time, the transitive property doesn’t apply.  For example, I may prefer coffee to tea, and I may prefer tea to hot chocolate, but that doesn’t necessarily mean I prefer coffee to hot chocolate.

From the book, “When faced with complex multidimensional alternatives, such as job offers, gambles or [political] candidates, it is extremely difficult to utilize properly all the available information.” It wasn’t that people actually preferred A to B and B to C and then turned around and preferred C to A. It was that it was sometimes very hard to understand the differences. Amos didn’t think that the real world was as likely to fool people into contradicting themselves as were the experiments he had designed.  And the choice created its own context: Different features might assume greater prominence in the mind when the coffee was being compared to tea (caffeine) than when it was being compared to hot chocolate (sugar). And what was true of drinks might also be true of people, and ideas, and emotions. The idea was interesting: When people make decisions, they are also making judgments about similarity, between some object in the real world and what they ideally want. They make these judgments by, in effect, counting up the features they notice. And as the noticeability of features can be manipulated by the way they are highlighted, the sense of how similar two things are might also be manipulated.”

Second, what Kahneman and Tversky called Prospect Theory, which is basically that humans are more motivated by the fear of loss as opposed to the greed of gain.  I’ve written about the “Fear/Greed Continuum” of my former boss from many years ago before.  I’m not sure he knew about Kahneman and Tversky’s work when he came up with that construct, and I certainly didn’t know about it when I first blogged about it years ago.  Do this experiment – ask someone both of these questions:  Would you rather be handed $500 or have a 50% chance of winning $1,000 and a 50% of getting nothing?  Then, Would you rather hand me $500 or have a 50% chance of owing me $1,000 and a 50% chance of owing me nothing?  Most of the time, the answers are not the same.

For fun, I tried this out on my kids and re-proved Prospect Theory, just in case anyone was worried about it.

Anyway, bottom line on this book – read it if you haven’t ready those other two books, skip it if you have, maybe skim it if you’ve read one of them!

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?

I’ve written a lot over the years about Return Path’s Core Values (summary post with lots of links to other posts here).  And I’ve also written and believe strongly that there’s a big difference between values, which are pretty unchanging, and culture, which can evolve a lot over time.  But I had a couple conversations recently that led me to think more philosophically about a company’s values.

The first conversation was at a recent dinner for a group of us working on fundraising for my upcoming 25th reunion from Princeton.  Our guest speaker was a fellow alumnus who I’ve gotten to know and respect tremendously over the years as one of the school’s most senior and influential volunteer leaders.  He was speaking about the touchstones in his life and in all people’s lives — things like their families, their faith, the causes they’re passionate about, and the institutions they’ve been a part of.  I remember this speaker giving a similar set of remarks right after the financial crisis hit in early 2009.  And it got me thinking about the origins of Return Path’s values, which I didn’t create on my own, but which I obviously had a tremendous amount of influence over as founder.  Where did they come from?  Certainly, some came from my parents and grandparents.  Some came from my primary and secondary education and teachers.  Some came from other influences like coaches, mentors, and favorite books.  Although I’m not overly observant, some certainly came from Hebrew school and even more so from a deep reading of the Bible that I undertook about 15 years ago for fun (it was much more fun than I expected!).  Some came from other professional experiences before I started Return Path.  But many of them either came from, or were strongly reinforced by my experience at Princeton.  Of the 15 values we currently articulate, I can directly tie at least seven to Princeton:  helpful, thankful, data-driven, collaborative, results-oriented, people first, and equal in opportunity.  I can also tie some other principles that aren’t stated values at Return Path, but which are clearly part of our culture, such as intellectually curious, appreciative of other people’s points of view, and valuing an interdisciplinary approach to work.

As part of my professional Reboot project, this was a good reminder of some of the values I know I’ve gotten from my college experience as a student and as an alumni, which was helpful both to reinforce their importance in my mind but also to remember some of the specifics around their origins – when and why they became important to me.  I could make a similar list and trade and antecedents of all or at least most of our Company’s values back to one of those primary influences in my life.  Part of Reboot will be thinking through all of these and renewing and refreshing their importance to me.

The second conversation was with a former employee who has gone on to lead another organization.  It led me to the observation I’ve never really thought through before, that as a company, we ourselves have become one of those institutions that imprints its values into the minds of at least some of its employees…and that those values will continue to be perpetuated, incorporated, and improved upon over time in any organization that our employees go on to join, manage part of, or lead.

That’s a powerful construct to keep in mind if you’re a new CEO working on designing and articulating your company’s values for the first time.  You’re not just creating a framework to guide your own organization.  You’re creating the beginning of a legacy that could potentially influence hundreds or thousands of other organizations in the future.

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.

Book Short – A Smattering of Good Ideas that further my Reboot path

Ram Charan’s The Attacker’s Advantage was not his best work, but it was worth the read.  It had a cohesive thesis and a smattering of good ideas in it, but it felt much more like the work of a management consultant than some of his better books like Know How (review, buy), Confronting Reality (review, buy), Execution (review, buy), What the CEO Wants You to Know ( buy), and my favorite of his that I refer people to all the time, The Leadership Pipeline (review, buy).

Charan’s framework for success in a crazy world full of digital and other disruption is this:

Perceptual acuity (I am still not 100% sure what this means)

1. A mindset to see opportunity in uncertainty
2. The ability to see a new path forward and commit to it
3. Adeptness in managing the transition to the new path
4. Skill in making the organization steerable and agile

The framework is basically about institutionalizing the ability to spot pending changes in the future landscape based on blips and early trends going on today and then about how to seize opportunity once you’ve spotted the future.  I like that theme.  It matches what I wrote about when I read Mark Penn’s Microtrends (review, buy) years ago.

Charan’s four points are important, but some of the suggestions for structuring an organization around them are very company-specific, and others are too generic (yes, you have to set clear priorities).  His conception of something he calls a Joint Practice Session is a lot like the practices involved in Agile that contemporary startups are more likely to just do in their sleep but which are probably helpful for larger companies.

I read the book over a year ago, and am finally getting around to blogging about it.  That time and distance were helpful in distilling my thinking about Charan’s words.  Probably my biggest series of takeaways from the book – and they fit into my Reboot theme this quarter/year, is to spend a little more time “flying at higher altitude,” as Charan puts it:  talking to people outside the company and asking them what they see and observe from the world around them; reading more and synthesizing takeaways and applicability to work more; expanding my information networks beyond industry and country; creating more routine mechanisms for my team to pool observations about the external landscape and potential impacts on the company; and developing a methodology for reviewing and improving predictions over time.

Bottom line:  like many business books, great to skim and pause for a deep dive at interesting sections, but not the author’s best work.

Brad wrote a fun post a couple years ago about rituals, including one about The Annual Dinner that he and Amy, Fred and Joanne Wilson, and Mariquita and I have been having not quite annually for almost 15 years now.  His most poignant comment (other than that apparently he and I are both getting larger and greyer in sync with each other) is about the power of marking the passage of time together with the same group of people.  We have a similar tradition at Return Path that’s worth noting in the context of my reboot program since it happened a few weeks ago and was part of the reboot cycle.

On the first anniversary of Return Path’s founding, I took my co-founder Jack Sinclair and our first two colleagues, Matt Spielman and Alexis Katzowitz, our to lunch where we shared lessons learned from the past year at the company and predictions for the company in the coming year with each other.  Jack, George Bilbrey, and I continued doing an end-of-year meal tradition with those two conversation topics for over a decade.  The last three years, since Jack left to join Stack Overflow, George and I have continued the tradition on our own.  Although some of our conversation every year isn’t really for public consumption, I’ve always regretted not blogging some highlights of it.  The tradition is a very powerful one of reflection and retrospective, which is deeply ingrained in Return Path’s culture, as a means of continuous improvement through renewal and refreshing.

Last month, we came up with a few good lessons learned that are featuring in my reboot.  Here they are:

• Growth covers up a lot of weaknesses.  While we still have a healthy growth rate as a company, it’s lower than is used to be – as is the case for all companies as they grow and face the law of large numbers.  What’s interesting, though, is how many weaknesses growth can cover up that start getting exposed as growth slows.  Think of it as an analogy to Technical Debt, call it Organizational Debt.  It’s the accumulation of small decisions over time to take an expedient path on a particular item.  It’s the “oh, we’ll throw a body at the problem now and automate the solution later” type thing that never gets automated, then gets compounded when the hired body needs to be replicated, then managed, then turned into a department.  You get the idea.
• Executive playbooks must be applied flexibly.  As is true of many growing companies, we’ve hired a number of outside senior executives over the last few years.  Some have worked out and others haven’t.  One thing we’ve learned, though, is that there’s a bit of a myth sometimes around the “I have the playbook” claim, the same way there’s a myth around hiring sales people who claim “I have a Rolodex” (or whatever the current version of that is).  Every company is unique, even in the same space.  Every situation is unique.  What makes an executive great is the ability to take learnings and experiences from prior roles and companies, both good and bad, and apply them thoughtfully to new situations, not the ability to run the same play over and over again in exactly the same way.  Sure, there are core business processes or systems that can be applied consistently, but most of those don’t require senior executive expertise.
• Know the job your customer is hiring you to do and what the alternatives are.  This is contemporary product management language, but it really rings true.  No matter who you are, no matter what job you do, you have a customer.  That customer is paying you something for a reason.  That money could go somewhere else.  Keeping that reason top of mind (and understanding when and why and how it shifts) is critical to developing the right solutions.

George, thanks for a decade and a half of reflections together (among other things!).

As I mentioned in last week’s post, I’m rebooting my work self this year, and this quarter in particular.  One of the things I am doing is getting back to basics on a few fronts.

Over the holiday break, as I was contemplating a reboot, I emailed a handful of people with whom I’ve worked closely over the years, but for the most part people with whom I no longer work day in day out, to ask them a few questions.  The questions were fairly backward looking:

1.       When I was at my best, what were my personal habits or routines that stand out in your mind?

2.       When I was at my best, what were my work behaviors or routines that stand out in your mind?

3.       When our EC was at its best, what were the team dynamics that caused it to function so well?

I got some wonderful responses, including one which productively challenged the premise of asking backward-looking questions as I was trying to reboot for the future.  (The answer is that this was one of several things I was doing as part of Rebooting, not the only thing, and historical perspective is one of many useful tools.)

Although the question clearly led itself to this, the common theme across all the answers was “back to basics.”  Part of evolving myself as a CEO as the company has grown over the years has been stopping doing particular things and starting others intentionally.  I try to do that at least once a year.  But what this particular exercise taught me is that, like the proverbial boiled frog, there were a slew of small and medium-sized things that I’ve stopped doing over the years unintentionally that are positive and productive habits that I miss.  I have a long list of these items, and I probably won’t want or need to get to all of them.  But there are a few that I think are critical to my success for various reasons.  Some of the more noteworthy ones are:

• Blogging, which I mentioned in last week’s post as an important way for me to reflect and crystallize my thinking on specific topics
• Ensuring that I have enough open time on my calendar to breathe, think, keep current with things.  When every minute of every day is scheduled, I am working harder, but not smarter
• Be more engaged with people at the office.  This relates to having open time on the calendar.  Yesterday I sat in our kitchen area and had a quick lunch with a handful of colleagues who I don’t normally interact with.  It was such a nice break from my routine of “sit at desk, order food in” or “important business lunch,” I got to clear my head a little bit, and I got to know a couple things about a couple people in the office that I didn’t previously know
• Get closer to the front lines internally.  Although I’ve maintained good external contacts as the company has grown with key clients and partners, our multi-business-unit structure has had me too disconnected from Sales and Engineering/Product in particular.  This one may take a couple months to enact, but I need to get closer to the action internally to truly understand what’s going on in the business
• Get back to a rigorous use of a single Operating System.  I’ve written a lot about this over the years, but having a David-Allen style, single place where I track all critical to do’s for me and for my team has always been bedrock for me.  I’ve been experimenting with some different ways of doing this over the last couple years, which has led to a breakdown in Allen’s main principle of “put it all in one place” – so I am going to work on fixing that
• Reading – while I have been consistently and systematically working my way through American history and Presidential biographies books over the years, I’ve almost entirely stopped reading other books for lack of time.  A well-balanced reading diet is critical for me.  So I’m working in some other books now from the other genres I love – humor (Martini Wonderland is awesome), architecture (see last week’s post on The Fountainhead), current events (I’m in the middle of Michael Lewis’ The Undoing Project and next up is Tom Friedman’s Thank You For Being Late), and business books (about to start Kotter’s A Sense of Urgency)
• Like reading, doing something creative and unrelated to work has always been an important part of keeping my brain fresh.  Coaching little league has helped a lot.  But I need to add something that’s more purely creative.  I am still deciding between taking guitar lessons (I halfway know how to play) and sculpting lessons (I don’t know a thing about it)

That’s it for now.  There are other basics that I never let lapse (for example, exercise).  But the common theme of the above, I realize now that I am writing it all out, isn’t only “back to basics.”  It’s about creating time and space for me to be fresh and exercise different muscles instead of grinding it out all day, every day.  And that’s well worth the few minutes it took me and my friends to work up this list!

Hopefully I’ll have more to say on the general topic of rebooting in another week or two as January craziness sets in with our annual kickoff meetings around the world.

Reboot – The Fountainhead

Happy New Year!  Every few years or so, especially after a challenging stretch at work, I’ve needed to reboot myself.  This is one of those times, and I will try to write a handful of blog posts on different aspects of that.

The first one is about a great book.  I just read Ayn Rand’s The Fountainhead for (I think) the 5^th time.  It’s far and away my favorite book and has been extremely influential on my life.  I think of it (and any of my favorite books) as an old friend that I can turn to in order to help center myself when needed as an entrepreneur and as a human.  The last time I read it was over 10 years ago, which is too long to go without seeing one of your oldest friends, isn’t it?  While the characters in the book by definition are somewhat extreme, the book’s guiding principles are great.  I’ve always enjoyed this book far more than Atlas Shrugged, Rand’s more popular novel, which I think is too heavy-handed, and her much shorter works, Anthem and We The Living, which are both good but clearly not as evolved in her thinking.

As an entrepreneur, how does The Fountainhead influence me?  Here are a few examples.

• When I think about The Fountainhead, the first phrase that pops into my head is “the courage of your convictions.”  Well, there’s no such thing as being a successful entrepreneur without having the courage of your convictions.  If entrepreneurs took “no” for an answer the first 25 times they heard it, there would be no Apple, no Facebook, no Google, but there’d also be no Ford, no GE, and no AT&T
• One great line from the book is that “the essence of man is his creative capacity.”  Our whole culture at Return Path, and one that I’m intensely proud of, is founded on trust and transparency.  We believe that if we trust employees with their time and resources, and they know everything going on in the company, that they will unleash their immense creative capacity on the problems to be solved for the business and for customers
• Another central point of influence for me from the book is that while learning from others is important, conventional wisdom only gets you far in entrepreneurship.  A poignant moment in the book is when the main character, Howard Roark, responds to a question from another character along the lines of “What do you think of me?”  The response is “I don’t think of you.”  Leading a values-driven life, and running a values-driven existence, where the objective isn’t to pander to the opinion of others but to fill my life (and hopefully the company’s life) with things that make me/us happy and successful is more important to me than simply following conventional wisdom at every turn.  Simply put, we like to do our work, our way, noting that there are many basics where reinventing the wheel is just dumb
• Related, the book talks about the struggle between first-handers and second-handers.  “First-handers use their own minds.  They do not copy or obey, although they do learn from others.”  All innovators, inventors, and discoverers of new knowledge are first-handers.  Roark’s speech at the Cortland Homes trial is a pivotal moment in the book, when he says, “Throughout the centuries, there were men who took first steps down new roads armed with nothing but their own vision.  The great creators — the thinkers, the artists, the scientists, the inventors — stood alone against the men of their time.  Every great new thought was opposed.”  In other words, first-handers, critical thinkers, are responsible for human progress.  Second-handers abdicate the responsibility of independent judgment, allowing the thinking of others to dominate their lives.  They are not thinkers, they are not focused on reality, they cannot and do not build
• The “virtue of selfishness” is probably the essence of Rand’s philosophy.  And it sounds horrible.  Who likes to be around selfish people?  The definition of selfish is key, though.  It doesn’t inherently mean that one is self-centered or lacks empathy for others.  It just means one stays true to one’s values and purpose and potentially that one’s actions start with oneself.  I’d argue that selfishness on its own has nothing to do with whether someone is a good person or a good friend.  For example, most of us like to receive gifts.  But people give gifts for many different reasons – some people like to give gifts because they like to curry favor with others, other people like to give gifts because it makes them feel good.  That’s inherently selfish.  But it’s not a bad thing at all
• Finally, I’d say another area where The Fountainhead inspires me as a CEO is in making me want to be closer to the action.  Howard Roark isn’t an ivory tower designer of an architect.  He’s an architect who wants to create structures that suit their purpose, their location, and their materials.  He only achieves that purpose by having as much primary data on all three of those things as possible.  He has skills in many of the basic construction trades that are involved in the realization of his designs – that makes him a better designer.  Similarly, the more time I spend on the front lines of our business and closer to customers, the better job I can do steering the ship

One area where I struggle a little bit to reconcile the brilliance of The Fountainhead with the practice of running a company is around collaboration.  It’s one thing to talk about artistic design being the product of one man’s creativity, and that such creativity can’t come from collaboration or compromise.  It’s another thing to talk about that in the context of work that inherently requires many people working on the same thing at the same time in a generalized way.  Someday, I hope to really understand how to apply this point not to entrepreneurship, but to the collaborative work of a larger organization.  I know firsthand and have also read that many, many entrepreneurs have cited Ayn Rand as a major influence on them over the years, so I’m happy to have other entrepreneurs comment here and let me know how they think about this particular point.

It feels a little shallow to try to apply a brilliant 700 page book to my life’s work in 1,000 words.  But if I have to pick one small point to illustrate the connection at the end, it’s this.  I realize I haven’t blogged much of late, and part of my current reboot is that I want to start back on a steady diet of blogging weekly.  Why?  I get a lot out of writing blog posts, and I do them much more for myself than for those who reads them.  That’s a small example of the virtue of selfishness at work.

You, Too, Can Take Six Weeks Off

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

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

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

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

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

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

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

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

A Path Forward in California!

Back in March I was proud to announce the launch of Path Forward, a nonprofit on a mission to get people back to work after they’ve taken time off to care for a loved one.  I’m even more thrilled today to announce the launch of a Path Forward program in California with six top tech companies — Go Daddy, Demandbase, CloudFlare, Coursera, Instacart and Zendesk. They are all accepting applications now for October start dates. Click on the links above to see all their opportunities.

As a CEO I know how hard it is to find great talent. The Center for Talent Innovation estimates that nearly 30% of college-educated women have taken away from their careers to serve as caregivers to children or aging family members. They have also found that while 90% of them try to return to work, only 40% are able to land full-time jobs. As an industry, we simply can’t afford to lose thousands of talented women who become frustrated by attempts to restart their professional careers.

Please join me in supporting this organization in fulfilling its mission. If you know people in California who might be looking for opportunities to restart their careers, send them to Your Path Forward in California where they can access all the job postings for the fall program.

And if you think Path Forward would be a great program for your company, email the fine folks at [email protected] to learn more.

Book Short:  Scrum ptious 

I just finished reading Scrum: The Art of Doing Twice the Work in Half the Time, by Jeff Sutherland and JJ Sutherland. This reading was in anticipation of an Agile Facilitation training my executive team and I are going through next week, as part of Return Path’s  Agile Everywhere initiative. But it’s a book I should’ve read along time ago, and a book that I enjoyed.

Sutherland gets credit for creating the agile framework and bringing the concept scrum to software development over 20 years ago. The book very clearly lays out not just the color behind the creation of the framework, and the central tenets of practice again, but also clear and simple illustrations of its value and benefits.  And any book that employs the Fibonacci series and includes Theodore Roosevelt’s “Man in the Arena” quote — my all-time favorite — is off to a good start by me.

I’ve always appreciated a lot of the underlying philosophy of Agile, such as regularly checking on projects, course correcting in response to feedback from customers or other stakeholders, and working hard to remove any impediments to progress in real time.

One of the author’s most poignant points is that “multitasking makes you stupid.”  I hadn’t focused in the past how agile allows you to clear away context shifts to focus on one task at a time, but that’s another great take away from the book.

Our Agile Everywhere initiative, which is designed to improve productivity across the organization, as well as increase accountability through transparency, is even more critical in my view after having read this book.

The thing that I am left struggling with, which is still very much a work in progress for us, and hopefully something that we will address more head on in our training next week, is the application of the agile framework to teams that are not involved in the production of a tangible work product, such as executive or other leadership teams.  That is something that our Agile Everywhere deployment team has developed a theory about, but it still hasn’t entirely sunk in for me.

I can’t wait for next week’s training session!  If you have any experience applying the agile framework to different types of teams in your company I’d love to hear more about it in the Comments.