What a Good Plan Does

A plan is a tool for decisions

A plan is not a document produced to obtain approval and then filed. It is the team's shared understanding of what will be delivered, how, by whom, when and at what cost. A good plan lets people answer practical questions quickly: What happens if this supplier is three weeks late? Can we bring the opening forward by a month, and what would it cost? Which work matters most this week? If a plan cannot answer questions like these, it is decoration.

A schedule is one part of the plan: the activities, their durations, their logical order and the resulting dates. The wider project plan also covers scope, cost, resources, risk, quality, procurement and communication. Many planning failures come from treating the schedule as the whole plan — for example, a schedule with confident dates and no link to the resources that must deliver them.

Planning effort should match the project

Planning has a cost. A two-month internal project may need a one-page milestone plan and a simple bar chart. A two-year construction project needs a fully linked, resource-loaded schedule with a dedicated planner. The intermediate skill is judging the right level: enough detail to see problems early and test options, but not so much that maintaining the plan takes more effort than it saves. A useful test: if this activity slipped by a week, would anyone need to know? If not, it may be too detailed to track separately.