
Track overview
About this track
Decision practice for operations managers choosing what to run next on a shared resource. Shortest-processing-time first (SPT) minimizes the average wait — provably, across all possible orders. Earliest-due-date first (EDD) minimizes the worst lateness when deadlines rule. Fair-order and loud-first optimize neither. And on one machine, reordering only moves the wait — the finish line never 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
What to Run Next: Why Shortest-First Beats "Fair" and "Urgent"
Five jobs wait on Cedarline's one print/label machine and everyone wants to go first. Fair says first-come; loud says the big account. Set the run order yourself — drag the jobs into a sequence and watch who waits — and discover the order nobody's instinct reaches for: shortest first makes everyone wait the least, on average. Then face the catches: deadlines need a different order (EDD), long jobs starve under pure SPT, and no clever sequence makes the batch finish any sooner.
12 lessons · 2 mini-sims · ~58 min
Begin module02/04
Two Machines in a Row: When Sequencing Finally Moves the Finish
Last module, the batch always finished at the same hour — the order was only a fairness call. Now there are two machines in a row at Cedarline: print, then finish. The same five jobs can land at hour 28 or hour 38 depending on the order — a 10-hour swing, nothing but sequence. Johnson's rule solves it: feed the finishing station fast, drain it last, reading each job by the machine it's short on, not its size. The press was never the lever; the finishing station's idle time was.
12 lessons · 2 mini-sims · ~58 min
Begin module03/04
Whose Deadline Wins: Sequencing When Some Jobs Matter More
This third turn adds what the first two modules left out: jobs that matter differently. Five client jobs wait on one machine, each with a processing time and a weight, how much its delay costs. Every order finishes the same work by the same time, but not at the same weighted wait, and the order that feels fairest, most urgent or most important is not obviously the cheapest. In what order do you run them, and can you defend where each job sits?
12 lessons · 2 mini-sims · ~58 min
Begin module04/04
The Changeover Cost: When Switching Is Expensive, Group Your Work
The capstone reopens the course's first truth. Module 1 proved that on a single machine the order can't change when you finish — and that was right, as long as nothing was lost between jobs. Add a wash between ink colours and the truth inverts: on one press, six jobs finish anywhere from 18 to 27 hours depending only on order. The winning order is a shock: it's not a priority order at all — it's a grouping. Batch each colour (group technology) and run the blocks White→Red→blacK (washes 1+1=2) → makespan 18, the floor of all 720 orders. Shortest-first (25) and as-arrived (26) scatter the colours and pay for it. The replay flips the cheap direction with new equipment, proving the rule, not the memorized order, is the keeper. Course complete: the right order is rarely the fair, urgent, or most-important one — and sometimes it isn't a priority order at all, but a grouping.
12 lessons · 2 mini-sims · ~58 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 Scheduling & Sequencing and how this track works.
Related · Other tracks





