A sankey chart showing flows of feedback between team members
**What it is:** This graph shows how much feedback each person gave on other people’s PRs, how much feedback they got on their own PRs, and how feedback flows between people. If you have[ levels set up](/configuration-and-setup/configuring-your-team.md), the graph will be color-coded by level, which can help you quickly see at-a-glance if feedback flows are as expected across your team.
**Why it matters:** The [top benefits of code reviews](https://smartbear.com/state-of-software-quality/code-review/) are improving code quality, knowledge-transfer, and learning. Moreover, there’s [bias in who gets good feedback](https://fortune.com/2014/08/26/performance-review-gender-bias/). Visualizing feedback flows can show us whether there are silos, and how we’re doing across the team at supporting each other.
**How we calculate it:** We look at the number of comments and reviews that each person (or team) gave and received on their PRs. We then show how the feedback moves across people and teams.
{% hint style="success" %}
**What good looks like**
In the best teams, everyone is giving feedback and everyone is receiving feedback, or at least asking questions about others’ work. In these teams, members in senior levels give plenty of feedback to juniors and intermediates – and juniors and intermediates feel comfortable asking questions to seniors.
{% endhint %}
We also look at several indicators of collaboration. In this bucket, we’re examining who gets support and who’s not getting enough support. We also show the people who are doing a lot of work to support others. This type of [“glue work”](https://noidea.dog/glue) is easy to miss but is important for team success and [benefits the whole organization](https://hbr.org/2018/07/why-women-volunteer-for-tasks-that-dont-lead-to-promotions).
These metrics show patterns in comments on GitHub. To see review patterns, you can turn on the `Show reviews only` filter; this will show only reviews with at least 1 comment, rather than all comments.
---
# 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://docs.multitudes.com/metrics-and-definitions/people-metrics/collaboration/feedback-flows.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.