5 Sources of Delivery Friction That Don't Show Up in Status Reports

Most delivery leaders know when a project is late. The harder question is why it got there — and why the warning signs didn't surface sooner.

In our experience assessing enterprise delivery functions, the root causes of slow, expensive, and unpredictable delivery are rarely the ones that appear in weekly status reports. Status reports capture symptoms: missed milestones, escalated risks, budget variance. They don't capture the structural friction that makes those symptoms inevitable.

Here are the five friction sources we see most often.

1. Decision latency

Work doesn't stall because people are idle. It stalls because decisions take too long. In many enterprise environments, approval chains add days or weeks to what should be a same-day call. Scope changes sit in inboxes. Prioritisation discussions get deferred to the next steering committee. Dependencies on other teams create a queue that nobody owns.

Decision wait time may not appear in a task status. Recording open decisions and their owners helps a team see where work is waiting and address delays across the portfolio.

2. Reporting overhead

As a portfolio grows, compiling status reports, slide decks and updates across tools can take time away from managing delivery. Measure the effort spent on reporting to see where a simpler process or AI-assisted draft could help.

This is also a quality issue: manually compiled reports need a clear data cut-off and a review of what changed before the steering committee meets.

3. Fragmented tooling

Delivery teams may use a PPM tool for portfolio tracking, an engineering tracker and spreadsheets for local planning. Without an agreed source for each measure, teams can spend time reconciling different views.

If updates need to be assembled across systems, programme-level visibility takes extra effort. Explicit imports provide a snapshot; they are not live sync with the source tools.

4. Unclear ownership at the seams

Within a well-run project team, ownership is usually clear. But delivery friction accumulates at the boundaries: between teams, between programmes, between delivery and business stakeholders. Who owns the dependency between Programme A's API team and Programme B's integration workstream? Who decides when a shared resource conflict gets resolved?

When ownership is unclear at the seams, coordination becomes informal. And informal coordination is the enemy of predictable delivery.

5. No feedback loop from delivery data to operating model

Most organisations collect delivery data — burndown charts, velocity, milestone completion. But very few use that data to improve how they operate. The same estimation approaches persist despite consistent overruns. The same governance ceremonies continue despite consistently failing to catch problems early. The same resource allocation model stays in place despite evidence that it creates bottlenecks.

Without a systematic feedback loop from delivery data to operating model design, friction reproduces itself indefinitely.

What to do about it

Friction isn't something you fix with a tool purchase or a process change memo. It requires a structured diagnosis of where friction exists, how severe it is, and which interventions will have the biggest impact.

That's what a delivery effectiveness assessment does. It scores your maturity across six domains — governance, planning, risk, execution, team, and tooling — surfaces the friction patterns that are costing you time and money, and produces a prioritised improvement roadmap.

If you recognise these friction sources in your own delivery function, an assessment will tell you exactly where to start.