Skip to content

Week 26 — Consolidate and set your next goals

This week

Grammar: Free choice: consolidate · Vocabulary: Free choice: consolidate · Idioms & phrasal verbs: Idiom review round · Speaking: Free choice: consolidate · Writing: Free choice: consolidate · Soft skill: Set your next 6-month communication goals

Last week of the communication track. Light week (20 minutes a day). Week 25 attacked your weakest area; Week 26 consolidates: you turn what improved into habit and lock in what has not yet moved. Each day gives a short method to decide what to consolidate, then three menus; do one per day. Have open docs/log/comm-errors.md, docs/log/comm-baseline.md and your Week 24 and Week 25 notes.

Day 1 — Grammar: Free choice: consolidate

⏱ 20 min · Mon · 5 min method, 10 min menu (timer), 5 min check and use it.

Rule in 60 seconds: what to consolidate

  1. From your Week 25 error-log prompt, list the errors that have not moved. Those are your priority.
  2. Test each with a cold check: produce a correct sentence about your work in 10 seconds, without preparation. If you fail, it is not yet a habit.
  3. Choose the menu by the kind of consolidation you need:
    • Menu A (timed mixed correction) when errors appear under speed: your slips.
    • Menu B (production from real work) when you know the rule but do not produce it spontaneously.
    • Menu C (rule teach-back) when you still cannot state the rule; explaining forces precision.
  4. Habit test. An error is consolidated when you notice it yourself in an email or meeting before someone else does. Track how often you catch your own errors; that count is the real measure.

Exception: if your Week 24 grammar score was 36 or above, spend the week on style instead (Menu B, sentence variety) rather than accuracy drills.

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

  1. The number of incidents have dropped since we introducing staged rollouts. (two errors)
  2. Had we knew about the limit, we would chosen a different design. (two errors)
  3. She suggested adding a retry, which it was a good idea.
  4. Not only the deployment failed, but the rollback also didn't work.
  5. I look forward to see the results of the review.
  6. The team, that I lead, is responsible for the tracking data.
Answers and explanations
  1. The number of incidents has dropped since we introduced staged rollouts. The number of takes a singular verb; since + past simple for the starting event.
  2. Had we known about the limit, we would have chosen a different design. Inverted third conditional: past participle, and would have + participle.
  3. ...adding a retry, which was a good idea. Which is the subject of the clause; a second pronoun it is redundant.
  4. Not only did the deployment fail, but the rollback also didn't work. Inversion after Not only.
  5. I look forward to seeing... To is a preposition.
  6. The team, which I lead, is... Non-defining clause: which, not that.

Write six sentences about your own work. Each must use the named structure. Then check with the model column.

# Structure Model (yours will differ)
1 Narrative tenses (past continuous + past simple) We were migrating the booking service when the vendor announced the deprecation.
2 Third conditional If we had load-tested earlier, we would have caught the throughput problem.
3 Passive with a by-phrase omitted The connector was delivered three weeks late.
4 Participle clause Faced with a late connector, we cut scope.
5 Inversion Rarely have I seen a rollback go so smoothly.
6 Cleft (emphasis) What worried me most was the missing monitoring.
Checklist for your own sentences

A sentence passes if: it is about your real work; the tense matches the time reference; the structure is complete (for example, inversion has an auxiliary before the subject; participle clause subject matches the main clause subject); and you can say it aloud without stumbling. Rewrite any that fail and add the best to comm-errors.md.

  1. Suggest / recommend: which patterns follow them?
  2. Present perfect versus past simple: when do you use each?
  3. Uncountable nouns: three common in business and how to quantify them.
Model explanations
  1. Suggest and recommend take an -ing form or a that-clause, never to + infinitive. "I suggest using a queue" or "I suggest that we use a queue." Wrong: "I suggest to use a queue."
  2. Past simple for a finished time; present perfect for a link to now or an unfinished period. "We released it on Monday" (finished). "We have released it" (result matters now). "We have worked on this for six months" (still true).
  3. Information, advice, feedback, equipment, software, evidence: no plural, no a/an. Quantify with some, a lot of, a piece of, an item of, a bit of: "a piece of advice", "some feedback", "several pieces of evidence".

Use it

Say your habit-test result: how many of your own errors did you catch this week before anyone else? Write the number in your log.

Day 2 — Vocabulary: Free choice: consolidate

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

Method: spaced consolidation (5 min)

Vocabulary that is not retrieved is lost. Use a Leitner-style plan:

  1. Take all Word tables from Weeks 1-25 (or your Anki export).
  2. Sort into three boxes by a 10-second recall test (meaning + collocation + a work sentence): Box 1 fail, Box 2 partial, Box 3 solid.
  3. Spend 80% of the time on Box 1, and re-test on days 1, 3, 7 and 14, then monthly.
  4. Menu A if you need meaning recall; Menu B if you need context use; Menu C if you need active production.

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

Word Part of speech Meaning Example
delineate verb To describe or mark out precisely, especially boundaries or responsibilities. Formal. The RFC delineates which team owns the data and which owns the API.
vindicate verb To show, after doubt or criticism, that a decision, claim or person was right. Formal. The postmortem vindicated the on-call engineer's initial diagnosis.
reaffirm verb To state something again, firmly, to confirm it still holds. Formal-neutral. Let me reaffirm the constraint: no downtime during peak season.
bolster verb To support, strengthen or reinforce something. Formal-neutral. Reliable event delivery bolsters every customer-facing feature.
encapsulate verb To express the essential nature of something briefly; in engineering, also to enclose behind an interface. This sentence encapsulates our strategy: fewer systems, clearer ownership.

Collocations and word family

  • delineate: delineate responsibilities / boundaries / roles / scope; noun delineation. In writing, prefer it for ownership and scope; do not use for simple description.
  • vindicate: vindicate a decision / a claim / someone's judgment; noun vindication; adjective vindicated ("felt vindicated"). Do not confuse with vindictive (seeking revenge).
  • reaffirm: reaffirm a commitment / a decision / a policy; noun reaffirmation. Slightly more formal than repeat; used to firmly restate something that might be doubted.
  • bolster: bolster confidence / an argument / support / defenses; the participle bolstered by. Close synonym of underpin (Week 20), but bolster suggests strengthening something already standing, while underpin suggests forming its base.
  • encapsulate: encapsulate the essence / the idea; noun encapsulation (also OOP sense). Verb + object: it is not "to encapsulate about".

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

Match each word to its meaning: 1 mitigate 2 spearhead 3 blast radius 4 ramification 5 contingent 6 candid a) dependent on an uncertain factor b) honest and direct c) to reduce severity d) to lead an initiative from the front e) the extent of damage if something fails f) a consequence, often complex

Answers

1 c · 2 d · 3 e · 4 f · 5 a · 6 b

  1. The document must ______ which team owns the data and which owns the API.
  2. We could not ______ the claim without logs from that week.
  3. I want to ______ the constraint: no downtime in the peak season.
  4. Automated testing ______ our ability to release daily.
  5. Review: a ______ approach means testing the failover before peak. (prudent / candid)
  6. Review: the launch is ______ on the vendor delivering the fix. (contingent / pivotal)
Answers
  1. delineate. 2. vindicate. 3. reaffirm. 4. bolsters. 5. prudent. 6. contingent.

Write a 5-sentence handover note (about 70 words) about a project you are leaving, using at least four of: delineate, vindicate, reaffirm, bolster, encapsulate, contingent, pivotal.

Model answer

The handover document delineates ownership: the platform team keeps the event pipeline; the product team owns the customer API. The architecture is bolstered by idempotent consumers, which is what lets us replay events safely. I must reaffirm one caveat: the December launch is contingent on the vendor's connector fix. The vendor's throughput claim is not yet vindicated, so please keep the load test in the release checklist. (61 words)

Check yours: at least four target words, each with a natural collocation; no word forced.

Use it

Say aloud the sentence in Menu C that you like best. Add any word you fumbled to Box 1.

Day 3 — Speaking: Free choice: consolidate

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

Method (5 min)

  1. Listen to your Week 0 baseline recording (first 60 seconds) and your Week 25 recording (first 60 seconds). Note three concrete differences: pace, fillers, structure, pronunciation.
  2. Choose the consolidation:
    • Menu A (re-record an earlier prompt) to lock in the improvement in one criterion.
    • Menu B (a 3-minute mini presentation) to test sustained delivery.
    • Menu C (tough Q&A) to test performance under pressure.
  1. Choose the prompt where you scored lowest in Weeks 21-25: STAR (Week 21), design narration (Week 22), career narrative (Week 23).
  2. Record it in 90 seconds, applying the one change that worked best in Week 25.
  3. Compare the new take against the old on the one criterion you targeted.
  4. Record a second take without the notes; the second take shows what has become habit.
  5. Write down the difference in seconds to the main point and in fillers per minute.
  6. Keep the better take as your "benchmark" recording for the next 6 months.
  1. Topic: "One thing our platform should do differently in the next year, and why." (Pick a real one.)
  2. Structure: point (15 s), problem with a number (30 s), proposal (60 s), trade-off (40 s), ask (25 s), one-line close (10 s).
  3. Rehearse once, record once. No slides.
  4. Count how many times you looked for a word; note them.
  5. Rewrite the three weakest sentences and re-say them.
  6. Check the time: 3 minutes plus or minus 15 seconds.

Answer each aloud. Use: acknowledge, answer, evidence, stop. 1. "Why did this take so long?" 2. "What if you're wrong about the root cause?" 3. "Why should we fund this instead of the alternative?" 4. "I don't think that's realistic. Convince me." 5. "What would you do differently?" 6. "What is the biggest risk, and what will you do about it?"

Pronunciation micro-drill (all menus, 2 min). Say five times: "The main risk is the vendor's deadline." Stress the content words (MAIN RISK, VENdor's DEADline); reduce the, is, the. Then the linking: "risk is" runs together (ris-kiz).

Self-check

  • I chose the menu based on the recordings I compared.
  • I can name at least three concrete differences from my baseline.
  • My delivery in the second take was smoother than the first.
  • I saved a benchmark recording.
  • I logged the number for the metric I targeted.

Day 4 — Idioms & phrasal verbs: Idiom review round

⏱ 20 min · Thu · Five more earlier idioms, chosen for use in negotiation and status talk.

Expression Meaning Example
find common ground To identify shared interests or points of agreement as a basis for compromise. Neutral, US and UK. We found common ground: we'll deliver the core in October and the rest in December.
a non-starter An idea or plan that has no realistic chance of being accepted or working. Neutral to informal. A full rewrite is a non-starter this year; we must refactor incrementally.
the path of least resistance The easiest course of action, requiring the least effort or conflict. Neutral, sometimes mildly critical. Caching the static lookups is the path of least resistance for latency.
a house of cards A plan or structure that looks fine but is fragile and could collapse if one part fails. Neutral to literary. The migration plan is a house of cards: if one vendor slips, every date moves.
just scratching the surface Dealing with only a small part of a much larger issue. Neutral, slightly dramatic. Those three tickets are just scratching the surface; the schema itself is the issue.

Exercise (6 items, timer 8 minutes)

  1. Fill: "After an hour of back-and-forth, we finally found common ______ on the release date."
  2. Fill: "A full rewrite is a ______ this quarter."
  3. Rewrite idiomatically: "These bugs are only the visible part of a much larger issue."
  4. Rewrite idiomatically: "There are too many separate components to give an exact date."
  5. Choose: "Let's take the (path of least resistance / path of most resistance / uphill path) and cache the static lookups first."
  6. Which idiom would be poor in a legal or contractual document, and why?
Answers and explanations
  1. ground. Find common ground is the fresh idiom this week; meet halfway (Week 4) is a close synonym. 2. non-starter. 3. "These bugs are just scratching the surface." 4. "This plan is a house of cards: too fragile to promise an exact date." 5. path of least resistance. 6. A house of cards, and most of the others: idioms are imprecise; contracts need literal wording.

When NOT to use them

The path of least resistance can sound like a criticism ("the lazy option"), so avoid it about someone else's decision in front of them. A house of cards signals alarm about fragility; use it only if you have evidence the plan really is that fragile. Do not use two idioms in the same sentence.

Day 5 — Writing: Free choice: consolidate

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

Method (5 min)

Take one real document you wrote in the last month. Run the three-pass edit: (1) cut 20-30%; (2) front-load the ask or conclusion in the first two lines; (3) check the six habits from your error log (articles, prepositions, verb patterns, agreement, tense, register). Pick the menu that matches the pass you find hardest:

  • Menu A cut hardest? Edit your own paragraph.
  • Menu B summarize hardest? Write an executive summary.
  • Menu C peer editing hardest? Edit a colleague's draft with comments.

Draft (60 words): In order to make sure that we are able to complete the project on time, it is really important that all of the teams involved in the project are able to provide us with their updated estimates for the remaining work by the end of the day on Friday, if at all possible.

Task: cut to 30-35 words.

Model answer

To finish on time, every team must send us updated estimates for the remaining work by Friday end of day. (19 words) A version closer to the original register: Please send updated estimates for your remaining work by Friday, end of day, so we can finish on time. (19 words)

Changes: "In order to make sure that we are able to" became "To"; "it is really important that" became "must"; "provide us with" became "send us"; the hedge "if at all possible" was cut (add it back only if the deadline truly is flexible).

Source: The tracking platform had three outages in Q3 (37 minutes, 2 h 10 min, 55 minutes), all traced to the same connection-pool setting. We fixed it in October and added an alert. Customer complaints fell 40%. Remaining risk: the failover path has not been tested at peak load. A test needs one engineer for a week and a two-hour window on a weekend in November.

Task: write a 50-word summary with the ask first.

Model answer

I need approval for a two-hour weekend test window in November and one engineer for a week to test failover at peak load. Three Q3 outages had one cause, a connection-pool setting, now fixed and alerted; complaints fell 40%. Untested failover is the remaining risk. (46 words)

Changes: the ask and the risk lead; the outage details are compressed to the cause and result; numbers that support the decision are kept (40%, week, two hours).

Colleague's draft: Hi team, the deployment tomorrow have been postponed because of the issues that was found in the testing. We will informed you the new date as soon as we know.

Task: correct the errors, and add one comment that helps the writer improve (not just a fix).

Model answer

Hi team, tomorrow's deployment has been postponed because of issues found in testing. We will let you know the new date as soon as we have it.

Comment: "Two agreement slips (has been, issues that were) and one missing form (will let you know). Suggestion: add the reason in one line and the next update time (for example, 'by 3 p.m. Thursday') so readers know when to expect news."

Changes: corrected have > has, that was found > found, will informed > will let you know / will inform you; the comment goes beyond corrections and teaches a habit (next-update time).

Day 6 — Speaking record: Free choice: consolidate, 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: "Where I started, what has changed in how I communicate, and what I will work on next." Use the arc: baseline (what you could not do) > evidence of change (one specific meeting, email or recording) > next target. Use at least one narrative tense, one achievement verb (Week 21), and one trade-off phrase (Week 22).

Structure. 0:00 main point ("I communicate more X than I did"); 0:15 baseline; 0:45 evidence with a number (fillers per minute, rubric score, words cut); 1:20 what remains; 1:45 next 6-month focus.

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). Pick a TED talk in which the speaker reflects on their own development (a "what I learned" talk), or a BBC Learning English "6 Minute English" episode; shadow 60 seconds twice and record the last attempt.

Log your score: Week 26 record: __/24 · Week 24: __/24 · Week 0: __/24 · recording file: ______. This is the last scored recording of the track; keep it as your benchmark.

Day 7 — Soft skills + weekly review: Set your next 6-month communication goals

⏱ 20 min · Sun · 8 min goals, 5 min recap, 4 min self-score, 3 min error log.

Method: derive goals from your data

Do not set goals from mood; derive them from the four comparison sources you already have:

  1. Baseline vs Week 24 tables: the areas that improved least.
  2. Error log: errors that have not moved after two rounds of fixes.
  3. Recordings: the rubric criterion averaging lowest over Weeks 21-26.
  4. Career plan: what your next role (Staff/Principal) will demand: writing RFCs, presenting to executives, interviewing others, mentoring.

A good goal is specific, measurable, dated and observed by someone else (a colleague, a recording, a document). Limit yourself to three goals (one accuracy, one visibility, one relationship).

Scenario. It is the last Sunday of the track. Your manager has asked you to send a one-paragraph "communication development plan" for the next six months as part of your Staff-engineer path. Task: write 120-150 words with three goals, each with a measure and a date, plus how you will check progress.

  • Menu A: accuracy goals. Example: "Reduce my top-3 errors to under one per 1,000 words in emails, checked monthly by sampling 5 emails." Measure: sampled error counts.
  • Menu B: visibility goals. Example: "Give one 10-minute talk to another team by March and publish one RFC by April." Measure: delivered, with written feedback.
  • Menu C: relationship goals. Example: "Hold one candid feedback conversation a month with a peer, using SBI." Measure: a note after each conversation.
Model response and annotation

Over the next six months I will focus on three goals. First, accuracy: I will bring my three most frequent errors (articles, "suggest to", tense with finished time markers) below one per 1,000 words, measured on five sampled emails a month, starting with the November sample. Second, visibility: I will present a ten-minute design talk to the payments team by January and publish one RFC by March, with written feedback from two reviewers. Third, relationships: I will run one structured feedback conversation a month with a peer or report, using SBI, and note what changed. I will re-record the Week 26 talk in April and compare rubric scores, and I would welcome your view on the plan at our next one-to-one.

Techniques: three goals only (focus); each has a number or an event and a date (measurable); each has an external observer (feedback, sampling); a scheduled re-test keeps the plan alive; a request for the manager's input turns the plan into a joint one.

Weekly recap (20 items)

  1. Which errors do you consolidate first?
  2. What is the habit test for an error?
  3. Correct: The number of incidents have dropped.
  4. Correct: Had we knew about it...
  5. Correct: I look forward to see you.
  6. Correct: The team, that I lead, is...
  7. Complete: Not only ___ the deployment fail...
  8. Define delineate.
  9. Define vindicate and its noun.
  10. What does reaffirm add compared with repeat?
  11. Bolster: give a collocation.
  12. Define encapsulate (two senses).
  13. What does find common ground mean?
  14. What does a non-starter mean?
  15. What is the path of least resistance?
  16. What does a house of cards refer to?
  17. What does just scratching the surface signal?
  18. What are the three passes of the edit method?
  19. What makes a communication goal good?
  20. What will you do on the first Sunday of next month?
Answers
  1. Errors that have not moved after two rounds of fixes. 2. You notice and fix it yourself before anyone else does. 3. has dropped. 4. Had we known... 5. seeing. 6. which I lead. 7. did. 8. To describe or mark out precisely, especially boundaries. 9. To show a claim or decision was right, after doubt; noun vindication. 10. It firmly confirms a point still holds, often because it was doubted or not heard. 11. Bolster confidence / an argument. 12. To express the essence briefly; in engineering, to hide detail behind an interface. 13. To identify shared interests as a basis for compromise. 14. An idea with no realistic chance of being accepted or working. 15. The easiest course of action, with least effort or conflict. 16. A plan that looks fine but is fragile and could collapse if one part fails. 17. Dealing with only a small part of a much larger issue. 18. Cut, front-load, check the six habits. 19. Specific, measurable, dated and observed by someone else. 20. Personal answer: for example, re-check the three goals and sample five emails.

Self-score

  • I decided what to consolidate from data (logs and recordings), not preference.
  • I recorded my habit-test result for grammar.
  • I moved at least five words from Box 1 to Box 2 or 3.
  • My Week 26 recording scored at least what it did in Week 24.
  • My six-month plan has three goals, each with a measure, a date and an observer.

Error log prompt. Write down your top 3 recurring mistakes, and the three you will keep working on during the next 6 months. Copy them to the front of docs/log/comm-errors.md. Set a calendar reminder for the first Sunday of each month: sample five emails, count these errors, and update the log.

Track complete

You have finished 26 weeks of communication drills. Keep the routine: 30 minutes a week on your top-three errors, one recorded talk a month, and a full re-test in six months (repeat the Week 24 instruments so the record continues).