(Re)imagining the Future of Work by Tatiana.
From the post:
Here at CrowdFlower, our Product and Engineering teams are a few months into an ambitious project: building everything we’ve learned about crowdsourcing in the past five years as industry leaders into a new, powerful and intuitive platform.
Today, we’re excited to kick off a monthly blog series that gives you an insider pass to our development process.
Here, we’ll cover the platform puzzles CrowdFlower wrestles with everyday:
- How do we process 4 million human judgments per day with a relatively small engineering team?
- Which UX will move crowdsourcing from the hands of early adopters into the hands of every business that requires repetitive, online work?
- What does talent management mean in an online crowd of millions?
- Can we become an ecosystem for developers who want to build crowdsourcing apps and tools for profit?
- Most of all: what’s it like to rebuild a platform that carries enormous load… a sort of pit-crewing of the car while it’s hurtling around the track, or multi-organ transplant.
Our first post next week will dive into one of our recent projects: the total rewrite of our worker interface. It’s common lore that engaging in a large code-rewrite project is risky at best, and a company-killer at worst. We’ll tell you how we made it through with only a few minor scrapes and bruises, and many happier workers.
Questions:
How is a crowd different from the people who work for your enterprise?
If you wanted to capture the institutional knowledge of your staff, would the interface look like a crowd-source UI?
Should capturing institutional knowledge be broken into small tasks?
Important lessons for interfaces may emerge from this series!