There is however some evidence of teams entering some kind of routine in sprint retrospectives after some time \cite{mchugh2011agile}, not achieving the desired level of reflection with retrospectives, thus reducing continuous improvement \cite{andriyani2017reflection} or “some several phenomena that could affect the outcome and efficiency of the team-level retrospectives\cite{lehtinen2017recurring}. This seemed to be the scenario we addressed here. The team was stalled in a kind of negative inertia after the agile transformation was consolidated and it was hampering the culture of continuous improvement brought by the adoption of Lean Kanban. It probably has to do with retrospectives being mostly focused on analyzing technical issues and short-term goals, or maybe the team environment was not favoring sincere communication. However, the fact is that the experience served to get back to the continuous improvement path.