It works better with your own checklist, right?
If people have to find their own actions based on the expectations and requirements, they really own their solution. Checklists they create are seen as a tool that helps them to do their work instead of being patronized by others. If people have a clear understanding of the expectations and are empowered to take the right actions, they can adjust their solutions to the current situation and needs more easily.
For instance, if a team has to use a strict template for a certain type of document, to provide information for maintenance for support, they will always deliver it in this way. Usually it doesn’t care if it helps in this way to do maintenance or if the way of creation is effective. A team who knows the expectations and builds their own solutions based on them can optimise the way of creation and deal with the users of the documentation to meet their needs. You should work on a clear understanding of what’s expected from the team so that a self organised team can work on how to achieve it.
I saw teams in this situation building themselves a checklist that helps them, but it felt different, because it was owned by them.
In one of the next blog posts we will talk a bit more about tools like Non functional requirements and Release Definition of Done to create clear expectations for a team and Story Definition of Done and Working Agreements as tools owned by the team to help them organise their work.