I think 'not ruffling feathers' is sure to be one of the biggest challenges; we also have to figure out how to manage team size (if >1) and work load. In 'the real world' we have things like budgets to constrain them and I wonder how that translates to projects where, theoretically, anyone can get involved. It would be a step backwards if we ended up lots of mediocre design-by-committee.
That said, lots of the most impressive products in recent software engineering have been accomplished by remote, disparate groups of strangers. I think that's really cool and something we as designers should get over our egos and strive to be a part of :)
Comments
Thanks :)
I think 'not ruffling feathers' is sure to be one of the biggest challenges; we also have to figure out how to manage team size (if >1) and work load. In 'the real world' we have things like budgets to constrain them and I wonder how that translates to projects where, theoretically, anyone can get involved. It would be a step backwards if we ended up lots of mediocre design-by-committee.
That said, lots of the most impressive products in recent software engineering have been accomplished by remote, disparate groups of strangers. I think that's really cool and something we as designers should get over our egos and strive to be a part of :)