Team feedback session

Photo by Wynand van Poortvliet on Unsplash

I recently had a feedback session with my team and my manager suggested a way for us to conduct this session. I found it very effective and I would like to share it with you all. It is the start, pause, stop and keep method, below is what each word stands for.


Here every member of the team lists what they think we should start doing as a team. For example, I suggested that we should start writing a changelog and release notes whenever we push changes to production. Everyone on the team went on to list what they thought we should start doing.


This is where everyone lists what they think we should pause doing. Of course, you must give a reason why the team should pause on that area and if the majority agrees with you, the team puts a pause on that area. Surprisingly we had nothing to pause on, so we moved on to the stop section.


This area is quite interesting because people are always hesitant to suggest what the team should stop doing. But nonetheless, we all had something we thought we should stop doing. For example, we had a slack reminder that would run at the start of the working day reminding us to post our standups but we would all post nothing. We jointly agreed to stop it since we have a tracker board that enables the product manager to track what every developer is working.


I liked this the most because the team was able to point out the good things we all collectively do. For example, everyone was happy with the team communication and initiative exhibited during the implementation of a given task. There were many things the team wanted to keep and I was happy because it meant that at least we all agreed that we were in sync with one another.

I hope you try out this method the next time you meet with your team. If you try it let me know of your experience in the comments below.

Thank you for reading this and if you find it worthwhile, please tag the clap button as many times as you have liked reading the article.