Those who have participated in a Coverdale training already know it: the process review after each work order. You can also design a retro in the OKR process in a very similar way.
One of the essential tools in collaboration – whether in classic or agile environments – is, in addition to a results flashback, the process flashback, called a retro in the OKR cycle. We reflect on how the collaboration worked in the previous cycle at this point in the process.
With this toolbox, I provide you with a small “roadmap” for facilitating a retroactive process to be able to design the process flashback helpfully:
In the first round, have all participants formulate two “catchwords” that come to mind when they look back on the past cooperation process. In a second round, each participant can explain their words.
This step creates a first picture of the different perspectives on the cooperation in the past cycle.
All participants write down what they perceived as helpful and what they perceived as a hindrance in the past cooperation.
In this step, it is essential that everyone focuses on the description of behaviour in the cooperation (i.e., the process) and that no evaluations occur.
After everyone has explained their helpful and hindering aspects, an agreement for the next cycle is affected, which includes four points:
Drop: What will we not do / “throw overboard” next time?
Add: What will we do that is new?
Keep: What will we keep?
Improve: What will we strengthen?
Ideally, you should formulate these agreements in complete sentences, each of which begins with “We …”, i.e. really have an “agreement character”. And don’t forget – visualize all these steps in a way that is understandable to all participants.
In the next retrospective, you refer to the agreements made, to what extent they have been lived, are still valid and are being supplemented.