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 most common outcome of competent technical work is a meeting that agrees the work was thorough and an operating process that continues exactly as before. The cause is not effort, and more effort will not fix it.
Read the article
Your Model Is Not the Answer
Model quality is an intermediate artifact, and presenting it as the deliverable is the central structural error in applied data science. The remedy is not clearer communication. It is a different definition of finished.
Read
How to Refuse a Brief Without Becoming the Obstacle
The first request is almost never the decision. Absorbing it anyway is the most expensive habit in technical work, and the standard objection to pushing back has a specific, practical answer.
Read
The Good Meeting Is the Most Expensive Failure
Agreement in principle feels like success, which is exactly why it is the hardest of the three failures to notice. A decision that never reaches an operating process was not a decision.
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.