The Tech Debt Ledger and Risk Register turns quiet technical exposure into a short, ranked list that a leadership team can act on.
Risk Register
| Category | R / Y / G | What we found | Owner | Next action |
|---|
| Cybersecurity | | | | |
| Legacy systems | | | | |
| Unsupported hardware | | | | |
| Brittle integrations | | | | |
| Vendor concentration | | | | |
| Key-person dependency | | | | |
Risk Entry Card
| Field | Entry |
|---|
| Risk | |
| Category | |
| Description | |
| Likelihood | |
| Business impact | |
| Current control / safeguard | |
| Rating | |
| Owner | |
| Remediation action / target date | |
Rating Test
| Question | Answer | Signal |
|---|
| Active problem or known near miss? | | Active exposure pushes toward red. |
| Business impact if it failed tomorrow? | | High impact raises the rating. |
| Working safeguard in place? | | No safeguard means red; partial means yellow. |
| Named owner? | | No owner is itself a risk. |
Top Three to Act on Now
| Priority | Risk | Category | Owner | Next action | Target date |
|---|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
Quarterly Risk Review
| Review question | Better | Worse | Notes |
|---|
| Did the top-three actions get done? | | | |
| Did any new incident or near miss appear? | | | |
| Did any yellow slip toward red? | | | |
| Should any risk move onto the roadmap or budget? | | | |