The field guide
How to plan a project, step by step.
Plan a project in five steps, from defining the deliverable to drawing the schedule. Follow a six-week website example and learn the terms as you go.
Written by the studio behind ganttchart.ai · a 6-minute read
Start by answering four questions: what will be delivered, what work will it take, which tasks depend on each other, and when can it be finished? The steps below turn those answers into a schedule.
Each step links to the plain-English glossary for definitions of the planning terms used here.
Start at the end
Name the finish line
Write down what the project will deliver and when it needs to be finished.
Name a concrete deliverable and its due date, such as "the new site is live by November 12." Add a milestone for any intermediate review or handoff. Use those dates to work backwards through the schedule.
Break down the work
List the work
Break the deliverable into tasks that someone can estimate and take responsibility for.
Create a work breakdown by splitting the goal into tasks. For a small project, aim for pieces that take a day or a few days. "Build the site" needs more detail; naming individual CSS variables is usually detail the task owner can manage separately.
Check dependencies
Put the tasks in order
Identify which tasks must finish before other work can begin.
A dependency links tasks: painting waits for the wall to be built, and launch waits for the copy to be ready. Mark these finish-to-start links before setting dates. Review them with the people doing the work so you can catch missing prerequisites.
Estimate and allow for delays
Estimate durations and leave a buffer
Estimate task durations, find the longest chain of dependent work, and allow time for delays.
Give every task a duration. Estimate a range to account for uncertainty. Then find the critical path: the longest chain of dependent tasks, which sets the earliest finish. Tasks off that path have slack; they can slip within that allowance without delaying the project. Keep a visible buffer before the deadline so the team can track how much contingency remains.
See it before it slips
Draw the schedule
Put tasks on a timeline and compare the current schedule with the version the team agreed to.
A Gantt chart shows tasks down the side and time across the top, with one bar per task. The timeline shows how the work overlaps; arrows show dependencies. Save the agreed schedule as a baseline, then compare it with the current version at each status update to see which dates have changed.
All five, in one picture
What the finished plan looks like
Here is a six-week website launch after all five movements: real tasks, in dependency order, with the critical path highlighted and a launch milestone at the end. This is the whole job, drawn once.
Want five more like this — a product launch, an app MVP, a move, a meetup? See the worked examples →
The failure modes
Four common planning problems
Check for these problems before agreeing to the schedule, and revisit them when the work changes.
The plan with no buffer
If every day before the deadline is allocated, a delay may push the finish date. Leave room for work that takes longer than expected.
The task that is really a project
Split a month-long task such as "Build the app" into smaller pieces so you can estimate and track its progress.
The plan nobody updates
Review the plan during the project and update it when dates or scope change. An old schedule cannot tell the team what to do next.
The false parallel
If two tasks need the same person at the same time, check whether that person can do both. Otherwise schedule the tasks in sequence.
One more decision
Do you even need a Gantt chart?
For independent tasks without deadlines, a to-do list or kanban board may be enough. A Gantt chart is useful when you need to track dates and dependencies. Our comparison explains how to choose.
Common questions
Planning, briefly
What are the basic steps to plan a project?
Define the deliverable and due date, break the work into tasks, identify dependencies, estimate durations and a buffer, then draw the schedule and keep it updated.
How detailed should a project plan be?
Make tasks small enough for one person to estimate and take responsibility for. For a small project, a day or a few days per task is a useful starting point. Keep detailed checklists with the task owner.
Do I need project management software to plan a project?
No. You can plan a project on paper, and for small projects that is often the right first move. Software earns its place once the plan has enough moving parts that you need it to reflow dates when something slips — that is the moment a Gantt chart beats a static list.
What's the difference between a project plan and a to-do list?
A project plan connects the tasks to a deliverable and schedule. It records dependencies and expected dates so the team can assess progress and the likely finish. A to-do list may be enough when those relationships do not need tracking.
What is the fastest way to draw a project plan?
Describe the project to ganttchart.ai to generate an initial chart with tasks, durations, dependencies, and milestones. Review the suggested schedule, adjust it, and share the result as a link.
Every planning term above is defined, jargon-free, in the plain-English glossary.
Skip to the drawn version
You've done the thinking. Describe the project in a sentence and let ganttchart.ai draw the first plan — tasks, durations, dependencies, and milestones included. You stay the editor.