Personal user manuals are a way for distributed workers to broadcast information about themselves to their colleagues. While they aren’t without their pitfalls, they can be an effective way to achieve some personal and team objectives.

Most tech companies want to run well-leveraged teams; i.e a few senior people and a bunch of junior people. But many of us lack the process discipline to do this well. How do you design a team environment that’s inclusive of junior people? That’s the million dollar question I address in this article.

Onboarding is one of the first areas where you’ll see payoff for the effort you spend in writing things up. In this post, let’s explore a few mindset shifts and a few tips and tricks you can use to bring people aboard your team. As you read on, you’ll notice how your handbook and your developer documentation are among the key ingredients to brew the perfect onboarding storm.

As a team scales, the need for documentation increases in parallel with the cost of not doing it. Daunting as it may seem, a handbook-first approach has many advantages, and will give your team a way to self-govern and self-organise. In this post, I’ll walk you through some ideas about what to include in such a resource and how you can create and maintain it.