Field notes
Technical notes from the work.
Not a blog. Field notes on the patterns we keep meeting in production: duplicated entities, brittle handovers, dashboards built before the model is stable, and systems that only work while the original builders are still in the room.
01
Start here
Three notes worth reading before the next system decision.
Each one is written as an operating memo: what fails, how to recognise it, what evidence we have, and what to ask before committing budget or organisational attention.
The Handover Test
A practical way to tell whether a vendor is building a system your team can own, or a dependency dressed as delivery.
Read note →Why Your Metrics Disagree
The deeper cause behind contradictory dashboards: unstable entities, temporal rules, and spreadsheet exceptions outside the governed model.
Read note →The First 90 Days
A concrete walkthrough of the first three months: model the operation, prove a narrow slice, widen carefully, and reduce the roadmap.
Read note →02
Why this exists
The useful problems are rarely the visible ones.
A dashboard disagreement is often an entity problem. A vendor dependency is often an architecture problem. A slow first phase is often a modelling problem disguised as stakeholder alignment. Field Notes is where we write those patterns down plainly.
launch notes, each tied to real delivery patterns
public case studies used as evidence, not decoration
buyer questions and operational checks you can reuse
03
Next
Forge the model. Build the system. Own it.
Ninety minutes with the people who own the problem, and a written point of view you keep either way.
Book a 15-min architecture call