An English training needs analysis should answer a business question: what must people do in English that is unnecessarily difficult today?
Starting with a course catalog or a general proficiency test reverses the process. It tells you what training exists before you have defined the work that needs support.
The framework below produces a short list of observable communication situations. That list can guide a pilot, a vendor brief, or individual practice without treating accent or nationality as evidence of a performance problem.
Analyze the work at three levels
1. Organizational needs
Identify why English matters to the business now. Examples include:
- serving customers in another market;
- integrating an international team;
- preparing managers for broader responsibilities;
- reducing confusion in cross-functional work;
- helping specialists present their expertise to leadership.
Keep the goal concrete. “Become a global company” is a strategic ambition. “Give accurate weekly updates to the US leadership team” is a trainable communication requirement.
2. Role needs
List the recurring situations attached to each role. A project manager may need to escalate a risk, negotiate scope, and summarize decisions. A frontline supervisor may need to delegate work, correct a problem, and confirm a handoff.
Do not create one generic list for the whole company unless the roles genuinely perform the same communication work.
3. Individual needs
Within the same role, people will have different strengths. One employee may need faster retrieval in meetings. Another may speak comfortably but struggle to calibrate tone in writing.
Individual diagnosis should support development. A low-stakes learning assessment is not automatically valid for hiring, promotion, discipline, or other employment decisions.
Use a situation matrix
Create one row for every important communication situation.
| Situation | Participants | Frequency | Consequence of failure | Current difficulty | Required behavior | Evidence of progress |
|---|---|---|---|---|---|---|
| Weekly project update | Project team and sponsor | Weekly | Medium | Update is long but leaves the decision unclear | State status, risk, recommendation, and owner | Listener can identify the decision and next step |
| Customer delay call | Account lead and customer | Occasional | High | Employee overpromises while trying to reassure | Explain known facts, uncertainty, and next update | Commitment remains accurate after the call |
| Performance feedback | Manager and employee | Monthly | High | Message becomes either vague or abrupt | Separate observation, impact, expectation, and support | Both parties can restate the expected change |
This matrix prevents “better English” from becoming an undefined goal. It also reveals when the real problem is not language. Missing decision rights, weak processes, or unexplained company shorthand require operational fixes.
Collect evidence from more than one source
Use several lightweight methods rather than trusting one score.
Understanding is only the first step.
Lyra Practice helps you retrieve and use high-value workplace expressions in realistic situations until they feel natural.
Start a practice session →Interview managers
Ask for recent moments, not impressions about a person:
- What conversation repeatedly takes longer than it should?
- Where do people avoid participating?
- Which messages require frequent rewriting?
- When has wording created an incorrect commitment?
Replace “their English is weak” with a description of what happened.
Ask employees
Employees often know where they compensate. Ask which situations they prepare for excessively, avoid, hand to a colleague, or replay afterward.
Participation should feel developmental rather than investigative. Explain what will be collected, who will see it, and how it will be used.
Review sanitized work samples
With appropriate permission, examine de-identified examples such as meeting updates, email patterns, or presentation openings. Remove customer information, employee identifiers, and confidential business details before using material in training.
Observe the workflow
A meeting may reveal that everyone lacks preparation time, questions are poorly framed, or senior participants interrupt frequently. Training one employee cannot repair a meeting design problem.
Prioritize by consequence, frequency, and trainability
Give each situation a simple rating:
- Consequence: What happens when communication fails?
- Frequency: How often does the situation occur?
- Trainability: Can focused practice change the behavior?
Start with situations that are frequent or consequential and narrow enough to practice. “Executive presence” is too broad. “Recommend one option and explain its trade-off in two minutes” is usable.
Avoid prioritizing only the most visible mistakes. A minor grammar error may be noticeable but harmless. An unclear commitment or unspoken risk may matter far more.
Convert the analysis into practice objectives
A useful objective names the situation, behavior, and evidence.
Weak objective:
Improve business English confidence.
Stronger objective:
In weekly leadership updates, state the recommendation before the supporting detail and answer one challenge without abandoning the position.
The stronger version tells the learner what to practice and gives the manager something observable to support.
Produce a one-page training brief
Your final brief should contain:
- the business outcome;
- the roles included;
- the three to five priority situations;
- the required communication behaviors;
- the practice format and frequency;
- the evidence you will review;
- the privacy and participation boundaries;
- the date when you will decide whether to continue.
That is enough to compare providers or design a small pilot. For the next step, use the 30-day workplace English training pilot or the broader workplace English training guide for small businesses.
Managers can also preview situation-based diagnosis with the free management English assessment. Treat the result as a development prompt, not an employment verdict.