Nothing Has to Be Perfect
One of the concepts that modern education tries to instill is the idea of “publication upon perfection.” In a world where publication budgets are slim, products must be finished, refined, and definitive, thus education has adapted to reflect this reality. One of the great things about digital technology is that publication isn’t necessarily the financial burden in the digital sphere that it is in the analog sphere, thus making the barrier to future releases dramatically lower.
Incremental release cycles are a prevailing workflow notion in the world of software development because of this economic reality. Many other industries are beginning to mimic this kind of development as well. Release cycles allow developers to tell their users about the user experience before a product is fully developed and users get to test that version of the product to help guide the developer through feedback.
I like this idea. I think it is okay to begin a project with a goal and publication form in mind, yet allow for mistakes. I think it is executed most successfully when release cycles are deadline oriented, with clear definitions about the usability delivered to users, and a final release date and goal cycle in mind. It also provides an incredible psychological response, because mercy is more easily leveraged when a user knows that certain accommodations need to be made before the final release date. It is a far more forgiving way to work and I heartily recommend adding it to your workflow. Perfection will only kill you.
