# Project evaluation ### Introduction This meetings tend to happen at the end of the project cycles, where a call is made by any project team member to hold it, and where all are invited and expected to participate. During this call client's feedback from Client's project evaluation should be already available. This should be a meeting to give constructive feedback between the team and to appreciate one another. The expected outputs are personal and collective learning. ### Prompts to drive the conversation Feel free to ask for prep. time before the meeting and/or leave space to make an active reflection on the spot. Some dimensions to focus during the reflection could be about our the impact on the client, the deliverables or results, how the process went with them, how the process went among us, our expectations of the project as captured in the [project canvas](/handbook/processes/team-setting.md#workplan), etc. Then Some questions * Check in * What's been our impact? How do we feel about it? * What we liked about the project and what we’d like to see more * What we liked about our peers and what we’d like to see more * What our main learnings we would like to share with the rest of the collective and/or design community? * Check out --- # Agent Instructions: 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: ``` GET https://weareholon.gitbook.io/handbook/processes/project-closure.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.