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.
Wither the News? (Plus a Bonus Book Short)
It’s unusual that I blog about a book before I’ve actually finished it, but this one is too timely to pass up given today’s news about newspapers. The Cult of the Amateur: How Today’s Internet is Killing Our Culture, by Andrew Keen, at least the first 1/2 of it, is a pretty intense rant about how the Internet’s trend towards democratizing media and content production has a double dirty underbelly:
poor quality — “an endless digital forest of mediocrity,”
no checks and balances — “mainstream journalists and newspapers have the organization, financial muscle, and and credibility to gain access to sources and report the truth…professional journalists can go to jail for telling the truth” (or, I’d add, for libel)
So what’s today’s news about newspapers? Another massive circulation drop — 3.6% in the last six months. Newspaper readership across the country is at its lowest level since 1946, when the population was only 141 million, or less than half what it is today. The digital revolution is well underway. Print newspapers are declining asymptotically to zero.
Don’t get me wrong. I’m an Internet guy, and I love the democratization of media for many reasons. I also think it will ultimately force old media companies to be more efficient as individual institutions and as an industry in order to survive (not to mention more environmentally friendly). But Keen has good thoughts about quality and quantity that are interesting counterpoints to the revolution. I hope at least some newspapers survive, change their models and their cost structures, and start competing on content quality. The thought that everyone in the world will get their news ONLY from citizen journalists is scary.
I’m curious to see how the rest of the book turns out. I’ll reblog if it’s radically different from the themes expressed here.
Update (having finished the book now): Keen puts the mud in curmudgeon. He doesn’t appear to have a good word to say about the Internet, and he allows his very good points about journalistic integrity and content quality and our ability to discern the truth to get washed up in a rant against online gambling, porn, and piracy. Even some of his rant points are valid, but saying, for example, that Craigslist is problematic to society because it only employs 22 people and is hugely profitable while destroying jobs and revenue at newspapers just comes across as missing some critical thinking and basically just pissing in the wind. His final section on Solutions is less blustry and has a couple good examples and points to offer, but it’s a case of too little, too late for my liking.
Book Short: Wither the Team
I keep expecting one of his books to be repetitive or boring, but Patrick Lencioni’s The Five Dysfunctions of a Team held my interest all the way through, as did his others. It builds nicely on the last one I read, Death by Meeting (post, link).
I’d say that over the 9 1/2 years we’ve been in business at Return Path, we’ve systematically improved the quality of our management team. Sometimes that’s because we’ve added or changed people, but mostly it’s because we’ve been deliberate about improving the way in which we work together. This particular book has a nice framework for spotting troubles on a team, and it both reassured me that we have done a nice job stamping out at least three of the dysfunctions in the model and fired me up that we still have some work to do to completely stamp out the final two (we’ve identified them and made progress, but we’re not quite there yet.
The dysfunctions make much more sense in context, but they are (in descending order of importance):
- Absence of trust
- Fear of conflict (everyone plays politically nice)
- Lack of commitment (decisions don’t stick)
- Avoidance of accountability
- Inattention to results (individual ego vs. team success)
For those who are wondering, the two we’re still working on at the exec team level here are conflict and commitment. And the two are related. If you don’t produce engaged discussion about an issue and allow everyone to air their opinions, they will invariably be less bought into a decision (especially one they don’t agree with). But we’re getting there and will continue to work aggressively on it until we’ve rooted it out.
There’s one other interesting takeaway from the book that’s not part of the framework directly, which is that an executive has to be first and foremost a member of his/her team of peers, not the head of his/her department. That’s how successful teams get built. AND (this is key) this must trickle down in the organization as well. Everyone who manages a team of group heads or managers needs to make those people function well as a team first, then as managers of their own groups second.
At any rate, another quick gem of a book. I’m kind of sorry there’s only one left in the series.
So far the series includes:
I have one or two more to go, which I’ll tackle in due course and am looking forward to.
Book Short: On The Same Page
Being on the same page with your team, or your whole company for that matter, is a key to success in business. The Four Obsessions of an Extraordinary Executive, by Patrick Lencioni, espouses this notion and boils down the role of the CEO to four points:
- Build and maintain a cohesive leadership team
- Create organizational clarity
- Overcommunicate organizational clarity
- Reinforce organizational clarity through human systems
Those four points sound as boring as bread, but the book is anything but. The book’s style is easy and breezy — business fiction. One of the most poignant moments for me was when the book’s “other CEO” (the one that doesn’t “get it”) reflects that he “didn’t go into business to referee executive team meetings and delivery employee orientation…he loved strategy and competition.” Being a CEO is a dynamic job that changes tremendously as the organization grows. This book is a great handbook for anyone transitioning out of the startup phase, or for anyone managing a larger organization.
I haven’t read the author’s other books (this is one in a series), but I will soon!
What is the News, These Days?
I’ve about had it with the news about the financial mess these days. It’s not the news about what’s happening that bugs me — that’s at least mildly useful. It’s the pundits’ explanation of what’s driving the news that’s driving me nuts.
It’s hard to see how these headlines and lead sentences are even remotely accurate. It’s not as if all global traders and investors operate on a common set of guidelines, or even have access to all the same information at the same time. Yet we are now told day in, day out, that the market is doing well “because the government finally approved the bailout.” Or the market is doing poorly “because investors are worried the bailout isn’t enough” (yes, same reason).
And this is a gem from Friday: “Oil prices jumped above $72 a barrel Friday in Asia from a 14-month low as investors bet fears that a severe global recession will devastate crude demand may be overblown.” So this headline, to be clear if you study it, is saying that yesterday’s fears which drove the market down — we’re now afraid we were wrong. Yeesh.
Book Short: Choose Voice!
I took a couple days off last week and decided to re-read two old favorites. One –Ayn Rand’s The Fountainhead — my fourth reading — will take me a little longer to process and figure out if there’s a good intersection with the blog. One would think so with entrepreneurship as the topic, but my head still hurts from all the objectivism. The second — Exit, Voice, and Loyalty, by Albert O. Hirschman — is today’s topic.
I can’t remember when I first read Exit, Voice, and Loyalty. It was either in senior year of high school Economics or Government; or in freshman year of college Political Philosophy. Either way, it was a long time ago, and for some reason, some of the core messages of this quirkly little 125 page political/economic philosophy book have stayed with me over the years. I remembered the book incorrectly as a book about political systems, and I think it was born consciously in the wake of Eugene McCarthy’s somewhat revolutionary challenge to a sitting President Johnson for the Democratic Party nomination in 1968. But the book is actually about business; it’s just about businesses and their customers, not corporations as social structures (the latter being more of an interest to me). Written by an academic economist (I think), the book has its share of gratuitous demonstrative graphs, 2×2 matrices, and SAT words. But its central premise is a gem for anyone who runs an organization of any size.
The central premise is that there are really two paths by which one can express dissatisfaction with a temporary, curable lapse in an organization: exit (bailing), or voice (trying to fix what’s wrong from within). The third key element, Loyalty, is less a path in and of itself but more an agent that “holds exit at bay and activates voice.”
You need to read the book and apply it to your own circumstances to really get into it, but for me, it’s all about breeding loyalty as a means of making voice the path of least resistance, even when exit is a freely available option (few of us run totalitarian states or monopolies, after all). That to me is the definition of a successful enterprise, both internally and externally.
With your customers: make your product so irresistible, and make your customer service so deep, that your customers feel an obligation to help you fix what they perceive to be wrong with your product first, rather than simply complain about price or flee to a competitor.
With your employees: make your company the best possible place you can think of to work so that even in as ridiculously fluid a job market as we live in, your employees will come to their manager, their department head, the head of HR, or you as leader to tell you when they’re unhappy instead of just leaving, or worse, sulking.
With your company (you as employee): make yourself indispensible to the organization and do such a great job that if things go wrong with your performance or with your role, your manager’s loyalty to you leads him or her to give you open feedback and coach you to success rather than unceremoniously show you the door.
Ok, this wasn’t such a short book short — probably the longest I’ve ever written in this blog, and certainly the highest ratio of short:actual book. But if you’re up for a serious academic framework (quasi-business but not exclusively) to apply to your management techniques, this short 1970 book is as valid today as when it was written. Thanks to David Ramert (I am pretty sure I read it in high school) for introducing it to me way back when!
Book Short: Steve Jobs and Lessons for CEOs and Founders
First, if you work in the internet, grew up during the rise of the PC, or are an avid consumer of Apple products, read the Walter Isaacson biography of Steve Jobs (book, kindle). It’s long but well worth it.
I know much has been written about the subject and the book, so I won’t be long or formal, but here are the things that struck me from my perspective as a founder and CEO, many taken from specific passages from the book:
- In the annals of innovation, new ideas are only part of the equation. Execution is just as important. Man is that ever true. I’ve come up with some ideas over the years at Return Path, but hardly a majority or even a plurality of them. But I think of myself as innovative because I’ve led the organization to execute them. I also think innovation has as much to do with how work gets done as it does what work gets done.
- There were some upsides to Jobs’s demanding and wounding behavior. People who were not crushed ended up being stronger. They did better work, out of both fear and an eagerness to please. I guess that’s an upside. But only in a dysfunctional sort of way.
- When one reporter asked him immediately afterward why the (NeXT) machine was going to be so late, Jobs replied, “It’s not late. It’s five years ahead of its time.” Amen to that. Sometimes product deadlines are artificial and silly. There’s another great related quote (I forget where it’s from) that goes something like “The future is here…it’s just not evenly distributed yet.” New releases can be about delivering the future for the first time…or about distributing it more broadly.
- People who know what they’re talking about don’t need PowerPoint.” Amen. See Powerpointless.
- The mark of an innovative company is not only that it comes up with new ideas first, but also that it knows how to leapfrog when it finds itself behind. This is critical. You can’t always be first in everything. But ultimately, if you’re a good company, you can figure out how to recover when you’re not first. Exhibit A: Microsoft.
- In order to institutionalize the lessons that he and his team were learning, Jobs started an in-house center called Apple University. He hired Joel Podolny, who was dean of the Yale School of Management, to compile a series of case studies analyzing important decisions the company had made, including the switch to the Intel microprocessor and the decision to open the Apple Stores. Top executives spent time teaching the cases to new employees, so that the Apple style of decision making would be embedded in the culture. This is one of the most emotionally intelligent things Jobs did, if you just read his actions in the book and know nothing else. Love the style or hate it – teaching it to the company reinforces a strong and consistent culture.
- Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!’” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page. There’s always a tension between listening TO customers and innovating FOR them. Great companies have to do both, and know when to do which.
- What drove me? I think most creative people want to express appreciation for being able to take advantage of the work that’s been done by others before us. I didn’t invent the language or mathematics I use. I make little of my own food, none of my own clothes. Everything I do depends on other members of our species and the shoulders that we stand on. And a lot of us want to contribute something back to our species and to add something to the flow. It’s about trying to express something in the only way that most of us know how—because we can’t write Bob Dylan songs or Tom Stoppard plays. We try to use the talents we do have to express our deep feelings, to show our appreciation of all the contributions that came before us, and to add something to that flow. That’s what has driven me. This is perhaps one of the best explanations I’ve ever heard of how creativity can be applied to non-creative (e.g., most business) jobs. I love this.
My board member Scott Weiss wrote a great post about the book as well and drew his own CEO lessons from it – also worth a read here.
Appropos of that, both Scott and I found out about Steve Jobs’ death at a Return Path Board dinner. Fred broke the news when he saw it on his phone, and we had a moment of silence. It was about as good a group as you can expect to be with upon hearing the news that an industry pioneer and icon has left us. Here’s to you, Steve. You may or may not have been a management role model, but your pursuit of perfection worked out well for your customers, and most important, you certainly had as much of an impact on society as just about anyone in business (or maybe all walks of life) that I can think of.
Book Short: The Little Engine that Could
Authors Steven Woods and Alex Shootman would make Watty Piper proud. Instead of bringing toys to the children on the other side of the mountain, though, this engine brings revenue into your company. If you run a SaaS business, or really if you run any B2B business, Revenue Engine: Why Revenue Performance Management is the Next Frontier of Competitive Advantage, will change the way you think about Sales and Marketing. The authors, who were CTO and CRO of Eloqua (the largest SaaS player in the demand management software space that recently got acquired by Oracle), are thought leaders in the field, and the wisdom of the book reflects that.
The book chronicles the contemporary corporate buying process and shows that it has become increasingly like the consumer buying process in recent years. The Consumer Decision Journey, first published by McKinsey in 2009, chronicles this process and talks about how the traditional funnel has been transformed by the availability of information and social media on the Internet. Revenue Engine moves this concept to a B2B setting and examines how Marketing and Sales are no longer two separate departments, but stewards of a combined process that requires holistic analysis, investment decisions, and management attention.
In particular, the book does a good job of highlighting new stages in the buying process and the imperatives and metrics associated with getting this “new funnel” right. One that resonated particularly strongly with me was the importance of consistent and clean data, which is hard but critical! As my colleague Matt Spielman pointed out when we were discussing the book, the one area of the consumer journey that Revenue Engine leaves is out is Advocacy, which is essential for influencing the purchase process in a B2B environment as well.
One thing I didn’t love about the book is that it’s a little more theoretical than practical. There aren’t nearly enough detailed examples. In fact, the book itself says it’s “a framework, not an answer.” So you’ll be left wanting a bit more and needing to do a bit more work on your own to translate the wisdom to your reality, but you’ll have a great jumping off point.
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.
The Advantage: Why Organizational Health Trumps Everything Else In Business is Patrick Lencioni’s newest book. Unlike most or all of his other books (see the end of this post for the listing), this one is not a fable, although his writing style remains very quick and accessible.
I liked this book a lot. First, the beginning section is a bit of a recap of his Five Dysfunctions of a Team which I think was his best book. And the ending section is a recap of his Death by Meeting, another really good one. The middle sections of the book are just a great reminder of the basic building blocks of creating and communicating strategy and values – about driving alignment.
But the premise, as the subtitle indicates, is that maintaining organizational health is the most important thing you can do as a leader. I tell our team at Return Path all the time that our culture is a competitive advantage in many ways, some quantifiable, and others a little less tangible.
A telling point in the book is when Lencioni is relaying a conversation he had with the CEO of a client company who does run a healthy organization – he asked, “Why in the world don’t your competitors do any of this?” And the client responded, “You know, I honestly believe they think it’s beneath them.” Lencioni goes on to say, “In spite of its undeniable power, so many leaders struggle to embrace organizational health because they quietly believe they are too sophisticated, too busy, or too analytical to bother with it.” And there you have it. More examples of why “the soft stuff” is mission critical.
Lencioni’s “Recipe for Organizational Health” (the outline of the book):
– Build a Cohesive Leadership Team
– Create Clarity
– Overcommunicate Clarity
– Reinforce Clarity
And his recipe for creating a tight set of “mission/vision/values” (the middle of the book):
1. Why do we exist?
2. How do we behave?
3. What do we do?
4. How will we succeed?
5. What is most important, right now?
6. Who must do what?
While there are lots of other good frameworks for doing all of this, Lencioni’s models and books are great, simple reminders of one of the CEO’s most important leadership functions. We’re recrafting our own mission and values statements at the moment at Return Path, and we’re doing it using this 6-Question framework instead of the classic “Mission/Vision/Values” framework popularized a few years back by Harvard Business Review.
The full book series roundup as far as OnlyOnce has gotten so far is:
5 Ways to Get Your Staff on the Same Page
[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO: A Field Guide to Scaling Up Your Business]
When a major issue arises, is everybody at your company serving the same interests? Or is one person serving the engineering team, another person serving the sales team, one board member serving the VC fund, another serving the early-stage “angels” and another serving the CEO? If that’s the case, then your team is misaligned. No individual department’s interests are as important as the company’s.
To align everyone behind your company’s interests, you must first define and communicate those goals and needs. This requires five steps:
- Define the mission. Be clear to everyone about where you’re going and how you’re going to get there (in keeping with your values).
- Set annual priorities, goals, and targets. Turn the broader mission into something more concrete with prioritized goals and unambiguous success metrics.
- Encourage bottom-up planning. You and your executive team need to set the major strategic goals for the company, but team members should design their own path to contribution. Just be sure that you or their managers check in with them to assure that they remain in synch with the company’s goals.
- Facilitate the transparent flow of information and rigorous debate. To help people calibrate the success, or insufficiency, of their efforts, be transparent about how the organization is doing along the way. Your organization will make better decisions when everyone has what they need to have frank conversations and then make well-informed decisions.
- Ensure that compensation supports alignment (or at least doesn’t fight it). As selfless as you want your employees to be, they’ll always prioritize their interests over the company’s. If those interests are aligned – especially when it comes to compensation – this reality of human nature simply won’t be a problem.
Taken in sequence, these steps are the formula for alignment. But if I had to single out one as the most important, it would be number 5: aligning individual incentives with companywide goals.
It’s always great to hear people say that they’d do their jobs even if they weren’t paid to, but the reality of post-lottery-jackpot job retention rates suggests otherwise. You, and every member of your team, “work” for pay. Whatever the details of your compensation plan, it’s crucial that it aligns your entire team behind the company’s best interests.
Don’t reward marketers for hitting marketing milestones while rewarding engineers to hit product milestones and back office personnel to keep the infrastructure humming. Reward everybody when the company hits its milestones.
The results of this system can be extraordinary:
- Department goals are in alignment with overall company goals. “Hitting product goals” shouldn’t matter unless those goals serve the overall health of your company. When every member of your executive team – including your CTO – is rewarded for the latter, it’s much easier to set goals as a company. There are no competing priorities: the only priority is serving the annual goals.
- Individual success metrics are in alignment with overall company success metrics. The one place where all companies probably have alignment between corporate and departmental goals is in sales. The success metrics that your sales team uses can’t be that far off from your overall goals for the company. With a unified incentive plan, you can bring every department into the same degree of alignment. Imagine your general counsel asking for less extraneous legal review in order to cut costs
- Resource allocation serves the company, rather than individual silos. If a department with its own compensation plan hits its (unique) metrics early, members of that team have no incentive to pitch in elsewhere; their bonuses are secure. But if everyone’s incentive depends on the entire company’s performance, get ready to watch product leads offering to share developers, unprompted.
This approach can only be taken so far: I can’t imagine an incentive system that doesn’t reward salespeople for individual performance. And while everyone benefits when things go well, if your company misses its goals, nobody should have occasion to celebrate. Everybody gets dinged if the company doesn’t meet its goals, no matter how well they or their departments performed. It’s a tough pill to swallow, but it also important preventive medicine.