Loomio

Recruitment process

Richard D. Bartlett PublicSeen by 64

Richard D. Bartlett

The code team are starting to work out a pretty robust recruitment process for new developers; we need to work out a collectively agreed process for bringing on non-coding volunteers too.

Apologies to @Dennis Lindner for using him as an example, but here goes:

I bumped into Dennis in the Enspiral office after he'd been invited by Keong to one of our UX sessions. Judging by the way our conversation flowed, I assumed a certain degree of values alignment and consequently invited him to join us at one of our Friday meetings. Dennis came along last Friday and by the end of the meeting had volunteered to help with our social media management.

I've started the process of bringing him onboard to do this task, which has got me thinking about recruitment in general. Gayatri has already done a bunch of work on defining this process, so perhaps now is a good time to go through that and see how it applies to this real life application:

https://docs.google.com/document/d/1Sdc-3c4fBuD_2RzzZ0jbxNsgDm3745FZow3P5YnVa3E/edit

What are the chief concerns we have to worry about when onboarding? The first things that come to my mind are:
- values alignment (how can this be tested?)
- skills match (are bringing the right people in at the right time?)
- diversity (we've brought on 11 men in the past couple weeks - it's basically impossible to maintain a balanced perspective within this environment)

I'm reluctant to go into a long winded or overly prescriptive process. I guess we want to be conscious of the needs of the whole team, and bring people on in a gradual manner where the level of responsibility increases in parallel with the level of trust.

I'm wary of creating an Us-Them environment, a concern which has to be balanced against the need for a kaitiaki group to be stewarding the vision. I'd like to see our structure develop in such a way that there is a clearly accessible path from first contact with Loomio, to becoming a user, to becoming a contributor, to becoming a team lead/kaitiaki/cooperative member/etc.

Sorry this is a bit rambly, it's a big sticky issue that is going to take a lot of time to refine. Think of this as the first iteration when you're adding your comments :)

Alanna Irving

  1. I think having better documentation of standard stuff like the Loomio story, profiles of who we are, how we relate to Enspiral, the overall roadmap for where we see the app and the org going, info about our shared document storage, regular meetings etc, will go a very long way. We need this stuff for lots of other reasons too.

  2. Eventually this issue will get thornier once we have revenue coming in and we're paying some people, but not other people. I think when we have some revenue but not lots, it's very reasonable for us to say "we're paying off debt to people who have been working on the project for months first, then we'll look at how to bring in new paid people"... but we should be clear and transparent about all of this to new people so they can manage their expectations and feel like it's fair.

Joshua Vial

I would recommend the friends/contributor/member model personally and define your own criteria / processes for moving between the roles.