Field NotesHafsteinn Runarsson · AI Konsulent04 Jun 2026 · 5 min

Why we ship in production, not in slides

A slide deck is a promise. A staging link is a stronger promise. Production is proof. Somewhere along the way, our industry decided that the deliverable of expensive thinking is a document about software rather than software — and clients learned to accept it.

We run the studio on a different rule: an engagement is not finished until something runs where real users can reach it. Not because documents are useless — we write plenty — but because production is the only environment that tells the truth. Staging flatters. Slides flatter harder.

Shipping to production changes how you scope. When the definition of done is live, you cut differently: the feature list gets shorter, the walking skeleton appears in week one, and the risky integration is built first, not last. Nobody wants to discover in the final week that the payment provider's sandbox behaves nothing like its live API.

It also changes the conversation with the client. Progress stops being a percentage in a status report and becomes a URL. Feedback arrives while it is cheap to act on, and the awkward questions — who owns the domain, where do the secrets live, who gets paged — are answered at the start instead of at the end.

There is a quieter benefit too. Teams that ship weekly stay honest about their own estimates. The gap between done and deployed is where projects go to die, and the simplest way to close it is to never let it open.