D-016
[?] open
- date:
- org:
- Infrakit · Head of product team
- category:
- Release quality
- title:
Make the release call from test evidence instead of hiring QA
- context:
- With AI-assisted building, more changes reach a release faster. Leadership wanted someone to own the overview of release quality. The obvious answer was a dedicated QA hire.
- decision:
- Proposed that I make the go/no-go call for releases, based on test data (which tests exist and what they show) plus my view of customer cases and how fragile they are, with end-to-end and regression tests part of the developers' definition of done.
- hypothesis:
- Releases that hurt fragile customers become rare. Missing test evidence is visible before a release, not after it. The call does not turn into a queue waiting on me.
- confidence:
- 60%
- review_date:
- reversibility:
- two-way
- related:
- D-015
- tags:
- proposal, release-quality, testing, ai-era

