A Team Trend Summary is a type of slack notification that shows a development team's metrics, and the value changes in comparison to the previous time period. Targets are based on academic research, domain knowledge, and industry benchmarks, such as Google’s DORA metrics or the SPACE framework for developer productivity.
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 show medians here as it is less likely to be skewed by outlier values, such as a specific PR with a very long wait time. We measure things like:
This section focuses on the value created for customers.
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:
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:
For more on why we’ve chosen these measures and how we calculate them, check out this blog post: What We Measure and Why.
A Team PR Alert is a type of slack notification that shows a development team's PRs that need to be reviewed.
The following metrics only look at non-draft PRs that have been updated (edited, commented, reviewed) in the past week, to avoid surfacing stale PRs.
These have been reviewed and waiting to be resolved/merged for more than 8 hours.
These have been reviewed and waiting to be resolved/merged for less than 8 hours.
A 1:1 prompt is a type of slack notification that shows the top 3 reflection ideas to discuss, based on a team member's data.
Who is included in a 1:1 prompt?
Anyone that is assigned to your Profile > 'Who you have 1:1s with'
When does this get sent?
You can pick a day to receive this, at a weekly or fortnightly cadence.
How can I share this with my team member?
Once your team member has configured their Slack connection to the Multitudes app, they will receive a copy of the conversation starters. To do this, the team member must have access to the app.
Good enough depends on a team’s working patterns and human context, so we recommend comparing to your previous summaries.
If you’d like to discuss your summaries with other engineers that care about supporting healthy team cultures, you can join #share-slack-summaries in our Multitudes Community Slack.