Create an account, integrate your tools, and act on insights in minutes.
We show insights like where work is blocked, who's not getting enough feedback, and who's at risk of burnout.
Get updates and stay on track towards your goals with nudges in Slack.
We guide you to dive deeper into the data, to understand what might have caused the trends we identify.
We support you to get context and set goals as a team, with dynamic questions for 1:1s and retros and action ideas.
Gain insights about your team’s process, collaboration efforts, and wellbeing.
Track your progress and receive nudges along the way to help you and your team improve.
Take on recommend next steps and get tips for 1:1’s and retros.
Choose an area for improvement and set goals with your team.
"Without Multitudes, learning and development is quite fuzzy. This tool is perfect for underpinning conversations around progression!"
"A big part of the value of Multitudes is understanding psychological safety on our teams – seeing whether people feel comfortable contributing and who needs support."
"We’ve talked about the 4 Accelerate metrics for a long time; Multitudes allowed us to start measuring and managing them."
"Multitudes gave me a better feedback loop on my role in the team – over just a couple weeks, I doubled the number of reviews I did for my peers"
"Multitudes showed us that some of our team members were getting less support than others and the tool helped us take action to ensure that we’re inclusive and equitable."
👥 We show performance-related metrics on a team level only.
It’s frustrating for everyone when work gets blocked. That’s why we look at how the work is flowing with Time to merge .
This measures the time it takes a PR to go from “ready for review” to merged. This metric is closely related to Lead time, one of the top four indicators of software team performance; more info from Google’s DORA research.
One measure of success for software development teams is what useful features they delivered to customers. To get an indicator of this, we look at Merge Frequency, the number of PRs merged on a team over time. This is related to Deployment Frequency, another one of Google's DORA metrics.
In addition to shipping features, we want to make sure they’re working well once we release them. As a lagging indicator of quality, we look at Change Failure Rate – the percent of deployments that cause a failure in production.
Coming soon: Mean Time to Respond
This measures how quickly an organization recovers from a production failure. These 2 metrics are the last of the 4 DORA metrics.
Code reviews support code quality, knowledge-sharing, and learning. How people participate in reviews can also be an indicator of psychological safety on teams (more in Google’s Project Aristotle).
To help teams understand their collaboration patterns, Multitudes looks at metrics like the Participation Gap (the range of comments, from least to most) and Feedback Flows (which shows the flows of feedback between people and teams).
Research shows that 60% of tech workers are burned out; that’s more than twice the rate of the general population. The COVID pandemic has made burnout worse.
That's why we look at Out-of-hours work , which shows how often people are creating commits outside of their preferred working hours. This is one warning sign of potential burnout.
Coming soon: We’re researching how we might measure big days with no breaks, or long stretches of activity without a day off.
You might be...
We integrate with the tools you already use. From that, we show past and future trends without interrupting your work.
Connect to our Github app to see insights based on your team’s PRs, commits, reviews, and comments.
See insights on how your team works and potential blockers.
Curious about security? Multitudes is built using modern cloud infrastructure practices.