English training for teams
The default working language for most distributed teams — and the one where the gap between reading it and speaking it is widest.
The business case
English is where corporate language budgets mostly go, and where they are most often wasted. Staff who read technical documentation fluently can still be silent in a meeting, and that silence is usually mistaken for a lack of ideas rather than a lack of speaking practice.
Who it is for
Engineering and delivery teams working with overseas colleagues, client-facing staff who present or negotiate, and managers who need to run a meeting rather than sit in one.
How the programme runs
Identical structure whichever language you run — only the content and the objective change.
Cohorts by level
Everyone is placed before the term starts, so nobody sits through lessons pitched two levels away from them.
Fixed weekly slots
Agreed with the team up front and held for the term, with recordings for anyone who has to miss one.
An objective, not a syllabus
The programme is built backwards from what has to be true at the end, rather than from a textbook running order.
Reporting per cohort
Attendance, hours delivered and level movement, per cohort and per learner, ready for a budget review.
What a term achieves
A term usually targets confident participation in meetings and written communication that does not need a colleague to review it first. For staff who need a certificate, IELTS or a comparable exam can be the endpoint instead.
We would rather set an objective a cohort can actually hit in a term than promise a level jump that sounds better in a proposal. Where a target is unrealistic for the hours available, we say so before the contract rather than in the end-of-term report.
Run a English cohort
Start with one team for a term — enough to produce real attendance and progress data before scaling.