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.
Book Short: What’s Your Meeting Routine?
Patrick Lencioni’s Death by Meeting is, as Brad advertised, a great read, and much in line with his other books (running list at the end of the post). His books are just like candy. If only all business books were this short and easy to read.
This fable isn’t quite what I thought it was going to be at the outset – it’s not about too many meetings, which is what I’ve always called “death by meeting.” It’s about staff meetings that bore you to death. With a great story around them featuring characters named Casey and Will (my two oldest kids’ names, which had me chuckling the whole time), Lencioni describes a great framework for splitting up your staff meetings into four different types of meetings: the daily stand-up, the weekly tactical, the monthly strategic, and the quarterly offsite.
There’s definitely something to the framework. We have over the years done all four types of meetings, though we never had all four in our rotation at once as that felt like overkill. But I think at a minimum, any 2 get the job done much better than a single format recurring meeting. As long as you figure out how to separate status updates from more strategic conversations, you’re directionally in good shape. We have almost entirely eliminated or automated status update meetings at this point at my staff level.
The book has some other good stuff in it, though, about the role of conflict in staff meetings, which I’ll save for your own read of the book!
So far the series includes:
- The Three Signs of a Miserable Job (post, link)
- The Five Temptations of a CEO (post, link
)
- The Four Obsessions of an Extraordinary Executive (post, link)
I have two more to go, which I’ll tackle in due course and am looking forward to.
Book Short: The Joys of Slinging Hash
Patrick Lencioni’s The Three Signs of a Miserable Job is a good read, as were his last two books, The Five Temptations of a CEO (post, link), and The Four Obsessions of an Extraordinary Executive (post, link). They’re all super short, easy reads (four express train rides on Metro North got the job done), with a single simple message and great examples. This one is probably my second favorite so far.
This book, which has a downright dreary title, is great. It points to and proposes a solution to a problem I’ve thought about for a long time, which is how do you create meaning for people in their day to day work when they’re not doing something intrinsically meaningful like curing a disease or feeding the homeless. His recipe for success is simple:
– Get people to articulate the relevance in their jobs…the meaning they derive out of their work…an understanding of the people whose lives are made better, even in small ways, by what they do every day
– Get people to measure what they do (duh, management 101), IN RELATION TO THE RELEVANCE learnings from the last point (ahh, that’s an interesting twist)
– Get to know your people as people
All of these are things you’d generally read in good books on management, but this book ties them together artfully, simply, and in a good story about a roadside pizza restaurant. It also stands in stark contrast to the book I reviewed and panned a few days ago by Jerry Porras in that it is nothing but examples from non-celebrities, non-success stories — ordinary people doing ordinary jobs.
Brad has blogged glowingly about Death by Meeting, so I’ll probably make that my next Lencioni read next month, with two more to go after that.
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.
Book Short:Â The Religion of Heresy
At the end of Tribes: We Need You to Lead Us, Seth Godin’s new book, Seth says this:
I’m going to get a lot of flak from people about what you just read. People might say that it’s too disorganized or not practical enough or that I require you to do too much work to actually accomplsh anything. That’s ok.
He’s kind of right. The book is a little breezy and meanders around, just like riffing with Seth. It’s not practical in the sense that if the entire world operated this way in the extreme, we’d have serious problems. But the fact that he requires you to do “too much work to actually accomplish anything” is part of the brilliance of his message.
This was Seth’s best book in years, mostly because it is fresh. It is not a rant about marketing; it is a wonderfully succinct look at how we as a society are rallying and organizing around causes, campaigns, companies, and collective beliefs. It’s not about the Internet, though its principles are easily implemented and amplified using online tools. It’s not a how-to guide to being a fancy corporate leader, but it’s one of the most pointed descriptions of the ethos of a certain type of leader (the upstart, or as Seth says, the heretic). It’s not about a particular revolution; it’s about how mini-revolutions are becoming the norm these days.
Tribes is short, inspirational, and pure Seth. Though quite different in its nature and mission, it really evoked for me Mark Penn’s Microtrends (post, link) — a study of larger tribes and heretics in contemporary America.
A listing of Seth’s books over the years follows:
Book Short: Wellness Redefined
Well Being: The 5 Essential Elements, by Tom Rath and Jim Harter from the Gallup organization, is a solid read and incredibly short. It’s one of those books that’s really a long article stretched and bound. But it goes beyond the basics of what I expected, which was something like “having healthy employees cuts down on absenteeism” and has a couple great elements of food for thought for leaders looking to build cutting edge and uber-productive organizations. It comes out of the same general body of research as four other very strong books I’ve written about over time — First, Break all the Rules, Now, Discover Your Strengths, 12: The Great Elements of Managing (book, review), and Go Put Your Strengths to Work (book, review).
The authors define well being as having five separate components:Â career well being, social well being, physical well being, financial well being, and community well being. Ok, that makes sense, but the three most interesting points the book made from my perspective were:
- Well being isn’t just about one of these five elements – it’s about all five, and how they interact together, and how the workplace can support all of them
- Achieving long-term objectives around well being requires finding short-term incentives that drive the same behavior in more obvious and immediate ways, as most long-term well being drivers require short term sacrifice. So figure out how to make eating a salad better for you not just years from now but TODAY (you’ll have more energy after lunch than if you eat that cheeseburger), for example
- Financial well being isn’t something a lot of companies focus on, and maybe it should be. Particularly in our industry we hire knowledge workers and assume therefore that they’re smart and educated about everything…but maybe there are ways that the company can support financial well being that aren’t necessarily obvious
The book is full of stats from the underlying research, most of which show that most people are shockingly unhappy, and that most workplaces dont do enough to support employee wellness. The book also notes, as is the case with most things, that promoting well being among employees requires more than just setting up programs. Doing it right requires constant vigilance, measurement, and follow up. At Return Path, we do a bunch of programs along the lines suggested by the book (but can and should do more!), but we’ve never been rigorous with follow up. Good food for thought.
Note there is also a free whitepaper on the economics of well being that you can download here. The white paper is ok…but not nearly as interesting as the book, and note that it does not substitute for the book. Thanks to my colleague Cathy Hawley for this book!
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: 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: The Anti-Level-5 Leader
The Five Temptations of a CEO, another short leadership fable in a series by Patrick Lencioni, wasn’t as meaningful to me as the last one I read, The Four Obsessions of an Extraordinary Executive (post, link), but it wasn’t bad and was also a quick read.
The book to me was the 30 minute version of all the Level-5 Leadership stuff that Collins wrote about in Good to Great and Built to Last. All that said, it was a good quick read and a reminder of what not to do. The temptations are things that most CEOs I’ve ever known (present company very much included) have at least succumbed to at one point or another in their career. That said, you as a CEO should quit or be fired if you have them in earnest, so hopefully if you do have them, you recognize it and have them in diminishing quantities with experience, and hopefully not all at once:
– The temptation to be concerned about his or her image above company results
– The temptation to want to be popular with his or her direct reports above holding them accountable for results
– The temptation to ensure that decisions are correct, even if that means not making a decision on limited information when one is needed
– The temptation to find harmony on one’s staff rather than have productive conflict, discussion, and debate
– The temptation to avoid vulnerability and trust in one’s staff
I’m still going to read the others in Lencioni’s series as well. They may not be the best business books ever written, but they’re solid B/B+s, and they’re short and simple, which few business books are and all should be!
Book Short:Â Alignment Well Defined, Part II
Getting the Right Things Done: A Leader’s Guide to Planning and Execution, by Pascal Dennis, is an excellent and extraordinarily practical book to read if you’re trying to create or reengineer your company’s planning, goal setting, and accountability processes. It’s very similar to the framework that we have generally adapted our planning and goals process off of at Return Path for the last few years, Patrick Lencioni’s The Advantage (book, post/Part I of this series). My guess is that we will borrow from this and adapt our process even further for 2014.
The book’s history is in Toyota’s Lean Manufacturing system, and given the Lean meme floating around the land of tech startups these days, my guess is that its concepts will resonate with most of the readers of this blog. The book’s language — True North and Mother Strategies and A3s and Baby A3s — is a little funky, but the principles of simplicity, having a clear target, building a few major initiatives to drive to the target, linking all the plans, and measuring progress are universal. The “Plan-Do-Check-Adjust” cycle is smart and one of those things that is, to quote an old friend of mine, “common sense that turns out is not so common.”
One interesting thing that the book touches on a bit is the connection between planning/goals and performance management/reviews. This is something we’ve done fairly well but somewhat piecemeal over the years that we’re increasingly trying to link together more formally.
All in, this is a good read. It’s not a great fable like Lencioni’s books or Goldratt’s classic The Goal (reminiscent since its example is a manufacturing company). But it’s approachable, and it comes with a slew of sample processes and reports that make the theory come to life. If you’re in plan-to-plan mode, I’d recommend Getting the Right Things Done as well as The Advantage.
This post was inspired by Startup CXO and was originally published by Techstars on The Line.
If you’re new to the Chief Customer Officer role, we’d like to share some advice we wish we had learned earlier in our careers. There are a few common misconceptions about customers and the service organization. If you don’t realize these as misperceptions, you can spend a lot of time dealing with issues that are not real, but perceived. We have identified five of these common misperceptions, although we are sure there are more.
Misperception #1: The service organization fully controls churn (customer attrition)
In a lot of organizations you’ll see the service organization be measured solely on customer churn. If you really think about it, there are many elements that come into play that impact churn, including
- How the customer is sold
- The quality of the product
- How easy it is to onboard the customer
- How easy it is to use the product
- How easy it is for the customer to understand what kind of value they’re getting out of the product
Of course, the service functions do have a critical role, but they’re not the only functions in a company that impact churn. The responsibility for churn also lies with sales, engineering, marketing, and other teams. One reason why you need a C-level senior person in charge of all service operations is because you need someone who understands the customer experience broadly and that person has to work cross-functionally to ensure customer retention.
Misperception #2: The service organization is just a cost center
In many businesses, if a function isn’t generating new revenue, it’s seen as “second class.” From our perspective revenue retained is revenue gained and the service organization has a big impact on retaining revenue. In addition, the account management portion of a service organization is often in charge of up-sale and cross-sale opportunities which can be huge areas of growth. CCOs should work within their company to alter that misperception of service as a cost center because the service organization can have a huge impact on revenues.
Misperception #3: Service teams should focus on responding to defections
I’ve recently found a situation where the customer success team is built to focus on the clients who have raised their hand and said, “I want to leave.” This reactive approach drives low job satisfaction and isn’t the “best and highest use” of a service team’s time. By the time a customer is frustrated enough, or isn’t seeing the value enough, that they want to leave — you’ve missed a window of opportunity. The right focus should be proactively helping customers reach their desired business objectives. If you can do that, most customers will stay. That’s the theory behind the rise of the customer success team and that’s what great companies are doing today.
Misperception #4: Service’s job is to “paper over” gaps in the product
There is a widespread practice of covering for product issues by throwing service at the problem. That certainly can work, but it’s not optimal. The superior approach is to focus the service team on becoming a trusted advisor for customers, helping those customers achieve their desired outcomes. To do that, the CCO will have to work cross-functionally with the product team, the marketing team, and the sales team to drive a more friction-free customer experience.
Misperception #5: Service is boring and tactical
There is a wide-spread misperception that working in the service organization is boring. It’s mundane, it’s tactical, it doesn’t appeal to people who think strategy is grander than tactics. I don’t agree with that at all. A great service organization starts with a strategy. It starts with an understanding of customer segmentation. It includes thinking about the different customer personas and how to define an appropriate and valuable customer experience. That core strategy actually takes a while to develop. Once the strategy takes hold, it is core to driving retention over time. And, while a lot of people perceive that the service organization jobs are boring, or just answering trouble tickets or reacting to client problems, that’s not the whole role. It is a strategic role as well.
The Chief Customer Officer has a big impact on the success of a company, especially startups and scaleups, and their function touches nearly every aspect of a company. To give your company the best chance of scaling, the Chief Customer Officer should understand, pinpoint, and manage misperceptions so that they can devote their time, energy, and resources to the real problems that help customers.
