Multitudes provides insights focused on a few key areas for teams. Here is a quick overview, but for more information on why we’ve chosen these measures, how we calculate them, and what good looks like, check out this page: What We Measure and Why.
⭐️ A star indicates a one of the 4 Key Metrics published by Google's DevOps Research and Assessment (DORA) team.
Flow of Work: These insights are all about how the work gets done – Multitudes shows how quickly the team finishes work and what’s blocking or interrupting people along the way. We measure things like:
Value Delivery: This section focuses on the value created for customers.
Quality of Work: This section balances the volume of work with the quality, answering questions like how much re-work is required or keeping track of releases with bugs.
*These metrics can relate to performance. Since PRs are a team sport, we only show these metrics at the team level, not the individual level.
Productivity is about more than just speed and output. As the recent paper on SPACE metrics points out, metrics signal what is important to an organization - and DORA metrics alone cannot capture critical dimensions like employee satisfaction, well-being, retention, collaboration, and knowledge sharing. This is why we also have people metrics to complement our process metrics.
Wellbeing: These insights provide an indicator of how people are doing – are they working long hours? Does the team communicate in ways that promote psychological safety? We measure things like:
Collaboration: These insights are all about how the team collaborates to get work done – who’s getting support and who’s not? Who’s doing a lot of work to support others? We measure things like:
Check out this blog post for more information: What We Measure and Why
Check that the email address that is in your local git config (<code-text>user.email<code-text> when you do <code-text>git config -l<code-text>) matches the email address(es) that are linked to your GitHub account. You can change this by either changing git config to match an email that’s in GitHub, or by adding your git config email address to your GitHub account under https://github.com/settings/emails. If the emails are different, GitHub won’t know how to match your commits to your GitHub login (although it still links it to the account because of your SSH keys).
We’ve left the team structure flexible so it can meet your needs: We allow people to be on multiple teams, or on no teams at all.
However, if someone is not on any team, then they won’t appear in our graphs (since our tool is focused on helping teams work better together). As soon as you add them to at least one team, then they will be included in our insights.
By measuring team behaviors, Multitudes is able to spot where people are being excluded in the day-to-day work. Because of systemic bias, good intent sometimes doesn’t translate to fair and equitable actions. Multitudes helps you track whether you’re living your values in practice, and then will point out any gaps and suggest potential next steps. As you take action to improve, you can use Multitudes to track your progress.