We would like to use Google Analytics to understand how people use Insyt. It sets cookies and only runs if you accept. Rejecting changes nothing else on the site.
Compares entity status across criteria using a red-amber-green matrix.
Table
Status
Comparison
What it answers
Where are status problems across entities and criteria?
Shape
Grid of coloured status cells
What it shows
Clusters of exceptions.
Example
The question
Which projects are behind on which dimension?
Project status by dimension, end of September
Grid of projects by time, cost, scope and risk; each cell carries a symbol and colour (cyan tick on track, purple ! at risk, pink cross off track). Website: time on track, cost on track, scope at risk, risk on track; ERP upgrade: time at risk, cost off track, scope at risk, risk on track; Data platform: time on track, cost at risk, scope on track, risk at risk; Office move: time off track, cost on track, scope on track, risk off track; Training: time on track, cost on track, scope on track, risk on track.
Illustrative data. It belongs to no company.
When to use it
Use it when
Scanning multiple entity-criterion combinations.
Avoid it when
Inconsistent thresholds or unreadable dense cells.
How to read it
Read row/column labels and status words or symbols.
Use one status per entity-criterion pair. Define missing versus not applicable.
Optional
Alternative wide matrix with criteria as columns.
Preparation
Confirm the metric definition, reporting period, target and favourable direction. Calculate rates or progress before applying transparent status rules.
Units
State each metric's unit. Achievement or completion needs its goal/baseline denominator; status colours and ordinal ratings are not numeric units.
A long table: one row per observation, few columns. New data adds rows.
Worked example
A: CostGreen, ScheduleAmber; B: CostRed. The matrix identifiesB's cost and A's schedule as attention areas under the rules.
