-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is at issue in onboarding? #1
Comments
What machinery, processes, and resources are needed to effectively respond to and facilitate a visitors experience and engagement with the project from first visit and click forward? |
Example? On Sat, Nov 7, 2015, 9:42 PM Doug Breitbart notifications@github.com
|
Do you mean: |
I think that there might have been an issue with the name (emphasis on might): some had mentioned the name itself sounded like jargon.
|
This seems like a perfect example characterizing the current 'user experience': example from @antiface posted to Peeragogy/Patterns Nov 8 2015
|
Compare Wikipedia. Their slogan: the free encyclopedia that anyone can edit. The Wikimedia Foundation mission statement: The mission of the Wikimedia Foundation is to empower and engage people around the world to collect and develop educational content under a free license or in the public domain, and to disseminate it effectively and globally. The short version from wikimedia.org: Wikimedia is a global movement whose mission is to bring free educational content to the world. (Followed by lots of pictures.) Whereas if you go to Peeragogy.org, you see "Welcome to the Peeragogy Handbook." But nothing that says "Our goal is to
To my mind, that's pretty clear! The bold part, together with a link "Join us" might draw people in. (If that's what we want.) As for the comment from @antiface's colleagues, that seems quite a typical response. Consider this comment from Reddit:
If the medium is the message, I think our table of contents is sending people a message: this is a big (possibly) important book that you (probably) don't have time to read. That said...! I think that we're doing something that is important and complementary to the Wikimedia project. They are focusing on "content" (the what) where as we are focusing on "form" or "in-formation" (the how). |
I that we need to make it clear what peeragogy is. Peer to peer learning. And then explain it is not that different from what they already do (give examples). Then explain that, while we do this a lot often informally, we sometimes have challenges when we try to do this on a larger "more organized" scale because cultural tendencies toward hierarchy tend to set in. While there are advantages to hierarchy as the number of people increases, there are also distinct drawbacks. We often take this drawbacks as "just the way it is" but we don't need to. Peeragogy attempt to help people navigate in such a way that they can move forward with a peeragogy mindset to minimize these drawbacks and help people deal constructively with the challenges that they may face when using peeragogy to accomplish things. Also, on boarder, I think, used to be called newcomer which was a little more intuitive IMO... |
At least for me, part of the goal is to increase pull and engagement and
|
I think @jblaing had an awesome point: One is the "prove yourself worthy" route. Think "Navy Seals."The other is the "Welcome everyone!" route. Think "Baseball Game." They are not mutually exclusive, both have advantages and disadvantages, but, at least from my newbie perspective, you might want to clarify what sort of stance you have on this. Now there seems to be an initial "Welcome Everyone" vibe (though there is a learning curve), followed by a "Prove You're Still Interested!" vibe. I think we should clarify which one we are. If we want to be super welcoming, I think multiple people should volunteer to "own" this aspect of the peeragogy project. They should commit to "nurture, encourage and support sel-motivation, intention and desire?" as @DougBreitbart said each new person who gets in touch with us. Also, while I do like the idea of explicitly defining peeragogy that @snowinla suggested, but I'd also say there is a "cost" to definition. If we say what it is, then other people can say what it isn't (h/t Ken Kesey). That's OK, just something to think about, e.g., what is the definition of "art"? Has art been hurt by not having a definition? Overall, I support defining to a degree (leaving it open for re-definition) and couching it w/in a wikimedia style mission statement as @holtzermann17 suggested. Or, maybe we explicitly need to only define the "peeragogy project" and leave peergaogy itself open to interpretation? |
Also, reaching out to other projects and orgs could be good, in a On Mon, Nov 9, 2015, 1:34 PM Charlie Danoff notifications@github.com
|
@daytripper @DougBreitbart Would you folks be willing take a stab at rewriting these notes into a pattern using our typical
and check the result into this repository, e.g. in the README or elsewhere? The repo currently looks a bit blank for anyone just passing by. Once that's done that it would be good to
|
Revisit? On Sat, Jan 9, 2016, 09:49 Joe Corneli notifications@github.com wrote:
|
Absolutely.
|
For some reason, many groups struggle to get their onboarding going, I don't have a ready-made, great solution yet either, but let's simply build one. With online, project, collaboration, maybe peer context too, what function should an onboarding process fulfill? If you were the newcomer wanting to be onboarded, or a veteran wanting newcomers being onboarded? Let's assume that the main point is to get new people up to speed, so they get be enabled quickly to either contribute to upstream or to learn how to do things on their own, to know their way around, to know whom to contact in case of problems/questions, to learn about the current status of everything (what's new/hot, what's old/broken, where's work needed, what's available/offered, etc.). A very rough sketch could be that there's a big "join"/"engage" button and/or invite links that can be spread everywhere, which starts with a very short introduction that can optionally expanded into every little detail and materials, and optionally allow the newcomer to provide contact information if he/she would generally want the Peeragogy project to learn about his/her interest (meaning, inviting to do all onboarding steps without providing any personal data or answering any questions). From this first page, the newcomer might choose one of several onboarding routes, which are prepared for different kinds of people (branching like this might be an option several times in separate, self-reliant and combinable "modules"). Work together and contribute to the Peeragogy project via content, software developer persona caring about repositories and technical tasks, teachers using the material and working on the methodology, students learning how to become peer teachers as well, maybe also highly specialized other onboarding routes too. The bulk would be a short but well-summarized tour over the most important/relevant parts, asking the newcomer questions to get feedback, setting up accounts, indicating current activities/topics and who's contributing. The whole onboarding environment should always allow the following actions:
So basically this should help with unattended onboarding, while human help could optionally be manned in real-time, or otherwise be followed up asynchronously. Obtained data should quickly be reviewed, all onboarding modules always up to date (manual curation supported by automated compilations/summaries/feeds). There should be a regular task to go through onboarding routes in order to check if they still work, are up-to-date and still make sense. Not to forget that this service may also be provided to people who don't want to join or contribute to the project at all, but instead want help + overview of how to make use of the materials and methodology on their own. Sounds more amazing than the actual first implementation would end up looking like and is a lot of work, but as a suggestion for a general direction. Can also be used for other contexts and probably better to always to a costly personal, human-attended onboarding/tour or none at all. Might eventually integrate to a work environment contributors or individuals may use for dealing with peeragogical things. |
Maybe get an onboarding buddy assigned from a pool of people who do onboarding, for handholding and checking back with the newcomer (also reminder), ideally doing a few things together or share personal impressions/experiences, etc. |
Curious what goes here?
The text was updated successfully, but these errors were encountered: