It is one of those compact books that are quite effective. Other books are a bit heavy and you almost feel like you have to memorize flow charts. This book is fairly formulaic, but with easy to remember formulas. A lot of the book may seem a little too soft/touchy, but fortunately when I read it I was reading other books that go into the details of the psychology behind communications (which this one doesn't), and there is a lot to back up the advice in the book.
Mind you, if this isn't your default style of communication, it will take a lot of practice (and perhaps years) to get there. I think for me it was about a year of trying before my first successful use of it in a hostile conversation. It's hard to stick to trying something if you don't see signs of success inside of a year.
I suggest folks read some good books on conversations and negotiations.
Bargaining For Advantage:
Getting To Yes:
Getting Past No (billed as a negotiations book, but really more of a conversations book):
I strongly recommend reading Influence before you read these - much of what is in the books above will make more sense once you've read Influence.
When you read these, keep in mind: Change is hard. Don't expect to read these and become good communicators quickly. It may take a few years of stumbling and practice.
I see a mixture of comments agreeing and disagreeing with the original submission. For those who disagree: Most of what the author is saying is in agreement with what the books say:
If your goal is to change someone, you will either fail, or will succeed at the cost of the relationship (and relationships at work do matter).
Another important related point: If you cannot summarize why the other person is acting this way without using phrases like "stubborn", "irrational" or similar negatives, then it means you have no idea about the other person's concerns and motives, and are being lazy. It is easier to label, and much harder to probe effectively. Additionally, people often act stubborn because they realize you are not really interested in their perspective. Internally their thought process (which is very rational) is "This person does not really want to hear me out, so I'm not going to invoke too many neurons engaging with him and will just dig in my heels." - which is why a lot of books focus a lot on listening skills (which includes skills to signal that you are listening - you may in reality be listening just fine but the other person does not know it - so you signal it by summarizing their stance).
A lot of the comments here are invoking false dichotomies. Since HN has a comment limit, I'll address some here:
>I don't believe you can have a successful software team with individuals who can't take a code review well.
This is tangential. You can give feedback in a code review poorly, or efficiently. Both ways allow for you to point out problems with the other's code. One way will not be taken well. The other way has a higher chance of being taken well. A big step forward is to realize you can have your cake and eat it too.
>I started to try and reason with people with carefully crafted questions to guide them towards my goal.
Leading questions is a bad idea (all the communications books say it). Learn how to state your concerns. It is OK to ask questions if genuinely curious. But if you want to point something out, learn how to state it in a non-defensive manner.
(3 separate comments below):
>If Kara's emotions and defensiveness can't handle a clearly articulated, rational, objective argument against design decisions, then for the sake of the product and the company, she probably needs to find another job. Avoiding discussions doesn't work for me.
>Learned to let go and he has his parts of the code base and I have mine.
>And this is how you end up with a terrible, in-cohesive product.
Again, false dichotomies. The solution is not to be quiet and let it go. The solution is to learn how to talk about the issues effectively. One of the books calls this "The Fool's Choice" - thinking that either you have to be quiet and not air your concerns (to save relationships), or that you have to air them and damage the relationship.
>It's either you convince them, or perhaps they convince you. Logic wins.
Logic alone rarely wins. One key point in one of the books: Don't pretend that emotions should not be part of the decision making process. The reality is that emotions are already part of the decision making process. If you get angry that someone cannot take your feedback well, emotions are present.
>It's safe to assume Kara wrote this article.
It is safe to assume that the author of this comment is unwilling to question his views on the topic.
That's what assumptions get you.
>I have seen more technical damage done by nice and competent people deferring to bullies in the workplace than by legitimate disagreements expressed passionately.
Another false dichotomy. What the submission describes is normal among non-bullies.
>The flaw here is that you assume that "Kara" will learn from her mistakes. Not always the case.
It is a similar flaw to assume that merely telling her what mistakes she made will make her learn from them. Definitely often not the case.
I mean, I solved more complex technical problems in my undergrad than I've ever had to in my career.
My suggestion: While you may want to master a technical skill or two, become good at what they don't teach you:
The Coursera course from the University of Michigan is decent, if you don't want to read. But the other course (from Yale?) - I would not recommend that as a starter.
(His work is often cited in other books - especially related to negotiations).
Finally, a word of advice. Most of us here on HN have no trouble reading stuff and grasping its content. Internalizing it, though, will take work. So don't run away reading all these books. Pick one topic (e.g. negotiation), and read up on it. Take notes (I forget 80% of what I've read after a few months). And try to practice it.
Life is a marathon, not a sprint. Just focus on one till you feel you are good at it (perhaps for a year). Then pick another topic.
Being "political" in this sense is a codependent behavior.
Instead of operating out of fear of others' reactions, I prefer to give people the space they need to feel their anger, embarrassment, etc. by checking in with them over how they feel & empathizing with them.
I'll also agree with OP that approaching people 1-on-1 about big changes is much easier than putting someone on the spot to be open about & own their emotions in front of a group of people. The group's likely been trained to "act professional" by hiding their emotions as opposed to being professional by producing quality work. Sadly, that's not the sort of culture typically found in a business.
The last engineer I worked with taught me a similar lesson after one of our last meetings: "You lost the moment you became emotional. Don't ever let people see your feelings in a meeting like that."
He was right about one thing: a group of "professionals" hates emotions. Go find a group of emotionally mature adults to work with & work on your own emotional maturity. Here are some hints for how to work on yourself that also acts as a list of mindsets to spot in others:
- nobody makes you feel anything
- you have a choice how to respond emotionally to all thing, though the amount of time your brain gives you to spot the choice may be unnoticeably small
- that spot can grow with practice (mindfulness meditation)
- whatever you're feeling in the moment is ok...you're allowed to feel it
- unpleasant feelings signal a fundamental human need going unmet...find the need & address/accommodate it
- everyone's doing the best they can and always have been...if someone isn't doing the best they can, the real culprit is you not accepting someone
- own your feelings...don't defend them, especially by blaming them on other people.
- apply all of this to every single person, including the worst of people.
- read "Nonviolent Communication" https://www.amazon.com/Nonviolent-Communication-Language-Lif...
Fresh book recommendations delivered straight to your inbox every Thursday.