On campus? Ask Stu instead. Stu already knows our methodology, so you can skip the setup and just describe your situation. Available to UC Berkeley staff, faculty, and students.
When to use it
After your milestone plan exists and before kickoff. The goal isn't a complete risk register, that comes later, with the team. This gives you a fast first pass so nothing obvious blindsides you in the first status meeting.
The "skeptical sponsor" framing does real work here. It pushes the tool to think like the person who will approve or question your project, so you hear the hard questions in private before you hear them in the room.
Make it better
Your first result is a draft, not an answer. Two follow-ups worth asking:
"Which of these risks is really a stakeholder resistance issue rather than a project risk?" Those belong in your change plan, not your risk register.
"What would you need to see before you'd approve this project?" This turns the risk list into a set of approval conditions you can act on.
Additional guidance
If the first results aren't quite right, add more detail, break the request into smaller steps, or have the tool interview you first. Try: "Ask me questions, one at a time, to gather anything you need before you start."
AI output is a starting point, not a finished product. Always review it against your own context, campus policies, and judgment before you use or share it.
Put it to work
Your risks and mitigations go into the risk section of your Project Charter. Get the template on the Initiate Project with Sponsor activity page.
