Book Short:  Like Reading a Good Speech

Leaders Eat Last, by Simon Sinek, is a self-described “polemic” that reads like some of the author’s famous TED talks and other speeches in that it’s punchy, full of interesting stories, has some attempted basis in scientific fact like Gladwell, and wanders around a bit.  That said, I enjoyed the book, and it hit on a number of themes in which I am a big believer – and it extended and shaped my view on a couple of them.

Sinek’s central concept in the book is the Circle of Safety, which is his way of saying that when people feel safe, they are at their best and healthiest.  Applied to workplaces, this isn’t far off from Lencioni’s concept of the trust foundational layer in his outstanding book, Five Dysfunctions of a Team.  His stories and examples about the kinds of things that create a Circle of Safety at work (and the kinds of things that destroy them) were very poignant.  Some of his points about how leaders set the tone and “eat last,” both literally and figuratively, are solid.  But his most interesting vignettes are the ones about how spending time face-to-face in person with people as opposed to virtually are incredibly important aspects of creating trust and bringing humanity to leadership.

My favorite one-liner from the book, which builds on the above point and extends it to a corporate philosophy of people first, customer second, shareholders third (which I have espoused at Return Path for almost 15 years now) is

Customers will never love a company unless employees love it first.

A couple of Sinek’s speeches that are worth watching are the one based on this book, also called Leaders Eat Last, and a much shorter one called How Great Leaders Inspire Action.

Bottom line:  this is a rambly book, but the nuggets of wisdom in it are probably worth the exercise of having to find them and figure out how to connect them (or not connect them).

Thanks to my fellow NYC CEO Seth Besmertnik for giving me this book as well as the links to Sinek’s speeches.

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

Book Short:  Sloppy Sequel

SuperFreakonomics, by Steven Levitt and Stephen Dubner, wasn’t a bad book, but it wasn’t nearly as good as the original Freakonomics, either.  I always find the results of “naturally controlled experiments” and taking a data-driven view of the world to be very refreshing.  And as much as I like the social scientist versions of these kinds of books like Malcolm Gladwell’s The Tipping Point and Blink (book; blog post), there’s usually something about reading something data driven written by a professional quant jock that’s more reassuring.

That’s where SuperFreakonomics fell down a bit for me.  Paul Krugman has described the book in a couple different places as “snarky and contrarian.”  I typically enjoy books that carry those descriptors, but this one seemed a bit over the top for economists — like a series of theories looking for data more than raw data adding up to theories.Nowhere is this more true than the chapter on climate change.  It’s a shame that that chapter seems to be swallowing up all the public discussion about the book, because there are some good points in that chapter, and the rest of the book is better than that particular chapter, but such is life.

As with all things related to the environment, I turned to my friend Andrew Winston’s blog, where he has a good post about how the authors kind of miss the point about climate change…and he also has a series of links to other blog posts debunking this one chapter.  If you’re into the topic, or if you read the book, follow the chain here for good reading.  My conclusion about this chapter, being at least somewhat informed about the climate change debate, is that the book seems to have sloppy writing and editing at best, possibly deliberately misleading at worst.  (Incidentally, the reaction in the blogosphere seems highly emotional, other than Andrew’s, which probably doesn’t serve the reactors well.)

But I’ll assume the best of intentions.  Some of the points made aren’t bad – there is no debate about the problem or the need to solve it, the authors express legitimate concern that current solutions, especially those requiring behavioral change, will be too little too late, and most interestingly, they show an interest in alternative approaches like geo-engineering.  I hadn’t been familiar with that topic at all, but I’m now much more interested in it, not because it’s a “silver bullet” approach to dealing with climate change, but because it’s a different approach, and complex problems like climate change deserve to have a wide range of people working on multiple types of solutions.  I met Nathan Myhrvold once (I almost threw up on him during a job interview, which is another story for another day), and it makes me very happy that his brilliance is being applied to this problem as a general principle.

As I said, though, beyond this one chapter, the book is good-not-great.  But it certainly is chock full of cocktail party nuggets!

I love the concept of Servant Leadership.  From the source, the definition is:

While servant leadership is a timeless concept, the phrase “servant leadership” was coined by Robert K. Greenleaf in The Servant as Leader, an essay that he first published in 1970. In that essay, Greenleaf said:

“The servant-leader is servant first… It begins with the natural feeling that one wants to serve, to serve first. Then conscious choice brings one to aspire to lead. That person is sharply different from one who is leader first, perhaps because of the need to assuage an unusual power drive or to acquire material possessions…The leader-first and the servant-first are two extreme types. Between them there are shadings and blends that are part of the infinite variety of human nature.

“The difference manifests itself in the care taken by the servant-first to make sure that other people’s highest priority needs are being served. The best test, and difficult to administer, is: Do those served grow as persons? Do they, while being served, become healthier, wiser, freer, more autonomous, more likely themselves to become servants? And, what is the effect on the least privileged in society? Will they benefit or at least not be further deprived?“

A servant-leader focuses primarily on the growth and well-being of people and the communities to which they belong. While traditional leadership generally involves the accumulation and exercise of power by one at the “top of the pyramid,” servant leadership is different. The servant-leader shares power, puts the needs of others first and helps people develop and perform as highly as possible.

This is a very broad societal definition, but it’s fairly easy to apply to a more narrow corporate, or even startup environment.  Are you as a CEO oriented primarily towards your people, or towards other stakeholders like customers or shareholders?  By the way, trying to do right by all three stakeholders is NOT a problem in a world of being oriented towards one.  It’s just a philosophy around which comes first, and why.  Our People First philosophy at Return Path is fair clear that at the end of the day, all three stakeholders win IF you do right by employees, so they do the best possible work for customers, so you build a healthy and profitable and growing business.

CEOs who practice Servant Leadership aren’t necessarily focused on power dynamics, or on helping those least privileged in society (at least not as part of their job)…but they are focused on making sure that their employees most important needs are met — both in the moment, as in making sure employees are empowered and not blocked or bottlenecked, and over the long haul, as in making sure employees have opportunities to learn, grow, advance their careers, make an impact, and have the ability to live a well balanced life.

I was in a meeting a couple weeks back with another leader and a few people on his team.  He *seemed* to practice Servant Leadership the way he was speaking to his team members.  But he wasn’t, really.  He was doing something I refer to as Sucking Down.  He was telling them things they clearly wanted to hear.  He was lavishing praise on them for minor accomplishments.  He was smiling and saying yes, when what he really meant was no.  He was practicing the art of Sucking Up, only to people on his team, not to a boss.  I got a sense that something wasn’t right during the meeting, and then post meeting, he actually fessed up to me — even bragged about it — that he was being disingenuous to get what he wanted out of his people.

There’s a clear difference between Servant Leadership and Sucking Down in the long run.  The danger comes in the moment.  Just as managers need to build good detection skills to sniff out evidence of someone on their team Sucking Up, employees need to be able to understand that clear difference in their managers’ behavior as they think about how to manage their careers, and even where to work.

Book Short:  Required Reading, Part II

Every once in a while, a business book nails it from all levels.  Well written, practical, broadly applicable to any size or type of organization, full of good examples, full of practical tables and checklists.   The Leadership Pipeline, which I wrote about here over six years ago, is one of those books — it lays out in great and clear detail a framework for understanding the transition from one level to another in an organization and how work behaviors must change in order for a person to succeed during and on the other side of that transition.  In an organization like Return Path‘s which is rapidly expanding and promoting people regularly, this is critical.  We liked the book so much that we have adopted a lot of its language and have built training courses around it.

The book’s sequel, The Performance Pipeline (book, Kindle), also by Stephen Drotter but without the co-authors of the original book, is now out — and it’s just as fantastic.  The book looks at the same six level types in an organization (Enterprise Manager, Group Manager, Business Manager, Functional Manager, Manager of Managers, Manager of Others, and Self Managers/Individual Contributors) and focuses on what competencies people at each level must have in order to do their jobs at maximum effectiveness — and more important, in order to enable the levels below them to operate in an optimal way.

This book is as close to a handbook as I’ve ever seen for “how to be a CEO” or “how to be a manager.”  Coupled with its prequel, it covers the transition into the role as well as the role itself, so “how to become a CEO and be a great one.”  As with the prequel, the author also takes good care to note how to apply the book to a smaller organization (from the below list, usually the top three levels are combined in the CEO, and often the next two are combined as well).  No synopsis can do justice to this book, but here’s a bit of a sense of what the book is about:

• Enterprise Manager:  role is to Perpetuate the Enterprise and develop an Enterprise-wide strategic framework – what should we look like in 15-20 years, and how will we get the resources we need to get there?
• Group Manager:  role is to manage a portfolio of businesses and develop people to run them
• Business Manager:  role is to optimize short- and long-term profit and develop business-specific strategies around creating customer and stakeholder value
• Functional Manager:  role is to drive competitive advantage and functional excellence
• Manager of Managers:  role is to drive productivity across a multi-year horizon, and focus
• Manager of Others:  role is to enable delivery through motivation, context setting, and talent acquisition
• Self Managers/Individual Contributors:  role is to deliver and to be a good corporate citizen

I could write more, but there’s too much good stuff in this book to make excerpts particularly useful.  The Performance Pipeline is another one of those rare – “run, don’t walk, to buy” books.  Enjoy.  For many of my colleagues at RP – look out – this one is coming!

Book Short:  Next, Write a Sequel

Written by Rodd Wagner and James K. Harter and billed as “the long awaited sequel to First, Break All the Rules” (one of the best management books I’ve ever read), I thought 12: The Elements of Great Managing, was good, but not great.  12…, along with the original book First… and Now, Discover Your Strengths, the latter two both by Marcus Buckingham, are all based on an extensive database of research done on corporate America by the Gallup organization over many years.  All three are valuable reads in one way or another, although I found this to be the weakest of the three.  (Note that Now… is different from the other two in that it’s not about management, it’s about self-management — very different, though based on the same research.)

Anyway, the elements of great managing, so say the authors, is all about creating employee engagement.  I totally buy into that.  And since no book short on 12… would be complete if it didn’t list out the 12…

1. Do I know what is expected of me at work?
2. Do I have the materials and equipment I need to do my work right?
3. At work, do I have the opportunity to do what I do best every day?
4. In the last seven days, have I received recognition or praise for doing good work?
5. Does my supervisor, or someone at work, seem to care about me as a person?
6. Is there someone at work who encourages my development?
7. At work, do my opinions seem to count?
8. Does the mission/purpose of my company make me feel my job is important?
9. Are my co-workers committed to doing quality work?
10. Do I have a best friend at work?
11. In the last six months, has someone at work talked to me about my progress?
12. This last year, have I had the opportunities at work to learn and grow?

The book fleshes out each of the 12, gives examples (some of which are better/clearer than others), and then addresses compensation in a very interesting chapter at the end.  Key takeaways on comp:

– Higher pay doesn’t guarantee greater engagement
– Good and bad employees are equally likely to think they deserve a raise
– Money without meaning isn’t enough
– Most employees, most of the time, feel undercompensated
– Individual pay can/should be private, but comp criteria should be very public
– People who feel well-compensated generally work harder

The book also cites a very provocative article suggesting that organizations would handle comp better if they made everyone’s comp public (in contrast to the final bullet above, yes).  I’m going to write more about compensation in future postings, so I’ll leave this section on those notes.

Finally, the book’s two closing thoughts are perhaps its most prescient:  one critical element of BEING a great manager is HAVING a great manager; and the managers who put the most into their people, get the most out of their people.

Book Short:  Like a Prequel to My Book

How to Start a Business, by Jason Nazar, CEO of our client Docstoc, is a great and quick (and free) eBook that feels a lot like a prequel to my book Startup CEO:  A Field Guide to Scaling Up Your Business (original outline here). My book is about scaling a business once you’ve started it.  Jason’s book is a really practical guide to starting it in the first place.

The thing that’s particularly good about this book is that it’s as much a resource guide as it is a book.  At the end of each of its 24 chapters (and within them as well), Jason adds a series of external links to other resources, from videos to checklists to templates.  The book answers a lot of really practical questions that are easy for product-focused entrepreneurs to gloss over or ignore, from corporate structures to insurance, from trademark registration to pitching VCs, from payroll to tax planning.

It’s great to see so much more being written for entrepreneurs these days.  Ash Maurya’s Running Lean: Iterate from Plan A to a Plan That Works (which I blogged about last week) is another related book that focuses on how to bring a new product to market.  But Jason’s eBook is a must read for anyone in TechStars or any accelerator program, or anyone contemplating starting a business.

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.

The Best Place to Work, Part 0

I keep getting questions about a deck I’ve used several times at Techstars, Seedcamp, DreamIt, and the like which is called “7 Ideas for Creating the Best Place to Work.”  So today I will launch a 7-part series over the next 7 weeks to describe my 7 points.  As always, this is not intended to be perfect or comprehensive, but it is a bit of lessons learned over the last 12-13 years at Return Path.  It’s just 7 ideas – not the only 7 ideas.  And there’s nothing magic about the number 7, despite what George Costanza says.  Or Steven Covey.

Here’s the outline:

1. Surround yourself with the best and brightest
2. Create an environment of trust
3. Manage yourself very, very well
4. Be the consummate host
5. Be the ultimate enabler
6. Let people be people
7. Create a thankful atmosphere

Let’s go!  I will create a tag cloud for this series called Best Place to Work.

Book Short: Not About Going With The…

Flow: The Psychology of Optimal Experience, by Mihaly Csikszentmihalyi (book, Kindle), was a great read and a nice change from either strictly business books or my regular fiction/non-fiction reading. It’s basically about the process of achieving happiness through control over one’s inner life, but it’s far from a self-help book. It’s almost more of practical psychology deep dive into what brings about happiness and peak performance – a state the author calls Flow but others have called other things over time, like being “in the zone.”

The author talks about achieving this control as synonymous with the enviable ability to persevere despite obstacles and setbacks and transform hopeless situations into challenges to be overcome, just through the force of personality. This ability comes directly from ways to order consciousness so as to be in control of feelings and thoughts. The normal entropy/chaos of the mind is the enemy. There were a few key moments or takeaways in the book for me.

1. When one’s experience is most positive – when one is achieving Flow – people cite the following conditions in this order of importance:

– Confront tasks we have a chance of completing

– Able to concentrate

– Concentration is possible because the task has clear goals and…

– …provides immediate feedback

– Act with a deep but effortless involvement that removes from awareness the worries and frustrations of everyday life

– Exercise a sense of control over actions

– Concern for the self disappears, yet paradoxically the sense of self emerges stronger after the experience is over

2. Becoming more Autotelic – learning how to make experiences ends in and of themselves – coming from the Greek words for “self” and “goal,” this concept is savoring a given activity for its own sake, NOT for its consequences and is a key to achieving Flow. Whether you create a mental construct around beating a personal record, doing math or pattern matching in your head, or something else, being able to focus enough energy on the task at hand and not be distracted by the world around (present or future) is key. It’s a little like what I wrote a few months ago about how achieving mental discipline in the small areas of one’s life can lead to much greater things by building confidence and clearing mental clutter.

3. The concept of the “Flow channel” – as skill increases, challenges must also increase proportionally in order for us to continue learning, growing, and excelling – and achieving Flow.

4. Transformational coping is the ability to cheat chaos – transforming a hopeless situation into a new flow activity that can be controlled and enjoyed and emerge stronger from…

– Unselfconscious self-assurance – ego absent but confident, not at odds with environment but part of it

– Focusing attention on the world – looking outward, not inward

– The discovery of new solutions – being able to perceive unexpected opportunities as a result

5. How to develop the autotelic self

– Set clear goals

– Become immersed in the activity

– Pay attention to what’s happening

– Learn to enjoy immediate experience

The book reminded me of a couple other things I’ve read, in case any of these resonate with you. First, Tim Gallwey’s “Inner Game” books where he talks about “relaxed concentration,” basically the Flow state, and the inner conflict between focus on the event and focus on the consequences, between mental chaos and mental discipline, personified as Self 1 and Self 2. If you haven’t read these, any are good and give you the general idea, depending on which piques your interest the most: The Inner Game of Golf (book, Kindle), The Inner Game of Tennis (book only), and The Inner Game of Work (book, Kindle). Second, David Allen’s Getting Things Done theory about how a clear, uncluttered mind can do its best work. As Flow says, achieving an ordered mental condition is difficult – unless a person knows how to give order to his or her thoughts, attention will be attracted to whatever is most problematic at the moment.

I’m not sure this book short does the book justice. It’s pretty complex and is rich with examples, but Flow (book, Kindle) is well worth a read if you’re into the theory of self control leading to better results and more happiness in life. Thanks to my friend Jonathan Shapiro for this book.

Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.