The day has passed, the date has changed, nothing has changed. What to do about silence at retrospectives

This article addresses a common issue in IT teams: ineffective retrospectives where discussions fail to lead to real changes and participants remain silent. The author notes that a lack of feedback does not always indicate that everything is fine; it is often a sign of burnout, distrust in the process, or a lack of psychological safety. The material analyzes the reasons for such behavior and offers practical recommendations for facilitators. The main focus is on how to turn unproductive complaining sessions into a constructive tool for improving workflows. The author emphasizes the importance of every team member's engagement and the necessity of documenting specific actions that will actually be completed before the next meeting. This article is useful for team leads and Scrum masters looking to improve productivity and team atmosphere.