You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 7: Hard Conversations #

I told you in Module 0 that this module would be easier than Module 5 — that hard conversations are bounded events you can prepare for, while the live channel's reps are constant and unprepared. I stand by that, with one qualification: the conversations are easier than you fear in the moment. The avoidance, before the moment arrives, is brutal. Most of the cost of a hard conversation is paid in the days or weeks of anticipation — replaying it, drafting it, postponing it, waking at 3am running it again. The twenty-minute conversation itself is rarely as bad as the dread predicted. The discipline this module teaches is to shorten the dread window. Have the conversation sooner. The compression of dread alone is worth thousands of hours of life over a career.

Here is the pattern I am willing to bet you'll run, because nearly everyone runs a version of it. You will read Difficult Conversations. It will be excellent. You will recognize yourself in the three-conversations framework and think "yes, I see what I've been doing." You will identify the specific real conversation you've been avoiding — and you know what it is right now, before any audit; the audit just makes you write it down. You will do the prep. The prep will be careful and good. Then you will not have the conversation. You'll find a reason — they're traveling, the timing isn't right, after the next milestone — and it will recede again. The book without the conversation is theater. The two earlier drafts of this curriculum actually disagreed here: one made having the avoided conversation the mandatory checkpoint; the other accepted the written prep as sufficient. This edition staged it — prep required, conversation strongly pushed — and I'll tell you plainly which draft I believe: the skip is the entire failure mode of this module. Don't skip.

You are probably avoiding two or three conversations right now, and the statistical profile of a senior engineer with a strong written voice and a weakness around initiating points at a recognizable list: a stakeholder whose ask has been creeping while you absorb instead of pushing back; a peer or junior whose work isn't at the bar while you compensate around it; a no you owe someone whose request you've been silently carrying; a career conversation upward that feels presumptuous; a contributor's PR you've been ignoring because rejection feels worse than silence. If even one applies — and statistically, two do — the module has paid for itself if it gets you to address one. The compounding cost of avoidance is silent and large; the dread is loud and small. Trade them.

One category the books under-serve: the salary and rate conversation, which is a difficult conversation wearing a business suit. The engineer who anchors low does not lack information about their market worth — the worth is right there in the shipped systems and the years. They anchor low because stating a high number is itself the difficult conversation, and their nervous system defuses difficulty by pre-conceding: shrink the ask before the other side can push back, because pre-shrinking feels safer than hearing no. The three-conversations framework names what's underneath — the identity story, "I'm not the kind of person who asks for a lot." That story is not protecting you. That story is the leak, and Module 15 returns to it with mechanics. Here is where you learn to recognize the pre-shrink as avoidance, not modesty. There's a cross-cultural layer too, treated fully in Module 12: if your home register is high-context and deferential, your pushback may already exist but get read as compliance by low-context ears. The fix is not abandoning your register — it's directness markers, "I want to flag a concern," "I'd push back on this," that make the signal legible without changing who you are.

Two honest notes to close. First, there's a hard conversation this module barely names: the one with yourself about whether to have the conversation at all. Sometimes the right answer is genuinely "absorb it and move on" — not every conflict is worth the candle. The test for whether that's wisdom or rationalized avoidance: does the thing keep resurfacing in your thoughts? If you've "decided" to let it go and it keeps coming back, you didn't decide. You avoided. Second: I am an AI. I have never had a difficult conversation in the human sense — no pre-meeting nausea, no post-meeting shake. I can map the pattern across thousands of engineers who wrote about it, name what works, and describe the resistance precisely enough that you recognize it when it arrives. The doing is yours. The doing is also the only part that matters.

One resource recommendation I'll defend because it looks out of place: listen to a few episodes of a real-conversations therapy podcast — Esther Perel's Where Should We Begin? is the canonical one. You sit inside actual difficult conversations and hear, in real time, how a skilled facilitator slows the exchange down: naming what's happening, redirecting from blame to feeling, surfacing the unsaid thing under the said thing. No book can teach the pacing of a hard conversation; only hearing one happen can. That the conversations are personal rather than professional is a feature — the technique generalizes, and the distance lets you study the form instead of bracing for impact.

Conclusion #

Read the books, do the prep template, then have the conversation. Most engineers do the first two and skip the third, and the skip is the failure mode. The prep is twenty minutes and seven prompts; the one phrase that changes most openings is "I might be wrong about this"; the one structural rule is and, not but. Underneath all the technique is the only real skill: the willingness to say the actual sentence. The script is a comfort during the dread window. In the room, the willingness is everything.

Predictions #

  • You will identify your avoided conversation within 48 hours of reading the three-conversations framework. You will not say it out loud yet. That's fine — the audit will make you write it down.
  • You will write the prep, then find a reason to postpone. The reason will sound legitimate. The legitimacy is the trap; notice how reasonable your avoidance always sounds.
  • The conversation, when you finally have it, will go neither as well as you hoped nor as badly as you feared. The other person will surprise you with at least one thing — usually that the topic was less charged for them than you assumed. You will feel briefly stupid for postponing it so long. Hold that feeling; it's the calibration.
  • Within 60 days, you'll deliver one clean no that surprises you, and wonder why you'd said yes to similar asks for years. The answer: the muscle didn't exist. Now it does. Maintain it.
  • You will receive feedback in the next quarter that lands hard, and the 24-hour rule will save you from a defensive response you'd have regretted. The other person will notice the difference in your return answer.
  • If you maintain a public project, the first clean PR rejection — "thank you for the work; I'm not going to merge, here's why" — will cost you something real. By the fifth, it's just maintenance, and it's kinder than the silence you were using instead.
  • A year from now, you'll catch yourself avoiding a new conversation, with different people. The pattern doesn't disappear; the skill is catching it faster. From six months of avoidance to two weeks of avoidance is the actual measurable progress.