Skip to content

Commit b0d646f

Browse files
author
Matt Swanson
committed
add five dysfunctions writeup, closes swanson#13
1 parent 565b03a commit b0d646f

File tree

2 files changed

+46
-0
lines changed

2 files changed

+46
-0
lines changed

Diff for: _posts/2012-10-23-the-five-dysfunctions-of-a-team.md

+46
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
layout: writeup
3+
title: "The Five Dysfunctions of a Team"
4+
categories:
5+
- writeup
6+
---
7+
8+
9+
![](/static/five-dysfunctions.jpg)
10+
[The Five Dysfunctions of a Team: A Leadership Fable][link]
11+
Patrick Lencioni
12+
ISBN: 0787960756
13+
14+
---
15+
16+
**What's the point?**
17+
There are five dysfunctions that plague workplace teams. A good team leader will identify
18+
how the dysfunctions are manifesting in their team and take action to overcome them.
19+
20+
**How was it?**
21+
The book uses an interesting format — a fiction company has hired a new CEO and
22+
we see meetings and interactions from her perspective as she tries to improve her
23+
executive team. The concept was new to me and helped to make the dysfunctions more
24+
concrete and the interactions more authentic.
25+
26+
I found the second dysfunction — fear of conflict — to be the most
27+
eye-opening. When a team lacks trust (the first dysfunction), people don't feel like they
28+
can provide open criticism and have objective debates. Instead, you end up with stupid
29+
office politics and you start holding grudges against your team members.
30+
31+
All the dysfunctions chain together nicely; the book uses a pyramid structure, which is
32+
appropriate. A team that fears conflict will never get buy-in from everyone because
33+
without an opportunity to voice their opinions, the team's vision will never be
34+
aligned. Without a collective direction, the team will fail to commit (the third
35+
dysfunction) and waste time waffling and revisiting decisions over and over again.
36+
37+
One of my takeaways was to spend less time worrying about personal career advancement and
38+
to try focusing on helping a team succeed.
39+
40+
**Who should read it?**
41+
It's a quick read and good for those working on teams that you don't feel tight-knit;
42+
while the fictional company does make software, a development background is not required
43+
to read this one.
44+
45+
[link]: http://www.amazon.com/Five-Dysfunctions-Team-Leadership-Fable/dp/0787960756
46+

Diff for: static/five-dysfunctions.jpg

12.6 KB
Loading

0 commit comments

Comments
 (0)