Skip to content

Latest commit

 

History

History
45 lines (31 loc) · 2.25 KB

onboarding.md

File metadata and controls

45 lines (31 loc) · 2.25 KB

Onboarding

Thoughts on the onboarding process.

The process of onboarding new people into your 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" on our org... 😢
(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 via 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 what our purpose is and people are keen to get started. We need to have a clear process

What?

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

How?

  1. Make the person feel welcome. 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
  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. Give person the tools they need to get started without delay. see: dwyl/hq#131
  6. Show the person the knowledge they will need before they can be productive: https://github.com/dwyl?utf8=%E2%9C%93&q=learn
  7. Ensure the person has a complete knowledge of our Why? What? and How?
  8. Help the person pick a task to start with from the backlog.