E-Learning Content Developer| PMIFlagstaff, Arizona, United States
This prompt uses the tree-of-thought approach to create a risk assessment matrix procedurally with the assistance of the LLM. It uses historical examples as guides for the matrix, and creates a detailed persona for both the user and the LLM. This prompt is meant to be chained with subsequent prompts for the optimal output.
I am an experienced project manager overseeing the implementation of a new ERP system in a mid-sized retail company with 150 employees, based in Phoenix, Arizona.
I need to create a detailed risk assessment matrix for the project. This matrix should identify potential risks, assess their impact and likelihood, assign risks to team members, and provide high-level, preliminary mitigation strategies, since we are still in the planning phase.
You are a Risk Management Professional of ten years, a PMI-RMP certification holder, and a project management assistant for our company and this project.
You will help me create a detailed risk assessment matrix that includes all of my requirement.
Here are the steps our organization historically follows when creating risk assessment matrices:
1. Identify potential risks associated with the ERP implementation.
2. Assess the impact and likelihood of each risk.
3. Develop mitigation strategies for each risk.
4. Assign risks and mitigation strategies to team members.
5. Organize the information into a clear and concise matrix format.
6. Review the matrix for completeness and accuracy.
For each step of development of the risk assessment matrix, both you and I will create the output. We will then present each of our solutions to the team for their thoughts, and depending on which strategies they like more, we will rule yours or mine out. Then, we will create the next section / perform the next step of creating the matrix.
I've attached 3 examples of risk assessment matrices for similar projects our company has completed in the past. Let's reference these examples for inspiration and guidance as we work.
I've also attached our team roles and responsibilities spreadsheet for assigning team members risks.
Do not include tips on how to present the data to the team.
Provide sources for your decisions and suggestions.
Let's start with step 1. You will create your potential risks, then ask for mine.
VenkataRatnakumar ChavakulaIT Solution Architect | Project Management | ERP Implementation Expert| Wipro Technologies, New JerseyMonroe Township, NJ, United States
This sounds good for my ERP project, modified and used it for my specific needs. Appreciate for creating and sharing this prompt. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Avinash Dhanraj Excellent approach!
The integration of tree-of-thought prompting with the collaborative creation of a risk matrix demonstrates a deep understanding of how to leverage LLMs in a structured and strategic way.
By involving multiple perspectives (user + LLM) and validating each step with the team, you are replicating a true cycle of risk co-design — something particularly valuable in ERP implementations, where risks are both technical and organizational.
I highlight three strong points:
- Iterative co-creation — comparing human and LLM outputs with team validation promotes ownership and aligns risk perceptions.
- Reference to historical cases from the organization — reinforces the contextual adaptability of the matrix.
- Clarity in roles and responsibilities — something often overlooked in the initial risk phase.
A suggestion to further strengthen the approach: consider already categorizing the risks (e.g., technical, organizational, change-related, legal, integration) as an additional axis in the matrix.
This facilitates later analyses and speeds up contingency planning decisions.
I’ll be following the next steps with interest — this is an excellent example of how AI and leadership can move forward side by side in risk management.
Amal Kumar SahuIFS Technical Solution Manager| ArcwideBangalore, India
Yes. I adapted the prompt to the ERP implementation context by including risks specific to retail operations, such as data migration, system integration, cybersecurity, user adoption, training, vendor management, and business continuity. I also added likelihood and impact scores, risk owners, risk ratings, and preliminary mitigation strategies. One improvement I would suggest is to have the AI identify assumptions and explain how risk scores were determined. I would also recommend reviewing and updating the matrix regularly as project requirements, resources, and implementation decisions become clearer. Overall, I found that adding specific project context and defining the desired output format made the prompt much more useful and practical for project management. Please use https://infinity.pmi.org/
This is a great framework for identifying and prioritizing risks in ERP implementations. The matrix makes it easier to assess risks based on their likelihood and potential impact, helping teams focus on the areas that need the most attention. Saving Changes...
A good starting point is to rate each risk by likelihood and impact, assign an owner, and add a simple mitigation plan. For an ERP project, focus on data migration, integrations, user adoption, scope creep, vendor delays, and budget risks. Review and update the matrix regularly as the project moves forward. Saving Changes...
PMI Team Member
