QA/Community/Outline-2013-Q4

Rotation

• Edwin takes the first new contributors on-list, then notifies Karl.
• Karl takes the next five to ten, and with any luck we have a rotation (and a New Community QA Contributor Flow) by the time he's done with those five, so he can pass the flow on to someone else.

What to do

1. Don't drop the people coming in the door.
2. Gather data on what folks want, what skills they have. (by hand at first, by survey later.)
3. Establish flows for each general user type.
4. High touch at first, gather data until we have a critical mass.
5. Then see what funneling techniques apply: meetups, hangouts, technical documentation?

Basic Community Testing Contributor types

Student

• In school, looking for the skills that lead to the internship that leads to the job.

Transfer

• Has some college in another field
• sees that field shrinking
• decides to re-tool skills

Refresher

• Has been in tech before, maybe with old skills.
• Looking to come up-to-date.
• Maybe between jobs -- likely to have lots of time and high commitment level
• Caution: Skills may be variable.

Explorer

• Already employed in tech, maybe in QA
• looking to expand skill set.
• May not be socially motivated.