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.
61 articles • Page 3 of 7
Why Your Team Games Every Metric You Set
Goodhart's Law says when a measure becomes a target it stops being a good measure. Here is why small teams accidentally reward the number instead of the outcome, and how to build metrics that resist gaming.
The Premortem: Assume the Project Failed, Then Work Backward
Imagining that a project has already failed raises a team's ability to correctly identify the reasons for a future outcome by about 30 percent, according to research by Deborah Mitchell, Jay Russo, and Nancy Pennington published in the Journal of Behavioral Decision Making. That single...
What Owning the Stack Actually Means for Your Clients' Data
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.
AI Agents That Run at 3am vs. AI Agents That Demo Well
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.
Two-Way Doors: Make Reversible Decisions Fast and Irreversible Ones Slow
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...
The Bus Factor: What Happens If Your Key Person Disappears
In a study of 133 popular open-source projects, 46 percent had a bus factor of one, meaning a single person held enough of the knowledge that the project would stall if they walked away, and 65 percent had a bus factor of two or fewer (Avelino, Passos, Hora and Valente, 2016). The bus...
Entropy: Why Every System Drifts Toward Mess, and Maintenance Is the Answer
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...
What I Stopped Outsourcing (and What I'll Never Build In-House)
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.