Para priorizar riscos em um projeto de alto risco, começo avaliando o impacto que cada risco pode ter no resultado final. Identifico quais riscos podem causar os maiores danos ao projeto, tanto em termos financeiros quanto operacionais. Depois, analiso a probabilidade de cada risco ocorrer, dando mais atenção aos que têm maior chance de se materializar. Também considero o custo e a viabilidade de mitigação, priorizando ações que possam minimizar riscos com menos impacto no orçamento e no cronograma. Dessa forma, consigo equilibrar a prevenção de riscos com a viabilidade do projeto.

Prioritize Risks in High-Stakes Projects: - Assess Impact: Focus on risks with the highest potential damage. (Example: “Prioritize supply chain disruptions that could halt the project.”) - Evaluate Likelihood: Address risks most likely to occur. (Example:* “Target risks like regulatory changes that are probable.”) - Consider Mitigation: Choose risks you can effectively manage. (Example: “Handle risks with available backup suppliers.”) - Monitor Trends: Keep an eye on emerging risk factors. (Example: “Track industry shifts that could impact project timelines.”) These steps ensure your contingency plans are both practical and impactful.

According to me, assessing severity is extremely important. By understanding the severity of a potential risk, you can prioritize efforts on those that could cause the most harm, regardless of their likelihood. Let us take a real life example. In 2017, British Airways experienced a major IT system outage that grounded flights and caused global disruption. Although the likelihood of a system-wide failure was considered low, the impact was severe, costing the airline an estimated £80 million and damaging its reputation. After this incident, British Airways invested heavily in improving its IT infrastructure to mitigate the impact of future risks. In FMEA, we often use RPN number where severity is taken into account.