Skip to content

Latest commit

 

History

History
55 lines (37 loc) · 3.13 KB

onboarding.md

File metadata and controls

55 lines (37 loc) · 3.13 KB
Raw

Onboarding

Thoughts on the onboarding process.

The process of onboarding new people into an organisation in general and developers specifically is one we've thought about extensively and is the purpose of the start-here repo!

We openly acknowledge that (besides a readme with links to other readmes) we are doing a woefully poor job of getting people "up-to-speed" in our org/team ... 😢
(even though this is the single highest value task we can perform!)

It would be great to get other people's thoughts on the process from the various perspectives you've had working in several different organisations. Have you ever worked somewhere that had a "bullet-proof" step-by-step process for new people joining a team/org? please share as comment(s): #106

Why?

Making people feel loved/included and part of the community/team instantly is the goal of the start-here repository.

how-much-you-care

After we have explained our mission and people are keen to get started, we need to have an unambiguous process.

What?

Make people feel welcome, loved and empowered to get started without delay!

image

People joining DWYL are family and want them to feel like DWYL is their home.

How?

The success of the new person (and continued thriving of the existing team which new person has joined) depends on several factors.

get_cape__wear_cape__fly

  1. Make the person feel welcome. Aim to make them feel like it's their Birthday and everyone is celebrating! 🎉
  2. Understand the person on a personal level: what makes them "tick"? Only by understanding a person's intrinsic motivations can you hope to work well with them.
  3. Contextualize and give the "Brief History of ..." so they know "where we came from".
  4. Introduce the person to all the relevant people in the org/team they are going to need to speak to and why.
  5. Reserve Time in the calendars of all necessary people (preferably the week before the new person starts) so that they can get the necessary 1:1 or team-time.
  6. Give the person the tools they need to get started without delay. see: dwyl/hq#131
  7. Show the person the knowledge repository they will need before they can be productive: https://github.com/dwyl?utf8=%E2%9C%93&q=learn
  8. Ensure the person has a complete knowledge of our Why? What? and How?
  9. Help the person pick a task to start with from the backlog.
  10. Encourage the new person to ask as many questions as they need to by searching through existing knowledge base and posting fresh questions (to which they did not find an adequate answer during their initial search)