> For the complete documentation index, see [llms.txt](https://handbook.sixpivot.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.sixpivot.com.au/our-culture/feedback.md). # Feedback ### Feedback culture Being a remote first we rely on great communication, and we think improving feedback is part of that. Giving and receiving feedback is not a natural skill. Working with Organisational Psychologist, Dr Jessica Tonissen we are implementing a feedback culture in a meaningful way that fits best for us (not some sort of corporate tick box exercise). ### Rules of engagement for giving feedback {% hint style="info" %} Giving feedback should be: **Genuine, Actionable, Timely, Specific, Safe** {% endhint %} 1. **Have positive intent**, focus of helping others improve. Feedback is not criticism. 2. Frequent and **as close to real time as possible**, however ask for an appropriate time. 3. Use the[ ](https://sixpivot.sharepoint.com/sites/HR/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2FHR%2FShared%20Documents%2FFeedback%2FIEIC%20model%2Epng\&viewid=32273849%2D421f%2D43cc%2D89fe%2Da29c0440303a\&parent=%2Fsites%2FHR%2FShared%20Documents%2FFeedback)[**IEIC framework**](https://sixpivot.sharepoint.com/sites/HR/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2FHR%2FShared%20Documents%2FFeedback%2FIEIC%20model%2Epng\&viewid=32273849%2D421f%2D43cc%2D89fe%2Da29c0440303a\&parent=%2Fsites%2FHR%2FShared%20Documents%2FFeedback) (authentication required). 4. **Ask for permission** to give feedback, make sure the receiver is in a good place to receive feedback - accept people not wanting feedback in that moment. Other considerations for feedback giver: * Allow the receiver time to reflect and ask questions, don't rush through the conversation * Focus on actions, outcomes * Ask questions and listen to responses * Be ok with the receiver disagreeing with you, and deciding not to take action * Positive and negative feedback is important, don't just look for opportunities in one or the other ### Rules of engagement for receiving feedback: {% hint style="info" %} Receiving feedback should be: **Safe, Respectful, Specific, Actionable** {% endhint %} 1. **Assume positive intent**, know that the feedback giver is doing this with the aim to help you improve. 2. **Be respectful**, and give them your attention. This can be hard, resist the feelings of defensiveness. 3. **Be thankful and mean it**, even if you don't agree. Appreciate that the giver has taken the time to give you feedback, most likely putting them in an uncomfortable position. Other considerations for the receiver of feedback * Be honest about your mindset, and defer the conversation if you need to * Listen to what is being said, even though you might not want to * Reflect on what you heard and ask questions, even if this means you need to defer the rest of the conversation * Make a decision on what actions you can take and who will be responsible for follow up if needed. Giver, receiver, or both? ### Our internal whole team training videos * Introductory session [here](https://sixpivot.sharepoint.com/:v:/s/HR/EbJYTA6E0T9DgDKXIsinKxkB1g2xMPZ9n7fh02D-jftzNQ?e=TvcsFW) * Neuroscience of feedback session [here](https://sixpivot.sharepoint.com/:v:/s/HR/EajU91iOcDRPqfdSHDtr_KQBA-96ZIUHlCd-3t6vsNkErw?e=mSBCap) * SixPivot's feedback culture [here](https://sixpivot.sharepoint.com/:v:/s/HR/Eb3GNEpANOtIqXyoYCxnVH4BFub-iiJpDNre9TtlwpxQ_Q?e=TdA2Th) * Framework deep dive [here](https://sixpivot.sharepoint.com/:v:/s/HR/EZxkjxTl87ZOmnbhyD0XUecB7p46WtzPIMXhPBpctLubcA?e=Yflr8E) --- # 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://handbook.sixpivot.com.au/our-culture/feedback.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.