People tend to be vague while stating objectives. But blurry objectives are difficult to assess. It’s important to be really precise and come up with objectives that are smart and nail the problem. You can also add quantities and numbers to make them more objective.

Talking about what didn’t work it’s important to not judge other colleagues or how you have perfomed, but to understand what was the process problem and learn from it. Everything it’s iterative, you can always go back and do it again.

https://kanbanize.com/lean-management/improvement/5-whys-analysis-tool

Remember to investigate also ‘positive’ outcomes. If something went so well that your numbers are exceeding your expectations, please try to understand why. You might have discovered something that can be really useful for the organization to succeed in the future.

Not all actions that you identified must be implemented immediately. Consider writing them down in the Innovation Dashboard. You might be able to tackle those in the future, when you’ll have time and adequate resources to start a new project cycle.

At the end of the 1st iteration of the business process review aimed at reducing the video publication time (link to the problem statement) the project manager performed an After Action Review over the hypothesis set around the solution identified. She detailed a further problem identified along the way and that can be summarized as following: we are not receiving enough videos from International Mobile Staff in the field, and the ones we receive require resources and time for editing, hence reducing their value. This issue, while somehow known, pushed the organization to set up a project that will allow us to understand better the needs and constraints of IMS in the field regarding production of videos.