Let's measure success in Digital Engineering

July, 2024

Everyone says Digital Engineering improves outcomes.

But here’s the problem: we rarely measure it well.

We talk about “transformation,” “efficiency,” and “collaboration”—but what data proves it’s working? In a world where 70% of construction projects still run over time or budget (McKinsey, 2023), claims aren’t enough.

To build trust and secure real buy-in, DE needs evidence.

And that starts with using the right metrics: not just lagging results—but leading signals.

Most Digital Engineering Metrics Come Too Late

The majority of DE success stories rely on lagging indicators—like fewer RFIs, reduced rework, or improved handover.

Those are great. But they arrive after the damage (or success) is already done.

You can’t steer a project by looking in the rear-view mirror.

Leading vs. Lagging: What’s the Difference?

Leading indicators = early signals of progress. They’re proactive, actionable, and within your control.
Lagging indicators = outcomes. They confirm results—but only after it’s too late to change them.

Use both. But lead with… leading.

Start Tracking Leading Indicators

Leading indicators are early, actionable signals that help you spot what’s working—before it's too late.

BIM Implementation: The percentage of design packages using coordinated models before IFC (leading) can predict a reduction in design conflicts detected during the construction phase (lagging).
Digital Collaboration: The number of virtual design and construction (VDC) sessions per design phase (leading) can lead to a decrease in Requests for Information (RFIs) during construction (lagging).
Digital Skills Development: Hours of digital technology training completed per team (leading) can result in smoother tool adoption (lagging).
Cloud-based Project Management: The percentage of project teams accessing the model via CDE weekly (leading) can predict better version control (lagging).
Mobile Technology on Site: The percentage of issues logged via mobile tools (leading) can decrease the time between issue identification and resolution (lagging).
Digital Quality Control: The frequency of digital quality checks performed during construction (leading) can reduce post-handover defects and warranty claims (lagging).

Leading indicators give you feedback when you can still act on it.

How to Test This in Your Project

You don’t need enterprise dashboards to try this. Start simple:

Pick 2–3 Leading Indicators: Choose ones that relate to a goal your project already cares about—like reducing rework or improving communication.
Set a Simple Baseline: Use last month’s data, or estimate based on past projects. Perfection isn’t the goal—visibility is.
Track Weekly or Fortnightly: Make it visible: a shared dashboard, a site board, or even a whiteboard in the meeting room. The key is frequency and consistency.
Share What You See: Review with your team. Discuss what’s helping—and what’s not. Adjust actions, not just dashboards.
Link to Lagging Outcomes: At project close, compare your leading indicators to actual outcomes. You’ll start spotting patterns—and building a case for smarter digital investment.

Example of how this can be developed into a simple management register:

Every project is unique, so the indicators that work best for your project may differ based on specific goals and challenges. Tailoring these metrics to your context ensures they remain relevant and actionable.

Shifting Focus: Begin with the Right Measurements

You can’t manage what you don’t measure. But you can’t measure only what’s already happened.

Digital Engineering is a long game—but it starts with short feedback loops.

The future of DE belongs to those who make its value visible, early and often.

Pick one leading indicator. Start tracking it next week.

Then tell your team: “We’re not just delivering models—we’re measuring momentum.”

Page updated

Google Sites

Report abuse