> how do we gather improvements that are worthwhile and specific enough to solve our problems...?<p>My teams have tried many ways, and we like using a lightweight template thanks to medical professionals: <a href="https://github.com/joelparkerhenderson/issues/blob/master/TEMPLATE.md" rel="nofollow">https://github.com/joelparkerhenderson/issues/blob/master/TE...</a>
I've seen different teams and sometimes for some reason it's quite challenging to get folks participate in retrospectives in a meaningful way. E.g. it's hard to come up with a few things that went bad for engineers. And it's not a matter of trust, it's something else. Does it come with practice? What are the techniques to get people involved?