Engineering governance · Portfolio view
Engineering Team Health Dashboard
A cross-team view of delivery, product quality, operational reliability, security and engineering practices. Use status patterns to guide conversations and interventions—not to rank teams.
Illustrative data only
Green status cells
13
Across 20 assessed indicators
Amber status cells
5
Issues to monitor and mitigate
Red status cells
2
Require urgent attention
Grey status cells
0
Missing or unvalidated evidence
Team health by dimension
Each circle represents a status against the agreed expectation for that dimension.
Green
Amber
Red
Grey
| Team | Delivery | Quality | Reliability | Security | Practices | Key issue |
|---|---|---|---|---|---|---|
ATeam A |
Green |
Green |
Green |
Green |
Green |
None material |
BTeam B |
Amber |
Green |
Amber |
Green |
Amber |
External dependency |
CTeam C |
Red |
Amber |
Green |
Red |
Amber |
Critical vulnerability |
DTeam D |
Green |
Amber |
Red |
Green |
Green |
Repeated incidents |
Consistent status rules
Apply the same definitions across the organisation, while allowing the evidence and expectations to reflect each product’s context and risk.
Green · Meets expectationNo material unmanaged risk; agreed outcomes and controls are in place.
Amber · Needs attentionA bounded or emerging issue has a credible mitigation and named owner.
Red · Urgent interventionA material threshold is breached, a commitment is not credible, or urgent action is required.
Grey · Evidence unavailableData is missing, stale or not yet validated. Never treat unknown as green.
How to interpret this view
Do not average away critical riskA red security status remains material even when delivery and other dimensions are green.
Look for patterns, not rankingsUse repeated amber or red signals to identify systemic constraints, dependencies and support needs.
Make action and ownership visibleFor each material issue, record evidence, accountable owner, mitigation and target date.