Visible Revision. An earlier rust-red curve remains visible beside a broader blue gesture. Original abstract editorial painting about acknowledging what changed and continuing the work.
Fair reporting needs careful investigation, proportionate accountability and visible follow through
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc..
A mistake has already happened. The next decision is whether anyone else will hear about it while something can still be done.
For a team member, that decision may carry more than embarrassment. They may wonder whether a supervisor will listen, whether the facts will be checked, whether a colleague will retaliate or whether one error will become their permanent reputation. For the organization, the same moment may determine whether a small problem is contained or allowed to travel into someone else's work.
Leaders have a responsibility to make reporting useful and fair. That means responding to the immediate problem, understanding how it happened, deciding what accountability requires and checking whether the corrective action actually worked. A reassuring speech cannot substitute for those steps.
This matters in a small business, a nonprofit, a community project or a team of volunteers. People receiving the service should not have to rely on everyone being perfect. They need an organization capable of noticing when its work falls short and doing something reliable about it.
What the research can tell us
Amy Edmondson's 1999 study of psychological safety and team learning combined surveys, interviews and observation in one manufacturing company. The survey included 427 members of 51 teams. Psychological safety concerned shared beliefs about the interpersonal risks of speaking up, asking for help and acknowledging difficulty.
The relationship was substantial: a model using team psychological safety to predict independently observer-rated learning behavior had an adjusted R-squared of 0.35. That describes variation accounted for in that statistical model, not a 35% improvement caused by a management practice. The cross-sectional survey could not establish causation, and findings from one company do not automatically generalize to every workplace.
Qualitative evidence supplied texture. Members of a production team described accepting feedback about defects, correcting their work and seeking outside opinions. The interviews illustrated how feedback could become usable rather than a trigger for defensive retaliation. They were observations and participants' accounts, not an experiment proving that one leadership technique works everywhere.
The practical question is whether your own team's arrangements make accurate information easier to share and act upon. Leaders cannot declare a team psychologically safe on employees' behalf. That confidence, where it develops, must be tested against people's experiences over time.
Make the first response dependable
When someone reports a mistake, begin with the situation. Is anyone at risk? Is an incorrect message still being sent? Can a faulty batch be held? Does another team need an immediate warning? A serious hazard requires the applicable emergency or specialist response, not an improvised discussion about culture.
Once immediate risks are addressed, acknowledge the information without deciding the whole case. Thanking someone for reporting does not require endorsing every detail of their account. Nor does it require promising that no consequence can follow. Explain what will happen next, who will review the facts and when the person should expect an update.
Avoid questioning someone in front of an audience merely to demonstrate that management is taking action. Collect facts privately where possible, preserve relevant records and distinguish what is known from what remains uncertain. Let the person correct a misunderstanding. If the report concerns their supervisor, provide a route to someone outside that supervisor's control.
Confidentiality needs equally precise language. Explain who may need to see the report and why. Do not promise absolute anonymity when a small team, a legal obligation or the facts of the event may make identification unavoidable. An alternative reporting route, limited access to records and a credible response to retaliation are more useful than a promise the organization cannot keep.
People should also be able to report a near miss, an unclear instruction or a weak process before there is an actual loss. The opportunity to prevent harm should not depend on first producing proof that harm has occurred.
Distinguish an error from negligence or misconduct
A poor outcome does not, by itself, explain the behavior that produced it. The same consequence can arise from a reasonable decision under uncertainty, a confusing instruction, a failure to take reasonable care or a deliberate violation.
For management discussion, it helps to distinguish three ideas. An error is an unintended action, omission or mistaken judgment. Negligence concerns a failure to exercise the care reasonably expected in the circumstances. Misconduct concerns behavior that breaches applicable standards, potentially including intentional deception, harassment or deliberate disregard of a requirement. These descriptions are not legal findings, and the categories can overlap. Applicable law, agreements and organizational policies determine the relevant standards and procedures.
Investigation should examine what the person knew at the time, their training and authority, the clarity of the instruction, the available resources and the choices realistically open to them. Ask whether a similarly trained colleague could have made the same mistake in those conditions. Consider repeated behavior and earlier support, but do not assume that repetition proves intent. A recurring design problem can repeatedly defeat conscientious people.
Equally, do not use a discussion of systems to excuse dishonesty or disregard the people harmed. Deliberately altering a record to hide an error is a separate action requiring examination. A manager who knowingly pressures staff to bypass a safeguard deserves the same scrutiny as the person carrying out the task.
Proportionate accountability can involve correction, coaching, closer supervision, changing responsibilities or formal discipline where justified through a fair process. Explain the reason for the response and provide the review or appeal route required by policy and law. Consistency means applying the same relevant standards to comparable circumstances, including senior staff. It does not mean imposing identical consequences for every unwanted result.
Aviation offers a useful boundary
The Federal Aviation Administration's Safety Management Systems guidance, AC 120-92D, makes an important distinction. Its guidance says aviation organizations should explain that gross negligence and deliberate misconduct are not protected behaviors. It also emphasizes documented reporting arrangements and clear behavioral expectations.
The underlying rules place these responsibilities together. 14 CFR 5.71 requires a confidential employee reporting system, without concern of reprisal for reporting, for entities subject to its requirements. 14 CFR 5.21 requires a policy defining unacceptable behavior and conditions for disciplinary action.
These are aviation-specific rules and guidance, not a ready-made legal policy for every employer. Their useful lesson is that protection for reporting can coexist with clearly stated accountability. Organizations in other sectors should develop suitable arrangements with qualified employment, safeguarding or regulatory advice where needed. Copying aviation terminology does not create legal protection or demonstrate a safe culture.
Investigate the work as it was actually done
An investigation that ends with an instruction to be more careful has often stopped too soon. Care matters, but the organization also needs to understand why its existing arrangements failed to prevent or detect the problem.
Reconstruct the sequence. What was supposed to happen? What actually happened? Which version of a document was available? When did the information change? Who had responsibility for telling the next person? Where could a check have caught the error, and why did that check not work?
Use records, observations and accounts from more than one perspective. Someone who designed a procedure may know little about the unofficial workaround that keeps it moving on a busy afternoon. Someone who received the output may see a consequence that the originating team missed. Invite those perspectives without turning the review into a search for the most convenient person to blame.
Keep the scope proportionate. A minor isolated administrative mistake may need a short review. An event involving serious harm, suspected abuse, fraud or a significant legal duty may require independent investigation and mandatory reporting. A team learning session cannot replace those processes. Where accounts conflict, record the disagreement and the evidence rather than forcing premature agreement.
Ask what the organization rewarded before the incident. If meeting a deadline was praised while checking work was treated as unnecessary delay, that incentive belongs in the findings. Accountability should reach the decisions that shaped the work, not stop with the last person who touched it.
An example from a community workshop
Consider a hypothetical organization preparing printed welcome packs for adult skills workshops. This is a nonclinical illustration, not a report about Feel Worldwide Foundation Inc. or any actual program.
A coordinator notices that a pack carries an old venue address and reports it immediately. A review of all 240 packs finds 18 with the wrong address. Four have already been dispatched; 14 can be corrected before dispatch. The identified error affected 7.5% of the packs, while approximately 1.7% of all packs had already left with that error. These invented figures illustrate why detection and consequences should be recorded separately.
The team first contacts the four recipients through an approved channel, supplies the correct address and checks whether anyone needs practical help with the change. It preserves the relevant file versions and pauses further dispatch until the remaining packs have been checked.
The investigation finds two similarly named templates, one stored locally and one in a shared folder. The address changed after printing began. The supervisor had asked the team to finish quickly but had not assigned anyone to withdraw the old template. Those facts would support examining document control and supervision. They would not, on their own, establish negligence or misconduct by the coordinator.
The corrective plan has named owners. The operations lead removes obsolete templates from the working location while retaining any records that must be kept. The workshop lead confirms venue information before release. The coordinator checks a sample against that confirmed information at the start of each print run and after any change. A deputy can perform the check when the usual person is absent.
The manager also reviews the urgent instruction they gave. If the staff member needs additional training, that can be arranged without pretending the supervisor's role was irrelevant. If later evidence establishes deliberate concealment or a knowingly bypassed requirement, that evidence must be considered fairly rather than excluded to preserve a comforting story.
Before closing the matter, the organization checks that the corrected information reached the affected recipients. During the next four workshop cycles, it reviews whether the new process is being used and whether incorrect versions reappear. The review date matters: without it, a list of actions can become another forgotten document.
Measure learning without rewarding silence
An organization should be cautious about celebrating a sudden fall in reported mistakes. Fewer reports could reflect better work. They could also reflect uncertainty about reporting, an inaccessible process, unresolved complaints or fear of the response. A rise could mean worsening operations, better detection or both.
Use more than the report count. Look at the severity and recurrence of problems, the amount of work being done, the time taken to contain an issue, whether affected people received a remedy and whether corrective actions were tested. Separate a near miss from an incident that caused harm. Keep definitions stable enough for comparisons to mean something.
Qualitative checks belong beside those measures. Ask a new colleague to explain how they would raise a concern. Ask someone who reported whether they understood the response and received an update. Look for teams or groups whose concerns never reach the formal process. A short survey may help identify questions, but a reassuring average cannot establish that everyone feels able to speak.
Avoid turning learning into a competition for the most admissions or the lowest error total. Both incentives can distort what people record. The purpose is to understand the work well enough to improve it while treating the people involved fairly.
Leaders make the follow through visible
A useful review ends with a small number of actions that have an owner, a completion date and a way to check effectiveness. Distinguish an action completed from a problem solved. Training attendance shows that people attended training; it does not show that the confusing handover has become reliable.
Return to the person who raised the issue. Share what can appropriately be shared about the findings and improvements, while protecting other people's privacy. Explain if an investigation is still open or a proposed change could not be adopted. Silence after a report can leave people wondering whether anything happened at all.
Leaders can also describe their own mistakes with specificity: the decision, its effect, what they should have checked and what they changed. This should not become a performance that requires staff to reassure the leader. It should make responsibility easier to recognize at every level.
The goal is a team that can face an uncomfortable fact without either humiliating the person who brought it forward or dismissing the harm involved. A report creates an opportunity. Careful investigation, appropriate accountability and sustained corrective work determine whether that opportunity becomes learning.
Support responsible organizational learning
Organizations and specialists interested in contributing practical leadership education or other relevant expertise can propose a scoped partnership with Feel Worldwide Foundation Inc. Describe the intended participants, contribution, location and boundaries of the proposed work. A proposal should not include confidential incident files or personal allegations. Readers wishing to support the Foundation's mission can review the available donation options. An inquiry or donation does not guarantee a partnership, a training service or a particular workplace outcome.
