Anti-Automation: The Tasks You Should Never Automate
Automation is worth it for repetitive, reversible work. But the tasks you should never automate hide accountability and remove the human who catches the exception.
70 articles • Page 4 of 8
Automation is worth it for repetitive, reversible work. But the tasks you should never automate hide accountability and remove the human who catches the exception.
Goodhart's Law says when a measure becomes a target it stops being a good measure. Wells Fargo staff opened about 1.5 million unauthorized deposit accounts chasing one metric. Here is how to build metrics that resist gaming.
A premortem assumes a project has already failed, then asks why. Imagining the failure as settled raises a team's ability to correctly identify reasons for a future outcome by about 30 percent (Mitchell, Russo, and Pennington, Journal of Behavioral Decision Making).
Over 92% of the Western world's data sits on U.S.-owned servers, and the CLOUD Act lets authorities demand access regardless of location. Owning the stack is not ideological. It is jurisdictional, operational, and the difference between answering 'where is the data' with a street address or a vendor FAQ.
Eighty-eight percent of AI agent projects fail before reaching production. The gap between AI agents in production and agents that demo well is not a quality problem. It is a design problem rooted in compound failure math that most teams never calculate.
Only 20 percent of executives say their organizations excel at decision making, and most report that much of the time they spend on it is used ineffectively. A large share of that waste comes from treating reversible decisions as if they were permanent. Amazon has a name for the...
In a study of 133 popular open-source projects, 34 percent had a bus factor of one and 65 percent had a bus factor of two or fewer. How to count your business's bus factor function by function, and raise it with runbooks and cross-training instead of new hires.
Developers spend about 42 percent of their working week, roughly 17 hours, on maintenance and dealing with bad code rather than building new features, according to Stripe's 2018 Developer Coefficient report. That number is entropy at work. Software entropy is the tendency of any...
Average DevOps engineer tenure is 2.3 years. When they leave, months of institutional knowledge walk out the door. The build-vs-buy framework that accounts for departure.