> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/project-work/working-practices/aar-after-action-review.md). # AAR - After Action Review The purpose of the AAR is to constantly improve our processes based on our experiences with projects. Our current process for this is: * Whole project team gets together after the project has been completed, booking between 1-2 hours. * Project team ideates with sticky notes on what didn't work on the project, this can be anything from client communication, contractual issues, deliverables, etc. * The facilitator creates categories of issues based on what he observes is being written down. * Each team member puts their points on the board and category and gives an overview. No solutions are discussed. * Everyone votes on what they feel are the most critical issues to avoid next time and fix right away. * The facilitator takes the most voted issues and arranges them in a row. * Solutions are discussed and one sticky note per solution is added. Multiple solutions for one issue is fine. * Next steps to solve issues permanently are done. * Spend 5-10 mins looking at what went well in the project! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://process.mad.co/project-work/working-practices/aar-after-action-review.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.