Business Risk Assessment Analyzer

Produces a structured risk matrix with mitigation strategies for any business decision.

Best For

•An operations lead planning a vendor switch runs the analysis to surface financial and operational risks before presenting the decision to leadership
•A project manager launching a new initiative uses the risk-scoring matrix to prioritize which of a dozen possible risks actually deserve a mitigation plan
•A founder preparing a board update uses the top-5 priority list and contingency plan to show investors the decision was made with eyes open

Prompt Template

Conduct a structured risk assessment for [PROJECT/INITIATIVE/BUSINESS DECISION]. Context: [DESCRIBE WHAT YOU'RE PLANNING TO DO AND WHY]. Timeframe: [TIMELINE]. Key stakeholders: [LIST STAKEHOLDERS]. Identify and analyze: (1) Strategic risks, threats to the achievement of objectives, (2) Operational risks, execution, process, and resource risks, (3) Financial risks, cost overruns, revenue shortfalls, market risks, (4) Reputational risks, public, media, or stakeholder perception risks, (5) Legal and compliance risks. For each risk identified, provide: risk description, likelihood (High/Medium/Low), potential impact (High/Medium/Low), a risk score (likelihood × impact), and 2 mitigation strategies. Conclude with a risk priority matrix: list the top 5 risks to address first and one recommended contingency plan for the highest-priority risk.

Pro Tip

Name your actual stakeholders and timeline rather than leaving them generic, since reputational and legal risk categories change substantially depending on who is affected and how much time there is to react.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Risk: Vendor data migration failure. Category: Operational. Likelihood: Medium. Impact: High. Risk score: 6. Mitigation: run a parallel system for 30 days post-migration; assign a rollback owner before cutover. Top priority risk: customer data loss during transition, with a contingency plan of maintaining read-only access to the legacy system for 60 days after go-live.