MDN Contributor Lifecycle model

Hi folks,

I've been doing some thinking about the lifecycle of MDN contributors,
both in the abstract, and specifically as applying to localization
contributors.

I based the abstract model on one for volunteers from academic
literature. It addresses the basics of attracting and retaining
contributors, and can help us refine our messaging to achieve that.

Here is my crude diagram of the model:
https://docs.google.com/drawings/d/1j_-q_dpGdMGt6v6zGIUgLaV8B0ln1Lwrvi8V7Y_BvAY/edit

If that doesn't make sense, here is a more textual description:
https://docs.google.com/document/d/18wtgzcBwBFzqcqL03kJ9O6oLUCHSAICtqtmqtIYb-Cs/edit

Ideally, we want to draw contributors into a virtuous cycle between
doing some activity, and then deciding to do another one, indefinitely.
(At the moment, the majority of contributors do one or a small number of
activities, and then exit the model, becoming inactive.)

What this model doesn't represent is the potential for increasing skill
and responsibility in activities (which is what I tend to think of with
the term "lifecycle"). For that, we need to get into specifics, which is
what I've done on the "Activities" tab of this spreadsheet:
https://docs.google.com/spreadsheets/d/1lDf4-wW-lI5QfBoyE-FH_7JBrjVEajYFeel4yDCOv6c/edit?usp=sharing

For each activity type, there is:

* Awareness, how a contributor knows than an activity is possible
* Trigger, how they learn about a specific contribution opportunity
(e.g., a page that needs to be translated)
* Knowledge and Skills, what they need to know or be able to do to
complete the activity
* Access, the account or permission they need in order to do it

Analyzing these factors can help us refine our communications and
processes to ensure that contributors get the information, skills, and
access they need to continue contributing in ways that satisfy their
motivations.

I welcome any feedback, both about the abstract model, and about the
specifics of localization activities (especially, did I miss anything?).

If you are not able to access Google docs, and would like to see these
documents, please let me know and I'll send you a PDF.

--

Janet Swisher <mailto:[email protected]>
Mozilla Developer Network <https://developer.mozilla.org>
Community Strategist

Hi Janet,

This is a really useful model, and I couldn’t find that much wrong with it. I had a couple of queries:

1. "Lack of time/priority” - would lack of interest be useful to mention here as well? Or would this come under priority?
2. “Not aware of opps” - "Not aware of further opps” ?

Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
[email protected] || @chrisdavidmills
> _______________________________________________
> mdn mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/mdn

It could be mentioned. I think lack of time, interest, and priority are
all aspects of the same thing -- it's not interesting or important
enough for you to make it a priority/make time to do.
Sorry, "opps" is short for "opportunities to contribute", that is,
specific things you could do.

It’s really a cost/benefit analysis situation. Do the benefits of participating adequately cover the costs?
Eric Shepherd
Senior Technical Writer
Mozilla Developer Network <https://developer.mozilla.org/>
Blog: https://www.bitstampede.com/
Twitter: https://twitter.com/sheppy

I've fleshed out this model with info for more types of contribution,
specifically English content, Kumascript, and Promotion.

https://docs.google.com/spreadsheets/d/1lDf4-wW-lI5QfBoyE-FH_7JBrjVEajYFeel4yDCOv6c/edit?usp=sharing

On the Activities tab, I'm looking for feedback on whether the list of
activities is complete, and if I've missed anything about the Awareness,
Trigger, Knowledge, and Access for the activities. The activities for
promotion are based on the brainstorming session
<https://docs.google.com/spreadsheets/d/1VAjcIPDwOPgH-0gWBLABkS_gFKoxOBDKQe0U-_fT2_U/edit?pli=1#gid=0>
that members of the staff team did recently while in Toronto.

The Phases tab relates to the lifecycle diagram, in terms of how we can
address each of the phases. On this tab, I made a separate column for
each contribution type, and also separated the sub-categories of
Promotion, since these may have very different needs, motivations, and
skills. Again, looking for feedback on anything that is wrong or missing.

The value that I see in doing this analysis is that it shows us areas
where we can be doing more/better to attract or retain contributors. We
don't have to address every item that's captured here, but at least we
have an inventory we can refer to.