Skip to main content

Crowdsourcing

Paul Boutin recently wrote an article in BusinessWeek about crowdsourcing, a "business trend in which companies get unpaid or low-paid amateurs to design products, create content, even tackle corporate R&D problems in their spare time." Another word for crowdsourcing is co-creation.

Boutin gives an example:

The first, Threadless, is a Chicago-based T-shirt maker whose
design process consists entirely of an online contest. Each week the company
receives hundreds of submissions from amateur and professional artists.
Threadless posts these to its Web site, where anyone who signs up may give each
shirt a score. The four to six highest-rated designs each week are put into
production, but only after enough customers have pre-ordered the design to
ensure it won't be a money-loser.
In this example, contest winners receive prize money. Boutin points out, however, that customers are often not compensated for their co-creation efforts.

Comments

Post a Comment

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos
32 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware
8 comments
Read more