Score Technical Debt Against Decision Criteria
The founder applies a standardised diagnostic rubric to evaluate the severity, maintainability impact, and refactoring cost of each identified debt area. They calculate an overall technical debt risk score that reflects the immediate threat to MVP stability and venture scalability.
Completing this action produces a quantifiable, objective score reflecting the venture's overall technical debt exposure. It provides a decision-ready benchmark that enables founders and investors to evaluate technical health against defined venture-building tolerances.
The founder must provide a completed scoring matrix detailing individual scores across security, scalability, maintainability, and code quality. This output must include a clear overall risk rating supported by explicit rationale for each sub-score.
Five questions an expert would ask when reviewing your output
Use these to challenge assumptions, pressure-test your logic, and check the quality of this action's output in the context of the parent task and wider venture development.
- 1
What specific benchmarks did you use to justify assigning a low risk score to your current automated test coverage?
- 2
How does this diagnostic score change if key engineering contractors leave the venture within the next month?
- 3
Why do you believe your refactoring cost estimates are realistic given your team's historical estimation accuracy?
- 4
How does this technical debt score compare with industry standards for ventures at a similar pre-seed or seed stage?
- 5
What sensitivity testing have you performed on this score against unexpected user growth surges?