--tiki-index: Before process undo Collaborative Translation Patterns Repository | Break Up Crowd Into Teams

Break Up Crowd Into Teams


This practice is mostly applicable in medium to large Collaborative translation communities.

Problem description

Very large communities present some disadvantages compared to smaller more tightly knit teams. They are more impersonal, provide less opportunities for members to interact and coordinate with each other at a deeper level. They also provide less opportunities for people to emerge as "local leaders".


If this is a problem for your community, consider breaking the community into smaller, more tightly knit teams. For example, you may split your community according to geographical or language lines.

Make sure there is at least one Community Manager per team, and provide ample opportunities for people to grow into local leaders (see: Find the Leader ).

Make sure you provide opportunities for the different teams to interact with each other as well, for example, to share success stories, best practices which are useful across teams, etc.

Links to related patterns

  • This practice is an alternative to Keep the Crowd Small
  • See also practices referenced in the above section.

Real-life examples

  • Kiva.org has found there were a lot of benefits to splitting their community of translators according to geographic lines, because translators need to work closely with people in the field who are producing loan applications.
  • Wikipedia is split according to language. Each language has its own wikipedia community, which works somewhat independantly of other language communities.