What Is Scheduling? How to Build a Plan That Does Not Fall Apart

The schedule looked perfect the day it was built, and two weeks later nobody is looking at it. Plans do not fall apart because of weak willpower. They fall apart because the collapse was already guaranteed at the point the plan was written. This article covers what scheduling actually decides, the four reasons plans fall apart, and a step-by-step method for building a schedule that holds up.

What Scheduling Is: Assigning Order and Dates So Work Can Actually Happen

Scheduling means assigning an order and dates to the work so that it can actually be carried out. It is not the act of filling a calendar. Anyone can produce a calendar that is merely full.

There is one test: do you personally believe that following this plan will get the work finished? A schedule you submit without believing it is not a plan, it is a wish. What this article covers is the procedure for turning a wish into a plan.

Four Reasons Plans Fall Apart

Before the method, it helps to know why plans collapse. Following the steps without understanding the causes produces the same outcome again.

1. The estimates are optimistic

People underestimate how long their own work takes. And even after overrunning repeatedly in the past, the next estimate comes out optimistic again, because each previous overrun gets interpreted as an exception.

This is not something awareness fixes, so handle it with a mechanism. Estimate from past actuals rather than from your sense of it. Looking up how long a similar piece of work took last time and using that number as the starting point is enough to improve accuracy. The procedure for feeding actuals back into estimates is covered in workload management.

2. Other people's time is not built in

A schedule built only from your own working days will always stretch. The days between sending something for review and getting it back, the wait for sign-off, an external partner's business calendar. None of these move on your schedule.

As a rule of thumb, allow one to two business days for an internal review and three to five for an external one. This waiting is not work, so it does not count as effort, but it lands on the calendar without fail. Separating effort from duration is the key move here.

3. Undecided things have been given dates

Easy to overlook, and the largest in impact. The tool has not been chosen, the budget has not been approved, the owner has not been named. Draw dates beyond that point and the entire plan slides backward from whenever the open question is finally settled.

The fix is to keep undecided items out of the task list. Instead, log "decide by when" with a deadline in the , and build the downstream dates from that decision date. Simply not mixing the settled with the unsettled extends the useful life of a schedule considerably.