> If yes, then in my current company I've learnt to script the hell out of them (though not too early — only once you see how the typical pattern/path is shaping up). Good automation (a.k.a. scripting) can help a lot to reduce brittleness of deployments.
Can you elaborate on how you accomplish this? I read the checklist manifesto a few years ago and started using checklists for things like checkins, code reviews, etc. I figured these kinds of lists could be automatable, but I was never able to come up with a UI that was easier than a pre-populated textarea.
Can you try to list some example of what you have on your checklist? It'd help me understand your particular trouble, currently I don't have a good idea of it. Also, haven't read "the checklist manifesto", I understand you mean the book by the title. On technical side, there are pre-commit, pre-push etc. hooks in git, and bots like Travis-CI for github.
Checklist automation does not have to be graphical, and does not even have to look like a todo list. A list of failing checks, separated from waived checks (with clear signoffs from specific usernames), is generally sufficient.
If yes, then in my current company I've learnt to script the hell out of them (though not too early — only once you see how the typical pattern/path is shaping up). Good automation (a.k.a. scripting) can help a lot to reduce brittleness of deployments.
Or "TODO" checklists? If yes, then personally I use https://github.com/jffrymrtn/temaki, though it has some limitations for me, so I'm trying to build a replacement/ripoff and extend it to my needs.