Imagine discovering that something has gone wrong at work. Perhaps you made a mistake, noticed an inconsistency, or encountered a result you cannot explain. Your first reaction might still be, “Shit.” But instead of worrying about how to protect yourself, you begin thinking about who could help.
You know that you can share what happened before understanding its cause. Colleagues will help contain the consequences, investigate the problem, and determine what needs to change. If you acted with reasonable care, exposing the problem will not become a reason to humiliate you, damage your performance review, or threaten your job.
I wonder how much organizational knowledge would become available if this were an ordinary experience at work. How many problems would reach someone capable of understanding them earlier? How much energy currently spent defending decisions could instead go into improving them?
Learning begins before we understand what went wrong
Bin Zhao’s chapter Why Is Learning from Errors Easier Said Than Done? describes learning as a process that begins with acknowledging an error, continues through reflection and identifying its causes, and leads to improved knowledge that is applied in subsequent action.[1]
The first step is particularly difficult. An error can occur without ever becoming something we are willing to examine. We may correct its immediate consequences, explain it away, or simply hope nobody notices. The organization loses an opportunity to learn before the investigation has even begun.
My argument is that organizations need to make acknowledgment both safe and useful. When someone exposes a problem, they should gain access to people, knowledge, and support that improve their ability to deal with it.
This sounds straightforward until we consider how differently people behave when they encounter problems in their private and professional lives.
Why asking for help feels different at work
When software on your personal computer stops working, you probably search for the error message, consult a forum, ask a knowledgeable friend, or turn to AI. You explain what you were trying to do and what happened because those details help someone identify a possible cause.
You have reached the limits of your own knowledge, so you look for knowledge elsewhere.
At work, the consequences may be more serious because customers, colleagues, money, or safety are involved. That should make access to relevant expertise even more valuable. Yet sharing the problem may feel more dangerous than struggling with it alone, especially when admitting uncertainty threatens how others perceive your competence.
We could attribute this reluctance to ego. Sometimes people do protect their self-image when they should question their understanding. But when employees have seen colleagues suffer for admitting mistakes, reluctance is also a rational response to what the organization has taught them.
Amy Edmondson’s research provides an important foundation for understanding this behavior. Her study of 51 work teams found an association between psychological safety, the shared belief that a team is safe for interpersonal risk-taking, and learning behavior.[2]
People need to believe that they can ask for help, question assumptions, and disclose mistakes without that exposure being used against them. Such beliefs develop through experience, including what managers and colleagues do after the initial conversation and what eventually happens in performance reviews and promotion decisions.
An organization cannot credibly ask people to be open while repeatedly making openness costly.
Discomfort is not the enemy
Psychological safety does not mean discovering an error should feel pleasant. Concern, frustration, and embarrassment may be natural responses when something goes wrong.
Zhao’s 2011 research complicates the assumption that negative emotions necessarily prevent learning. In a laboratory study, negative emotionality was positively associated with motivation to learn, contrary to the original prediction, while different emotions showed different relationships with learning. Perceived managerial intolerance also increased negative emotionality.[3]
The practical distinction is between discomfort that motivates investigation and fear that encourages concealment. Someone can be concerned about the consequences of an error while still feeling able to seek help.
The objective should therefore not be to eliminate uncomfortable feelings. It should be to create conditions in which people can respond constructively to them.
The knowledge needed may already exist somewhere else
Organizations contain far more knowledge than any individual employee can access. A colleague in another department may recognize a pattern, understand a dependency, or know how a similar problem was resolved.
But that knowledge remains unavailable if the problem never leaves the person who discovered it.
Cathy van Dyck and her colleagues studied what they called an error management culture: shared practices of communicating about errors and detecting, analyzing, and correcting them quickly. Across studies in the Netherlands and Germany, they found a positive association between such a culture and firm performance.[4]
This does not establish that openness alone causes better performance. It does, however, support examining how organizations respond after errors occur.
The distinction matters because encouraging people to report problems is only half the task. The other half is ensuring that the information reaches someone who can help and that the organization can act on what it learns.
A company could become very good at collecting incident reports without becoming any better at resolving the conditions that produced them.
Interested in working together?
Prevention is necessary, but it is not enough
Michael Frese and Nina Keith argue that error prevention needs to be supplemented by error management: the ability to deal effectively with errors after they occur, limit their consequences, and learn from them.[5]
These approaches are complementary. Organizations should prevent avoidable errors through appropriate standards, training, safeguards, and controls. But no system can guarantee that every error will be prevented, particularly when work involves changing conditions and incomplete knowledge.
The question is therefore not whether organizations should prevent errors or learn from them. They need to do both, and they need to distinguish the situations in which each response is appropriate.
This becomes especially important in startups and corporate innovation, where unexpected results are not necessarily evidence that someone made a mistake. A carefully designed experiment may disprove an assumption, or customers may behave differently from what the team anticipated.
Such observations require investigation before they can be classified as execution errors, inadequate explanations, or potential opportunities.
When every disappointing result becomes evidence of poor performance, employees have a reason to favor activities with predictable outcomes. Risk avoidance can gradually become the organization’s practical governance, even while its strategy calls for exploration and innovation.
Facing a decision under uncertainty?
Before you commit more capital, credibility, or resources, let’s examine what you know, what you assume, and what evidence would justify your next move.
I work with founders, executives, and teams on decisions about what to test, scale, or stop.
Available online worldwide and in person across Europe.
Request a 20-minute introductory conversation.
Making room to learn without making harm acceptable
I think of a child learning to walk. We make room for attempts and manageable falls while protecting the child from serious harm. The goal is not to celebrate falling, but to help the child develop an ability that cannot be acquired by avoiding every possibility of losing balance.
Organizations face a similar distinction. They need to establish acceptable boundaries for exploration, contain harmful consequences, and learn from unexpected outcomes. That does not excuse negligence or deliberate disregard for safeguards. It recognizes that developing new capabilities requires confronting situations in which the correct response is not yet fully known.
The question for leaders is whether someone can say, “Something is wrong, and I do not yet know how to handle it,” with a reasonable expectation of receiving help.
The answer determines how much of the organization’s collective knowledge becomes available when an individual reaches the limits of their own.
The free section of INNOVATION& is offered freely, and you are welcome to keep reading it that way. If these articles help you make better decisions in your working life, please consider becoming a paid subscriber. Researching and writing them takes time, and paid subscriptions provide the income I need to continue. Your support also helps keep part of this work available to everyone.
Thanks for reading INNOVATION&! This post is public so feel free to share it.
Start paid learning and application section
How to Make Reporting an Error Lead to Help
The research suggests that learning from errors depends on more than encouraging people to speak up. Organizations also need a credible response that connects disclosure to expertise, investigation, and meaningful change.
I would start with one team and one recent incident rather than launching a company-wide initiative. Following the incident from the moment someone noticed the problem to the point where something changed makes the actual experience visible. It also reveals where people had to hesitate, improvise, or proceed without support.




