No one gave any feedback…so now what?
We’ve all been in that meeting. The meeting where the organizer asks for feedback on a project. What went well? What can we do better next time? What they got as an answer was…crickets. Nothing. Nada. What happens then?
Retrospectives, whether part of an Agile project or not, make good teams better. When a project runs smoothly, is on time and produces a successful outcome, what is there to discuss? Quite a few things, actually. Continuous improvement takes time. It can be viewed as team building or as process improvement. No matter how you slice it, retrospectives are important. Here are four positives that come from conducting retrospectives, even when feedback is at a minimum:
Boost morale: When individual contributions are recognized, attitudes and moods improve.
Learn to adapt: the only thing you can count on is change, and discussing changes, both good and bad, helps navigate those changes more smoothly.
Create trust: Discussing projects’ positives and negatives regularly strengthens trust among your peers.
Empowerment: Everyone’s voice is heard, and all contributions are important. This encourages better participation in all roles.
So the next time you’re in that meeting and the organizer asks for feedback on a project, know that there is plenty to discuss, discover, and decide in your group. If there’s a team and a project, you should have a retrospective meeting.
Interview: The Value of Medical Device Connectivity: Sitting Down with Doug Frede
Download our interview with True Process President Doug Frede to get an insider’s view of the business value of medical device connectivity, including:
internal vs. external value propositions, the technologies pushing connectivity forward, and the four basic challenges currently preventing widespread connectivity adoption.