Field notes
Posts on product observability, building with AI, and keeping up with products that change faster than anyone can follow
Latest
PRODUCT MANAGEMENT6 MIN READProduct Observability: The Missing Dashboard
You already instrument every layer of your stack — infra, errors, latency, usage — except the product itself. Product observability is the missing pane.
ENGINEERING5 MIN READWhy Claude Code Is Not the Solution
AI coding agents can answer questions about your codebase. They can't replace a shared spec — different artifact, different audience, different lifetime.
ENGINEERING5 MIN READYour AI Coding Agent Reads the Same Stale Docs You Do
Cursor, Claude Code, and Copilot read your docs before they write code. Stale docs feed stale context. The fix isn't more docs — it's a living spec.
PRODUCT MANAGEMENT5 MIN READHow Much Is Documentation Drift Actually Costing You?
The hourly bill from stale specs is bigger than most teams realise. Here's how to model the cost of documentation drift, with cited research behind it.
PRODUCT MANAGEMENT5 MIN READThe Silent Release: What Actually Shipped Last Tuesday?
Release notes describe what was planned. Code describes what was built. The gap is where stale support answers, surprised PMs, and customer-found bugs live.
ENGINEERING4 MIN READComprehension Debt: The Real Cost of AI-Assisted Coding
AI-assisted coding ships code faster than anyone can read it. Comprehension debt is the new technical debt — and it's widening with every release.
PRODUCT MANAGEMENT4 MIN READNobody on Your Team Can Explain the Whole Product
Product knowledge lives in people's heads — fragmented, incomplete, and one resignation away from gone. Here's why that's structural, not a people problem.
PRODUCT3 MIN READConfluence vs Specsight: Documentation vs Observability
Confluence is where you write things down. Specsight shows you what shipped and how it behaves, read from the code. They are not the same category — here is the difference.
PRODUCT MANAGEMENT5 MIN READContext, Action, Outcome: A Better Format for Product Specs
Most product specs are too vague or too technical. Context/Action/Outcome is a format precise enough to be unambiguous, readable enough for anyone on the team.
PRODUCT MANAGEMENT3 MIN READWhat Is a Living Product Specification?
A living specification is an always-accurate, automatically maintained record of how your product actually behaves. Here's what it contains and who it's for.
PRODUCT MANAGEMENT4 MIN READWhy Product Documentation Always Falls Out of Sync
Specs fall out of sync almost as soon as they're written. It isn't laziness — it's a mismatch between how specifications are made and how products change.