On a longer timeframe, PDCA (Plan-Do-Check-Act) / PDSA (Plan-Do-Study-Act) models[0] are common, and I run into them frequently in non-profit social/community work. The "Do" part of the cycle is frequently misunderstood, it's more of a test.
I've found PDSA to be challenging with developers, with a tendency to want to short-circuit the process and leap intuitively to the "solution" at the end of the cycle. Talented, experienced, and ignorant all end up looking like P-A-P-A (or just AAAA with a spectacular thud at the end when things finally hit the fan).
The author "recommended a process of “deductive destruction”: paying attention to your own assumptions and biases, then finding fundamental mental models to replace them." -- going to borrow a few ideas from the article and try a different approach for a few of our Mavericks...
I've found PDSA to be challenging with developers, with a tendency to want to short-circuit the process and leap intuitively to the "solution" at the end of the cycle. Talented, experienced, and ignorant all end up looking like P-A-P-A (or just AAAA with a spectacular thud at the end when things finally hit the fan).
The author "recommended a process of “deductive destruction”: paying attention to your own assumptions and biases, then finding fundamental mental models to replace them." -- going to borrow a few ideas from the article and try a different approach for a few of our Mavericks...
[0] https://asq.org/quality-resources/pdca-cycle