Oct 20, 2026 · 4 min · 5 segments
A schedule needs to show how tasks depend on one another, not just when you hope they will happen. We look at task links, slack, and the critical path through a project. A construction sequence helps…
The move is straightforward.
You take the tasks from your work breakdown structure and you lay them out in chronological order from the start of the project to the end.
Some tasks come before others, some come after.
In the language of scheduling, a task can be a predecessor to the ones that depend on it, and a successor to the ones it depends on.
Now, those links between tasks aren't all the same, and there are a few relationships worth knowing by name.
The first is begin-begin.
That means two tasks start at the same moment on the timeline.
They kick off together.
the second is begin end that means one task begins exactly when another one ends okay so the finish of the first marks the start of the second like a baton being passed the third is end end that means two tasks finish at the same moment however they got there begin begin begin end and end Three simple ways tasks can be tied together in time.
Here's something that should be a relief.
As an architect, kind of, you are not required to learn the heavy scheduling software.
Whether it's Primavera or Microsoft Project or any of the others, nobody expects you to be an operator of those tools.
What you are expected to understand is the principles, the logic underneath them.
You'll often hear the timeline itself called a Gantt chart, though it goes by other names too.
And honestly, the name matters far less than the idea.
The move is straightforward.
You take the tasks from your work breakdown structure and you lay them out in chronological order from the start of the project to the end.
Some tasks come before others, some come after.
In the language of scheduling, a task can be a predecessor to the ones that depend on it, and a successor to the ones it depends on.
Now, those links between tasks aren't all the same, and there are a few relationships worth knowing by name.
The first is begin-begin.
That means two tasks start at the same moment on the timeline.
They kick off together.
the second is begin end that means one task begins exactly when another one ends okay so the finish of the first marks the start of the second like a baton being passed the third is end end that means two tasks finish at the same moment however they got there begin begin begin end and end Three simple ways tasks can be tied together in time.
Here's something that should be a relief.
As an architect, kind of, you are not required to learn the heavy scheduling software.
Whether it's Primavera or Microsoft Project or any of the others, nobody expects you to be an operator of those tools.
What you are expected to understand is the principles, the logic underneath them.
You'll often hear the timeline itself called a Gantt chart, though it goes by other names too.
And honestly, the name matters far less than the idea.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
