Article

Deliver, learn and improve

Three-panel comic: a chef serves an enormous burger, the customer cannot fit it into his mouth, and both enjoy smaller burgers after the chef adjusts the serving.
The first serving needed a little feedback.

My machine is a very small market.

I still enjoy the moment something finally works. After enough debugging, even an unremarkable screen can look beautiful.

To get there I already asked myself: Can someone else use it? Can I deploy it again? Will I know when it fails? Can I recover?

Delivery exposes assumptions that development can hide. Real users bring different habits, unexpected data and devices I apparently should have tested.

I want the first release to be useful and manageable, with enough visibility to understand what happens next. That includes errors, support questions and the features people quietly ignore.

I’m particularly interested when someone exports the data and finishes the job in a spreadsheet. There’s usually a conversation worth having there, once I’ve recovered from my initial disappointment.

And that's why before implementing anything I think as much as possible where can that lead.