Constructive Failure

In events and in any kind of project I go through, I always make an analysis of the things that worked and those that worked less. This strategy is very useful for me to settle methods, procedures and tools for continuous improvement.

If bugs occur even in software, mistakes can happen to us humans! However, it is necessary to work on our mistake in a functional way to avoid failure so that individual responsibilities are clear and appropriate to the stage of work, goals are realistic, timeframes are appropriate for opportunities to experiment, emotional experiences, which are triggered by the error, are given value and meaning, and help is sought when the burden becomes too great. 

A repeated and unprocessed experience of error becomes failure. It is important to see failure as an opportunity to make a diagnosis, find different options and thus try to improve the project. Failure becomes constructive if it is accepted, faced and processed. In order to grow, you must always find a way to improve in both success and failure.

A tool that I consider very useful in my work as Event & Project Manager is self-assessment, i.e., the ability to build a system – rules, criteria for analysing and judging yourself and your own performance – that allows you to work realistically, and then face external evaluation.

When I proceed with self-assessment, I must take an objective stance to avoid, as we easily tend to do, attributing successes to internal factors, thinking that it is our merit if things went well, and instead attributing failures to something external believing that we have done everything possible, thus safeguarding ourselves. 

Attributing failures to something external and uncontrollable does not allow one to grow, we must always try to improve for ourselves.

Alibis do not make us grow. This is worth keeping in mind!