How many engineers are on your team?

Full-time people whose primary job is writing code.

In a typical week, how many of them ship something to customers?

Anything reaching production — features, fixes, improvements.

When was your last production release?

The last time new code reached customers.

Top-quartile teams: multiple times per day.

What share of your engineers use AI coding tools daily?

Tools like Cursor, Claude, or Copilot that help engineers write code.

Top-quartile teams: 60% or above.

When something breaks in production, how long until it's fixed?

From "we noticed" to "customers are okay."

How long between work being ready and reaching customers?

The lag between "engineer thinks it's done" and "users see it."

AI-first teams: under one business day.

How often does your team write automated tests for what they ship?

Tests are code that checks other code. More tests, fewer surprises.

Healthy teams: most of the time.

Would you trust your engineering lead's answer to "how many features shipped last month"?

A reliability check on your team's internal visibility.