
Track overview
About this track
Decision practice for managers who own a deadline on work that has dependencies. A project's finish is set by its critical path — the longest chain of dependent tasks with zero slack — not by its biggest or scariest job, which often has slack to spare. Find the critical path, spend your effort and attention there, and re-find it after every slip, because the moment a task slips past its slack the path moves.
How each module works
Every module in this course runs the same three steps, from the first lesson to the debrief. The loop is what makes Decyde a place to practise, not just to read.
Step 1
Read
The lessons. Read the situation, the evidence and the shape of the trade-off before you commit.
Step 2
Size
The simulation. Put numbers on both sides of the trade-off, then make the call against the engine.
Step 3
Defend
The debrief and report. See what your call bought and why, so you can defend it or change it.
The same loop in every module, and a new decision each time. Judgment compounds.
Modules · In order
4 modules in this track
Each module is one decision: short readings, the decision itself, then a debrief and a replay in a shifted world.
01/04
The Critical Path: What Actually Determines When You Finish
Cedarline has committed a seasonal catalog to its biggest retail partners, and the launch date is on the line. Seven tasks stand between it and the shelves, some waiting on others, and everyone is watching the two biggest jobs: eight days of paper and nine of copy. You have one rush crew that cuts any single task by two days. Trace how the tasks depend on each other, place the crew, and see whether the launch moves.
14 lessons · 2 mini-sims · ~62 min
Begin module02/04
Where to Crash: Buying Time on the Critical Path
Last module you learned to find the chain that sets the finish. Now marketing pulls Cedarline's catalog launch from day 20 to day 17, and moving that chain costs money. You can crash tasks — pay for overtime, extra crews, express suppliers — but each has its own price per day and a floor. The instinct is to crash the cheapest thing on the board, the paper order at $1/day, and it buys zero days, because paper isn't on the critical path. The days live on a quiet chain of ordinary tasks, and you build the plan a day at a time: crash the cheapest critical task, watch the copy chain rise to tie the design chain, then cut across both once they go co-critical — while the marginal cost climbs 2, 2, 4. The proven minimum to day 17 is $8 (layout ×3 + copy ×1, paper untouched). Then the twist: the copywriters run long, both chains are critical from the start, and the same three days now cost $12. The day worth buying is rarely the cheapest one.
15 lessons · 2 mini-sims · ~68 min
Begin module03/04
Buffer the Schedule: Where Safety Time Belongs
The last two modules found Cedarline's critical path and paid to shorten it — both pretending durations were known. This one drops the pretense. The catalog runs again with uncertain task times, and you must commit to a launch date and place a fixed pool of schedule buffer to protect it. Two traps fire at once. The most-likely estimate is biased low: work is right-skewed, so the copy task's most-likely of 8 days has an expected time of 11 and a tail to 32 — plan to 8 and you're late more than half the time. And the longest chain isn't the riskiest: the production chain is critical by average (mean 12) but predictable (spread 1), while the shorter copy chain (mean 11) is wild (spread 5), and it is the one that blows the deadline. Classic PERT reads only the critical path and reports 98% on-time; because both chains must make the merge, the truth is 71% — a 27-point lie of omission. Then you distribute six buffer-days and see the payoff: pour them onto the critical production chain and the gauge barely twitches (71% to 73%); pool them on the wild copy chain and it climbs to 94%. The lesson is to pool the buffer where the variance lives, not where the length is — plus the aggregation insight (one buffer of the root-sum-of-squares beats padding every task) and a replay where a new printer flips the variance and the buffer must move. The chain worth protecting isn't the longest one — it's the most uncertain.
15 lessons · 2 mini-sims · ~70 min
Begin module04/04
The Resource Conflict: When the Critical Path Runs Through a Person
The first three modules found Cedarline's critical path, paid to shorten it and protected it under uncertainty, and all three assumed that whenever a task was ready, somebody was free to do it. This capstone pulls that floor out. Cedarline has one art director, Maya, needed for both the layouts (6 days) and the copy (9 days), two tasks the plan runs side by side from day 4. Whose turn is it first, where does a crash-day still help, and what would it take to win the lost days back?
16 lessons · 2 mini-sims · ~72 min
Begin moduleAuthored on Decyde Practice loop curated for decision discipline
Vocabulary
What you'll engage
The decision skills you'll practice are paired with the underlying patterns you'll learn to recognize. Both vocabularies compound across the Operations Decisions domain.
Decision skills you'll practice
Capacity triageSupplier trade-offsQuality-vs-cost balanceBottleneck readingThroughput-vs-quality callsInventory judgment
Patterns you'll see
Practice evidence recorded on Decyde
Every decision practiced builds your Decision Profile
Replays supported
Practice the same decision differently · iteration builds judgment
English
Additional languages on v1.3+ roadmap
What's next · One recommendation
The other Operations Decisions courses each practise a different kind of decision.
Begin practice →FAQ
Questions about this track
Common questions about Project & Schedule Management and how this track works.
Related · Other tracks





