Hi AACE Community,
First time to share something on this platform, I will this thread to get your valuable feedback to improve the idea and move it forward if possible.
_____
How Many of Your Activities Are Quietly Dragging Behind the Data Date?
In project planning, we've all seen this:
Tasks that were supposed to start… but didn't.
Tasks that started… but barely progressed.
They don't raise red flags.
They ride the data date.
They get re-baselined.
They look harmless-until they aren't.
And then the delay hits.
Gradually, then suddenly!
🚨 This Is Why I Created the Execution Drag Index (EDI)
EDI is a forward-looking early warning metric that quantifies how much of your remaining scope is already under silent strain-before it impacts the critical path or earned value.
🧱 I developed EDI as part of a broader initiative to build an early warning system for giga projects-something that gives planners a high-level insight into complex, detailed schedules before diving into thousands of lines.
Because in high-stakes delivery, you don't need another report.
YOU NEED A SIGNAL!
At its core EDI = Adjusted Dragging Durations / Total Remaining Schedule Duration
🧩 Let's dive into the basic elements of the EDI:
Identify Dragging Activities: Dragging activities fall into two main types:
1- Dragging Start: Activities that should have started but are still "riding the data date" (not yet initiated) for more than one update cycle.
2- Dragging Finish: Activities that have started but are experiencing progress issues, causing their completion to drag later than originally planned for more than one update cycle.
3- Persistence Rate: This metric quantifies how many reporting periods an activity has been either not-started, or started with slow to no progress, while "riding the data date."
🧩 Factors to Consider in EDI Calculation
When calculating the EDI, two main factors for consideration:
1️⃣ the criticality of the dragging activities and 2️⃣ their persistence rate. Both metrics should be factored into the calculation of the adjusted remaining duration for each dragging activity.
For example, if a dragging activity is critical or near-critical, its remaining duration should be given a higher weighting (e.g., 20%). Similarly, if an activity persists across multiple reporting periods with no progress (as measured by its persistence rate), its remaining duration should also receive additional weight (e.g., 10%) to penalize such behavior.
Example:
Task A, Duration = 10d, Not started for three update cycles, and still non-critical. Adjusted duration = 10+(10%*10) = 11d.
Task B, Rem. duration = 20d , started with slow or no progress for 3 update cycles, the activity is near critical. Adjusted rem. due. = 20+(20*20%)+(20*10%)= 26d
Total Schedule Remaining Duration = 150 days
EDI= (11+26) / 150= 0.247, meaning that 25% of the remaining scope is backlog.
Now let's answer two questions:
First Question, how EDI is different than SPI and BEI (Baseline Execution Index)
1️⃣ EDI, It measures the proportion of remaining scope that is already delayed and dragging. It's a forward-looking index.
2️⃣ SPI, It measures earned progress vs. planned progress (EV ÷ PV). It focuses on past performance vs. baseline.
3️⃣ BEI, It measures actual starts vs. baseline planned starts (Activities Started ÷ Planned to Start). It measures execution reliability.
In a nutshell, EDI is unique because it quantifies future execution risk by detecting activities that are silently stalled-before they impact earned value or the critical path. Unlike traditional metrics, EDI surfaces persistence-based drag in remaining scope, making it a proactive early warning signal, not a reactive performance score.
Second, Execution Drag Index (EDI) – RAG Thresholds & Responses
🟢 EDI < 10%, RAG Value: Green, Minimal execution drag.
Most remaining work is progressing or ready to proceed as planned.
🟠 10-20%, RAG Value: Amber, Growing pockets of delay. Noticeable backlog forming in future activities.
Actions; Trigger targeted schedule audit. Identify recurring dragging activities. Assign task owners to resolve blockers. Escalate to discipline leads where needed.
🔴 >20%, RAG Value: Red, Significant portion of remaining scope is dragging. High risk of slippage to future milestones.
Actions; Escalate to senior management. Initiate a formal recovery plan. Conduct cross-functional review of constraints (approvals, design, procurement, etc). Consider reforecasting major milestones.
Reading (EDI) month-on-month is crucial because it reveals whether execution drag is building, stabilizing, or recovering over time. Tracking trends helps planners detect early warning signals, validate whether interventions are working, and prevent gradual delays from becoming sudden schedule slippage.
This is a trial-a work in progress that might grow into something much bigger.
Or it might need to be challenged, reshaped, and refined by smarter minds than mine.
Thanks,
Mahmoud Eltahawy
------------------------------
Mahmoud Eltahawy
Senior Planning Manager
Riyadh
mahmoud.ma.eltahawy@icloud.com------------------------------