The Anti-Spec Movement Is Going Too Far
As a designer, I have nothing against the anti-spec movement. Created in response to speculative work (i.e., work commissioned with the possibility of payment but no guarantee) and crowd-sourcing (e.g., design contests which reward only one winner), the anti-spec community has been protecting designers' right to be paid for the work that they do.
However, the movement has been going too fara€‰-a€‰expanding to cover every kind of design contest and groups where design and art are created for fun, not just profit. Anti-spec is detrimental to community and social good projects, and it hurts more designers and artists than it saves by going too far.
Anti-spec is hurting pro bono design
At Brooklyn Beta 2011, Todd Park of the US Department of Health and Human Services spoke passionately about the need for designers to work for the public good, to spend their free time building and experimenting on current public issues. He called for designers to take the massive amount of health data released by the government and use it to build public solutions, and he specifically mentioned that, yes, the government could pay one individual or studio a massive amount of money to find one solution, but that the most amount of innovation and creativity comes from the community.
Recently, The Designer Fund and the White House presented the Health Design Challenge dedicated to redesigning the electronic medical record. On the TechCrunch coverage, The Designer Fund co-director says, a€oThere are so many meaningful problems in the world. Healthcare, clean energy, environmental issues, city design. We feel like we'd be able to make a much bigger dent in these problems if designers went at them.a€ť Of course, there were anti-spec responses such as this:
The Designer Fund and the White House could pay a consulting firm to create a solution for the electronic medical record, but like Todd Park mentioned, the greatest amount of innovation and creatively comes from a massive amount of designers working togethera€‰-a€‰more innovative, cost-effective, and interesting solutions will always come from a community project such as this rather than one paid consulting firm.
Anti-spec is hurting open source, design collaboration, and education
Being a designer jumping into development, I would have been completely lost if it wasn't for sites like Stack Overflow, where people can post problems they're having with development and get answers and help for free. The free advice and help from Stack Overflow made it easy to jump into development. So many people are looking to jump into design, but huge communities for design help like Stack Overflow are lackinga€‰-a€‰Stack Overflow for design isn't big enough and Dribbble exists more for sharing small details. Large communities don't exist due to the stigma against asking for design help for free.
For developers, open source development has lead to innovation on the Internet and online products. I was able to build my startup using a programming language called Python and a framework called Django, both of which are available online for free, even though they represent thousands of hours of work. The developers worked for free, in their spare time, to build something to help others. It's worth noting that it would be odd to have anything but free programming frameworks and pluginsa€‰-a€‰developers in the open source community embrace working for free in order to build free resources for the benefit of others.
What if designers were more open with their free time? What if we embraced opening up to others, embracing community? A huge issue in the open source community is the lack of design helpa€‰-a€‰poor UX and UI design on open source projects which hinders adoption and understanding by non-developers. Designers should work with developers to further promote and aid adoption of great open source projects, which, in turn, helps nearly everything we use on the Internet today.
Anti-spec is hurting community
Truncated by Planet PHP, read more at the original (another 2520 bytes)