Milestone 20 Onboarding comments and suggestions by AngelaRichmondFuller

From crowdresearch
Jump to: navigation, search

Additional ideas: Additional comments - 1. To help people catch up on missed meetings and to move things forward quickly, spend the last 3-5 minutes of each meeting summarising (and agreeing) the main points verbally and identifying "next steps" and actionable items along with who will take on what and items where other volunteers are needed. To spread the work-load, someone other than the DRI could volunteer to write those up to post in #announcements-discuss. @arichmondfuller

2. DRIs list who contributed to each milestone in #announcements at the end of each week helped to show who was doing what. The main problem @arichmondfuller found with this system previously is that you can't tell how much (or the quality of work, for that matter) that each person contributed. ​*Suggestions:*​ DRIs list contributors for each milestone in the order of percentage of contribution - first being the top contributor and the last place as having contributed the least. @arichmondfuller


Issue: Not knowing anyone or where to jump in

Solution: -1. Allocate a mentor to each newbie who can be for support in the first couple of weeks -2. Allocate a DRI each week to give "pastoral care and help". They can choose to host a meeting or slack channel time. Often this pastoral support falls on the shoulders of only a few. It is a lot of work (rewarding of course) but should be shared out to everyone to help out with. -3. Sign newbies up to a newbie trello card where they can work on a task together to slowly ease them into Slack and life in the project. Maybe do this for the 1st two weeks or so as an induction and then open the whole project up to them. This may help newbies from feeling overwhelmed by it all.


Issue: Slack is 24/7. Feeling pressure, whether it be internal or external, to show commitment to Daemo by working at unsociable hours. In some cases, this leads to sleep deprivation.

Solution: Identify which time zones people are in. Identify on the Trello Milestone cards the timezone of the DRI. Perhaps we could encourage newbies to sign up to cards who have at least one other person who is in a similar time-zone so that when they work and are on Slack that someone else will be around to collaborate with. Encourage everyone to be aware of the time-zones of others. In fact, it might be worth everyone noting what timezones normally work best for brainstorming sessions/meetings so that the DRI can plan the milestone work in an efficient way.


Issues: Being asked to contribute by writing ideas/comments on a wiki and submitting to meteor

Solution: Make available 3 minute training YouTube clip showing how to make a wiki and how to submit a document to meteor. Include troubleshooting ideas.



Issue: Coming across some sort of stumbling block and being not sure how to find out the info or who to ask for help

Solution: Make a Help-Requested channel on Slack - a space for people to easily request help



Issue: Seeing/reading some useful information and then not being able to locate it again in future.

Solution: Identify and implement data management system.



Issue: Missing important meetings.

Solution: Ensure all meetings are listed on Google Calendar at least 48 hours in advance. Put the links to the YouTube videos into the calendar notes so that people can easily find the links to the meetings they've missed in order to catch up. Post announcements of meetings in the Announcements channel.



Issue: Misinterpreting messages.

Solution: Identify (or create) and offer training on cultural and gender-specific communication styles to raise awareness and minimise misunderstandings.



Issue: Some contributions are not getting recognised or rewarded for various reasons. (I'm not talking about my contributions specifically. Rather I think this is one of the reasons some of left this research project. At times when I was DRI I forgot to mention individuals who completed work - not on purpose, of course - so we need to identify ways to avoid this.)

Solution: Create a system that is fit for purpose so that contributions to Daemo can be identified and tracked effectively. Is there a way that individuals can take responsibility for tracking and making others aware of their contributions? Only if participants think this is necessary, of course.


Issue: Feelings on not having a voice on various issues.

Solution: Identify ways to get participants to voice their opinions and ideas? Is the way we go about doing this at the moment ok? Perhaps Rajan can include this question in his survey.


Issue: Wanting to know who the people are in the project.

Solution: Foster community and trust through further develop the work we started in the Introductions channel. Have a place where each participant can share a bit about their interests in the project, their goals and anything else about themselves they'd like to share. For me, I like to make connections with people and know about their lives/interests/passions. I also think that it helps to build compassion and community.


Issue: Finding skills gap. Ha ha.... for example, you can see by my Wiki that I need some serious Wiki writing skills development training! Some that others have identified are marketing, branding, logo design, design thinking, abstract writing, programming related skills, etc.

Solution: Identify training and disseminate info through a robust data management system so that participants can further develop their own skills based on their needs/wants.