Phrased positively,[1] the steps are:
- Awareness. Registering that there is, in fact, a problem. "The first step is admitting you've got a problem". Here, "The ports of LA/Long Beach are at a standstill."
- Diagnosis. Recognizing a problem, and correctly identifing the type or symptoms. Failures often occur through superstition / mythology, poor understanding, or other modeling / framing errors, frequently of the "what you know that just ain't so" variety. Here, trucks that can't unload empties cannot load new, loaded containers for delivery.
- Etiology. Correctly identify the root cause. Here: "If you can’t get the empty off the chassis, you don’t have a chassis to go pick up the next container."
- Objective. Determining a preferable (or attainable, or stable) resolved state. Here, "overwhelm the bottleneck and create yard space at the ports so we can operate".
- Redress (or method). Having figured out where you are and where you want to be, how to get there. Here, "allow truck yards to store empty containers up to six high instead of the current limit of 2". (Among other measures.)
- Communication. Convincing others. Peterson's Twitter thread and CTA, of which the HN discussion is a part.
- Execution. Having secured agreement and/or support, acting and executing effectively. The Getting Shit Done problem. Apparently in process, as the box-stack-height limit has been lifted: https://nitter.kavin.rocks/RobertGarcia/status/1451679404757...
- Assessment. Did you actually solve / address the situation effectively? Learning from it and passing this on for future knowledge? Not so critical in terms of the present problem, but useful for future iterations. We're not there yet, but that's the final step in the loop.
My earlier list (phrased as the negative of the above) here: https://old.reddit.com/r/dredmorbius/comments/2fsr0g/hierarc...
________________________________
Notes:
1. I'd originally written the list as a "hierarchy of failure", itself a tool to properly identify stuck processes.