Hold a brief debrief that identifies what helped, what created friction, and what the team should repeat or adjust. Keep the discussion focused on learning and practical improvements rather than blame.
What questions should a change debrief include?
A team can ask what it expected, what actually happened, which parts helped people do their work, and where information or support fell short. Close by agreeing on one or two changes to carry into the next transition.
Bringing Play into the review adds curiosity, so the team can test ideas without treating an imperfect first attempt as proof that experimentation was a mistake. For example, after a new scheduling process creates confusion, employees might map the handoff, try a clearer template for one cycle, and compare what is easier to follow.
How can the team turn the debrief into a useful next step?
Keep the review short and specific. Invite people closest to the work to speak, separate observations from assumptions, and assign an owner to each follow-up. A useful debrief ends with a clearer next attempt, not a longer list of complaints.
Questions like this one, and many more about teamwork and morale, are explored in the FISH! Philosophy upgraded trial, which gives your team 30 days of access to the FISH! film and its digital guides.
