# How to tell whether your team can sustain the pace AI set | LinearB Blog

> The engineering health dashboard in LinearB shows who absorbs your review volume, how much each developer holds at once, and where delivery drags. 

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._


```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://linearb.io/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "How to tell whether your team can sustain the pace AI set",
      "item": "https://linearb.io/blog/engineering-health"
    }
  ]
}
```

[Home](https://linearb.io/)

/

[Blog](https://linearb.io/blog)

/

How to tell whether your team can sustain the pace AI set

# How to tell whether your team can sustain the pace AI set

![Photo of Jamie Birss](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/headshot_8d1e617011?_a=BAVMn6ID0)

By [Jamie Birss](https://linearb.io/blog/engineering-health#jamie-birss)

|

September 9, 2026

![Feature_b918f11193](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/Feature_b918f11193?_a=BAVMn6ID0)

Your merge rate is up, your teams are shipping more than they did a year ago, and the same handful of engineers open every review that matters. AI raised the volume of code arriving, and the work of judging that code goes to whoever holds the most context about your systems.

That volume does not convert evenly. In LinearB's benchmark data, drawn from [more than 8.1 million pull requests](https://linearb.io/resources/engineering-benchmarks), AI-generated pull requests merge at 32.7% while human-written ones merge at 84.4%. Review capacity is what the volume runs into, and the reviewing itself is toil that's being created for a small number of people. Getting visibility into that is challenging with the metrics most engineering orgs track, because cycle time, deployment frequency and PR throughput describe how fast code moves rather than who absorbs the cost of the speed.

The engineering health dashboard in LinearB reports on that cost directly, and it's available now to every customer with [metrics builder](https://linearb.helpdocs.io/article/uubbonyo3o-metrics-builder-in-linear-b) enabled.

Your browser does not support the video tag. 

## **See who absorbs your review volume**

An average review count across your organization can look healthy while most of the reviewing sits with a handful of people. The average is the number that hides the problem, because the load that wears people down is the load that concentrates.

Review load imbalance in LinearB reports how many more reviews your top 20% of reviewers complete than everyone else, against the previous period. When that multiple climbs while your reviewer count stays flat, more of your delivery depends on fewer people.

![image.png](https://assets.linearb.io/image/upload/v1788878003/image_e4633c1568.png)

Underneath it, reviewers by weekly review load groups your reviewers by how many reviews each one completes per week, so you can see the shape of the distribution. Weekly review load by group tracks the same split over time, plotting the share carried by the top 20% against the bottom 80%.

Weekend activity is the other half of this, reporting on the percentage of developers who are using their personal time to get through their workload. 

Active developers on weekends trends that week by week, so a sustained rise separates one hard release from a pattern your delivery has come to depend on.

When the distribution is skewed, the fix is usually routing rather than hiring. [Kraken cut their review time by more than half in four months](https://linearb.io/case-studies/kraken), from 2 days 15 hours to 1 day 3 hours at P90, after finding that 70 to 80% of their slowdown came from time zone differences, team silos and reviewer availability rather than from the size or complexity of the changes.

## **Parallel work is where cognitive load shows up first**

Reviewing is interrupt-driven and arrives on top of whatever a developer is already carrying. The Context Switch metric reports the average number of work items a developer handles at once, indicating how much context switching your delivery currently requires.

Planned vs. unplanned completion compares completed and uncompleted items across planned and unplanned work, urgent work items % shows the weekly share of items at each priority level, and tickets in progress per developer trends the total in progress against the per-developer figure. When you read the three together, they tell you whether a rise in parallel work came from more work entering or from the same work sitting longer.

## **Check whether the work reaching review is ready for it**

Reviewers can clear a long queue when the work in it is finished. What eats the week is the work they have to send back, and queue length never tells you how much of that is coming.

Task readiness in LinearB reports average PR maturity, which is how complete and ready work is when someone reviews it, and PR maturity trend breaks that down weekly across maturity bands. 

A falling score means more of what arrives needs rewriting once a reviewer looks at it properly.

Development drag shows the average time work items wait at each workflow stage. The stage with the longest wait is where your delivery accumulates frustration, and it is rarely the stage your team assumes.

## **Get complete visibility into engineering health in LinearB**

Each of these answers one piece of whether you're absorbing AI's output in a way your engineering organization can sustain, and together, on one dashboard, they answer the whole of it. You can see who carries the review load, how much each developer holds at once, how much of the work arrives unplanned, and whether what reaches review is ready for it, cut by team and trended against the previous period.

If your delivery pace currently depends on a small group of people, this is where you find out which people and by how much. [Book a demo,](https://linearb.io/book-a-demo) and we'll walk your own numbers with you.

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

![headshot_8d1e617011](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/headshot_8d1e617011?_a=BAVMn6ID0)

## Jamie Birss

Jamie is a product marketer at LinearB with a soft spot for great technology and the humans who make it. Outside of work, you'll usually find him out running a trail, or shipping his next puzzle game.

### Connect with

[](https://www.linkedin.com/in/jamie-birss/)

## Your next read

[![Cover image for How to keep seeing when your software factory runs in the dark](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/Blog_Post_Name_2400x1256_5_c9af1d9dc4?_a=BAVMn6ID0)](https://linearb.io/blog/software-factory-night-vision)

AI

[How to keep seeing when your software factory runs in the dark](https://linearb.io/blog/software-factory-night-vision)

How to keep visibility as your SDLC runs without humans: LinearB, HumanLayer and Warp on tracking autonomy and measuring quality past the merge. 

[![Cover image for Why the best agentic security removes engineering friction](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/Blog_Whythebestagenticsecurityremoves_2400x1256_e31ce7ae58?_a=BAVMn6ID0)](https://linearb.io/blog/1password-nancy-wang-agentic-security-no-long-lived-secrets)

AI

[Why the best agentic security removes engineering friction](https://linearb.io/blog/1password-nancy-wang-agentic-security-no-long-lived-secrets)

1Password CTO Nancy Wang on why the best agentic security removes engineering friction. Discover how no long-lived secrets keep agents and engineers safe.

[![Cover image for Simplicity in model-driven agents and MCP drives real engineering gains](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/Blog_Simplicity_in_model_driven_agents_2400x1256_e67f24d00b?_a=BAVMn6ID0)](https://linearb.io/blog/aws-clare-liguori-model-driven-agents-mcp-simplicity)

AI

[Simplicity in model-driven agents and MCP drives real engineering gains](https://linearb.io/blog/aws-clare-liguori-model-driven-agents-mcp-simplicity)

AWS's Clare Liguori on why the model, not the scaffolding, should carry the load in agent development. Discover how simpler agents and MCP drive real gains.

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io/",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to tell whether your team can sustain the pace AI set",
  "url": "https://linearb.io/blog/engineering-health",
  "author": {
    "@type": "Person",
    "name": "Jamie Birss"
  },
  "datePublished": "2026-09-09T08:30:00.000Z",
  "dateModified": "2026-09-09T08:30:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1788877918/Feature_b918f11193.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "The engineering health dashboard in LinearB shows who absorbs your review volume, how much each developer holds at once, and where delivery drags. "
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Watch now](https://linearb.io/resources/the-great-software-factory-debate)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)