Bring a real risk from your project.
Write it as Cause, Effect, and Impact. You'll get coaching on what your team would still have to guess — then revise it and run it again. Most risks take three or four passes to get sharp, and the first pass is supposed to be rough.
What Cause, Effect, and Impact mean
Instead of “I'm worried the architecture might not get done in time and things could slip” —
Cause: The data platform architecture has not been finalized as of May 9. The API team has been waiting on schema decisions since Sprint 12.
Effect: The API team cannot begin integration testing, which will push the integration milestone past the June 1 target.
Impact: If integration slips past June 1, the Q3 customer pilot for Acme Corp ($400K committed revenue) cannot start on schedule.
The goal is to reduce the telepathy — to say enough that your team doesn't have to guess what you mean.
Your risk stays in this browser tab. It is never stored on our servers, and it clears when you close the tab. .