Interactive widget covering the three scheduling skills: sequencing tasks, reading rosters, and reading timetables

The hardest part isn't doing the work — it's figuring out what order

Three skills, one habit of mind. Sequencing tasks is about dependencies — most delays happen because someone started a task before the thing it needed was ready. Reading rosters is about two directions at once: across a row for one person's week, down a column for one day's coverage. Reading timetables is about working backwards from when you must arrive. Pick a view and drag the slider.

Project timeline Planning phase
Drag to advance through project stages
Week 0 • Planning
Start Week 3 Week 6 Week 9 Done
Tasks complete
0/8
Days ahead/behind
On track
Sequential scheduling means tasks happen one after another — you finish Task A, then start Task B. This is safer when tasks depend on each other, like you can't paint a wall before you've built it. But sequential schedules take longer because nothing overlaps. If your eight tasks each take one week and you do them sequentially, your project takes eight weeks. The trade-off is predictability: you always know exactly where you are, and you're never juggling multiple moving parts at once.
Know This

A dependency is any task that must finish before another can start — understanding these relationships determines whether you can run tasks in parallel or must schedule them sequentially. The same reading skill runs through all three views: rosters are read in two directions — across a row for one person, down a column for one day — and timetables are read backwards from the time you must arrive, never forwards from when you would like to leave.