Systems
The system knew what happened. It did not know what was missing.
01
3 minute read The Job Ran. The Outcome Never Arrived.
A file arrived on schedule. Nothing errored. The job completed.
An enduring record
Field Notes
Observations from real operational work: what broke, what changed, and what proved useful enough to keep.
Notes, in the order they were kept
10 entriesMetrics
Sometimes the report is technically right and the shared definition is missing.
02
3 minute read When the Dashboard Is Right and Reality Is Wrong
Before rebuilding the dashboard, make sure everyone means the same thing by the number.
Systems
If the process only works because someone remembers the next step, memory is part of the system.
03
3 minute read Your Process Shouldn’t Need Someone to Remember It
Repeated questions are often a sign that the answer lives in a person instead of the process.
Decision Making
The real requirement often appears after someone reacts to the first version.
04
3 minute read Requirements Are Discovered, Not Collected
An incomplete first answer can reveal the question that should have been asked.
AI
The bottleneck was not writing the code. It was knowing what needed to exist.
05
4 minute read AI Didn’t Build It. It Let Me Build It.
AI shortened the distance between understanding the problem and testing a solution.
Documentation
It took days to discover. It took thirty seconds to explain.
06
3 minute read Good Documentation Is Compressed Experience
The final answer was simple. Finding it was not.
Metrics
The number wasn’t wrong. What it was measuring was.
07
4 minute read The Number Wasn’t Wrong
The definition took days to find and thirty seconds to explain.
Systems
The dashboard was the interface. The decision was the product.
08
3 minute read The Dashboard Wasn’t the Product
A useful view does more than display the work. It changes what people can decide.
Building
Planning answers what we expect. Shipping shows what is true.
09
3 minute read The First Version Is for Learning
The first version does not need to prove the idea. It needs to expose it.
Systems
Every workflow looked reasonable on its own. The contact still received twelve emails.
10
3 minute read A List of Workflows Is Not an Experience
The failure only appeared when the system was viewed from the contact’s side.