Who makes the final go/no-go call on your releases, and what do they look at?

A question for anyone who ships software.

On every team I've worked with, the final "ship it" was a judgment call in a meeting. QA said green. Translations were "done". Nobody had looked at accessibility since the last audit. Each report was fine on its own, and the bugs that hurt us were sitting in the gaps between them.

AI made the building part much faster. The deciding part is still the same meeting.

So how does it work on your team?

1. Who makes the final call? One person, a checklist, or whoever is in the room?

2. What do they look at before saying yes?

3. Has a release ever passed every check and still gone wrong? What got through?

I'm on the founding team at KaDeep AI and this question is most of my job right now, so I'd like the real answers more than the process-doc ones.

6 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.