Article

Lag vs explicit activities: what actually works in practice

Target keywords: lag in project management, Gantt lag vs activities

Lag is common in professional scheduling.

It is also one of the most misunderstood features in project management tools.

What lag does

Lag applies an offset directly to a dependency:

  • Finish-to-Start + 3 days
  • Start-to-Start − 2 days

It modifies behavior — without adding a visible task.

Why lag causes confusion

Lag:

  • Is not visible in the timeline
  • Cannot be reported on
  • Is easy to forget
  • Hides logic inside metadata

This makes schedules harder to review and explain.

The explicit alternative

An explicit wait activity:

  • Appears in the plan
  • Can be named and explained
  • Can be reported on
  • Makes delays intentional

From a modeling standpoint, it is clearer and safer.

Why many tools still support lag

Lag persists because:

  • It exists in legacy tools
  • Users expect it
  • It’s fast for simple cases
  • Compatibility matters

A pragmatic approach

The most effective approach is:

  • Encourage explicit wait activities
  • Allow lag for compatibility
  • Make lag visible when used

This preserves clarity without alienating experienced users.

Final thought

Lag is not wrong — but hidden logic always is.