Here are some questions to ask as you begin to look back at how the work was conducted.
- What guidelines should be used to ensure the review is a safe space?
- Who should participate in the review?
- Based on what we discover in our review, what do we want to continue doing?
- Based on what we discover in our review, what do we want to stop doing?
- Is there anything we should have done that we did not do?
- Who owns the implementation of any process changes needed?
Digging Deeper
Reviewing is a critical part of the ROAMER Model that encourages reflection on the solution as well as the health of the stakeholders involved. For instance, a team going through a leadership change management process may want to look back and ask if there was anything they could have done better, or anything they would do again. Another team building a software engineering solution may want to look back at a previous block of work and evaluate how successfully they were able to deliver code, and whether or not there are any optimization opportunities to streamline future delivery. Alternatively, a group working on building a new in-person experience may want to take the opportunity to evaluate their progress in improving one part of the experience, and ask themselves whether they can improve their efforts in the next part of the work.
