Step-by-step guidance
Who can do this: AI and project access are required; financial evidence appears only when the user can view it.
Before you begin
- A project with current status and evidence
- Recorded delivery signals relevant to the question
Steps
- Choose Explain risk in the project insight area.
- Review which current signals are available.
- Compare the explanation with underlying records.
- Record the human-owned mitigation in the normal project workflow.
Expected result
The user can inspect which recorded signals may be increasing delivery risk.
Next action
Assign and monitor a concrete mitigation rather than treating the explanation as a decision.
Common problems
- Unrecorded facts cannot be considered.
- Correlation does not prove delay cause.
- AI does not change health, dates, staffing, or budget.