Download - Crowd conf 2011
Building Killer Crowds:How to Build, Manage and Sustain a Workforce to Maximize Crowd ROI
James [email protected] 2, 2011
What We’ll Talk About
Building Killer Crowds
Building Killer Crowds
How to Get an ROI
1. Create Clear Processes2. Create Forums of
Discussion
Building Killer Crowds
Create Clear Processes
1. Quality Control2. Avoiding Ambiguity
Making Clear Processes: Quality Control
Figure this out first• Reduce the Number of “Retries”
• Produce Scalable Quality
Making Clear Processes: Quality ControlWell-Understood
Methods• Compare Answers• Control Access• Peer Review
Making Clear Processes: Quality ControlStrictly Control
Access
Making Clear Processes: Quality Control
Peer Review
Making Clear Processes: Quality Control
What Are The Risks?Being Too Rigid
• May be process• May be expectations
Making Clear Processes: Quality ControlCase Study: Yolanda,
Yolanda
Making Clear Processes: Avoid Ambiguity
Declare War Against Ambiguity
Making Clear Processes: Avoid Ambiguity
Case Study: The Green Tent
Making Clear Processes: Avoid Ambiguity
The Green Tent
Making Clear Processes: Avoid Ambiguity
What would you choose?• Good• Fair• Poor
Building Killer Crowds
How to Get an ROI1. Create Clear Processes2. Create Forums of
Discussion
Create Forums for Discussion
So, what do we want to accomplish with our “forums” of discussion?
1. Open Discussions2. Scaled Knowledge Base3. Self-Managed Crowds
(Promised Land of Profitability)
Create Forums for Discussion
More than forums
• Scaled Conversations• Easy to Use• Champions
…but those too
Creating Forums of Discussion
Position the Crowd to Manage Itself
Building Killer Crowds
Numbers for Context1. 3 new crowd members per
day2. Attrition of 1.5/day3. Reduce attrition to 0.75/day4. 30%+ drop in acquisition
cost
Building Killer Crowds
Numbers for Context1. Crowd Size: 100,0002. Inquiries Per Day: 100 (.1%)3. Cost Per Day: $2504. Cost After Crowd Answers
90% of Inquiries: $25 (per day)
5. Savings Per Year: $82K+
CrowdConf 2011: Building Killer Crowds
James DiPaduaCompany: Servio
(www.serv.io)Email: [email protected]: @i_crowdsource Blog: jamesdipadua.comSlideShare: