Interesting, I have a very different experience. My team does retrospective once a month (we don't do Scrum, so it's not tied to "sprints") and every month we a

Interesting, I have a very different experience. My team does retrospective once a month (we don't do Scrum, so it's not tied to "sprints") and every month we actually do some improvements. Sometimes the problems are small, let's say our products have inconsistent CLI interfaces for developers, and that slows us down, so we decide to unify it. Sometimes it's big stuff, for example the team feels that we don't have enough clarity about long term of the product, or there are too many interruptions. Then it's my (EM) or PM's role to figure stuff out. Some of the good things we changed as a result of retro: we removed stand-ups, we agreed to meet in the office once a week, we introduced a daily support rotation for our users (we build internal tools). We can't fix everything, but every month we get something done, and that keeps the team motivated to bring new ideas to retros.