Set targets for your key metrics

Key metrics show you where your engineering organization stands today. Now you can also show where you want it to go.

You can set a target at the organization level, and it applies to all of your teams. From there, you can adjust the target for individual teams where it makes sense. If an organization-wide target isn’t a fit, you can skip it and only set targets team by team instead.

Improvement projects tend to go better when everyone knows what they’re aiming for. Targets make that goal visible to everyone who looks at the metric, not just the people who set it.

When you set a target, the selector plots your teams against Swarmia benchmark ranges. Targets that are too far out of reach don’t help anyone, so it’s a good idea to start from where your teams are.

Once a target is in place, you’ll see it on the key metric cards and in the table. The sparkline on the card highlights when a team dips below its target, so you can spot the change without digging into the data.

Admins can set targets for any key metric today.


Subscribe to our newsletter

Get the latest product updates and #goodreads delivered to your inbox once a month.

More changelog updates
· Sep 11, 2026

Find out how much of your cycle time is spent in draft

Cycle time is an aggregate metric, and alone it doesn’t describe where things slow down. Now you can look at each pull request stage and analyze outliers in each — whether it’s review time, merge time, in progress time or time as a draft. Draft time shows how much of a pull request’s cycle time it…
Read more
· Sep 7, 2026

Connect GitHub Issues to Swarmia [beta]

You can now connect GitHub Issues to Swarmia as an issue tracker, alongside a growing number of other issue trackers . Once connected, your GitHub issues flow into Swarmia and behave just like any other issue. That means you get the full picture: metrics like cycle time and flow efficiency, plus an…
Read more