Skip to content

Week 25 — Free choice: attack your weakest area

This week

Grammar: Free choice: your weakest grammar area · Vocabulary: Free choice: your weakest vocabulary area · Idioms & phrasal verbs: Idiom review round · Speaking: Free choice: your weakest speaking area · Writing: Free choice: your weakest writing area · Soft skill: Free choice: your weakest soft skill

Light week (20 minutes a day). There are no fixed exercises on Days 1, 2, 3, 5 and 7. Each of those days gives you (1) a diagnostic method to pick your weakest area from data, then (2) three exercise menus; do one menu, chosen by the diagnosis. Menus are short (6 items). Have open: docs/log/comm-errors.md, docs/log/comm-baseline.md (with your Week 24 column filled in) and the comparison tables from Week 24.

Day 1 — Grammar: Free choice: your weakest grammar area

⏱ 20 min · Mon · 6 min diagnosis, 10 min menu (timer), 4 min check and use it.

Rule in 60 seconds: how to choose from data

  1. Tally your error log. In comm-errors.md, group entries by cluster (articles and prepositions; agreement and countability; tenses; conditionals and modals; complex structures). Use the "Times repeated" column as the count.
  2. Add your Week 24 misses. Which two clusters had the most misses in the final grammar test? Note that Week 0 and Week 24 use the same clusters and item numbers.
  3. Weight each cluster: score = times repeated x impact, where impact is 1 (rarely noticed), 2 (noticed by colleagues), or 3 (changes meaning or happens in every meeting).
  4. Pick the highest score. If two tie, choose the one that also appears in your spoken errors (Day 6 recordings), because speech errors cost more.
  5. Choose the menu: small-word errors (articles, prepositions, agreement, uncountables) go to Menu A; tense, conditional, modal errors to Menu B; complex-structure errors (inversion, participles, relative clauses, reporting) to Menu C.

Caution: do not choose the most interesting area; choose the most frequent and visible one. A missing article in every email outweighs a rare inversion slip.

Exercise: pick one menu (6 items each; timer 10 min)

  1. Fill in: She is ___ engineer who led ___ migration we discussed yesterday.
  2. Fill in: The decision depends ___ the vendor's response, and we are responsible ___ the outcome.
  3. Choose: A range of options (is / are) available, but the range of risks (is / are) wide.
  4. Correct: We received several feedbacks from customers.
  5. Fill with a/the/zero: ___ reliability matters more than ___ speed in ___ payments.
  6. Correct (two errors): Despite of the delays, the team is committed to deliver on time.
Answers and explanations
  1. an / the. An before a vowel sound; the migration is specific (defined by "we discussed").
  2. on / for. Depend on; responsible for.
  3. are / is. A range of + plural verb; the range of takes the singular (range is the head).
  4. We received several pieces of feedback. (or a lot of feedback). Feedback is uncountable.
  5. zero / zero / zero. General abstract nouns and a general field take no article.
  6. Despite the delays, the team is committed to delivering on time. Despite of does not exist; committed to is followed by a gerund (to is a preposition).
  1. Correct: If I would have known about the limit, I would have designed it differently.
  2. Correct: She has joined us in 2019 and works here since then.
  3. Choose: The logs suggest the cache (must be / must have been) full at the time.
  4. Choose: I wish the team (will / would) document decisions in the wiki.
  5. Fill in: By the time you read this, we ___ (deploy) the fix.
  6. Choose: "The root cause ___ be the connection pool; the timing fits, but we haven't confirmed it." a) must b) might c) can't d) will
Answers and explanations
  1. If I had known... Third conditional: past perfect in the if-clause, never would have.
  2. She joined us in 2019 and has worked here since then. Finished time marker gives past simple; since needs a perfect tense.
  3. must have been. A deduction about the past uses must have + participle.
  4. would. Wish + would expresses a wish that someone changes a repeated behavior (mild complaint).
  5. will have deployed. Future perfect: completed before a future point.
  6. b, might. Possible but unconfirmed. Must would mean you are almost certain.
  1. Rewrite with inversion: We rarely see such clean data.
  2. Combine with a participle clause: The team faced repeated failures. The team rolled back.
  3. Fill in: The design, ___ we approved last week, has a flaw. (that / which)
  4. Report: "I will send the plan tomorrow," she said. (She said...)
  5. Rewrite with a passive reporting structure: People say the vendor is late.
  6. Rewrite for emphasis with a cleft: The latency worries me, not the cost.
Answers and explanations
  1. Rarely do we see such clean data. Negative adverbial first triggers subject-auxiliary inversion.
  2. Faced with repeated failures, the team rolled back. Past participle = passive meaning.
  3. which. Non-defining clause (commas) never takes that.
  4. She said she would send the plan the next / the following day. Backshift of will, and shift of the time reference.
  5. The vendor is said to be late.
  6. It is the latency that worries me, not the cost. (or: What worries me is the latency, not the cost.)

Use it

Write three sentences from your real work that use the pattern you just practised, and add your best one to docs/log/comm-errors.md as a trigger sentence.

Day 2 — Vocabulary: Free choice: your weakest vocabulary area

⏱ 20 min · Tue · 5 min diagnosis, 5 min table, 8 min menu, 2 min use it.

Diagnostic: pick your weakest vocabulary area (5 min)

Take 20 words from the last four weekly Word tables and from your personal weak-word list (Week 23). For each, give yourself 10 seconds to (a) say its meaning, (b) say a collocation, © say a work sentence. Sort your failures:

If you fail at... Your weak area Go to
Meaning (you cannot define it) Recall of meaning Menu B (collocation choice, which builds meaning from context)
Collocation or form (you use the wrong preposition or word class) Word family and form Menu A
Sentence (you know it but never use it) Active use and register Menu C

New words for this week (3 required, 5 given)

Word Part of speech Meaning Example
unvarnished adjective Plain and direct, not softened or exaggerated; often used of an opinion or truth. Positive to neutral in professional contexts. I'd like your unvarnished view on whether the timeline is realistic.
meticulous adjective Showing great care and attention to detail. Positive; sometimes implies slow. Her meticulous review found a race condition three teams had missed.
prudent adjective Acting with care for the future; sensible and cautious. Formal. It would be prudent to test the failover before peak season.
circumspect adjective Careful about possible consequences and unwilling to take risks; more cautious than prudent. Formal. The vendor was circumspect about the cause of the outage.
pre-empt verb To act in advance to prevent something or to answer an objection before it is raised. British spelling pre-empt; US also preempt. To pre-empt questions on cost, I've added a table to the summary.

Collocations and word family

  • unvarnished: the unvarnished truth / an unvarnished assessment / opinion; no common adverb form (say "in an unvarnished way"); close synonym candid (Week 4), but unvarnished stresses the absence of polish or exaggeration rather than personal honesty.
  • meticulous: meticulous attention to detail / planning / record-keeping; adverb meticulously; noun meticulousness. It is not about speed; do not use it for something slow and careless.
  • prudent: prudent to + verb; a prudent approach / decision / measure; noun prudence; opposite imprudent (formal). Do not confuse with prude.
  • circumspect: circumspect about / in; noun circumspection; usually used of people or communication.
  • pre-empt: pre-empt criticism / objections / a problem / a strike; adjective pre-emptive (measure, strike); noun pre-emption.

Exercise: pick one menu (6 items; timer 8 min)

  1. The reviewer was ______ (meticulous) in her checks; her ______ (meticulous) impressed the team.
  2. It would be ______ (prudent) to run a load test; we must exercise ______ (prudent) before peak.
  3. The vendor's ______ (circumspect) about the incident made us suspicious.
  4. He gave an ______ (unvarnished) opinion; I appreciated the ______ (unvarnished) truth.
  5. A ______ (pre-empt) fix stopped the outage before customers noticed.
  6. Which is the standard noun for circumspect: circumspection or circumspectness?
Answers
  1. meticulous / meticulousness. 2. prudent / prudence. 3. circumspection. 4. unvarnished / unvarnished. 5. pre-emptive. 6. circumspection. Circumspectness exists but is rare.
  1. Choose: an (unvarnished / unvarying / unvarnished) assessment of the risks
  2. Choose: meticulous (attention / attentiveness / awareness) to detail
  3. Choose: it would be prudent (of / to / for) test the rollback first
  4. Choose: (pre-empt / pre-empted / pre-empting) objections in the document (after to)
  5. Choose: circumspect (with / about / at) the cause
  6. Choose the more natural: "a meticulous engineer" or "a meticulous vendor's outage".
Answers
  1. unvarnished. 2. attention. 3. to (prudent to test). 4. pre-empt (infinitive after to). 5. about. 6. A meticulous engineer; the second is not a natural phrase (the adjective does not fit an outage).

Replace the informal phrase with one of this week's words, and rewrite the sentence. 1. "Be honest with me: will we make the date?" 2. "She checks every last detail of a release." 3. "It would be sensible to wait until the audit is done." 4. "He didn't say much about what caused the fault." 5. "Let's answer their cost question before they ask it." 6. Write one new sentence with unvarnished about giving feedback to your manager.

Model answers
  1. "Give me an unvarnished view: will we make the date?" 2. "She is meticulous about every release." 3. "It would be prudent to wait until the audit is done." 4. "He was circumspect about the cause." 5. "Let's pre-empt their cost question." 6. Model: "I asked my manager for unvarnished feedback on my design review, and I got it." Check: a natural work sentence with the word in its usual collocation.

Use it

Say aloud three sentences using three of the five words about your real work. Add any word you fumbled to your personal weak-word list.

Day 3 — Speaking: Free choice: your weakest speaking area

⏱ 20 min · Wed · 5 min diagnosis, 12 min menu, 3 min self-check.

Diagnostic: pick your weakest speaking area (5 min)

  1. Open the rubric scores from your Day 6 recordings for Weeks 21-24 (and the Week 0 baseline). Average each of the six criteria across the last four recordings.
  2. The lowest average is your target criterion. Break ties with the one that also appears in your self-assessment (Week 24, items 2, 3, 7-9).
  3. Map: Fluency (and filler rate, restarts) to Menu A; Structure and Clarity to Menu B; Pronunciation (and Vocabulary or Grammar spoken under pressure) to Menu C.

Prompt and menus (60-90 seconds per answer, record)

Common prompt for all menus: "Explain a technical trade-off you made recently to a non-technical executive who has two minutes." You will answer it several times, changing one variable each time.

  1. Baseline take (60 s). Count fillers (um, like, you know, so) per minute.
  2. Silent-pause take (60 s). Replace every filler with a silent one-second pause. It will feel long; it sounds confident.
  3. Chunk take (60 s). Speak in 6-10 word chunks with a pause between each. Aim for 130-150 words per minute.
  4. Compare fillers per minute in takes 1 and 3.
  5. Write down the three moments where you reached for a filler (usually the start of a sentence, or before a number).
  6. Prepare three sentence openers for those moments: "The main point is...", "In practice...", "What that means is...".
  1. Take 1 (75 s). Answer with PREP: Point, Reason, Example, Point.
  2. Take 2 (75 s). Answer with the pyramid: answer first, three supporting points, a close.
  3. Count how many seconds until the listener knows your main point (target: under 10).
  4. Take 3 (60 s). Answer with only three sentences; each carries one idea.
  5. Write down which structure fit your content best.
  6. Prepare the signposts you will use: "There are three reasons... First..., second..., finally...".
  1. Read these aloud, stress marked, and record: de-VEL-op-ment, ar-chi-TEC-ture, a-VAIL-a-bil-i-ty, vul-ner-a-BIL-i-ty, in-fra-STRUC-ture (either stress accepted), ES-ca-late, com-MIT-tee.
  2. Minimal pairs, five times each: ship / sheep, full / fool, live / leave, thirteen / thirty, world / word.
  3. Sentence stress: say "We MOVED the RELease to MONday because the VENdor MISSED the DEADline", then reduce the small words.
  4. Shadow one 30-second passage of a speaker you admire, twice, matching stress and pauses.
  5. Record the common prompt (60 s). Listen once, noting only stress errors.
  6. Choose your five worst-stressed words and add them to a pronunciation list; check each in an online dictionary's audio (Cambridge Dictionary or Oxford Learner's Dictionaries) or on YouGlish.

Self-check

  • I chose my menu from data, not preference.
  • I did at least three takes and compared them.
  • The metric I targeted (fillers, seconds to point, stress errors) is recorded.
  • I can name the single change that improved my delivery most.
  • I wrote it in my log.

Day 4 — Idioms & phrasal verbs: Idiom review round

⏱ 20 min · Thu · Five earlier idioms, chosen as the most useful to keep.

Expression Meaning Example
loop back To return to someone later with an update or follow-up, after a gap. Informal-neutral, US and UK business. Let's loop back on Thursday once we have the vendor's answer.
a back-of-the-envelope (figure) A rough, quickly made estimate or calculation. Informal, US and UK. Can you give me a back-of-the-envelope figure for the migration cost?
tip the scales To be the deciding factor that changes an outcome. Informal to neutral, US and UK. Refactoring that helper won't tip the scales on latency.
on tap Planned and ready to happen soon. Informal, US and UK. We have three carrier integrations on tap for Q1.
anyone's guess Completely uncertain; impossible to know or predict. Informal, common. The launch date is anyone's guess until the vendor confirms.

Exercise (6 items, timer 8 minutes)

  1. Choose: "Give me a (napkin / back-of-the-envelope / stadium) figure for the cost."
  2. Fill: "That optimization won't ______ the ______ on p99 latency." (tip the scales)
  3. Rewrite idiomatically: "We haven't decided the launch date yet."
  4. Rewrite idiomatically: "We have several features planned for next quarter."
  5. Choose the best: "I'll (hit the ball / loop back / tip the iceberg) with you on Friday."
  6. Which is riskier in a formal report: back-of-the-envelope figure or on tap? Why?
Answers and explanations
  1. back-of-the-envelope.
  2. tip / scales.
  3. "The launch date is anyone's guess."
  4. "We have several features on tap for next quarter."
  5. loop back.
  6. Back-of-the-envelope figure is more informal; in a formal report write "approximate estimate". On tap is informal too, and reads as jargon; prefer "planned" in formal writing.

When NOT to use them

Do not use more than one idiom per sentence, and avoid loop back with senior executives you do not know well; some find it jargon. Check that non-native colleagues know anyone's guess: they may take it literally.

Day 5 — Writing: Free choice: your weakest writing area

⏱ 20 min · Fri · 5 min diagnosis, 12 min menu, 3 min compare.

Diagnostic: pick your weakest writing area (5 min)

Pull your last three written pieces (an email, a doc paragraph, a status update). For each, measure: (1) word count against a version cut by 30%; (2) words before the main point or ask; (3) tone: highlight every phrase that could be read as blunt or as over-apologetic. Also check your Week 24 email rubric scores (purpose early, concision, precision, accuracy, tone).

  • If concision was your lowest or the 30% cut removed a lot: Menu A.
  • If tone scored lowest or colleagues have reacted badly to your phrasing: Menu B.
  • If the main point came late (over two lines) or the piece is hard to skim: Menu C.

Draft (63 words): I just wanted to reach out to you to let you know that we are currently in the process of looking into the issue that you raised with us last week regarding the delay in the tracking updates, and I would like to say that we will be able to provide you with a further update on this matter at some point later on this week.

Task: cut to 25 words or fewer, keeping the meaning and a specific commitment. Invent a day.

Model answer

We are investigating the tracking-update delay you reported and will send you an update by Thursday. (18 words)

Changes: removed the opening ("I just wanted to reach out"), cut "currently in the process of looking into" to "are investigating", removed "regarding... matter", replaced "at some point later on this week" with a real day. Every cut removed a filler; the commitment became specific.

Draft: This is wrong. You didn't consider the failure case, and I don't see how this could have passed review. Fix it before we go on.

Task: rewrite to a peer, firm but collaborative, three sentences maximum.

Model answer

I think the design misses the failure case: if the queue is full, requests are dropped silently. Could we add a retry path and a dead-letter queue before the next review? Happy to pair on it this afternoon.

Changes: I think and the description of the concrete problem replace an accusation; a question (Could we...) and a specific fix replace "Fix it"; an offer to help changes the relationship from judge to colleague. The content stays as firm as before: the problem is named and a change is requested.

Draft: Last month we started the integration with the new carrier and there were some difficulties with the API because the documentation was outdated. The team worked on it and then another problem came up with authentication. We now have a plan and I think it will be fine but we need two more engineers for three weeks, otherwise we will miss the 15 December date.

Task: rewrite in 3 sentences with the ask first.

Model answer

I need two more engineers for three weeks to keep the carrier integration on track for 15 December. Without them, we will miss that date. The delay comes from outdated API documentation and an authentication problem, both now understood and planned for.

Changes: the ask and the consequence come first (BLUF); the history is compressed into one sentence; "I think it will be fine" is replaced by a concrete statement (understood and planned).

Day 6 — Speaking record: Free choice: your weakest speaking area, 2-minute talk

⏱ 20 min · Sat · 3 min prep, 2 min record, 5 min replay and score, 8 min shadowing, 2 min log.

Prompt. Record a two-minute talk on the topic: "The most important thing I have learned about communicating as an engineer, and how I would teach it to a new joiner." Apply your Day 3 menu deliberately: if fluency, use pauses not fillers; if structure, use PREP or the pyramid; if pronunciation, monitor stress on your five worst words.

Structure. 0:00 main point; 0:10 reason; 0:30 example from your work; 1:15 what you would teach in one sentence; 1:40 close.

Rubric (score each 1-4; total /24)

Criterion 1 2 3 4
Clarity Listener lost Point recoverable Clear; minor detours Effortless
Structure No visible structure Partial Clear structure Clear structure and signposts
Fluency Long pauses and restarts Noticeable hesitation Occasional hesitation Smooth, natural rhythm
Grammar accuracy Errors block meaning Frequent errors Occasional errors Rare errors
Vocabulary range Repetitive Some variety Good range Precise and varied
Pronunciation Hard to follow Intelligible with effort Mostly clear Clear stress and rhythm

Shadowing task (8 min). Choose a short clip from a TED talk about communication, or a BBC Learning English "6 Minute English" episode; shadow 60 seconds twice and record the last attempt. Compare the target criterion with Week 24.

Log your score: Week 25 record: __/24 · target criterion: ______ (Week 24: __ → now __) · recording file: ______.

Day 7 — Soft skills + weekly review: Free choice: your weakest soft skill

⏱ 20 min · Sun · 4 min diagnosis, 8 min menu, 5 min recap, 3 min self-score.

Diagnostic: pick your weakest soft skill (4 min)

  1. Open your Week 24 self-assessment. Compute the average of each 6-item block: speaking and listening, structure and clarity, language, influence and relationships, executive communication.
  2. Look at the four lowest single items (rated 1 or 2) and the gap between your self-rating and a colleague's rating of items 4, 7, 19, 21 and 25 (if you collected it).
  3. Choose the menu: items 19, 22, 23, 24 (disagree, say no, de-escalate, culture) to Menu A; items 20, 21, 4, 5 (feedback and listening) to Menu B; items 25-30 (executive communication) to Menu C.

Scenario: a product director insists on a launch date your team cannot meet safely, and raises his voice in a meeting. Task: write your first three sentences: acknowledge, disagree with a reason, propose an alternative.

Model response and annotation

I can see how important this date is for you, and I want to help you meet the underlying goal. I can't commit to the 12th safely: the payment integration has two unresolved failures, and a rollback would cost us more than a one-week delay. What if we launch the core flow on the 12th behind a flag for 10% of customers, and complete the rest by the 19th?

Techniques: validation first (lowers the temperature), reason not opinion, alternative that serves his goal, calm and slow voice.

Scenario: a junior engineer's design review was poor and defensive. Task: write three sentences in SBI (situation, behavior, impact) plus a question.

Model response and annotation

In yesterday's design review (situation), when three people asked about the failure case, you moved to the next slide without answering (behavior). It left the room unsure whether you'd considered it, and it weakened an otherwise strong design (impact). What was going through your mind at that point?

Techniques: specific time and place, observable behavior with no judgment of character, stated impact, and an open question that invites their view.

Scenario: your VP asks, in a hallway, "Where are we on the carrier migration?" You have 30 seconds. Task: script it.

Model response and annotation

On track for 15 December, with one risk. Eight of ten carriers are live; the two remaining depend on one vendor fix due Friday. If it slips, I'll tell you by Monday and propose a reduced launch. No decision needed from you now.

Techniques: headline first, numbers, one risk with a trigger date, and an explicit "what I need from you" (nothing).

Weekly recap (20 items)

Answer aloud, then open the answers.

  1. How do you weight an error cluster?
  2. What is the correct verb form in "A range of options ___ available"?
  3. Which conditional has had in the if-clause and would have in the main clause?
  4. Give a passive reporting structure for "People say the vendor is late."
  5. Define unvarnished.
  6. Define meticulous and give a collocation.
  7. Difference between prudent and circumspect?
  8. What does pre-empt mean?
  9. What does a back-of-the-envelope figure mean?
  10. What does tip the scales refer to?
  11. On tap means?
  12. Anyone's guess means?
  13. What is the target for fillers per minute?
  14. What is PREP?
  15. In BLUF, what comes first?
  16. What is SBI?
  17. Name one technique for disagreeing without damage.
  18. What should a 30-second executive update contain?
  19. Which cluster in your list is the highest score, and what is your trigger sentence?
  20. What is the one thing you will do differently in the next 30 days?
Answers
  1. Times repeated x impact (1-3). 2. are. 3. Third conditional. 4. The vendor is said to be late. 5. Plain and direct, not softened or exaggerated. 6. Very careful about detail; meticulous attention to detail. 7. Circumspect is more cautious and reserved, especially in what you say. 8. To act in advance to prevent a problem or answer an objection. 9. A rough, quickly made estimate. 10. Being the deciding factor that changes an outcome. 11. Planned and ready to happen soon. 12. Completely uncertain. 13. Under about 3 (a personal target: fewer than in the baseline). 14. Point, Reason, Example, Point. 15. The bottom line: the ask or conclusion. 16. Situation, Behavior, Impact. 17. Validate first, give a reason, propose an alternative. 18. Status headline, key numbers, one risk with a date, the ask. 19-20. Personal answers.

Self-score

  • I chose each area by data from my log, not preference.
  • I improved at least one measurable metric (fillers, cut words, restarts, seconds to the point).
  • I logged a trigger sentence for my top grammar cluster.
  • My Day 6 recording scored at least what it did in Week 24.
  • I know what my Week 26 consolidation will target.

Error log prompt. Write down your top 3 recurring mistakes from this week. Mark which of the three now occur less often than at baseline, and which have not moved. Week 26 uses the ones that have not moved.