Anthony pulls two ideas out of the video: How our need to assign and take the credit for ideas can mess things up; and how sometimes information should just fade from view as it gets older, rather than being always perfectly preserved.
I pulled out another: That releasing software in beta is an important statement about the underlying attitudes towards innovation and development, and sets the scene psychologically for change and progression. In the Web 2.0 community, the ‘release early, release often’ ethos is well known and frequently used. Start-ups release the most basic version of their software, gather user feedback, watch for emergent behaviour and then develop the next release accordingly. Users are primed by the word ‘beta’ to expect problems – so they are less upset when they occur – and also to expect change. The process doesn’t always go smoothly, but it is a cost-effective way of developing software and web services quickly.
Enterprise really needs to embrace the idea of beta, not just in software development but in their project planning too. The idea that everything has to be perfect at launch, that launch is an end instead of a beginning, and that addressing bugs and flaws after launch is somehow a sign of weakness is an anachronism. I can’t count the number of projects where all the effort has gone into a final deadline and the results of all our hard work withered on the vine because no one thought about what to do with the work we had produced.
This is especially true of social software and social media projects where the tools are evolving faster than even the professionals can keep up. Social media projects of whatever stripe should be be seen as an ongoing process of change as the tools, ideas and culture all slowly mature. It’s much more like cheese that ripens slowly than a souffle that flops if not consumed immediately.