One time earlier in my career some tasks slipped and I tried fixing it by doing two types of testing in parallel. Absolute disaster. I told the team it was a terrible decision, that we were going to take a hit to the project by going back and doing it right. Saving Changes...
Product Operations Program ManagerBarcelona, Cataluña, Spain
In your question there is partially the answer. Hiding the failure is not advised, it needs to be communicated (I am refering to failures that cause large impact on the project well-being).
My advise is: do not just communicate the failure, also elaborate on why it has happened (root cause), what will be done to avoid in the future (preventive) and how will the issue be solved in the present (corrective). Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First thing is: you must not think and behave as it was a failure. After your first impression analyze it and be carefull if it is a failure. Second: a project manager is hire to avoid surprises. Then, if you are publishing not desire things with enough time to prevent and react you are making your work. Saving Changes...
How you will communicate it depends on the failure, is not the same if we deployed a new program in accounting that broke all the general ledger of the organization than if you sent an email to an incorrect vendor.
However applying Eduard rules will always work. Saving Changes...
Community Champion
