Unlock the CORE 4 Metrics: Boost Engineering Speed Today

Let's be honest: measuring engineering productivity is hard. For decades, leaders have struggled, relying on flawed metrics like lines of code or ticket counts that tell a tiny fraction of the story. They measure activity, not impact. They create pressure, not progress. What if there was a better way?

Enter the CORE 4 metrics, a modern, balanced framework that acts as a holistic "report card" for your engineering team. It isn't just another acronym. As detailed in resources like Lenny's Newsletter, it was developed by experts from the communities behind DORA, SPACE, and DevEx, designed to finally unify how we think about engineering performance [1].

What Are the CORE 4 Metrics?

CORE 4 is an opinionated framework that gives you a comprehensive and balanced view of your engineering organization's health. It was introduced to provide a new standard that combines quantitative data with qualitative feedback for a more complete picture.

The most important principle of CORE 4 is that the metrics are designed to be used together. This is their superpower. By tracking them as a system, you create a healthy tension that prevents teams from gaming the system. For example, you can't just optimize for raw speed if it tanks your quality. It forces a balanced approach, which is exactly what high-performing teams need.

The Four Pillars of CORE 4 Explained

The framework is built on four key areas that cover the entire engineering lifecycle, from the developer's keyboard to the end user's experience.

1. Speed (Diffs per Engineer)

Speed is a simple proxy for output and team activity. It’s typically measured by the volume of code changes—like pull requests or merge requests—per developer over a specific period. It helps you understand the rhythm and cadence of your team's work.

Crucially, this is an aggregate, team-level metric. It should never be used to compare or stack-rank individual engineers. Its purpose is to spot trends. Is the team's overall pace increasing or slowing down? That’s the question Speed helps you answer.

2. Effectiveness (Developer Experience Index - DXI)

Productivity isn't just about code output; it's about the developer's journey. Effectiveness moves beyond code to quantify friction in the development process. It's measured with a Developer Experience Index (DXI), usually through surveys that ask engineers about their satisfaction with tools, the speed of their feedback loops, and the quality of documentation.

A high DXI score is a leading indicator of productivity. It means developers can stay in a state of flow, solving problems and shipping value without fighting their tools or processes.

3. Quality (Change Failure Rate)

This metric is borrowed directly from the highly-respected DORA framework. Quality is measured by the Change Failure Rate (CFR), which is the percentage of deployments to production that result in a failure requiring remediation, like a hotfix, rollback, or patch.

CFR is the essential counterbalance to the Speed metric. It ensures that shipping faster doesn't mean breaking things more often. A low CFR is a sign of a mature, stable, and reliable delivery process. If you want to boost delivery speed, you have to keep an eye on quality.

4. Impact (% of Time on New Capabilities)

Impact is the most business-centric metric of the four. It measures the proportion of engineering effort spent on building new, value-adding features versus "keeping the lights on"—the necessary work of maintenance, bug fixes, and paying down tech debt.

This metric is vital for connecting your team's day-to-day work directly to business goals. It helps answer the big-picture question: "Is our engineering investment driving the business forward?" Tracking Impact ensures that your team’s incredible talent is focused on work that truly matters [2].

How CORE 4 and DORA Work Together

Many teams are already using DORA metrics, and that’s a great starting point. The good news is that CORE 4 and DORA aren't competitors; they're partners. They provide different lenses to view the same goal: building a high-performing engineering organization.

Think of it this way:

• DORA metrics are the industry standard for measuring the health and efficiency of your delivery process. They tell you how fast and stable your software pipeline is.

• CORE 4 metrics add crucial human and business context on top of DORA's process-level data. This gives engineering leaders a more complete guide to what’s really happening.

Here’s a simple analogy: DORA is the health check for your delivery engine, while CORE 4 is the balanced report card for the entire car's performance—including the driver's experience and whether you're heading in the right direction. For a deeper dive, you can explore more about DORA-driven analytics tools.

How to Get Started with CORE 4

Adopting this framework doesn't have to be a massive, disruptive project. You can start small and build momentum with this actionable plan.

Step 1: Start with DORA as Your Foundation

If you aren't already, begin by establishing a baseline for the four DORA metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service). Connect your Git provider and CI/CD tools to an analytics platform to automate data collection. This gives you an objective look at the health of your delivery pipeline without manual effort. Remember the golden rule: DORA measures the system, not the individuals. Use it to find system-level bottlenecks first.

Step 2: Layer in CORE 4 for Deeper Context

Once you have your DORA baseline, use CORE 4 to understand the "why" behind the numbers. As the creators explain, the goal is to unify developer productivity frameworks into a single, cohesive view [3].

This combination of process and people metrics gives you a powerful diagnostic tool. For example:

• Is your Lead Time for Changes (DORA) high? Your Developer Experience Index (CORE 4) might reveal that slow code reviews or a clunky local development environment are the root cause.

• Is your Deployment Frequency (DORA) low? Look at your Impact metric (CORE 4). Is the team bogged down by an overwhelming amount of unplanned maintenance work, preventing them from shipping new features?

• Is your Speed (CORE 4) high but Impact is low? This might suggest your team is busy but not necessarily effective, spending too much time on low-value tasks or code churn.

Step 3: Automate Measurement with a Unified Platform

Manually collecting, cleaning, and correlating all this data from Git, Jira, and survey tools is a huge headache. It's time-consuming, prone to errors, and just isn't scalable. This is where modern analytics platforms become essential.

Platforms like Weave automate the entire process. Weave connects to your existing toolchain to provide DORA metrics alongside deeper insights into engineering work. Instead of just counting PRs, Weave uses AI to normalize engineering work into a single unit, moving beyond simple activity counts to measure the substance of the work itself.

By turning raw data from your tools into actionable intelligence, you can get a clear, objective view of performance that perfectly aligns with the balanced principles of CORE 4, all without the manual busywork.

See the Full Picture

The CORE 4 metrics—Speed, Effectiveness, Quality, and Impact—offer a balanced, actionable, and modern way to understand engineering performance. When combined with the process insights from DORA, they give leaders the complete picture needed to debug bottlenecks, improve developer happiness, and connect engineering work directly to business outcomes.

To continue learning, explore more topics on the Weave blog.

Are you ready to see the full story behind your team's performance?