This is a nice idea and it’s interesting to see it invented and applied in another technical field (I consider cooking for large numbers to be an engineering ta

This is a nice idea and it’s interesting to see it invented and applied in another technical field (I consider cooking for large numbers to be an engineering task!). I’ve tried to apply something similar to feature development too: the idea of thin vertical slices, integrated end-to-end (a la agile). The common thread with this and the cooking and blog examples from the article is that they’re low risk. That is, you can work on a build pipeline, feature, or chopping vegetables for as long as you like: getting things wrong or not “just so” is fixed with rework. As a counter example, I don’t think you could as easily apply it to something like incident response. Here you’re trying to do the most high impact and high pressure thing first: stem the bleeding/errors/outage. Perhaps this suggests categories of task where mise en place is appropriate and others where it’s not. Though it’s not immediately clear to me whether even ostensibly unsuitable tasks may have suitable sub tasks within them.