My book log
Even now, in this time of abundance of free blog posts, Internet articles, TED talks, and screencasts, I still love reading books. This is where I get a lot of ideas from. To keep track of what I read for myself, and to potentially help others choose a good book to read next, I maintain this list.
Very entertaining and pretty light, but also insightful. It is called a “Fable”, meaning it is an invented story rather than a non-fiction book. Tells us about a business turning around because the new CEO gets the top management to trust each other and work together more effectively. Pretty good. Have a look at this video to get an impression.
I like this book very much, and I recommend it to anybody who is even remotely involved with people management. Its quintessence is that every person is unique, and that you should capitalize on this uniqueness instead of trying to make everybody the same. “Don’t try to put in what was left out. Take out what was left in. That is hard enough.”
The book offers a lot of valuable advice and useful ways of looking at things, like:
- The distinction between talents (which you won’t be able to change much in a person), skills, and knowledge (the latter two you can change).
- Twelve questions to measure the quality of a workplace.
- A good manager acts as a catalyst that turns the unique combination of his employees’ talents into performance for his organization.
- You cannot study excellence by studying bad performance and inverting your conclusions.
- You should spend the most time with your best people.
- And many more…
So much has been written about this legendary book that will try to keep it short. Most importantly: I loved it from the start. Especially the sections about quality, team dynamics, motivation, and brain time vs. body time are absolutely world-class. Others are, by now, slightly outdated, and can be skimmed over. All in all, a must-read.
Interesting and partly entertaining, with a lot of gripping and fascinating real-life anecdotes. Buckingham tries to give “the one, controlling insight” into management (capitalize on the uniqueness of each person), leadership (capitalize on what is common to all your people), and sustained individual success (identify what you do not love doing and stop doing it).
I enjoyed it, but I would not consider it essential reading. It is a good addition to “First, Break All The Rules” (if you choose one of the two, choose that one), and most he writes about management has already been covered there. Here, he goes deeper into the distinction between management and leadership, and I think he does a very good job in doing that. The chapters on sustained individual success are a nice bonus on top.
A high-density gem full of practical, actionable advice. Andrew Grove, long-time president of Intel, draws from decades of intense experience and shares both practices that work and that don’t work with us. There is little theory, and virtually every paragraph bursts with useful thoughts that are, for the most part, directly applicable in everyday working life. An engineer by training, Grove knew how to keep his explanations short and to the point.
Topics covered include work organization, performance reviews, motivation of employees, salary, effective meetings, and several more. It is like a “manager’s manual of everything” in condensed form. Highly valuable. Whether you are a newly promoted manager, or you have ten years of management experience: I bet that you will get a lot out of that book.
An often-cited book in the world of managers and team leads. Introduces the terminology of Autonomy, Mastery, and Purpose, which are essential to unleash the intrinsic motivation of employees. Definitely worth a read if you want to know more about motivation. It’s also rather short, so not a huge time investment. I liked especially the part on experiments showing that rewards can be detrimental to intrinsic motivation, and the chapter on mastery and flow. This book made me want to read Flow by Mihaly Csikszentmihalyi.
Contains a lot of techniques, habits, and strategies how engineers and engineering managers can increase their impact and be more effective. Lau, who worked at Google and several startups, is a good writer and knows what he is talking about. He delivers a large collection of real-world stories that underline his points, partly lived through by himself, partly by senior engineers at Facebook, Instagram, and others.
The guiding principle of the book is leverage, a concept that also occurs in High Output Management. Continuous learning is a high-leverage activity, as is investing in iteration speed. Personally, I liked the sections on prioritization and on minimizing your operational burden very much, because these are things that are, I think, often neglected.
A remarkable book by Steven Pressfield about creativity as hard work, about the inner resistance that everybody feels in their life, and about what it means to be a professional. It is like a collection of mantras, or like a creative’s confession, that can help you grow your determination to break free and follow your creative destiny. If you know you were meant for more than you are currently doing, but you keep avoiding getting started with something, this book might be for you. The one thing that I took away from this book is that even people we perceive as successful geniuses might feel miserable and scared when they sit down to do their work, or when they are about to go on stage. They do it anyway, and that is why they ultimately succeed. This is what I remind myself of when I am unsure if I will be able to come up with a reasonably interesting blog post this week. Don’t wait for inspiration. Sit down and do the work.
A book about principled negotiation, which teaches us how we can, in a negotiation, be hard on the substance, but soft on the people on the other side. While it was published already in the 80s, the principles still hold: Separate the people from the actual problem, identify the underlying interests behind the positions, develop a diverse set of options, and, maybe most importantly, invest in developing your BATNA (Best Alternative to a Negotiated Agreement) so you know when to walk away from a stalled negotiation. If you do a lot of negotiating, you should probably give this book a try.
Ben Horowitz emphasizes several times how much he adores Andy Grove and his management classic “High Output Management” (he even wrote the foreword for the current edition). When reading “The Hard Thing About Hard Things”, I thought a couple of times: “This is the High Output Management” of our time”. There is no fluff about it. Instead, it offers practical advice for common real-life situations and problems you face in management, like how to promote or fire somebody, how to give feedback, how to minimize office politics, how to think about organizational and process design, how to deal with departments who don’t get along, and many more.
Moreover, it is densely packed with breathtaking, fascinating, and educative anecdotes from Horowitz’ event-rich tenures as CEO of Loudcloud and Opsware, of his time at Netscape, and his experiences as a venture capitalist. Most of the book is written from the perspective of CEOs, but it is useful for anybody who has to do with management.
Some sections of the book, like Peacetime CEO, Wartime CEO or Why Startups Should Train Their People are available on Horowitz’ blog. I still recommend reading the book, it’s just damn good.
A long book, obviously, but with many entertaining and enlightening anecdotes and a lot of insights on leadership, focus, and strategy. It is stunning to read testimonials of early Apple employees who assure that they consider themselves very lucky to have worked for Jobs, even though he bullied, insulted, and terrorized his employees on a regular basis. That’s the power of vision and purpose. I would not call it a must-read, but it is certainly a powerful lesson of how to think big and get things done.
Having seen my share of “slackless” organizations, I was really looking forward to this book, and I was not disappointed. On merely 200 rather short pages, it contains a lot of wisdom on organizational dysfunction, blind hurrying, and overtime that does more harm than good. I wrote some blog posts on what were to me the most useful insights from this book: That busyness is not a virtue and can do harm, that the white space in an org chart plays an important role, and what the must-haves are for substantial organizational change. Absolutely recommended book!
This book has received a lot of praise, and justly so. I consider it required reading if you are in some “people-related” role, be it a middle manager, or a member of an HR team. The book is full of valuable quantified insights gained by Google’s People Operations team. The scale at which Google operates enables this team to run studies and experiments that most academic psychology departments should probably be jealous of.
Most relevant and interesting to me were the chapters on recruiting (especially the predictive power of certain methods like unstructured interview, structured interview, work sample test, etc.), salaries (performance in knowledge work follows a power law, not a normal distribution), training, and nudging people to do the right thing.
Great book about how to approach and behave in important conversations, so that you are at your best communication behaviour when it matters the most. Some passages and techniques reminded me a bit of “Getting to Yes” (invent mutual purpose, separate the strategy from the goal, invent new options, etc.). If I had to choose between the two, I would choose Crucial Conversations because I think it is more focused.
The book teaches you to observe conversations for a lack of safety, and for people going to silence or violence. You will learn to look behind aggressive communication patterns, and get to know ways to defuse tense situations. I found the “Master My Stories” part especially useful, where you learn that between some action and your emotional response, there is something else, and this something is the story you tell yourself in your own head about what happened and why. Sounded very true to me out of my own experience :-)
The authors shoot a lot of acronyms at you like STATE, AMPP, CRIB, and repeat them until they haunt you in your dreams, but most of them actually make sense, and it can help remembering certain techniques. The numerous dialogs (some real-world, some made up) make things easy to follow and illustrate the practicality of the techniques.
Why would someone who uses a Dell computer easily switch to HP, while an Apple user is fiercely loyal to her brand? Because people don’t buy WHAT you do, they buy WHY you do it. Their choosing Apple is not about Apple, it’s about them. Apple’s WHY, the reason they exist, is challenging the status quo, and people who share that WHY will be drawn towards Apple products again and again.
Simon Sinek draws an interesting connection between neurobiology and the choices we make: Decisions are made in the part of the brain that is responsible for emotions, but not for language. Therefore, in order to generate loyalty and repeatable, long-term success, this part of the brain is what companies should target. They can do this by sending a very clear message of what they are about. If you do not have a clear, consistent WHY, then you will be a commodity: Exchangeable, arbitrary, competing on features, price, and promotions.
Interesting read with some convincing reasoning. Has become something like a classic already. I think it oversimplifies things a little here and there, but since the basic idea has quite some truth to it, I would definitely recommend it.
Marcus Blankenship shares with us some valuable insights from his vast experience both as a developer and a manager of developers. Seven habits that can ruin your technical team are illustrated through anecdotes that actually happened, and that clearly show the detrimental effects.
One of the habits is withholding feedback “until the time is right”, another one is forgetting how hard writing good code is. Personally I liked chapter 3 best: “Fixing other people’s mistakes”. I think this is one of the less obvious ones, and Marcus does a great job showing exactly how this bad habit can start a downward spiral. It also happens to be one that I have witnessed myself, and probably not for the last time.
The book is a short read, around 50 pages, and gives great guidance for novice team leads as well as great real-world cases to compare for more experienced managers.