ChatDiagram
Data · Analysis

Project risk assessment heatmap

The Orion launch team uses a likelihood-by-impact heatmap to agree which risks deserve attention first. Scores rise toward the likely, high-impact corner, providing a shared view for prioritising mitigations. This is a decision aid, not a forecast: the individual risk register should still identify the owner, trigger and response for each item. Agree the scoring definitions before the workshop so one person’s “possible” is not another person’s “likely,” and keep the matrix compact enough to read in a project review. Before sharing it, compare the chart with the source table and make the scope explicit. A clear date range, population and unit help another reader interpret the pattern correctly and decide whether follow-up analysis is needed.

유형 히트맵엔진 echarts-heatmap업데이트됨 2026. 9. 24.
Orion Launch Risk Assessment
Drawing preview
요청 내용

“Create a project risk heatmap for the Orion launch with likelihood rows and impact columns, scored from 1 to 20.”

그렇다면Add a red flag to likely critical-impact risk.Change the title to Q3 launch risk assessment.
이 도면에 담긴 내용

그 이면의 의사결정을 읽어 보세요.

01Set the scope

Use one reporting period and one clear unit.

02Read the pattern

Identify the largest concentration or directional change.

03Check the source

Confirm the displayed values against the underlying data.

Use this heatmap when the stated values and labels are the information the reader needs to compare.

모든 히트맵 템플릿 보기 →

자주 묻는 질문

자주 묻는 질문

What does this heatmap show?

A heatmap uses colour to show the size of a value at the intersection of two categories. It helps readers spot concentrations, gaps and repeated patterns quickly.

How should I read this heatmap?

Choose a colour scale whose minimum and maximum match the data, and include cell labels when precise values matter to the decision.

Can I adapt this heatmap example?

Yes. Replace the title, labels and values with your own data, then check that the prompt still describes every important element in the chart.