What is Pacing (Program)?
Pacing is deliberately timing component starts, finishes, and outputs so the program flows: benefits arrive when the organization can absorb them, shared resources aren't double-booked, and dependent components meet instead of colliding. It's tempo management at the layer above any single schedule.
A perfectly fast component can be a program problem — delivering change faster than operations can absorb it destroys the benefit it carries.
Worked example
A retailer's transformation program slows the store-rollout component on purpose: stores are converting faster than the training component can certify staff, and early converted stores show sales dips. Pacing holds conversions to twelve per month — slower than possible, exactly as fast as beneficial.