When something goes wrong at work, a good organization focuses on what caused the problem and what can be done to ensure it does not happen again. If someone has made a mistake, we expect them to own that mistake and learn what they can do differently to prevent the same error in the future.

For example, sometimes there is a problem with the environment. Lots of work in user interface design identifies how small changes in the way a product is designed can reduce the number of errors people make.

In many situations, though, an error sets off a search for someone to blame. And sometimes, the blame falls on you. Obviously, if you’re the one who caused the problem, accepting the blame is important. But what happens when you’re the one who is set to take the fall for something you didn’t do?

A lot depends on why you’re taking the blame and what the consequences are.

Sometimes, when you become the fall guy it’s because you’re trying to fix a bigger problem. A client may be upset at the way a project is going and they believe that your company is to blame. While you could fight with them over why your team is actually in the right, it is sometimes easier to apologize for the problem, reset the relationship, and try to move forward.

In situations like this, your team knows that you are not the source of the problem. You are putting on a show for the client.

Source link