Menu
We go into detail on our metrics here: What We Measure and Why
In addition to helping you visualize key metrics, we also share insights about those metrics. Insights are made up of the following:
The insight value is outside of the target and not getting closer to it
The insight value is outside of the target zone but trending towards it, or within the target zone but close to the threshold
The insight value is well within the target
Any changes to custom targets will immediately affect the insights (text, value, trend, and status) and Actions in the app. Of course, the time range of data will also affect insights and Actions, in this case, it's important to know that the At a glance view and Trend Summary behave differently.
At a glance view
As this view is designed to be a high-level overview, the date range is fixed to the last 6 weeks. The insights and Actions are only affected by changing custom targets.
In other words, changes to selected dates in the Trend Summary section will not affect this view.
Trend Summary
As this view is designed to help teams take action with granular data, the date range can be modified. The insights and Actions are therefore affected by both changing dates and changing custom targets.
To give an idea of what “good” looks like, our metrics show a default industry benchmark. We also allow teams to set custom targets, because we recognize that teams may have different considerations (e.g., hardware teams may be limited in Lead Time due to physical operations, some teams may want to beat industry standards).
Targets, whether custom or industry benchmarks, are what drive the insights that Multitudes shows you, whether in app or via our notifications in Slack or email.
There are two ways to customize targets:
Navigate to Settings > Targets or click the “Customize targets” button on the top right of the At a glance section on the My Insights homepage. Customizing a target is as simple as clicking on a target and editing it!
To be clear, in this table:
For a cell with a given team row and metric column, if the text of the cell is colored:
Note that this table currently lets you set targets for 5 of our metrics, Lead Time, Merge Frequency, Change Failure Rate, Out-of-Hours Work, and PR Participation Gap. To set targets on other metrics (or also for these metrics, as a secondary option), see the option below.
On a metric-specific pages (as accessed from the left hand menu bar), wherever you see a chart with a green target zone, you can customize the target here by going to the legend and clicking on the small target icon next to the “Target” label. This will show a modal from which you can edit the target. Click “Save Changes” to trigger a chart refresh.
Note that if you’ve selected multiple teams or have “All” as the team filter at the top right of the page, the target shown in the legend will be the target for the organization as a whole.
Install our Jira integration to get insights like Types of Work and Feature vs Maintenance Work.
We pull up to 200 Jira projects, ordered by the latest issue updated. We check for new projects and update this list daily.
Note that in order to install this integration, you must have Owner or Manager level permissions.
On the Multitudes app, go to the Integrations page (from the menu, find Account, click Settings, then click the Integrations tab across the top). Find the card that says Jira in the top Integrations section and click ‘Connect’ at top right.
After you click 'Connect' on the Jira card on the Integrations page, on the resulting pop-up click ‘Connect Jira projects’
This opens a new page on Atlassian Marketplace, click ‘Try it free’
This pops up a modal. In this modal, first, select your site; second, click the button to ‘Start free trial’. Don’t worry this integration is not separately charged beyond your instance of Multitudes!
This pops up a new modal, click ‘Get started’
This will close the modals, on the resulting page, a dialog box should pop up on the lower left hand corner indicating that the install is in progress. Once complete, it will show success, from this dialog box, click ‘Get started’
A new tab will open, on this tab, click ‘Allow access’
A new tab will open, scroll to the bottom and click ‘Accept’
This will close the last tab. On the resulting page, click the button ‘Connect with Multitudes’
Now, you should be brought back to our app, where you’ll see a pop-up asking you to link Jira projects to Multitudes teams. First, make the selections as desired. Second click ‘Finish linking teams’
Lastly, you’ll see a success message in the pop-up!
⚠️Please note that once the installation is finished and teams are linked, you will need to wait a few minutes, then refresh the app to see the charts. Until the charts are ready, you will see the message "No data for this time period" on the Value Delivery page:
Install our Linear integration to get insights like Types of Work and Feature vs Maintenance Work.
Note that in order to install this integration, you must have Owner or Manager level permissions.
On the Multitudes app, go to the Integrations page (from the menu, find Account, click Settings, then click the Integrations tab across the top). Find the card that says Linear in the top Integrations section and click ‘Connect’ at top right.
After you click 'Connect' on the Jira card on the Integrations page, on the resulting pop-up click ‘Continue to set up Linear’
This opens a new page, click 'Authorize Multitudes'
Now, you should be brought back to our app, where you’ll see a pop-up asking you to link Linear teams to Multitudes teams. First, make the selections as desired. Second click ‘Finish linking teams’
Lastly, you’ll see a success message in the pop-up!
Set up our GitHub Actions integration to get insights like Deployment Frequency , Lead Time through to deploy, Deploy Time, and Deployment Failure Rate.
NOTE: You can use either our Deployments API or our GitHub Actions integration to provide us with data about deployments. If you already have our Deployments API integration configured, you will need to revoke that action token before connecting with our GitHub Actions integration.
In the Multitudes app, go to Settings > Integrations and click on the Connect button in the Github and Github Actions card
On the resulting modal, click to configure Github Actions data
On the next page of the modal, you can choose either the “Environment/Deployments” or “Workflows” option, based on how you use GitHub Actions. See details below the image.
Don't know what to pick? Here are some common scenarios:
“I have one workflow that deploys to multiple environments
A note on historical data availability: Due to constraints on GitHub’s API, we will not be able to fetch historical deployment data for this option.
Here's a concrete example
“I have a specific workflow that deploys only to prod”
With respect to data availability in either case, once you have integrated GitHub Actions, we will have real-time data, and will take the first successful attempts to deploy to production going forward (since that is when the change is first available to customers).
Once you’ve made a selection, the following page of the modal will prompt you for further configuration. In either case you will:
Screenshot for if you selected “Environment/Deployments”
Screenshot for if you selected “Workflows”
All done!
If you need help with this integration, please contact support@multitudes.co.
This is the installation part complete. You can now revoke the API token in PagerDuty as we only use it to set up the webhook. In the top navigation bar, navigate to Integrations > API Access Keys, find the API key you just created, and click Remove on the right hand side of the row.
The next two steps in Multitudes help you configure your data so that it is accurate and comprehensive.
1. User linking: see the section on user linking for how to match your Multitudes team members to PagerDuty users, so that incident assignments and pages are attributed to the correct people in Multitudes.
2. Default filter setting: choose which field would be most useful for you to filter incidents on, between urgency and priority level.
We use your API token to create a webhook. You can see this in PagerDuty by navigating to Integrations > Generic Webhooks (v3).The webhook sends us events on updates to incidents, which powers our PagerDuty-related insights about incidents and pages in Multitudes.
Please don't edit this webhook, as it will impact the delivery of data into Multitudes and affect the accuracy of your insights. This includes the multitudesId custom header is used to identify your PagerDuty organization inside Multitudes.
If you have any questions about the settings, please contact support@multitudes.co.
To uninstall the app, please contact support@multitudes.co.
To uninstall the webhook:
1. In PagerDuty, in the top navigation bar, navigate to Integrations > Generic Webhooks (v3).
2.Under Subscriptions, find the webhook called https://pagerduty.prod.multitudes.co/events. Click the "..." menu on the right hand side of the card, and click Delete.
Some insights on Multitudes, such as Mean Time to Restore (MTTR) require your organization to install an integration with Opsgenie. After you’ve installed Opsgenie, you’ll be able to see insights for more metrics!
.png)
Note: Multitudes tracks MTTR by looking at your Opsgenie <code-text>incidents<code-text>. It does not look at Opsgenie <code-text>alerts<code-text>. The Opsgenie <code-text>incidents<code-text> feature is only available to paying Opsgenie customers.
Multitudes contributors must be linked to their corresponding user accounts from your integrations, in order for integration data to appear in the app. This is so that Multitudes knows whose data is whose, and so that contributors can have confidence that their data is being attributed accurately.
For example, if you link the contributor <code-text>Sam Smith<code-text> in Multitudes with the user <code-text>sam-smith<code-text> in Jira, that tells us that the issues assigned to <code-text>sam-smith<code-text> should be attributed to the <code-text>Sam Smith<code-text> and the teams they're part of in Multitudes.
We currently have user linking for our GitHub, Linear, and Jira integrations. We are in the process of rolling it out for all our other integrations too.
There are 3 states that a user can have:
If verification is required (e.g. the contributor has access to Multitudes, and the email they use for Multitudes is different to the email they use for the integration in question), we send an email to the user's integration email address. The user can then click the magic link from their email, which lets us know that they are indeed the same person.
If they are linked to users in other integrations, and they also use the same email address, those links will automatically be verified.
Example: The Multitudes contributor "Sam Smith" logs in to Multitudes using <code-text>sam.smith@acme.org<code-text>. They have the following user links:
Unfortunately, Jira does not allow us to retrieve email addresses of users (upvote this feature request to expedite this!). This means that we can't verify user links. Our UI will show links to Jira users as linked with no further action required, but on hover you will see a tooltip that indicates that they are not verified and that verification is not available.
Go to Settings >Integrations. Click "Configure" on the integration that you'd like to edit the user links for. This will bring up a modal listing all your Multitudes contributors. You can use the dropdowns next to ech contributor to select the corresponding user in the integration.
You can link an unlinked contributor, or change the link of an already-linked contributor, in one of these three places. Unless you are a Manager or Owner, you can only edit user links for your own team member.
1. Settings > Team Members: Click on a specific team member. Under their display name, you will see a row of tags showing the integrations you have installed. Clicking on these will open a modal for editing that link.
2. My 1:1s: Click on a specific team member's 1:1. Under their display name, you will see a row of tags showing the integrations you have installed. Clicking on these will open a modal for editing that link.
3. Settings > Teams: Click "Edit" on a team. There is table of user links, with contributor names & profile images, and the logos of installed integrations. You can click the checkboxes/icons to open a modal for editing that link.
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).
On the Merge Frequency chart on the Value Delivery page, you’ll see an option to choose between Collaborative PRs orAll PRs in the top-right corner of the chart. This toggle lets you only see PRs that had input from other team members (not just the PR author), like a comment, a review, or a merge.
In either situation, PRs authored by bots are excluded.
We generally try to filter out bot activity as this does not represent actual collaboration or work by team members. PRs authored by bots includes:
On some Trend Summary cards on our My Insights page, and on the Flow of Work > filters bar > “Show more filter” menu, there is an Exclude weekend hours toggle.
You can turn this toggle on to exclude weekend hours from the calculations like Lead Time. “Weekend hours” are personal to each individual; it includes all hours during their custom non-working days. For example, if someone works part-time Monday to Wednesday, and the toggle is turned on, any hours on Thursday, Friday, Saturday and Sunday would be excluded because this is their weekend.
You can configure non-working days for each team member in Settings.
Multitudes uses people’s working hours to calculate out-of-hours work. We have a default setting for this (Mon-Fri, 9 am - 5 pm in the timezone of your company’s headquarters), but because people work flexibly, we strongly recommend that you configure this for your individual preferences.To change the working hours for you or a teammate, go to Settings > Team Members, and select the person you want to adjust. Scroll down to the “Working Times” section, make changes as needed to the Timezone, Work days, or Working hours, and then choose “Confirm.”
Some insights on Multitudes, such as out-of-hours work, are based on a team member’s working times. These are individually configurable but we start with the following defaults:
If you have a team member who works different hours or in a different timezone, you will likely want to update the default settings and back-date the changes so that person's historical data matches their actual working hours. To do that, follow the steps below.
First, go to Settings > Team Members, and select the person you want to adjust. Scroll down to the “Working Times” section and make changes as needed to the Timezone, Work days, or Working hours.
After you make changes to the "Working Times" section, a banner will appear (see screenshot below). Choose “Yes, back-date these changes”.
This will back-date your current working time settings, applying the current settings to the last 12 months of data for this person. This includes recalculating metrics that use these settings, such as Out-of-Hours work.
If you do not want to back-date the changes to Working Times, click “No, update from today” and the app will apply your settings from that point onwards, just like any other setting.
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.
You can configure the seniority of team members who are Contributors to provide color-coding on the Feedback flows chart. At the moment, anyone can edit seniority for anyone else.
To do so, go to Settings > Team members, click on a Team member who is a Contributor (see the column on Data Inclusion). On the page that opens for that team member’s profile:
See image below
