Skip to content

Week 16 — Consolidation checkpoint: error review, 100-word check, pitch

This week

Grammar: mixed error review (your personal error log) · Vocabulary: review and 100-word check (plus five new words: ostensibly, tenable, fast-track, germane, tacit) · Idioms & phrasal verbs: idiom review round (plus five new: on the back burner, bite the bullet, a double-edged sword, cut corners, the elephant in the room) · Speaking: a 5-minute pitch · Writing: the one-pager · Soft skill: executive presence

Checkpoint comm-4. This is a consolidation week. On Day 7, record your scores (100-word check, Saturday rubric, error-log count) as your comm-4 checkpoint evidence, and compare with the previous checkpoint.

Day 1 — Grammar: mixed error review (your personal error log)

⏱ 30 min · Mon

Rule in 60 seconds

Fluent speakers do not fail on grammar they have never seen; they fail on a small set of fossilized errors that they repeat under pressure. The fastest gain is to find your own list and drill only that.

Method (10 minutes):

  1. Open the error logs from weeks 1-15 (your Sunday "top 3" lists) and your recorded talks.
  2. Group errors into buckets: articles, prepositions, tense/aspect, agreement, word order in questions/embedded questions, verb patterns (suggest doing, explain to), uncountables, false friends.
  3. Choose your top 3 buckets. Write the correct pattern next to a real sentence of yours.
  4. Every day this week, say the three corrected sentences before you start work.

Ten patterns fluent speakers repeatedly get wrong (check which are yours): since/for needs present perfect; discuss/explain/suggest have fixed patterns; information/feedback/advice/equipment are uncountable; embedded questions use statement word order; if clauses do not take would; responsible for (not "of"); whose (possession) versus who's (who is); on Monday (not "in Monday"); "explain something to someone"; "look forward to + -ing".

Exercise

Correct each sentence (one error each). The items mix patterns from weeks 1-15; your own log takes priority over this list.

  1. "I am working on this service since 2019."
  2. "We discussed about the migration plan yesterday."
  3. "The informations from the vendor are incomplete."
  4. "Can you explain me the failure mode?"
  5. "If we would have more time, we would test it properly."
  6. "She suggested to postpone the release."
  7. "Nobody knows where is the config file."
  8. "The team is responsible of the outage."
  9. "The review is in next Monday."
  10. "He is the engineer who's design was approved."
Answers and explanations
  1. "I have been working on this service since 2019." Since with an ongoing situation requires present perfect (continuous), not present simple/continuous.
  2. "We discussed the migration plan." Discuss is transitive; no about. (You can "have a discussion about".)
  3. "The information from the vendor is incomplete." Uncountable: no plural, singular verb.
  4. "Can you explain the failure mode to me?" Explain takes the indirect object with to.
  5. "If we had more time, we would test it properly." No would in the if clause.
  6. "She suggested postponing the release" or "suggested that we postpone the release." Suggest does not take to + infinitive.
  7. "Nobody knows where the config file is." Embedded questions use statement word order.
  8. "responsible for": fixed preposition.
  9. "on Monday" or "next Monday" (without a preposition). "In next Monday" is not possible.
  10. "whose design": possessive relative pronoun; who's is a contraction of "who is/has".

Use it

Write your top three personal errors, each with the corrected sentence about your real work, and post them somewhere you see daily (phone lock screen, monitor note). Say the three corrected sentences aloud now.

Day 2 — Vocabulary: review and 100-word check

⏱ 30 min · Tue

Part A: five new words

Word Part of speech Meaning Example
ostensibly adverb Apparently or officially, but perhaps not in reality "The change was ostensibly a performance fix, but it also removed a feature customers relied on."
tenable adjective Able to be defended or maintained against criticism "Running two data centers for a single workload is no longer a tenable position."
fast-track verb To make something happen or be approved faster than the usual process (informal to neutral, common in business English) "We paid for an express security review to fast-track the release."
germane adjective Relevant to the matter being discussed; formal "The only germane finding of the audit is that no access was ever revoked."
tacit adjective Understood or implied without being stated "There is a tacit agreement that the on-call engineer owns the rollback."

Collocations: ostensibly for/to (ostensibly for security reasons); a tenable position / argument / assumption, and its opposite untenable; fast-track a request / a shipment / an approval; germane to the discussion / point / question; tacit knowledge / agreement / approval / understanding. Pronunciation: os-TEN-si-bly, TEN-a-ble, FAST-track, jer-MANE, TAS-it.

Part B: the 100-word check

Below are 100 C1 business words in five blocks of 20. It includes headline words from weeks 7-15 and general C1 vocabulary. For each word give yourself 2 if you can use it in an accurate sentence of your own, 1 if you recognize it but would hesitate to use it, 0 if you do not know it. Maximum 200.

  • Block 1 (analysis): roughly, approximately, marginally, materially, consequently, whereas, hinge on, compelling, tangible, rationale, anomaly, granular, corroborate, outlier, cohort, substantiate, extrapolate, correlate, skew, baseline.
  • Block 2 (strategy): leverage, trajectory, headwinds, mandate, remit, accountable, incumbent, differentiator, pivot, scalable, sustainable, viable, feasible, contingency, dependency, prerequisite, milestone, deliverable, constraint, alignment.
  • Block 3 (negotiation and influence): concession, deadlock, reciprocate, contingent, entrenched, concede, stipulate, leverage (again: use it in a negotiation sentence), stakeholder, buy-in, consensus, compromise, ultimatum, mediate, arbitrate, endorse, advocate, sponsor, dissent, reservations.
  • Block 4 (change and risk): mitigate, de-risk, unblock, champion, escalate, deprecate, migrate, decommission, remediate, contain, cascade, degrade, regress, exacerbate, precipitate, forestall, avert, pre-empt, safeguard, contingency plan.
  • Block 5 (style and precision): nuance, ambiguity, concise, verbose, redundant, cohesive, coherent, articulate, elaborate, clarify, reiterate, summarize, paraphrase, caveat, qualify, emphasize, downplay, overstate, underscore, distill.

Scoring guide

Score Interpretation Action
170-200 Strong active C1 range Focus on collocation and register; stop drilling isolated words
130-169 Solid working range, some passive words Turn every 1-score word into a sentence about your work
90-129 Wide passive, narrow active vocabulary Use each 1-score word aloud three times this week
below 90 Gaps in core vocabulary Prioritize words scored 0, five per day, with example sentences

Write your 0-score and 1-score words into a personal weak-word list; Week 23 revisits it.

Collocations and word family (short list)

  • exacerbate a problem; precipitate a crisis; forestall an outage; remediate vulnerabilities; stipulate in the contract that.
  • Word family: tenable / untenable; tacit / tacitly; germane (no common derived forms; near-synonym relevant); fast-track (also used as an adjective and noun, the fast track); ostensible / ostensibly.

Exercise

Cloze. Word bank: ostensibly, tenable, fast-track, germane, tacit, accountable, entrenched, corroborate.

  1. The vendor's delay was ______ caused by a customs issue, but the invoice suggests otherwise.
  2. After the third outage in a month, the current on-call model is no longer ______.
  3. Can we ______ the legal review? The launch slips a week if we wait.
  4. Which point is more ______ to this postmortem: the missing alert or the missing owner?
  5. There is a ______ assumption that senior engineers approve their own changes; let's make it explicit.
  6. Each service owner should be ______ for their error budget.
  7. The audit logs ______ what the customer reported.
  8. The old routing rules are so ______ that nobody dares to touch them.
Answers and explanations
  1. ostensibly: officially claimed, but doubted.
  2. tenable: cannot be defended any more.
  3. fast-track: speed up the process.
  4. germane: relevant to the matter at hand.
  5. tacit: unspoken.
  6. accountable (week 13): answerable for results.
  7. corroborate (week 8): confirm with evidence.
  8. entrenched (week 14): firmly established, hard to change.

Use it

Say three sentences about your work using ostensibly, tenable and germane. Then re-score any word from the 100-word check that you have just used correctly.

Day 3 — Speaking: a 5-minute pitch

⏱ 30 min · Wed

Prompt. Pitch a platform investment (for example, a shared event-streaming layer) to a VP who has 5 minutes and no technical background. Deliver a two-minute practice version today (the full 5 minutes is Saturday's recording).

Structure: H-P-S-P-A (Hook, Problem, Solution, Proof, Ask)

  1. Hook (20 s): a surprising number or a customer moment: "Last month 1 in 8 booking updates reached the customer more than an hour late."
  2. Problem (40 s): cost of the current situation in business terms.
  3. Solution (60 s): what you propose, in one sentence, then how it works in plain language.
  4. Proof (60 s): evidence: a pilot, benchmark, comparable company.
  5. Ask (20 s): exact decision and date.

Use the rule of three for emphasis, and pause for two seconds before the ask.

Pronunciation micro-drill: stress shifts with suffixes

Stress moves when the suffix changes; practise the sets:

Word Related forms
e-CON-o-my eco-NOM-ic, e-CON-o-mist
AN-a-lyze a-NAL-y-sis, an-a-LYT-ic
STRAT-e-gy stra-TE-gic
re-spon-si-BIL-i-ty re-SPON-si-ble
or-gan-i-ZA-tion OR-gan-ize

Say each row, then a sentence: "The analysis shows the economy of scale is strategic."

Self-check - [ ] The hook was a fact, not "Hi, I'm going to talk about...". - [ ] Each section had a clear transition ("So what does this mean?", "Here's the proof"). - [ ] I paused before the number and before the ask. - [ ] I stayed inside the time limit without speeding up. - [ ] My suffix-stress words were correct (eco-NOM-ic, a-NAL-y-sis).

Day 4 — Idioms & phrasal verbs: idiom review round

⏱ 30 min · Thu

New idioms (five), then a review mix.

Expression Meaning Example
on the back burner Postponed; low priority for now. Informal, neutral tone. "The logging cleanup is on the back burner until Q1."
bite the bullet To do something unpleasant that cannot be avoided, decisively. Informal; common in the US and UK. "We bit the bullet and rewrote the auth module."
a double-edged sword Something with both benefits and drawbacks. Neutral; suitable in formal writing. "Microservices are a double-edged sword: more autonomy, more operational overhead."
cut corners To skip steps to save time or money, usually reducing quality. Negative; never say of yourself in a good light. "We can't cut corners on the security review."
the elephant in the room An obvious problem everyone avoids mentioning. Informal but acceptable in meetings. "Let's address the elephant in the room: the timeline is unrealistic."

Exercise (8 items)

  1. Choose: "Automatic retries are ______; they hide errors but reduce user-visible failures." (a double-edged sword / on the back burner)
  2. Fill in: "We've delayed the migration too long; it's time to ______."
  3. Fill in: "Skipping load tests to hit the date means ______ on quality."
  4. Fill in: "Nobody mentioned the budget cut, the ______ in the room."
  5. Review: which phrasal verb (week 9) means to formally approve? (roll out / sign off / scale up)
  6. Review: "This outage is just the ______" (week 15 idiom).
  7. Review: "Please ______ the security team in the thread" (week 11 phrasal verb: loop in / flag up).
  8. Rewrite more idiomatically: "We decided to postpone the redesign and give it low priority."
Answers and explanations
  1. a double-edged sword: benefit and drawback.
  2. bite the bullet: do the unavoidable unpleasant thing.
  3. cutting corners (present participle).
  4. elephant ("the elephant in the room").
  5. sign off: formal approval; roll out is release, scale up is increase capacity.
  6. tip of the iceberg (week 15).
  7. loop in (week 11): include someone in communication; "flag up" means to draw attention to an issue.
  8. "We put the redesign on the back burner."

When NOT to use them: "elephant in the room" can feel confrontational if said about a specific person's decision; name the topic instead ("Can we discuss the timeline risk?"). Avoid cut corners in customer-facing text, as it implies negligence. In formal proposals prefer "postponed", "unavoidable decision", "trade-off".

Day 5 — Writing: the one-pager

⏱ 30 min · Fri

Bad draft (for a director who will decide in 2 minutes):

Subject: Observability

We have been thinking a lot about observability and how we do it now is not really working well. There are many tools and teams use different ones, which causes confusion and sometimes people can't find logs during incidents. It would probably be good to consolidate somehow. I've looked at a few tools and they all have pros and cons. We should discuss.

Task. Rewrite as a one-pager (around 180-220 words) with these headings: Recommendation, Why now, Options, Risks, Ask. It must be skimmable in two minutes, with numbers (invent plausible ones), one option rejected with a reason, and one named risk with mitigation.

Model answer

One-pager: Consolidate observability on one platform by Q2

Recommendation. Standardize on a single observability platform (logs, metrics, traces) by end of Q2 and retire the other four tools.

Why now. During incidents, engineers spend a median 17 minutes locating the right logs across five tools, and 3 of the last 5 sev-1 incidents lasted longer because of it. Licensing across tools costs about 620k dollars a year, of which roughly 200k is duplicated capability.

Options. 1. Consolidate on Platform A (recommended): covers all three signals, existing integration with our deployment pipeline; migration effort about 10 engineer-weeks. 2. Keep the status quo: no migration cost, but the incident-time penalty remains. 3. Build in-house: rejected; ongoing maintenance cost exceeds the license saving within 18 months.

Risks. Migration could disrupt alerting. Mitigation: run both platforms in parallel for six weeks and cut over per service.

Ask. Approve Platform A and 10 engineer-weeks by 15 October.

What changed and why: - Headings and order (recommendation first) make it skimmable; the director can decide after the first paragraph. - "Confusion" became a measured cost (17 minutes, 3 of 5 incidents, 200k duplication). - "Somehow" and "pros and cons" became named options with a rejection reason. - One risk with a mitigation shows you have thought beyond the pitch. - "We should discuss" became a dated ask.

Day 6 — Speaking record: the 5-minute pitch

⏱ 30 min · Sat

Record the full pitch. Deliver the platform-investment pitch from Wednesday in 5 minutes (record video if possible; executive presence includes posture and eye line). Add one anticipated objection and your answer.

Structure: Hook (20 s) - Problem (60 s) - Solution (90 s) - Proof (60 s) - Objection and response (40 s) - Ask (30 s).

Scoring rubric (1 to 4)

Criterion 1 2 3 4
Clarity Message unclear Point emerges late Clear main point Point is unmistakable and memorable
Structure No visible order Some order, jumps Clear sequence Signposted, timing controlled
Fluency Frequent stops/fillers Occasional long pauses Mostly smooth Smooth with deliberate pauses
Grammar accuracy Errors block meaning Frequent errors Few errors, no confusion Rare errors; top-3 log errors avoided
Vocabulary range Repeats basic words Some C1 words Good range Precise, varied, natural
Pronunciation Hard to follow Stress errors distract Generally clear Clear stress and rhythm

Shadowing task. Shadow two minutes from a strong pitch-style talk: a TED talk with a clear ask, or a Toastmasters-style speech (toastmasters.org has resources). Copy the pause before the key claim.

Log your score: total out of 24, plus how many of your top-3 error-log mistakes you heard in your own recording (aim for zero).

Day 7 — Soft skills + weekly review: executive presence

⏱ 30 min · Sun

Scenario. In a leadership review, the CFO interrupts your slide: "Your cost estimate feels 30 percent too low. Why should I trust this?" Eight senior people are watching. Your estimate is sound but based on one assumption you haven't mentioned.

Task. Script your reply in about 150 words: composed tone, answer first, evidence, and honest handling of the assumption. Do not become defensive.

Model response

[Pause for a beat; lower your pitch.] "That's a fair challenge, and I'd want to be able to defend it. Short answer: I believe the estimate is sound, and it depends on one assumption I should have put on the slide.

Here's the basis. We built the figure from actual costs on the last two comparable migrations: 14 and 16 engineer-weeks respectively. The assumption is that we reuse the existing payments adapter. If we have to rebuild it, add roughly 5 weeks, which brings the estimate closer to your number.

So the range is 15 to 20 weeks, and the low end is contingent on the adapter. I'll confirm that with the payments team by Thursday and send you the revised number. Does that address your concern?"

Techniques used: (1) A pause and lower pitch before answering signals calm. (2) Validate the challenge without conceding the point ("fair challenge"). (3) Answer first, then evidence. (4) Disclose the assumption yourself before it is exposed; this builds credibility. (5) Turn a single number into a range. (6) Commit to a follow-up date. (7) Close with a check question to return control.

Weekly recap (20 items)

  1. Correct: "I am working here since 2019."
  2. Correct: "Can you explain me the plan?"
  3. Correct: "Nobody knows where is the file."
  4. Which preposition follows "responsible"?
  5. Complete: "If we had more time, we ______ test it."
  6. "Suggest" is followed by -ing or to + infinitive?
  7. Define ostensibly.
  8. Opposite of tenable?
  9. What does fast-track mean?
  10. Which word means relevant to the matter at hand?
  11. What is tacit knowledge?
  12. Where is the stress in eco-NOM-ic?
  13. Name the pitch structure (five parts).
  14. "On the back burner" means...?
  15. "Bite the bullet" means...?
  16. Which idiom describes something with benefits and drawbacks?
  17. Why avoid "cut corners" in customer-facing text?
  18. Which phrasal verb means formally approve: sign off or scale up?
  19. In an interruption, what should you do before you answer to show composure?
  20. What should you do with a hidden assumption when challenged?
Answers
  1. "I have been working here since 2019." 2. "Can you explain the plan to me?" 3. "...where the file is." 4. for. 5. would. 6. -ing (or that-clause). 7. Apparently or officially, but perhaps not truly. 8. untenable. 9. To make a process happen faster than usual. 10. germane. 11. Understood but unstated. 12. The third syllable. 13. Hook, Problem, Solution, Proof, Ask. 14. Postponed, low priority. 15. Do something unpleasant but unavoidable. 16. A double-edged sword. 17. It implies negligence. 18. sign off. 19. Pause and lower your pitch. 20. Disclose it yourself and give a range.

Self-score - [ ] I have a personal top-3 error list and can correct all three on demand. - [ ] My 100-word check score is recorded, with my weak-word list started. - [ ] I delivered a 5-minute pitch within the time limit. - [ ] I can write a one-pager with a recommendation, options, risk and dated ask. - [ ] I recorded my comm-4 checkpoint numbers (100-word score, rubric total, log count).

Error log. Write down your top 3 recurring mistakes this week and note whether they are the same as last month's. If yes, that bucket is your priority for Week 18.