[matt_the_bass]

I use a number of types of checklists at work. They include:

1. Printed checklists that we provide to our integrators that summarize the details we describe in our design guide (we make industrial equipment that needs to be designed into our customers physical and computer systems). These are intended for our customers to confirm the covered all the important details in our design guide.

2. We have a similar type of checklists as #1 for our dealers' technicians to follow when commissioning one of our systems. In this case, the technician needs to sign it and also get the customer to sign it (marking it complete). Plus the technician needs to submit it to us to ensure warranty coverage.

3. We have production checklists when physically assembling and testing our hardware. These require a signature from a supervisor. The purpose is to help ensure that no steps were missed. We keep these in version control with our other documentation and they are updated as we change the process/assembly or find improvements.

4. We have less formal checklists that we manage in Trello. We use them for lightweight project manager. We also save templates of some Trello checklists for reoccurring processes (think sw release todos).

I know that sounds like a lot but we try to keep things as simple as possible. We've found that checklists are easy ways to reduce mistakes and communicate progress/requirements across customers, colleagues, and partners.