Decision Making
The real requirement often appears after someone reacts to the first version.
01
3 minute read Requirements Are Discovered, Not Collected
An incomplete first answer can reveal the question that should have been asked.
An enduring record
Field Notes
These aren’t tutorials or polished case studies.
They’re observations collected while building.
Every note started with a real problem.
Every lesson stayed because it was useful.
Notes, in the order they were kept
07 entriesAI
The bottleneck was not writing the code. It was knowing what needed to exist.
02
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.
03
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.
04
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.
05
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.
06
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.
07
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.