19 Nov Pick two of the dysfunctions that is described in the book, and reflect on the importance of a leader addressing each specific dysfunction Write about how you as a leader would address th
If you would like to help with the assignment contact me in chat. text book attached.
- Pick two of the dysfunctions that is described in the book, and reflect on the importance of a leader addressing each specific dysfunction.
- Write about how you as a leader would address these dysfunctions (using course material, and material in the textbook). What can leaders do to ensure these dysfunctions are regularly avoided and what can leaders do if they encounter this within the team?
Also by Patrick Lencioni
The Five Temptations of a CEO
The Four Obsessions of an Extraordinary Executive
Death by Meeting
Silos, Politics, and Turf Wars
Overcoming the Five Dysfunctions of a Team
The Five Dysfunctions of a Team
A LEADERSHIP FABLE
Copyright © 2002 by Patrick Lencioni. Published by Josscy-Bass
A Wiley Imprint 989 Market Street, San Francisco, CA 94103-1741 www.josseybass.com
No part of this publication may be reproduced, stored in a
retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400, fax 978-646-8600, or on the Web at www.copyright.com. Requests to the publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, 201-748-6011, fax 201-748-6008, or online at http://www.wiley.com/go/permissions.
Limit of Liability/Disclaimer of Warranty: While the
publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.
Readers should be aware that Internet Web sites offered as citations and/or sources for further information may have changed or disappeared between the time this was written and when it is read.
Jossey-Bass books and products are available through most
bookstores. To contact Jossey-Bass directly call our Customer Care Department within the U.S. at 800-956-7739, outside the U.S. at 317-572-3986, or fax 317-572-4002.
Jossey-Bass also publishes its books in a variety of
electronic formats. Some content that appears in print may not be available in electronic books.
Library of Congress Cataloging-in-Publication Data
Lencioni, Patrick, 1965- The five dysfunctions of a team: a
leadership fable / Patrick Lencioni. p. cm. ISBN 978-0-7879-6075-9 1. Teams in the workplace. I. Title. HD66 .L456 2002 658.4’036—dc21 2001008099 FIRST EDITION
HB Printing 20 19 18
Luck Part One: Underachievement Part Two: Lighting the Fire Part Three: Heavy Lifting Part Four: Traction
An Overview of the Model Team Assessment Understanding and Overcoming the Five
A Note About Time: Kathryn’s Methods A Special Tribute to Teamwork Acknowledgments About the Author
To Dad, for teaching me the value of work.
And to Mom, for encouraging me to write.
Not finance. Not strategy. Not technology. It is teamwork that remains the ultimate competitive advantage, both because it is so powerful and so rare.
A friend of mine, the founder of a company that grew to a billion dollars in annual revenue, best expressed the power of teamwork when he once told me, “If you could get all the people in an organization rowing in the same direction, you could dominate any industry, in any market, against any competition, at any time.”
Whenever I repeat that adage to a group of leaders, they immediately nod their heads, but in a desperate sort of way. They seem to grasp the truth of it while simultaneously surrendering to the impossibility of actually making it happen.
And that is where the rarity of teamwork comes into play. For all the attention that it has received over the years from scholars, coaches, teachers, and the media, teamwork is as elusive as it has ever been within most organizations. The fact remains that teams, because they are made up of imperfect human beings, are inherently dysfunctional.
But that is not to say that teamwork is doomed. Far from it. In fact, building a strong team is both possible and remarkably simple. But it is painfully difficult.
That’s right. Like so many other aspects of life, teamwork comes down to mastering a set of behaviors that are at once theoretically uncomplicated, but extremely difficult to put into practice day after day. Success comes only for those groups that overcome the all-too-human behavioral
tendencies that corrupt teams and breed dysfunctional politics within them.
As it turns out, these principles apply to more than just teamwork. In fact, I stumbled upon them somewhat by accident in my pursuit of a theory about leadership.
A few years ago I wrote my first book, The Five
Temptations of a CEO, about the behavioral pitfalls that plague leaders. In the course of working with my clients, I began to notice that some of them were “misusing” my theories in an effort to assess and improve the performance of their leadership teams—and with success!
And so it became apparent to me that the five temptations applied not only to individual leaders but, with a few modifications, to groups as well. And not just within corporations. Clergy, coaches, teachers, and others found that these principles applied in their worlds as much as they did in the executive suite of a multinational company. And that is how this book came to be.
Like my other books, The Five Dysfunctions of a Team
begins with a story written in the context of a realistic but fictional organization. I have found that this allows readers to learn more effectively by losing themselves in a story and by being able to relate to the characters. It also helps them understand how these principles can be applied in a nontheoretical, real-world environment, where the pace of work and the volume of daily distractions make even the simplest of tasks seem arduous.
In order to help you apply the material in your own organization, a brief section following the story outlines the five dysfunctions in detail. That section also includes a team assessment and suggested tools for overcoming the issues that might be plaguing your team.
Finally, although this book is based on my work with CEOs and their executive teams, its theories are applicable for anyone interested in teamwork, whether you lead a small department within a company or are simply a member of a team that could use some improvement. Whatever the case may be, I
sincerely hope it helps your team overcome its particular dysfunctions so that it can achieve more than individuals could ever imagine doing alone. That, after all, is the real power of teamwork.
Only one person thought Kathryn was the right choice to become CEO of DecisionTech, Inc. Luckily for her, that person was the Chairman of the board.
And so, less than a month after the previous chief executive had been removed, Kathryn Petersen took the reins of a company that just two years earlier had been one of the most talked-about, well-funded, and promising start-up companies in the recent history of the Silicon Valley. She could not have known just how far from grace the company had fallen in such a short period of time, and what the next few months had in store for her.
DecisionTech was located in Half Moon Bay, a foggy,
coastal farming town just over the hills from the San Francisco Bay. It was not technically part of the Silicon Valley, but the Valley is not so much a geographical entity as a cultural one. And DecisionTech certainly fit within that world.
It had the most experienced—and expensive—executive team imaginable, a seemingly indestructible business plan, and more top-tier investors than any young company could hope for. Even the most cautious venture firms were lining up to invest, and talented engineers were submitting their resumés before the company had leased an office.
But that was almost two years earlier, which is a life- time for a technology start-up. After its first few euphoric months of existence, the company began experiencing a series of ongoing disappointments. Critical deadlines started to slip. A few key employees below the executive level unexpectedly left the company. Morale deteriorated gradually. All of this in spite of the considerable advantages that DecisionTech had amassed for itself.
On the two-year anniversary of the firm’s founding, the board unanimously agreed to “ask” Jeff Shanley, the com pany’s thirty-seven-year-old CEO and cofounder, to step down. He was offered the job of heading business development, and to the surprise of his colleagues, he accepted the demotion, not wanting to walk away from a potentially huge payout should the company eventually go public. And even in
the difficult economic climate of the Valley, the company had every reason to go public.
None of DecisionTech’s 150 employees were shocked by Jeff’s removal. While most of them seemed to like him well enough personally, they couldn’t deny that under his leadership the atmosphere within the company had become increasingly troubling. Backstabbing among the executives had become an art. There was no sense of unity or camaraderie on the team, which translated into a muted level of commitment. Everything seemed to take too long to get done, and even then it never felt right.
Some boards might have been more patient with a stumbling executive team. DecisionTech’s was not. There was just too much at stake—and too high a profile—to watch the company waste away because of politics. DecisionTech had already developed a reputation within the Valley for being one of the most political and unpleasant places to work, and the board couldn’t tolerate that kind of press, especially when the future had looked so promising just a couple of years earlier.
Someone had to be accountable for the mess, and Jeff was the man at the top. Everyone seemed relieved when the board announced the decision to remove him.
Until three weeks later, when Kathryn was hired.
The executives couldn’t agree on which of Kathryn’s features presented the biggest problem. There were so many.
First, she was old. Ancient, at least by Silicon Valley standards. Kathryn was fifty-seven.
More important, she had no real high-tech experience other than serving as a board member of Trinity Systems, a large technology company in San Francisco. Most of her career had been spent in operational roles with decidedly low-tech companies, the most notable of which was an automobile manufacturer.
But more than her age or experience, Kathryn just didn’t seem to fit the DecisionTech culture.
She had started her career in the military, then married a teacher and basketball coach at a local high school. After raising three boys, she taught seventh grade for a few years until she discovered her affinity for business.
At the age of thirty-seven, Kathryn enrolled in a three- year business school night program, which she completed a semester early at Cal State Hayward, which was not exactly Harvard or Stanford. She then spent the next fifteen years in and around manufacturing, until her retirement at the age of fifty-four.
The fact that Kathryn was a woman was never an issue for the executive team; two of them were women themselves. With much of their collective experience coming from the somewhat progressive world of high tech, most had worked for women at some time during their careers. But even if her gender had
been a problem for anyone on the team, it would have been dwarfed by her glaring cultural mismatch.
There was just no mistaking the fact that, on paper, Kathryn was an old school, blue-collarish executive. That presented a stark contrast to the DecisionTech executives and middle managers, most of whom had little experience working outside of the Valley. Some of them even liked to brag that they hadn’t worn a suit—outside of a wedding—since graduating from college.
It was no surprise that after first reading her resume, board members questioned the Chairman’s sanity when he suggested they hire Kathryn. But he eventually wore them down.
For one, the board believed their Chairman when he flat out assured them that Kathryn would succeed. Second, he had been known to have extremely good instincts about people, notwithstanding the problem with Jeff. He certainly wouldn’t make two mistakes in a row, they reasoned.
But perhaps most important of all (though no one would admit it), DecisionTech was in a desperate situation. The Chairman insisted that there weren’t too many capable executives willing to take on such a messy job given the current state of affairs at the scarred company. “We should consider ourselves lucky to have such a capable leader as Kathryn available,” he successfully argued.
Whether or not that was true, the Chairman was determined to hire someone he knew and could trust. When he called Kathryn to tell her about the job, he certainly could not have known that he would be regretting the decision just a few weeks later.
No one was more surprised about the offer than Kathryn. Although she had known the Chairman for many years on a personal level (Kathryn had actually first met him when her husband coached his oldest son in high school), she could not have imagined that he thought so highly of her as an executive.
Most of their relationship had been social, centering around family, school, and local athletics. Kathryn assumed that the Chairman had little idea about her life outside her role as a mother and coach’s wife.
In fact, the Chairman had followed Kathryn’s career with interest over the years, amazed at how successful she had become with such relatively modest training. In less than five years, she had become chief operating officer of the Bay Area’s only automobile manufacturing plant, a U.S.Japanese joint venture. She held that job for the better part of a decade and made the plant one of the most successful cooperative enterprises in the country. And while the Chairman knew little about the car industry, he knew one thing about Kathryn that convinced him she was perfect to fix the problems at DecisionTech.
She had an amazing gift for building teams.
If the executives at DecisionTech had any doubts about Kathryn when her hiring was first announced—and they did— they were even more concerned after their new leader’s first two weeks on the job.
It wasn’t that Kathryn did anything controversial or misplaced. It was that she did almost nothing at all.
Aside from a brief reception on her first day and subsequent interviews with each of her direct reports, Kathryn spent almost all of her time walking the halls, chatting with staff members, and silently observing as many meetings as she could find time to attend. And perhaps most controversial of all, she actually asked Jeff Shanley to continue leading the weekly executive staff meetings, where she just listened and took notes.
The only real action that Kathryn took during those first weeks was to announce a series of two-day executive retreats in the Napa Valley to be held over the course of the next few months. As though she needed to give them any more ammunition, none of her reports could believe she had the gall to take them out of the office for so many days when there was so much real work to be done.
And to make matters worse, when someone suggested a specific topic for discussion during the first retreat, Kathryn refused. She had her own agenda already set.
Even the Chairman was surprised, and a bit unnerved, about the reports of Kathryn’s early performance. He came to the conclusion that if she didn’t work out, he should probably
leave along with her. That was beginning to feel like the most probable outcome.
After her first two weeks observing the problems at
DecisionTech, Kathryn had more than a few moments when she wondered if she should have taken the job. But she knew that there was little chance that she would have turned it down. Retirement had made her antsy, and nothing excited her more than a challenge.
While there was no doubt that DecisionTech would be a challenge, something seemed different about this one. Though she had never really feared failure, Kathryn could not deny that the prospect of letting the Chairman down spooked her a little. To tarnish her reputation so late in her career, and among friends and family, was enough to worry even the most secure of people. And Kathryn was certainly secure with herself.
After surviving a stint in the military, raising her boys, watching countless buzzer-beating basketball games, and standing up to union bosses, Kathryn decided she was not about to be intimidated by a bunch of harmless yuppies whose greatest hardships in life so far had been fighting off the first signs of a receding hairline or an expanding waistline. She believed that as long as the board would give her enough time and leeway, she would be able to turn DecisionTech around.
And Kathryn’s lack of in-depth software experience did not concern her. In fact, she felt certain that it provided her with an advantage. Most of her staff seemed almost paralyzed by their own knowledge of technology, as though
they themselves would have to do the programming and product design to make the company fly.
Kathryn knew that Jack Welch didn’t have to be an expert on toaster manufacturing to make General Electric a success and that Herb Kelleher didn’t have to spend a life-time flying airplanes to build Southwest Airlines. Despite what her limited technical background might have indicated, Kathryn felt that her understanding of enterprise software and technology was more than sufficient for her to lead DecisionTech out of the mess it was in.
What she could not have known when she accepted the job, however, was just how dysfunctional her executive team was, and how they would challenge her in ways that no one before had ever done.
Employees referred to the DecisionTech executives as The
Staff. No one referred to them as a team, which Kathryn decided was no accident.
In spite of their undeniable intelligence and impressive educational backgrounds, The Staff’s behavior during meetings was worse than anything she had seen in the automotive world. Though open hostility was never really apparent and no one ever seemed to argue, an underlying tension was undeniable. As a result, decisions never seemed to get made; discussions were slow and uninteresting, with few real exchanges; and everyone seemed to be desperately waiting for each meeting to end.
And yet, as bad as the team was, they all seemed like well-intentioned and reasonable people when considered individually. With just a few exceptions.
JEFF—FORMER CEO, BUSINESS DEVELOPMENT Essentially a generalist who loved networking within the
Valley, Jeff Shanley had raised a considerable amount of the company’s initial money and attracted many of the current executives. No one could deny his prowess when it came to venture capital or recruiting. But management was another story.
Jeff ran staff meetings as though he were a student body president reading from a textbook on protocol. He always published an agenda before each meeting, and then distributed
detailed minutes afterward. And unlike most other high-tech companies, his meetings usually began on time and always concluded exactly when they were scheduled to end. The fact that nothing ever seemed to get done during those meetings didn’t appear to bother him.
In spite of his demotion, Jeff maintained his seat on the board of directors. Kathryn initially suspected that he might resent her for taking his job, but she soon came to the conclusion that Jeff was relieved to be, well, relieved of his management responsibilities. Kathryn had little concern about his presence on the board, or on her management team. She suspected that his heart was in the right place.
MIKEY—MARKETING Marketing would be a critical function at DecisionTech,
and the board had been ecstatic to get someone as sought after as Michele Bebe. Mikey, as she liked to be called, was well known throughout the Valley as a brand-building genius. Which made it all the more astonishing that she lacked a few key social graces.
During meetings, she talked more than the others, occasionally coming up with a brilliant idea, but more often complaining about how the other companies she had worked for did everything better than DecisionTech. It was almost as though she were a spectator or, better yet, a victim of circumstance, at her new company. Though she never argued outright with any of her peers, she was known to roll her eyes in apparent disgust when one of them disagreed with anything she had to say about marketing. Kathryn decided that Mikey was unaware of how she came across to others. No one would purposefully act that way, she reasoned.
So in spite of her talent and accomplishments, it was no surprise to Kathiyn that Mikey was the least popular among the rest of the staff. With the possible exception of Martin.
MARTIN—CHIEF TECHNOLOGIST A founder of the company, Martin Gilmore was the closest
thing that DecisionTech had to an inventor. He had designed the original specs for the company’s flagship product, and although others had done much of the actual product development, the executives often said that Martin was the keeper of the crown jewels. That analogy was due at least in part to the fact that Martin was British.
Martin considered himself to know as much about technology as anyone else in the Valley, which was probably true. With advanced degrees from Berkeley and Cambridge, and a track record of success as a chief architect at two other technology companies, he was seen as DecisionTech’s key competitive advantage, at least when it came to human capital.
Unlike Mikey, Martin didn’t disrupt staff meetings. In fact, he rarely participated. It wasn’t that he refused to attend those meetings (even Jeff wouldn’t allow such a blatant act of revolt); it was just that he always had his laptop open, and he seemed to be constantly checking e-mail or doing something similarly engrossing. Only when someone made a factually incorrect statement could Martin be counted on to offer a comment, and usually a sarcastic one at that.
At first, this was tolerable, maybe even amusing, to Martin’s peers, who seemed in awe of his intellect. But it began to wear on the staff over time. And with the company’s recent struggles, it had become an increasingly grating source of frustration for many of them.
JR—SALES In order to avoid confusing him with Jeff Shanley,
everyone called the head of sales JR. His real name was Jeff Rawlins, but he seemed to enjoy the new moniker. JR was an experienced salesperson and a little older than the others— mid-forties. He was usually tan, never rude, and always agreed to do whatever the staff asked of him.
Unfortunately, JR rarely followed through. In those cases when he came clean and acknowledged having made a commitment that went unfulfilled, he apologized profusely to whomever he had let down.
In spite of what the staff called JR’s flakiness, he was able to maintain a measure of respect from his peers because of his track record. Before coming to DecisionTech, he had never missed a quarterly revenue number in his entire career in sales.
CARLOS—CUSTOMER SUPPORT Though DecisionTech had relatively few customers, the
board felt strongly that the company would need to invest early in customer service in order to prepare for growth. Carlos Amador had worked with Mikey at two previous companies, and she introduced him to the firm. Which was ironic because the two of them couldn’t have been more different.
Carlos spoke very little, but whenever he did, he had something important and constructive to say. He listened intently during meetings, worked long hours with no complaint, and downplayed his prior accomplishments whenever someone asked about them. If there was a low-maintenance member of the staff, and a trustworthy one, it was Carlos.
Kathryn was thankful not to have to worry about at least one of her new direct reports, although she was somewhat troubled that his specific role had not yet fully developed. The fact that he willingly took on responsibility for product quality and any other unattractive duties that fell through the gaps allowed her to focus on more pressing concerns.
JAN—CHIEF FINANCIAL OFFICER The role of the chief financial officer had been a
critical one at DecisionTech and would continue to be as long as the company intended to go public. Jan Mersino knew what
she was getting into when she joined the company, and she had played a key role supporting Jeff as he raised impressive amounts of money from venture capitalists and other investors.
Jan was a stickler for detail, took pride in her knowledge of the industry, and treated the company’s money as though it were her own. While the board had given Jeff and the staff virtual free rein when it came to expenditures, they did so only because they knew that Jan would not let things get out of control.
NICK—CHIEF OPERATING OFFICER The final member of the executive staff was the most
impressive on paper. Nick Farrell had been vice president of field operations for a large computer manufacturer in the Midwest, and had moved his family to California to take the DecisionTech job. Unfortunately for him, he had the most ill- defined role of anyone on the team.
Nick was officially the chief operating officer of the company, but that was only because he had demanded the COO title as a condition of accepting the job. Jeff and the board gave it to him because they believed he would earn it within the year anyway if he perform