How to practice: getting it into your mouth

Reading a phrasebook does not install it. Under pressure (the exec question, the heated review, the incident channel), you fall back to whatever patterns are automatic, and patterns become automatic only through repetitions. This closing chapter is the training plan: four loops that fit inside a normal work week, using your actual job as the gym.

Loop 1: input (steal deliberately)

You already consume hours of professional English; the upgrade is consuming it with a thief's eye.

• Shadow one strong communicator at your org. Every team has someone whose messages get answered and whose pushback lands. Read their last month of channel messages once; steal three frames verbatim. This outperforms any generic corpus because it is pre-tuned to your team's register (Chapter 15's harvest-locally rule).
• Engineering talks and podcasts, ten minutes a day, but with a notes file for phrasing, not content: how did the speaker handle the hostile question, hedge the estimate, land the joke?
• Reread your own team's best artifacts (the postmortem everyone praised, the RFC that sailed through) as language samples, and note which templates from the cheat sheet they were unknowingly following.

Loop 2: written output (the rewrite journal)

Writing is the low-pressure gym for the high-pressure spoken game, because every pattern that becomes automatic in text is halfway to automatic in speech.

• The daily rewrite: once a day, take the weakest message you sent and rewrite it in a private note using the book's patterns: ask visible, BLUF, one hedge, purpose tag. Two minutes. After a month, the first drafts start coming out rewritten.
• Frame of the week: pick one frame (say, the costed no, or "what led us to X?") and deliberately use it three times that week in real messages. One frame at a time beats memorizing the catalog; this is habit stacking, not studying.
• Templates into muscle memory: put the five templates you need most (status, bug report, escalation, PR description, standup) into your snippet manager or notes app. Filling a skeleton teaches the skeleton; after twenty fills you will not need it.

Loop 3: spoken output (small stakes, real reps)

• Record your standup once a week (phone, thirty seconds) and listen once. Excruciating and unmatched: you will hear the filler, the trailing "so, yeah", the missing outcome-verbs (Chapter 8) within two sessions, and self-heard flaws fix themselves faster than corrected ones.
• Read aloud ten minutes a day (anything technical). This is the single highest-yield pronunciation drill: it decouples producing sounds from composing content, which is why it works when "just talk more" does not. Fold in the Chapter 24 tables: read a config file aloud, symbols and all.
• Rehearse the openers only. Before a review, a demo, or a hard conversation, say the first two sentences out loud, twice. Not the whole script (scripts shatter on contact); just the opener, because a clean start settles the voice and the rest follows (Chapter 17).
• Roleplay the hard ones with an AI assistant before doing them live: "Play a skeptical staff engineer; I'm going to propose splitting the queue; push back hard." Modern and genuinely effective, with two rules: no confidential details in the prompt, and treat it as sparring (reflexes), never as a script to recite (Chapter 31's scenes make good scenarios).

Loop 4: feedback (close the loop or plateau)

• One targeted ask per month (Chapter 19's narrow-question rule, aimed at language): "One thing about how I come across in reviews that I could sharpen?" Rotate the venue: reviews, meetings, docs, incidents.
• Collect your corrections. Every time someone rephrases your words back better ("so what you mean is...") or a native speaker edits your doc, that diff is free tuition; keep the before/after pairs. Patterns repeat: most people have five habitual errors, not fifty (Chapter 17's tables are everyone's union; your personal set is small).
• Measure by outcomes, not feelings: fewer clarifying questions coming back at you, faster review turnarounds, your summaries becoming the ones that get linked, being asked to present. These move within a quarter of deliberate practice, and they are the point; accent reduction is not (Chapter 17: clarity beats accent, always).

Don't be confused: fluency and accuracy are competing training goals, and drilling them together stalls both. Fluency practice means keep talking, errors allowed, no self-interruption (the standup recording, the roleplay). Accuracy practice means slow, corrected, deliberate (the rewrite journal, the pronunciation table). Alternate them like heavy and light gym days. And in live meetings, always choose fluency: a confident sentence with a wrong article beats a perfect sentence that arrives after the moment has passed. Accuracy is for the practice room; the meeting is the game.

A 30/60/90 plan

Ninety days of this is invisible day to day and unmistakable in the rearview mirror, which is how all compounding works.

The last word

Every technique in this book is a special case of one sentence from the introduction: soften the person, sharpen the substance, and make things easy for the reader. The phrases are scaffolding; what they build, message by message and standup by standup, is the reputation that makes people relax when your name appears in a thread, because whatever arrives will be clear, fair, and worth their time. That reputation is the actual asset. The English is just how it compounds.

👉 That is the end of the book. The References hold the sources behind these chapters, each worth your time in full.