Coach K Ran 12 Final Fours. Your DC Can't Run Peak.

Mike Krzyzewski coached 12 Final Four teams. Not 12 talented rosters. Twelve teams that performed when the margin for error collapsed to zero. At the Manhattan Associates EDGE conference, he broke down how. The lesson wasn't about basketball. It was about what happens to your DC when inbound volume spikes 40% in the first week of November and your two best shift leads are pulling doubles.

Pressure Exposes the System You Actually Have

Every brand thinks it has a fulfillment system. Most have a fulfillment habit. A habit is what your team does when nothing is wrong. A system is what executes when three conveyors go down, a carrier misses a pickup, and your top-velocity SKUs are slotted in the wrong zone. Those are two different things. Krzyzewski's core point: elite performance isn't improvised under pressure. It's rehearsed before pressure arrives. Your Q4 playbook should be written in June. Most operators write it in October. That gap is where NetPPM leaks.

The Bench Depth Problem Nobody Budgets For

Peak season DC failures rarely trace back to robots or software. They trace back to the associate on night shift who doesn't know the exception protocol. Or the supervisor promoted in September who hasn't run a high-velocity pick wave without a senior lead watching. Bench depth isn't a headcount metric. It's a capability metric. Count how many people on your floor can make a correct slotting decision without escalating. Count how many shift leads can run a cycle count cohort and catch a discrepancy before it becomes a shrinkage problem. If that number is two or fewer, you have a single point of failure wearing a hard hat.

Decision Rights Are Your Offensive Scheme

Krzyzewski talked about decision rights. Who calls the play when the timeout runs out. In your DC, the equivalent question is this: who has authority to reroute a pick wave when a zone goes down mid-shift? If the answer requires a manager approval chain, you're already two hours behind. Top-decile operators pre-assign decision rights by scenario. Zone failure goes to lead associate, no escalation required. Carrier no-show triggers a pre-negotiated backup carrier contact, not a phone tree. ASIN velocity spike on a fragile SKU triggers a re-slot request without waiting for the weekly ops meeting. Write the scenarios down. Assign the names. Laminate it and post it at every pack station.

Repetition Is the Only Honest Prep

Duke ran the same out-of-bounds plays for 30 years. Not because Krzyzewski lacked creativity. Because repetition builds the kind of muscle memory that survives a hostile crowd and a one-point deficit. Your team needs the same thing. Run your peak-season scenarios in July. Simulate a conveyance failure during a planned drill, not during Black Friday. Walk your night shift through the carrier exception protocol before the first time they need it. The operators who consistently post top-quartile on-time ship rates aren't running smarter software than you. They've run the drill more times. That's the whole secret.

Three Questions to Pressure-Test Your Leadership System

First: Name the last time your team rehearsed a specific failure scenario. Not a training module. An actual live drill with a clock running. Second: For your top five highest-velocity ASINs, can every shift lead recite the exception protocol from memory, without looking it up? Third: If your single most capable DC lead called out sick on November 29th, which specific decisions would stall and for how long? Run those three questions through your ops review this week. The answers tell you exactly where your system ends and your habit begins. Fix the gap before Q4 does it for you.