[icebraining]

I've been convinced that checklists are great (by theory and by practice), yet I still write way fewer than I should.

I strongly dislike repetitive mental work, and writing a checklist is essentially resigning myself that such work will be necessary. Until I write it, I can still convince myself I'll be able to automate the process.

[MaulingMonkey]

I use checklists to turn mental work ("uhh, let me think, what all do I need to do...") into straightforward physical work ("check, next step..."). I also use checklists as a first step towards automation and a stopgap until automation is complete, since I live in a constant state of infinite backlog.

If I run through the checklist a couple times and it seems to:

    [ ] Cover everything
    [ ] Not require complicated decision making or value judgments
    [ ] Has few edge cases in need of handling
    [ ] Doesn't require automation-opaque tooling
    [ ] Not change more frequently than I execute the checklist

Then I know I have a prime candidate for automation, and already have great documentation of exactly what to automate.

[Cyphase]

Awesome, a meta-checklist.

[TeMPOraL]

Isn't a checklist something you'd end up writing anyway in the process of determining how to automate process?

At least that's what I keep telling myself. I also write much fewer checklists than I should.