This book was sitting in our office and people I've ran into quoted it or said "I read it and liked it"
I read it. I was however frustrated with it (due to the part it is a story). I'll explain how this book can be great and how not so great.
How this book is or can be great:
1. You haven't been a manager at all. It's a story of what you are diving into, the book describes the pitfalls you will run into.
2. You want to "explain" why teams do the things they do.
3. Throw some ideas out on how to help repair the problems it mentions (after the story)
4. Motivational tool for teams that are struggling, I can see the book getting people refocused.
5. It's easy to read, don't have to bang your head on terms.
Why it did not meet my expectations:
1. It was a story. A lot of us know the story of broken teams and most likely experienced it a few times in our lives which is why you have the book. It was like reading a book on Microsoft Vista where it tells you the story of the things you can do with Vista but doesn't tell you what to do until the end of the book.
"Jorrian started his computer excited that Windows Vista will turn on and show him a Desktop...but he was expecting trouble. While he was wondering how to get on to the Internet, he noticed an icon called Internet Explorer on the Desktop. His thinking was confidence. Jorrian clicked Internet Explorer and a program opened"
I wasn't expecting 184 pages of that.
2. The book assumes everyone knew their job description and acted on it 100%. All we needed to do was take 8 individuals that knew their job and acted on it 100% to work as a team. Definitely not realistic from what I've seen personally.
3. It wasn't a story on cold hard facts and "true story". If the entire 184 pages of story was on a real company with cold hard facts because of the principles in the book then I would have been 100% more engaged, as opposed to reading about a fictional management team. Reading at the end that "Decision Tech the fictional company caught up to their 2nd competitor and profit increased 20%" just wasn't convincing enough for me to [b]ACT [/b]on the book.
I could read a book on building a house, but if I am not personally compelled to build a house, doesn't mean I can build houses.
Sorry for making this so long, I didn't just want to write "This book is not recommended cause I didn't like it" or "I recommend this book to this type".
If anyone has used and acted on the model in this book because of the book, sharing your story would be fantastic!