Week 23 — Error-log final push and the full mock loop¶
This week
Grammar: Personal error log: final push · Vocabulary: Personal weak-word list · Idioms & phrasal verbs: Idiom review round · Speaking: Full mock loop speaking practice · Writing: Follow-up and thank-you emails · Soft skill: Building rapport quickly
Difficulty: high (C1+), timed. Next week is the final assessment (comm-6). This week is your last chance to close the gaps that still show up in your own error log at docs/log/comm-errors.md. Have that file open on Day 1 and Day 2.
Day 1 — Grammar: Personal error log: final push¶
⏱ 30 min · Mon · 8 min triage, 12 min exercise (timer), 5 min check, 5 min use it.
Rule in 60 seconds¶
An error you have made three times is not a knowledge gap; it is a habit. Habits are fixed by cues and repetition, not by re-reading the rule. Classify each entry in your error log first, because each class has a different fix.
| Class | How to recognise it | Typical example | Fix |
|---|---|---|---|
| Rule gap | You cannot explain why the correct form is correct | "suggest to use" (should be suggest using) | Learn the rule once, in one sentence; write 3 examples from your own work |
| Transfer | The wrong form mirrors your first language | "explain me", "discuss about", "I am agree" | Memorise the correct chunk as one unit: "explain it to me", "discuss the plan", "I agree" |
| Slip | You know the rule; you get it right in writing, wrong in speech | dropped third-person -s, "the data are/is" | Slow down the verb; practise in speech drills, not grammar sheets |
| Fossil | You have said it wrong for years, and it sounds right | "in the next Monday", "since 3 years" | Replace the entire phrase with a correct one you rehearse daily for a week |
The 3-3-3 protocol for your top three errors: write 3 correct sentences from real work; say each 3 times aloud; check them again on 3 separate days (day 1, day 3, day 7). Sentences must come from your own emails and meetings; invented sentences do not stick.
Exceptions and cautions: do not try to fix more than three errors at once; the fourth pushes out the first. Fix by frequency x impact: an error in every meeting (e.g. missing articles) matters more than a rare fancy one (e.g. an inversion slip). And check the pattern, not the word: "explain me" and "suggest me" are one error (transitive verbs taking the person as the object).
The error fluent speakers make with error logs: collecting mistakes without cues. Each log entry needs a trigger ("when I say 'explain'..., I think 'to') or it never fires in live speech.
Exercise¶
Timer: 12 minutes. Correct each sentence, then write its class (rule gap, transfer, slip, fossil). Two are commonly debated: mark those as "either".
- The data shows that the migration have reduced our costs.
- We are looking forward to work with you on the rollout.
- She has left the company in March.
- Could you please to send me the latest report?
- I am agree that we should postpone the release.
- The company offers many opportunities of growth.
- Despite the fact that was late, we shipped on schedule.
- Do you know where is the runbook?
- We have a meeting on next Monday.
- He said me that the deadline moved.
Answers and explanations
- ...the migration has reduced our costs. Agreement; data shows/show are both accepted (mass noun in business English); the error is have. Slip.
- ...looking forward to working... To is a preposition here, so a gerund. Rule gap / transfer.
- She left the company in March. Finished time marker: past simple. Rule gap.
- Could you please send me... After could, bare infinitive. Transfer.
- I agree... Agree is a verb. Transfer.
- ...opportunities for growth. The collocation is opportunity for (or to + verb: opportunity to grow). Fossil / transfer.
- Despite the fact that it was late... A clause needs a subject. Slip.
- Do you know where the runbook is? Indirect questions use statement word order (no inversion). Rule gap. Common even at C1.
- We have a meeting on Monday. No next with on: "on Monday" or "next Monday" but not both. Fossil.
- He told me that the deadline had moved / was moved. Say does not take a person object directly (say to me); tell does. Transfer.
Use it¶
Open docs/log/comm-errors.md. Choose your top three errors by frequency and impact. For each: class, correct sentence from real work, and a trigger cue. Write them in the log with today's date. Say each sentence three times aloud. Re-check on Wednesday and Sunday.
Day 2 — Vocabulary: Personal weak-word list¶
⏱ 30 min · Tue · 10 min list, 10 min new words, 5 min cloze, 5 min use it.
Build your personal weak-word list (10 min)¶
Collect 10 words from these sources, in order:
- Words you rated N or R in the Week 0 vocabulary check that you would want to use in your job.
- Words from Weeks 1-22 you got wrong in a cloze exercise or recap.
- Words you avoided in an email or talk in the last month because you were unsure (the most valuable source: the word you did not use).
- Words you heard a senior colleague use and did not fully understand.
For each, write: the word, its exact collocations, and one sentence from your own work. Test each by covering the sentence and saying it. Any word you cannot produce in five seconds goes to Week 25 practice.
Five words to add to that list, because they appear in leadership writing but rarely in learner materials:
| Word | Part of speech | Meaning | Example |
|---|---|---|---|
| ramification | noun (usually plural) | A consequence, often complex or unwelcome, of an action or decision. | The legal ramifications of storing customer data in that region were not clear to the team. |
| tentative | adjective | Not fixed or certain; provisional, subject to change | The launch date is tentative until the vendor delivers the connector. |
| instrumental | adjective | Important in making something happen; playing a key part | Her decision to freeze the schema was instrumental to the on-time delivery. |
| concede | verb | To admit a point or give something up, often reluctantly. | I concede that our estimate was optimistic; here is the revised one. |
| validate | verb | To confirm that something is accurate, sound or well-founded, often by testing it | The logs validate the customer's account of the timeout. |
Collocations and word family¶
- ramification: far-reaching / legal / financial ramifications; consider / understand / assess the ramifications of. Usually plural. Do not confuse with ramp-up or repercussion (close; repercussion is more negative, implication is more neutral).
- tentative: a tentative date / agreement / plan; adverb tentatively; do not confuse with
contingent(dependent on a condition being met) orprovisional(week 4), both close near-synonyms. - instrumental: instrumental in / to; do not confuse with the musical sense ("an instrumental track"); close synonym
pivotal(of central importance). - concede: concede a point / the argument / defeat; concede that...; noun concession (negotiation). Stronger than admit; implies you had resisted.
- validate: validate a hypothesis / an assumption / a finding / a design; noun validation; adjective validated. Common in engineering and product contexts; do not confuse with
valid(correct or legally acceptable).
Exercise¶
Timer: 8 minutes. Fill each gap (some are review words from Weeks 1-22; choose from: mitigate, streamline, orchestrate, throttle, trade-off).
- The go-live date is ______, pending the security review finishing this week.
- Before agreeing, we must consider the ______ for our data-residency commitments.
- Two independent metrics ______ the theory that the cache is the cause.
- I'll ______ that our first estimate missed the integration work, but the new plan accounts for it.
- The vendor's decision to open the API was ______ to our ability to integrate carriers quickly.
- To ______ the risk, we ran both systems in parallel. (review)
- We have to ______ each partner to protect the shared gateway. (review)
- The ______ is speed against consistency; we cannot have both. (review)
Answers and explanations
- tentative. Not yet fixed.
- ramifications. Consequences of a decision.
- validate. Independent evidence confirms the theory.
- concede. Admitting a point.
- instrumental. Played a key part in an outcome.
- mitigate. Reduce the severity (also de-risk works from earlier weeks).
- throttle. Limit request rates.
- trade-off.
Use it¶
Write one sentence for each of your top five personal weak words, using each in a sentence you could send to your manager this week. Say each aloud twice.
Day 3 — Speaking: Full mock loop speaking practice¶
⏱ 30 min · Wed · 3 min setup, 20 min loop, 7 min review.
Prompt. Run a solo mock interview loop with four stages. Record all four in one take. Use a phone timer.
| Stage | Question | Time |
|---|---|---|
| 1. Opening | "Walk me through your background, and why this role?" | 90 s |
| 2. Behavioural | "Tell me about a time you had to change your approach after new evidence." | 90 s |
| 3. Technical judgment | "You have to choose between a rewrite and an incremental refactor of a critical service. How do you decide?" | 2 min |
| 4. Your questions | "What questions do you have for us?" | 45 s |
Structure.
- Opening: present-past-future. "I'm currently... (10 s). Before that, the work that shaped me was... (35 s). What draws me to this role is... (25 s)."
- Behavioural: STAR with the Result and a lesson, as in Week 21.
- Technical judgment: criteria first. "I decide by three criteria: risk, cost of delay, and reversibility. On risk... On cost of delay... On reversibility... So my default would be X unless Y." (Trade-offs as in Week 22.)
- Questions: ask two, one about the work and one about how success is measured. "What would success look like in the first six months?" "What is the hardest technical trade-off the team is facing right now?"
Pronunciation micro-drill: sentence stress and linking in interview phrases. Stress the content words (nouns, main verbs, adjectives, numbers), reduce the rest.
- "I'm CURrently LEADing the PLATform TEAM at a LARGE logistics COMpany." (Content words stressed, at a reduced to /ət ə/.)
- Linking consonant to vowel: "walk_me_through_it" runs together: wor-kmee-through-it.
- Intrusive /r/ and /w/ in fast speech: "go_on" /gou w ɒn/; "I_am" /aɪ j əm/ (do not fight this; it is natural).
- Question intonation: rising for yes/no questions ("Do you have the numbers?"), falling for wh-questions ("What would success look like?").
- Say aloud five times each: "in the first six months", "the hardest trade-off", "what I'd like to understand".
Self-check
- All four stages finished inside their time limits.
- The opening followed present-past-future.
- The technical answer stated criteria before the recommendation.
- I asked two questions of substance, not "what is the culture like".
- I fixed at least one slip cleanly by correcting once and moving on.
Day 4 — Idioms & phrasal verbs: Idiom review round¶
⏱ 30 min · Thu · Review of five earlier idioms, chosen for use in senior conversations.
| Expression | Meaning | Example |
|---|---|---|
| true north | A fixed guiding principle that all decisions are steered by. Neutral, widely used in tech and strategy (US and UK). | Our true north is on-time, in-full delivery; every roadmap item must serve it. |
| the lay of the land | The current overall situation, especially before deciding how to act. Neutral, slightly formal. | Before we debate the schema, let's get the lay of the land: what problem do customers have? |
| a moonshot | A highly ambitious, groundbreaking goal, often with a real chance of failure. Neutral to informal, common in tech. | Sub-second tracking updates are a moonshot; the committed target is five seconds. |
| go to bat for (someone) | To support or defend someone, especially to a third party. Informal, mostly US. | On on-call weeks, we go to bat for each other with the incident commander. |
| hold your own | To perform capably and confidently, even under pressure or against strong competition. Neutral to informal. | Everyone held their own during the migration, so no one burned out. |
Exercise¶
Timer: 10 minutes.
- Choose: "Our (true north / south pole / red line) metric is customer wait time."
- Fill: "Let's get the ______ of the land before we argue about naming."
- Fill: "We committed to 99.9%, but 99.99% is a ______."
- Rewrite idiomatically: "We all support each other when things go wrong."
- Rewrite idiomatically: "He struggles to keep up during the on-call rotation."
- Which idiom describes an aim beyond your promise: a moonshot or true north?
- Choose: "With so many priorities, we need one guiding metric: a (moving target / true north / low-hanging fruit)."
- Say whether it is safe to use go to bat for each other in a formal report to executives. Explain.
Answers and explanations
- true north.
- lay.
- moonshot.
- "We go to bat for each other."
- "He struggles to hold his own in the on-call rotation."
- a moonshot (an ambitious extra); true north is a guiding principle you keep.
- true north. A moving target is a goal that keeps changing; low-hanging fruit = easy wins.
- Not really. It is informal; use "we support each other" or "the team covers for one another" in formal writing.
When NOT to use them
True north is now so common that it can sound empty; use it only when you can name the actual metric. Hold your own can sound like faint praise if overused; be specific about what someone did well. Overusing business jargon (true north, the lay of the land, moonshot) in one paragraph reads as management-speak.
Day 5 — Writing: Follow-up and thank-you emails¶
⏱ 30 min · Fri · 5 min read, 15 min rewrite, 10 min compare.
Bad draft (a thank-you after a final-round interview):
Subject: Thanks
Hi,
I wanted to say thank you very much for taking the time to meet with me today, it was really a great experience and I really enjoyed the conversation with you and the team. I am very excited about the opportunity and I think that I would be a good fit for the role because I have a lot of experience. Please let me know if you need any further information from my side. I hope to hear from you soon.
Best, Rahul
Task. Rewrite in 90-110 words. Constraints: a specific subject line; one specific detail from the interview (invent one: the interviewer asked how you would migrate a legacy tracking system without downtime); one added piece of value (a link, a diagram, or a short answer you did not give in time); a clear next step; no clichés ("great experience", "good fit", "any further information from my side").
Model answer and what changed
Subject: Follow-up: migration approach we discussed
Dear Anna,
Thank you for the conversation today; the discussion about migrating the legacy tracking system without downtime was the part I enjoyed most.
I was not satisfied with how briefly I answered your question about rollback, so here is the fuller version: I would run both systems in parallel for two weeks, compare outputs automatically, and route 5% of traffic to the new path first, with a one-command switch back. I can send the one-page design if that would help.
I am keen to help the team deliver this, and I look forward to hearing about next steps. Please tell me if there is anything I can clarify before your decision on Friday.
Best regards, Rahul Singh
What changed and why
- Subject line names the content. "Thanks" gets lost; "Follow-up: migration approach we discussed" is findable and signals value.
- A specific detail ("migrating the legacy tracking system without downtime") proves you listened; generic praise proves nothing.
- Added value. You use the email to close a gap in your interview answer: the most useful thing a follow-up can do.
- A concrete next step (offer the one-page design; refer to the decision date) replaces "hope to hear from you soon".
- Cut the clichés and hedges ("really a great experience", "I think I would be a good fit because I have a lot of experience"); replaced with evidence-led language.
Day 6 — Speaking record: Career narrative, 2-minute talk¶
⏱ 30 min · Sat · 5 min prep, 2 min record, 5 min replay and score, 15 min shadowing, 3 min log.
Prompt. Record a two-minute answer to: "Take me through your career in a way that shows how you got from where you started to Staff-level engineering, and where you are going next." Use a clear arc: origin > turning points (two) > present > direction. Include one past perfect, one present perfect for the bridge to today, and at least two achievement verbs (Week 21).
Structure. 0:00 origin in one sentence; 0:15 turning point 1 (what changed in your thinking); 0:45 turning point 2; 1:15 present role, one proof point with a number; 1:40 direction (what problem you want next); 1:55 one closing sentence.
Rubric (score each 1-4; total /24)
| Criterion | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Clarity | Timeline unclear | Point recoverable | Clear arc; some detours | Effortless; the arc is memorable |
| Structure | No arc | Chronological list only | Arc with turning points | Arc, proof and direction; proportional timing |
| Fluency | Frequent long pauses | Noticeable hesitation | Occasional hesitation | Smooth, natural rhythm |
| Grammar accuracy | Errors block meaning | Frequent tense errors | Occasional errors | Rare errors; narrative tenses correct |
| Vocabulary range | Repetitive | Some variety | Good range, some imprecision | Precise and varied |
| Pronunciation | Hard to follow | Intelligible with effort | Mostly clear | Clear stress and rhythm |
Shadowing task (15 min). Choose a TED talk by someone who tells their professional journey (a "how I got here" talk), or a BBC Learning English "6 Minute English" episode with a guest describing their career. Shadow a 60-second passage, three times; then record it once without the audio. Focus on how the speaker links stages: "and that led me to...", "it was then that...", "what I hadn't realized was...".
Log your score: Week 23 record: __/24 · lowest criterion: ______ · recording file: ______.
Day 7 — Soft skills + weekly review: Building rapport quickly¶
⏱ 30 min · Sun · 10 min scenario, 10 min recap, 10 min self-score and error log.
Scenario. You start a new engagement next month with a Director, Marcus Lindqvist, who has been burned by a previous platform team and is openly sceptical. You have a 30-minute first call and no shared history. You want him to leave the call trusting your judgment and willing to be candid with you.
Task. Script your first 150 words: how you open, one question that shows curiosity about his concerns, how you show that you listened, and how you close. No small talk about weather; no defending the previous team; no promises you cannot keep.
Model response and annotation
Marcus, thanks for making the time. I'd like to use these thirty minutes mostly to listen. I've heard the last platform rollout was rough, and I'd rather hear what happened from you than guess. What was the one thing you'd most want us to get right this time? ...(listen)... So if I'm hearing you correctly, the pain was surprise: things changing without your team knowing. Is that fair? Then let me propose one commitment: a Friday note from me, five lines, with anything changing next week and anything at risk. If it isn't useful after a month, we'll change it or stop. Is there anything else you'd want me to know that I haven't asked?
Techniques used: (1) Framing the time ("mostly to listen") lowers his guard and sets expectations. (2) Naming the difficulty shows awareness without blaming anyone. (3) One open question about his priority ("the one thing") gets a concrete answer, not a speech. (4) Reflective paraphrase ("if I'm hearing you correctly... Is that fair?") proves listening and invites correction. (5) A small, specific commitment with an exit clause builds trust faster than a large promise. (6) A closing "anything else" question invites candour and makes the next call easier.
Weekly recap (20 items)¶
- What are the four classes of error in your log, and which needs speech practice?
- What is the 3-3-3 protocol?
- Why do you fix no more than three errors at once?
- Correct: Do you know where is the runbook?
- Correct: I am agree.
- Correct: He said me that the deadline moved.
- Correct: We are looking forward to work with you.
- Which preposition after opportunities?
- Define ramification.
- What does tentative mean?
- Define instrumental and give a collocation.
- Difference between concede and admit?
- Use validate correctly in a sentence.
- What is true north, and what must you be able to do before using it?
- Moonshot versus committed target?
- Which is informal: go to bat for someone or hold your own? (Trick: both are informal-neutral; which is warmer?)
- What is the present-past-future structure for an opening?
- What should a thank-you email add beyond thanks?
- Which question shows curiosity and not small talk to a sceptical director?
- What kind of commitment builds trust fastest?
Answers
- Rule gap, transfer, slip, fossil; slips need speech practice.
- 3 correct real sentences, said 3 times each, checked on 3 days.
- The fourth error displaces the first; habits need focused repetition.
- Do you know where the runbook is?
- I agree.
- He told me that the deadline had moved.
- ...looking forward to working...
- for (opportunities for growth), or opportunity to + verb.
- A consequence of a decision, often complex.
- Not fixed or certain; provisional, for example a tentative launch date.
- Important in making something happen; instrumental in / to the outcome.
- Concede implies you resisted first, and is stronger.
- Model: The logs validate the customer's account.
- A fixed guiding principle you steer by; you must be able to name the actual metric.
- A moonshot is a highly ambitious, groundbreaking target beyond the commitment; the committed target is what you promise.
- Go to bat for someone is the warmer, more personal one.
- Present role, formative past, and future direction.
- Value: a detail, a link, or a better answer, plus a next step.
- An open question about his priority or what he wants us to get right.
- A small, specific commitment with an exit clause.
Self-score¶
- My top three errors are written in the log with class, sentence and trigger.
- I can produce the five new words and five review idioms in a sentence in under five seconds each.
- I completed the full four-stage mock loop within the time limits.
- My Day 6 recording scored 18/24 or above.
- My follow-up email adds value beyond thanks.
Error log prompt. Write down your top 3 recurring mistakes now. If one of them is the same as last week's, note that and replace the fix with a new trigger cue; if it is new, add it. Next week's assessment will show whether the fixes held.