# Why software managers should allow mistakes at work

DevFeed: [Why software managers should allow mistakes at work](<https://devfeed.tech/articles/is-it-ok-to-make-mistakes-at-work-24932.md>)

Original publisher: [Read original article](<https://codeahoy.com/2016/04/14/mistakes-at-work-are-not-sins/>)

Author: umer

Published: 2016-04-14T00:00:00Z

Content type: opinion

Language: en

Sources: [Code Ahoy - Articles](<https://devfeed.tech/sources/code-ahoy-articles.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>)

Tags: [customer](<https://devfeed.tech/tags/customer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [mistakes](<https://devfeed.tech/tags/mistakes.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [team](<https://devfeed.tech/tags/team.md>)

## AI overview

This opinion article argues that software managers should not stigmatize ordinary mistakes. Excessive fear of errors can make developers defensive, discourage experimentation, and reduce motivation, while high-risk customer-facing areas should receive additional oversight.

## Source excerpt

I have not failed. I have just found 10,000 ways that won't work. -Thomas Edison Software development is an activity that requires serious brain power. And it's only natural that software developers make mistakes along the way. However, many organizations and managers stigmatize failures. It's considered a sin to make an error on the job. A sin that is not going to be forgotten any time soon. We are taught from an early age that mistakes are bad. Students are marked by the number of mistakes and the society looks down on failures. So why should managers allow it? The answer is simple: people will make mistakes in any activity that requires imagination and creativity. That's how they learn and improve. DeMarco and Lister explained it better: Fostering an atmosphere that doesn't allow for error simply makes people defensive. They don't try things that may turn out badly. You encourage this defensiveness when you try to systematize the process, when you impose rigid methodologies so that staff members are not allowed to make any of the key strategic decisions lest they make them incorrectly. The average level of technology may be modestly improved by any steps you take to inhibit error. The team sociology, however, can suffer grievously. The last sentence is the key: The team sociology, however, can will suffer grievously. As a software manager, your primary day job is to make it possible for your team to do work. When people become defensive, they lose motivation to do good work. Whenever a 'bug' is reported by customer or a client, instead of focusing their efforts to objectively locate the bug, employees spend time and energy on 'covering their asses' and collecting data to 'prove' that there has to be something "wrong with the other system." The biggest fear managers have is that mistakes made will cost their company money or damage customer relationship. While this is true, most mistakes made in the workplace don't damage company's reputation. Managers should iden