Project Manager
PMs communicate constantly — in Slack, Jira, Google Docs, and board presentations. This path focuses on status updates, meeting facilitation, scope negotiation, and managing stakeholder expectations.
Topics covered
- OKRs & KPIs
- Roadmap language
- Stakeholder updates
- Risk communication
- Retrospective facilitation
Vocabulary spotlight
4 terms every Project Manager should know in English:
The gradual, uncontrolled expansion of project scope beyond original boundaries
"Three new requirements added after sign-off — we have significant scope creep."
The amount of work a team completes in a sprint, measured in story points
"Average velocity dropped from 45 to 30 points — we need to investigate blockers."
Tracking document for Risks, Assumptions, Issues, and Dependencies
"The third-party API dependency is already in the RAID log."
To remove a feature from a release to meet a deadline or stay within budget
"We'll need to descope the export feature for v1 to hit the launch date."
📚 Vocabulary Reference
Key terms organised by category for Project Managers:
Agile & Scrum
Stakeholder Communication
Estimation & Planning
Reporting
Recommended exercises
Real-world scenarios you'll practise
- Writing a weekly status update for executive stakeholders
- Facilitating a retrospective with a cross-functional team
- Negotiating scope reduction with a stakeholder
- Presenting a risk register update to the project board
- Communicating a delivery delay to a senior stakeholder — maintaining trust while being transparent
🎯 Interview questions specific to this role
Practise answering these questions out loud — or in writing. Each question targets a real interviewer concern for Project Managers.
- How do you handle a situation where a stakeholder keeps adding requirements mid-sprint?
- Describe a time you had to communicate bad news to a senior stakeholder.
- How do you prioritise the backlog when everything seems urgent?
- What does a good Definition of Done look like in your experience?
- How do you build relationships with an engineering team as a PM?
Recommended reading
Frequently Asked Questions
What English skills do Project Managers most need to improve?+
Project Managers most commonly need to improve: technical vocabulary (the correct English terms for domain concepts), collocation accuracy (using the right verb for each action), written communication (bug reports, PR descriptions, technical docs), and spoken communication for standups, code reviews, and stakeholder meetings.
How long does the Project Manager learning path take?+
The Project Manager learning path contains 20–40 hours of material studied comprehensively. Most learners focus on the highest-priority modules first and return to the rest over time. Spending 30 minutes per day for 4–6 weeks produces noticeable improvement in workplace English.
What vocabulary should a Project Manager prioritise first?+
Start with the vocabulary that appears most in your daily work — terms you read in documentation, use in commit messages, and hear in meetings. The Project Manager path begins with the most frequent vocabulary clusters before moving to advanced communication patterns.
Are there interview exercises for Project Manager roles?+
Yes. The Project Manager path includes role-specific interview question modules with model answers and key phrases — the actual questions interviewers ask and the vocabulary needed to answer them fluently. There is also a dedicated Interview Practice hub for general interview skills.
Does this path include pronunciation help?+
Yes. The path links to pronunciation exercises for the technical terms most commonly mispronounced in this domain. The Pronunciation hub includes drills for acronyms, silent letters, word stress, and minimal pairs — all in IT context.
What are the most common English mistakes Project Managers make?+
The most common mistakes: incorrect collocations (using the wrong verb with a technical noun), false friends from L1, tense errors when narrating past incidents or walkthroughs, and using overly formal or overly casual register in written communication.
How do I improve my English for code reviews?+
Learn the standard code review collocations: approve a PR, request changes, leave a nit, address feedback, block a merge, resolve a conversation. Use hedging language for suggestions: "This might be cleaner as…", "Have you considered…?". The Collocations section includes a dedicated Code Review set.
Can I use this path alongside my daily work?+
Yes — the path is designed for working professionals. Each exercise set takes 10–15 minutes. The most effective approach is to study a vocabulary module before a meeting or task where you'll use that vocabulary, then practise immediately after. Context-linked practice produces much faster retention.
Is the content free?+
Yes, completely free. No registration required, no payment, no time limit. All vocabulary modules, exercises, glossary entries, and learning path guides are open access.
How do I track my progress through this path?+
Progress is tracked in your browser's local storage — completed exercise sets are marked with a checkmark when you return. No account is needed. You can bookmark specific modules and use the exercises overview to see which sets you've completed.