The handbook-first approach
Distributed teams must consolidate tribal knowledge into documentation.
Tribal knowledge is any information about a process that lives only in the minds of employees. It may vary between employees, but it remains undocumented.
To solve this, let me introduce you to the handbook-first approach.
It is counterintuitive to communicate changes to documentation. When they wish to do it, by default, people send a Slack message, an email, give a presentation, or tell people in a meeting—anything but edit documentation.
But Slack is an instant messaging tool masquerading as async. It is not suited to host business-critical knowledge.
The benefits of having a handbook are real:
- Consolidated knowledge will compound over time and save you time in the long run.
- While it is slower than any other option, you are building a solid business foundation for your following projects.
- Ensures that whatever is merged into the handbook has a proper trail, full of context and is universally accessible.
- If an expert leaves the company, you don't sweat the consequences of losing precious knowledge.
With the proper system and tooling, we can solve documentation at scale.
Here are 10 tips to get started.
1. Host your handbook in a single platform
You don't want people to switch platforms to find what they want.
Centralize to maximize discoverability.
2. Require at least comments, drafts, and version control
You can build a website and use Git to edit it.
Again, check out Almanac for a full-stack solution.
3. Have an excellent search engine
This is the fastest way to access knowledge. I strongly recommend Algolia.
4. Single source of truth
Be sure the handbook is the single place for your content with no duplication. Not two. Only one.
Link every content together.
5. Allocate time to edit it
Find capacity for your teams to invest in your handbook. Leadership MUST be on board.
Build a system for it. Some companies implement strict message retention to encourage teams to consolidate knowledge.
6. Link pages
Link a page when replying to someone.
If the knowledge is not there, add it.
7. Make it public
Build accountability by making it public. Have an internal one for private matters, but ensure it is the last resort.
Do you know another benefit of having your handbook public? You can search it on Google too.
8. Write notes elsewhere
Use another tool like Notion to take notes, but refine and consolidate them afterward into the handbook.
9. Make ownership clear
Organize it to ensure every item has a location and owner to keep it up to date.
10. Bring expertise
Consider hiring scribes to help edit the handbook and support your teams.
Don't wait to act
Building a handbook when scaling is challenging, as you change processes and culture while operating the business.
As a team grows, the need for documentation increases with the cost of not doing it.
The best moment to start is now.
Let's discuss building better companies.
You have better chances of finding me active on Twitter. I tweet about leadership, remote work, software engineering, personal growth, and systems. I also build my company publicly.
I'm also active on LinkedIn, where I post longer thoughts.
You can also contact me by email.
The handbook-first approach
Distributed teams must consolidate tribal knowledge into documentation. To solve this, let me introduce you to the handbook-first approach.
I decided to pivot my business
The world is crumbling under exponential complexity, diverting and consuming people's attention for the worse and generating tons of process waste. A story on why I pivot my business.
Why I advocate working from anywhere
The story of how I came to advocate remote work and swore to solve its challenges as an entrepreneur through the prism of my recent family history and origins.
Building trust early with an introduction letter to my teams
A very honest attempt to be more transparent about me to quickly build trust with my teams.
Who am I—a story on personal growth
I always been attracted by the concept of personal growth: getting to know yourself and working on it to reach your full potential.
Distribute features by executing in cycles
A straightforward product development approach builds around six-week cycles separated by two-week cool-down periods, inspired by Basecamp techniques.
A system attempt for startup studios
One of the greatest force of a startup studio is the powerful intellectual property (IP) that it owns, which unlock startup scalability potential, engineer and customer high-quality experiences, and massive business technological strike capacities.