The leadership test comes after someone speaks up

A manager thanks an employee for raising a concern. The meeting ends politely. A week later, the employee has heard nothing, their usual project has gone to somebody else, and their supervisor is noticeably less willing to speak with them. Whatever the company intended, the employee now has a different question: was speaking up a mistake?

This is a fictional example. It illustrates why leaders should examine what happens after a concern enters the organisation, rather than judging their reporting process solely by whether employees can find the right form. An invitation to speak up creates an expectation of a response. The practical work begins with deciding who will provide it and what happens while the concern is being considered.

Senior leaders cannot personally investigate every complaint. They can, however, require a process that gives a concern an owner, keeps relevant information intact and checks how the employee is being treated. Those expectations are useful whether the issue concerns conduct, pay, working conditions or a decision the employee believes is unfair.

Make the first conversation useful

The first manager to hear a concern may feel pressure to defend a colleague, explain a decision or decide immediately whether the complaint is justified. That can turn a reporting conversation into an argument before the facts are clear.

Start by asking what happened and what the employee wants the organisation to understand. Clarify dates, the people involved and whether there is an immediate issue requiring attention. A manager can acknowledge that someone has raised a concern without endorsing every allegation or promising a particular outcome.

Avoid asking the employee to supply a legal label. “I think my supervisor is punishing me for reporting harassment” conveys something different from a general disagreement about assignments, even if the employee cannot identify the relevant statute. A sensible process captures the substance and routes it to someone qualified to assess it.

In the United States, the Equal Employment Opportunity Commission’s retaliation guidance explains that reasonably opposing perceived unlawful discrimination can be protected even when the opposition is informal. Protection does not necessarily depend on the underlying complaint succeeding. This is a US employment-law perspective; legal duties differ by jurisdiction and by the nature of the concern.

The initial record should distinguish what the employee reported from the manager’s assessment. “Employee says they were excluded from client meetings after reporting harassment” preserves an allegation for review. “Employee upset about workload” may erase the very issue that needs attention.

Give the response an owner

A concern can disappear between people who each believe somebody else is handling it. The manager thinks HR has taken over. HR is waiting for a written account. A department head assumes the employee will follow up if the problem continues.

Name the person responsible for the next step and tell the employee how to contact them. Where an investigation requires several people, distinguish responsibility for the investigation from responsibility for keeping the employee informed. The same person need not do both jobs, but the employee should understand whom to approach.

Agree on the next contact date. It can be a date for an update rather than a promise to finish the investigation. If the responsible person is away, identify a substitute and transfer the record through an approved system. A concern should not depend on one person’s memory or availability.

Leaders should also provide an alternative reporting route where the concern involves the employee’s manager. Requiring that manager to approve an escalation can make the route unusable precisely when it matters most.

Look at decisions made during the review

Business operations continue while a complaint is open. Projects change, schedules move and performance discussions still take place. The question is whether those decisions have sound reasons and whether someone can explain them consistently.

Return to the opening example. Reassigning a project might reflect a genuine client requirement. It might also remove an opportunity from the person who reported a concern. Before making the change, the decision maker should consider its effect, the available alternatives and how comparable situations have been handled.

The EEOC explains that whether an action is materially adverse depends on its circumstances, and that an independent review of a proposed adverse action can help reduce retaliation risk. Reporting a concern does not excuse misconduct or poor performance. Equally, a performance label does not settle whether a decision was retaliatory.

Keep the operational explanation and supporting records from the time of the decision. An explanation assembled later may be harder to assess against the original events. Where the manager making the decision is implicated in the complaint, appropriate independent oversight becomes particularly useful.

This does not require freezing every management decision. It requires enough care to identify a change that might discourage reporting or place an unnecessary burden on the person who raised the concern.

Keep the employee informed without promising secrecy

Employees may understandably want to know who will see their account. Explain how information will be handled and that relevant details may need to be shared to investigate. Avoid an absolute promise of confidentiality that the organisation cannot fulfil.

An update can be brief and still useful. Explain which stage the matter has reached, whether further information is needed and when the next update will come. If the timetable changes, say so. Silence leaves the employee to guess whether the organisation has forgotten the concern or dismissed it.

At the end, share the outcome to the extent appropriate while respecting other people’s privacy. Tell the employee where to raise a continuing concern. Check whether an agreed change has actually happened. A completed case entry is evidence that an administrative step occurred; it does not establish that the employee received the promised response.

Review the process beyond the case count

Executives often see totals: complaints received, cases open and cases closed. Those figures are useful for workload planning, but they cannot show whether a particular concern was handled well.

Periodically review a small sample of cases using appropriately restricted access. Ask whether there was a clear owner, whether contact dates were met and whether relevant decisions were explained. Examine cases that moved between departments, where responsibility is easier to lose. Findings should guide improvements to the process without exposing personal details unnecessarily.

Managers also need practice in receiving concerns. Training can use fictional conversations to help them listen, record the substance and recognise when they need assistance. Give them a clear escalation route rather than expecting confidence to substitute for expertise.

The employee in the opening example does not need a speech about organisational values. They need to know who is handling the concern, when they will hear back and how to report a further problem.


Author bio

George S. Azadian is a California employment attorney and President of Azadian Law Group, PC. His practice focuses on representing employees in workplace disputes, including wrongful termination, discrimination, retaliation, harassment and wage-and-hour matters.