Leanmote now supports as a first-class integration — bringing the same depth of engineering analytics to teams using Microsoft's DevOps platform as we've long offered for GitHub, GitLab, and Bitbucket.

## What Gets Connected

With a single OAuth connection, Leanmote syncs data from two Azure DevOps surfaces:

## How to Connect

Once connected, your Azure DevOps data flows into all the same dashboards your team already uses: Performance Delivery, Project Financials, Strategic Overview, and more.

## Who This Is For

Any engineering team that uses Azure DevOps as their primary platform — whether for repositories, project tracking, or both — can now get the full Leanmote experience without needing to migrate tools or maintain manual exports.

If your organization uses a mix of Azure DevOps and GitHub (or other platforms), Leanmote handles multi-source setups automatically, combining data across all connected integrations into a single unified view.

## Why It Matters

Azure DevOps is widely adopted across enterprise engineering teams, particularly in organizations with Microsoft-centric infrastructure. This integration removes the last barrier for those teams to adopt Leanmote's engineering intelligence platform without changing their existing toolchain.

Leanmote now includes — a dedicated dashboard available in both and that answers the question every engineering leader is asking:

## AI Impact in Performance Delivery

The AI Impact section in Performance Delivery is split into two views:

### Delivery Correlation

This view connects AI usage data directly to your team's delivery metrics, surfacing three key signals:

- — lines produced via tab-style completions (e.g., Copilot suggestions accepted by the developer)

- — lines written directly by an AI agent flow, with minimal manual editing

This distinction matters: delegation is a stronger signal of AI reliance than assistance. The dashboard shows the split as a percentage and tracks how it evolves over time.

### Adoption & Usage (AI Impact - Others)

This view gives you the raw adoption data behind the signal:

## AI Impact in Project Financials

The AI Impact tab in Project Financials adds a financial lens to AI usage:

## How to Connect AI Data

AI Impact works with (with Copilot telemetry enabled) and . Once connected via Productivity Tools, metrics appear automatically — no additional setup needed.

## Why It Matters

AI tools represent a significant and growing investment for engineering teams. AI Impact gives you the data to move beyond anecdotal evidence and measure — with real delivery and financial data — whether that investment is paying off.

We're launching — a new AI-powered module that automatically detects where your engineering workflows are slowing down, before those slowdowns turn into missed deadlines or frustrated teams.

## What Is Bottleneck Insights?

Bottleneck Insights continuously analyzes your engineering data and surfaces the patterns that are degrading delivery performance. Instead of waiting for someone to notice that velocity is dropping or PRs are piling up, the AI proactively identifies the root causes and brings them to your attention.

## What It Detects

The AI looks across your full delivery workflow and flags issues like:

## How It Works

Bottleneck Insights runs in the background and surfaces findings with a dedicated section in the product where you can browse current and recent bottlenecks, each with supporting data and a plain-language explanation of what's happening.

Each insight includes the context needed to act: which team, which repo, which time period, and what the expected baseline was. No manual analysis required.

## Why It Matters

Engineering teams generate enormous amounts of delivery data, but the signal is often buried in the noise. Bottleneck Insights applies AI to do the hard work of pattern recognition — so your engineering leaders spend less time diagnosing and more time removing blockers.

This is the first module in Leanmote's track, with more AI-driven analysis coming throughout the year.

now includes engineering performance data alongside investment information — giving engineering leaders and finance stakeholders a single place to understand not just is being spent, but it's being delivered.

## What's New: DORA Metrics in Project Financials

The four DORA metrics are now surfaced directly within Project Financials for each project or initiative:

Seeing these metrics in context with project spend lets you answer questions like:

## What's New: PR Activity in Project Financials

In addition to DORA, is now visible per project:

## Why the Combination Matters

Traditionally, engineering investment data and delivery performance data lived in separate tools and separate conversations. By bringing them together in Project Financials, Leanmote enables a new kind of analysis:

This update is available for all projects tracked in Project Financials. No additional setup required — if your repositories are already connected, the metrics will appear automatically.

We've significantly expanded the dashboard with two major upgrades: a full Cycle Time breakdown and a new set of advanced filters — giving engineering teams and their leaders the precision they need to identify exactly where work slows down.

## Full Cycle Time Breakdown

Cycle Time now goes beyond a single number. It's broken down into its four key stages, so you can pinpoint where delays are happening in your delivery pipeline:

Understanding which stage is the bottleneck is the first step to fixing it. A long Review Time points to a code review process problem. A long Deploy Time might signal a slow CI/CD pipeline. Now you have the data to act on the right thing.

## Advanced Filters: Branch, Author & More

The Software Delivery dashboard now supports a richer set of filters so you can slice data with more precision:

These filters work in combination, so you can ask questions like:

## Why It Matters

Generic averages hide the real story. With Cycle Time broken down by stage and advanced filters, teams can have more targeted conversations about where to improve — and leaders can track whether those improvements are working over time.

We're introducing — a new high-level module designed for engineering leaders who need a consolidated, real-time pulse on their entire organization without jumping between dashboards.

## What Is Strategic Overview?

Strategic Overview is a command center that surfaces the most critical signals across your engineering org in a single screen. Instead of drilling into individual team or project dashboards, leaders can now get an at-a-glance view of:

## Who Is It For?

Strategic Overview is built for CTOs, VPs of Engineering, and engineering managers who are responsible for multiple teams or the full org. It's the answer to the question: — without needing to ask anyone.

## How to Access It

Navigate to in the main menu. You can customize which metrics and teams are visible using saved views, and share the view with other leaders using a public link or team share.

## Why It Matters

Before Strategic Overview, getting a cross-team picture of engineering health required either manual reports or switching between multiple dashboards. Now, everything your leadership team needs to make fast, informed decisions is in one place — always up to date, no prep required.

You can now save, share, and duplicate custom views in Performance Delivery and Project Financials — making it easy to collaborate with your team, align stakeholders, and build on existing configurations without starting from scratch.

## Personal Saved Views

Each user can create and save their own private dashboard configurations. Saved views capture your filters, metrics, and layout so you can return to them in one click — no need to reapply settings every time.

## Share Views with Your Team

Collaboration is now built in. Once you've saved a view, you can share it in three ways:

## Duplicate Views

Need a similar configuration with small tweaks? Duplicate any existing view and modify it without affecting the original. This is especially useful for creating variants (e.g., one view per team or project) based on a standard template.

## Where It's Available

Share and Duplicate are available in both and dashboards.

## Why It Matters

We’re redesigning the Team Interaction Map to better reflect how collaboration happens at scale. The new version will focus on clarity, structure, and directional insights, making it easier to analyze cross-team communication and engagement.

Key Improvements:

Team-Level Grouping: Users will be visually grouped by their assigned teams, simplifying the analysis of internal vs. external collaboration.

Directional Arrows: Arrows will now indicate the direction of interactions, showing who initiates communication and who receives it.

Scalability: Optimized for large organizations — the new map will support up to 200 users without performance degradation.

Multiple View Modes:

Total Interactions View: See all user-level communication across the org.

Grouped by Team View: Understand team-to-team relationship dynamics.

Enhanced Color Coding & Layouts: Clearer visual clusters and less node overlap to improve usability and pattern recognition.

User Value:

This improvement will help engineering and people leaders:

Detect communication silos or bottlenecks

Identify under- or over-engaged teams

Improve coordination in distributed or multi-team setups

We’re excited to announce that Leanmote now integrates with Notion!

You can now track key project management metrics directly from your Notion databases.

What’s new?

Automatic sync with Notion projects

Visibility into task cycle times, throughput, and team workload

Works seamlessly with existing Jira, Monday.com, and ClickUp integrations

Full support for custom status fields and project views

This update helps teams using Notion streamline performance tracking and improve delivery insights — all in one place.

➡️ To enable the integration, head to Productivity Tools > Notion Integration in your Leanmote dashboard.

We’ve expanded Leanmote’s analytics with new team activity metrics to give you deeper insight into sprint planning and task execution patterns.

🆕 What’s new?

🌀 Sprint Efficiency (Jira)

Measure what percentage of planned tasks were actually completed during sprints over the selected period — helping you track commitment vs. delivery accuracy.

🗂️ Assigned Tasks (Jira)

View how many tasks were assigned in sprints during the selected time frame. Great for spotting load distribution trends.

🔁 Reworked Tasks

Identify tasks that moved backwards in status during their lifecycle — a signal of blockers, rework, or scope changes.

These new metrics provide greater visibility into how your team plans, executes, and iterates — enabling better retrospectives and continuous improvement.

➡️ Available now in the Team Metrics and Sprint Reports sections.