A to-do list tells you what to do. A project plan tells you when, and what happens to everything else when one thing slips. The gap between the two comes down to three ideas that sound technical but are genuinely simple. You don’t need a PM certification to use them.
1. Dependencies: what has to come first
A dependency is a task that can’t start until another finishes. You can’t paint a wall before it’s built; you can’t deploy before the code is written. The most common type is “finish-to-start”: Task B starts after Task A finishes.
Once you mark dependencies, your flat list becomes a chain (or a web) of “this, then that.” This is the single highest-value thing you can add to a task list, because it’s what lets dates be calculated instead of guessed. Set the start date and each task’s estimate, and the dependencies determine when everything else can actually happen.
2. The critical path: the chain that sets your finish date
Some tasks have wiggle room. Others don’t, if they slip, the whole project’s end date slips with them. The critical path is the longest chain of dependent tasks through your project. Its length is your shortest possible finish date.
Here’s the practical payoff: if you want to finish sooner, only shortening tasks on the critical path helps. Speeding up a task that isn’t on it does nothing for your end date, it just creates more idle time. Knowing your critical path tells you exactly where to put effort (or extra people) to actually move the deadline.
3. Slack: how much a task can slip before it hurts
Slack (or float) is how long a task can be delayed without pushing the project’s end date. Tasks on the critical path have zero slack, any delay there is a delay everywhere. Tasks off it have some breathing room.
This is why “everything is behind!” is usually wrong. Often only the critical-path tasks are truly urgent; the rest have slack you can spend. Knowing which is which keeps a small delay from feeling like a crisis.
Putting it together
- List the tasks and give each a rough estimate.
- Mark dependencies, what must finish before each task can start.
- Let the dates calculate from a start date plus the estimates and dependencies, rather than typing dates by hand.
- Watch the critical path. When something slips, you immediately see whether it threatens the finish date or just eats into slack.
The reason to let software calculate this rather than maintain it in a spreadsheet is that real plans change constantly. Move one task and a tool can ripple the dates through every dependent task instantly; doing that by hand is where spreadsheets go to die.
A note on capacity
Dependencies answer “what order?” They don’t answer “does one person have time to do all of this at once?” A good planner also accounts for who’s assigned, so two tasks owned by the same person don’t get scheduled on top of each other even when their dependencies would allow it. Order plus capacity is what makes a schedule realistic.
The takeaway
Dependencies turn a list into a chain. The critical path tells you which links set your deadline. Slack tells you where you have room. Together they’re the difference between hoping a project lands on time and knowing what it would take.
teckyz builds the schedule for you, mark dependencies and estimates, and it calculates dates, highlights the critical path, and ripples changes when something moves. It even drafts the initial plan with AI. See how it works or start a trial.