Notes / Fieldwork
Notes from
the work.
What I am learning about technical leadership, useful AI, delivery, and the evidence behind difficult decisions.
Working notes
These notes come from decisions, systems, and recurring problems I encounter in the work.
Field dates identify when an observation was recorded. Each article discloses its actual publication date.
Operating evidence / July 2026
Analytics belong in the release plan—not the cleanup list
For a conversion-focused release, loading the page is only the start. The team also needs to see whether the intended path works, where it fails, and what to change next.
Read ↗02Technology leadership / June 2026
You cannot outsource outcome ownership
Every vendor can satisfy its contract while the overall initiative still fails. Someone must own the space between the scopes.
Read ↗03Practical AI / May 2026
Diagnose the work before buying AI
The responsible starting point is not a model or a tool. It is the repeated task, its cost, its exceptions, and the consequence of getting it wrong.
Read ↗04AI operations / April 2026
An AI policy is not an AI operating model
A policy can establish boundaries. It rarely explains how a useful idea becomes an approved, monitored capability with a real owner.
Read ↗05Fractional CTO / March 2026
Technology decisions need an owner—not another opinion
Advice can clarify a choice. Ownership connects the choice to consequences, execution, and the evidence that tells leadership whether it was right.
Read ↗