What you have at the end of a Discovery
A map, three numbers and a proposal: the four things on the table at the end of a Discovery, and why we charge for them.
Insight
Short notes on getting software that fits an operation.
Four ways internal software dies
The dashboard that became a nicer morning report, the spec written in a conference room, the big-bang launch, the vendor who left. One cause.
The engineer on the other end of the receiving-dock call
Why the engineer who writes your software watches the real work first, over video, what that looks like week to week, and when it is the wrong idea.