Writing
Articles
Longer pieces on the specific ways competent technical work fails to change anything. Every article applies one or more entries from the method and links back to them.
Forty-Seven Slides and the Rule Did Not Change
The usual outcome of competent technical work is a meeting that agrees it was thorough and a process that runs exactly as before. Effort will not fix it.
Read the article
The Solver Was Right and the Plant Overrode It
The failure mode of applied optimization is not an infeasible model or a slow solve. It is a correct model that a planner silently overrides.
Read
Your Model Is Not the Answer
Model quality is an intermediate artifact. Presenting it as the deliverable is the structural error in applied data science, and clearer writing is no remedy.
Read
How to Refuse a Brief Without Becoming the Obstacle
The first request is almost never the decision. Accepting it anyway is the most expensive habit in technical work, and the usual objection has an answer.
Read
The Good Meeting Is the Most Expensive Failure
Agreement in principle feels like success, which is why it is the hardest failure to notice. A decision that never reaches an operating process was not one.
Read
The Two Questions That Do More Than Any Framework
What would change the ranking, and what does Tuesday do now. Neither can be answered with a chart, which is precisely why they work.
Read
The method
The articles are commentary. The method is the reference.
Eighteen entries, one per chapter, free and complete, with worked examples from operations.