3. Perpetual Beta

If the previous chapter was the diagnosis, this is the prescription.

The term is perpetual beta. In software it describes a product kept in a permanent state of improvement: never declared finished, updated continuously, with users treated as co-developers whose feedback shapes what ships next. Tim O'Reilly, who popularised it in the Web 2.0 years, set it against the old packaged-software rhythm of long development cycles ending in a single big launch.¹ The alternative was release early, release often. It was "no accident," he liked to point out, that Gmail and Google Maps carried a "beta" label for years while millions of people relied on them daily. The label was a message: this is useful, and it is not done, and it never will be.