Again. a thoughtful post. My pay grade is well
below yours BUT, when I was in school, I came up
with a way to teach history in an encapsulated
form ala James Burke. In 1970. I was an undergrad
and asked by the History Dept to lecture to the
500 level,which were ALL teachers ( no surprise,
it WAS a business and teaching college) and one
of my favorite 'capsules' was 'The Effiency Movement.'
Key to that was a man named Frederick
Winslow Taylor. In his writings you will find
a parallel stance and an 8 decade lag. Also see
the Barths.

Back in the days when men were men and software was written on punch cards, we estimated 6-10 lines of DELIVERED code per man-day. The key is DELIVERED, since you may need to code, recode, test, archive, and integrate along the way, with another 50-200 lines of code to make that happen.

The miracle 4 decades later is that I still deliver 6-10 lines per day, but with tools that work at a much higher level of abstraction. Six lines of today's Mathematica do the work of 200-300 lines of 20th Century FORTRAN, and it only takes another 6 lines to do the housekeeping.

Attention to "Process" works great for mass production; I've yet to see a checklist that tells me how to be creative or even innovative. Like some foolish woggie voting for an Islamic State, I fear making that final innovation: control everyone's PROCESSES, including my own.

I always thought it was "The Fifty-Nine Second Employee," billed as a way to stay one second ahead of your boss...

By God, you're right. I'd forgotten even though I was the editor.

Corrected. With thanks.