Published thinking.
Products, Not Projects
A serial builder who runs a portfolio as disconnected projects has built a system that cannot improve. Stabilize before you scale.
Read the note →The Handover Gap
Why building data expires after handover — and what the organizations that avoid it do differently.
Read the note →You Became the Wire
Run more than two or three LLM chats at once and you become the integration layer — the wire shuttling context between sessions that can't see each other. The fix isn't a bigger tool.
Read the note →No Model in the Room
Most coordination runs on a shared model. This one didn't — and what got solved anyway showed what the model was actually for.
Read the note →The Red Pencil
Blueprints, redlines, and a stamp that never carried my name. The platforms changed for twenty years; the cycles survived every one. What were we buying when we bought the tool?
Read the note →We Said Modernize. Nothing Moved.
A friend with thirty years in the field asked what governance was, and the clean answer wouldn't come. The honest one — whether the decision survives the room it was made in, and why the hero on the hard job is the symptom, not the save.
Read the note →Governance Is Not a Document
A coordination plan can name every risk, assign every owner, and still change nothing. The missing piece isn't a better plan — it's who's allowed to decide.
Read the note →The Coordination Window
The period before installation when changes are still cheap to make. Why no one is watching it, and what protected looks like.
Read the note →New notes when they publish.
Notes on VDC operating model design, governance, and the structural layer most construction firms skip.