Planning around open decisions, not dates
The skill is seeing what actually limits a project and scheduling that instead. Larson's claim is that most projects are not constrained by execution time but by missing decisions, approvals and handoffs, so reshuffling the roadmap to free calendar time is a distraction; the thing to accelerate is "making high-quality decisions." You still set one slightly conservative external date, because "dates are the external interface for coordinating across companies," and then manage the work internally as a list of open decisions to close. His example: a credit card application project whose real work was about two weeks was planned for two months, because it carried "a dozen ambiguous decisions" and the plan assumed the team's existing decision pace. Most planning advice tries to estimate effort better; this says effort was never the bottleneck. His other example is passkeys, which never got onto the roadmap: he built it behind a disabled feature flag, used that for review, and it shipped.