# Crucial Conversations: the 2002 book that teaches FDEs how to talk when a meeting is about to fail > Once a client stops telling you the truth, no log or evidence will save the meeting. This book shows what to do first. Bản gốc: https://fdetimes.net/en/books-courses/crucial-conversations-fde-tense-client-meetings/ This book came out in 2002. It has sold more than two million copies, been translated into 28 languages, and remains more worth reading for an engineer who wants to become an FDE than most of the material on agents published this year. The reason lies in the nature of the job. FDEs sit close to the client, so a meeting that goes wrong can slow a project as much as a production bug: the client feels belittled, the engineer feels blamed, and from then on nobody tells the truth. *Crucial Conversations: Tools for Talking When Stakes Are High* is written specifically for moments like these. ## Who wrote it, and which editions exist? The authors are Joseph Grenny, Kerry Patterson, Ron McMillan and Al Switzler. Newer editions add Emily Gregory. Crucial Learning, the authors' own company, describes them as business consultants working across many countries. McGraw-Hill first published the book in 2002, and the second edition followed in 2012. The book does not stand alone. Crucial Learning built a course on the same principles, called Crucial Conversations for Mastering Dialogue. Its aim is to help learners raise concerns, work through disagreement and reach agreement when it matters most. ## The first lesson: pick the right conversation The course's opening lesson is not about how to speak. It teaches you to spot the conversations standing between you and what you want. That sounds simple, but for an FDE an avoided conversation can hold a project still without anyone naming it. Imagine you are deploying a system for a bank. The client's data has arrived in the wrong format for three weeks, and the team has quietly written patch code rather than raise it directly with the head of data on their side. The conversation blocking the project is not in the pipeline. It is the one nobody has dared to start. ## Idea one: safety first, content second This is the idea most worth keeping. According to Crucial Learning, when you face a Crucial Conversation, your first goal is to create safety. Many engineers' reflex is to bring more data, more logs, more evidence. But if the other side does not yet feel safe, more evidence is easily heard as more accusation. **Điểm mấu chốt:** When a meeting starts to turn tense, don't fix the argument. Restore safety first. ## Idea two: safety stands on two legs Crucial Learning splits safety into two conditions, a split that suits an engineer's debugging mindset well. Mutual Purpose means the other person believes you care about their concerns. Mutual Respect means they believe you care about them as a person. The two conditions fail in different ways. If the client thinks you just want to close the ticket, Mutual Purpose has broken. If they think you consider their IT team incompetent, Mutual Respect has broken. To fix the right thing you have to diagnose which leg is giving way, just as you have to read the right stack trace to patch the right spot. Lesson 8 of the course, Seek Mutual Purpose, goes a step further: find common ground even when there seems to be none. In a deployment, that common ground usually already exists. Both sides want the system running in production; nobody has said so out loud. ## Idea three: Contrasting, a tool you can use tomorrow Crucial Learning defines Contrasting as a don't/do statement and places it among the techniques for restoring safety. First you state clearly what you do not mean, then what you actually want. Go back to the bank. The head of data hears you mention the format problem and immediately becomes defensive. A Contrasting statement might be: "I don't mean your team did anything wrong. I want us to agree on one format together so we go live on time next week." The first sentence repairs Mutual Respect; the second restates the goal both sides share. ## Where does Contrasting go wrong for beginners? The most common mistake is turning Contrasting into a token apology. "I don't mean to criticise your team, but..." followed by exactly that criticism. The "but" wipes out the first half of the sentence, and the other side will hear it at once. The second mistake is saying the "don't" half and forgetting the "do" half. A denial alone tells the other person what you don't want, but not what you do, so Mutual Purpose is left hanging. The third mistake is using Contrasting when the "don't" is not true: if you really do think their team got it wrong, find a respectful way to say so rather than denying it. ## Who should read it, and in what order? If you are a developer with two to eight years of experience who works mainly through tickets and Slack, the book fills the biggest gap you will face in moving to an FDE role. Read the book first, and pay attention to the three ideas above. The course is the next step, for those who want guided practice, and the self-paced online version is the easiest place to start. When reading job descriptions, look for lines about working with stakeholders or handling ambiguous situations with clients: that is where you can demonstrate the skills from the book. On your CV and in interviews, don't write "good communication skills". Describe a specific time you opened a difficult conversation, what you did to keep it safe, and how it turned out. Good code gets you invited into the room with the client. Whether you stay in the room depends on whether the client still dares to tell you the truth. **Thử ngay tuần này:** - Write down one conversation you are avoiding, with a client, PM or tech lead. Add one sentence: what avoiding it is costing you. - Before your next difficult meeting, prepare a Contrasting statement in the form 'I don't want... I do want...' and use it when you see the other side becoming defensive. - After every tense meeting, ask yourself two questions: does the other person believe I care about their concerns, and do they believe I respect them? ## Nguồn - [Crucial Conversations - Free Book Resources | Crucial Learning](https://cruciallearning.com/crucial-conversations-book/) - [Crucial Conversations: Tools for Talking When Stakes Are High](https://en.wikipedia.org/wiki/Crucial_Conversations:_Tools_for_Talking_When_Stakes_Are_High) - [Crucial Conversations for Mastering Dialogue | Crucial Learning](https://cruciallearning.com/solutions/crucial-conversations-for-dialogue/) - [Crucial Conversations Skill Summary: Make It Safe](https://cruciallearning.com/blog/crucial-conversations-skill-summary-make-it-safe/)