Public preview
Team Handbook
One document answering every "how do we work here?" question for new hires.
Goal
End "first-week pain" where new hires lose 30h asking the same questions 10 times.
Steps
-
1
Section 1 — Comms channels: what for what?
Expected Outcome
Immediate
Next new hire becomes productive in 7 days instead of 21.
Evidence base
School: GitLab Public Handbook
Founders: Sid Sijbrandij · GitLab (2014)
GitLab — first fully-remote company with public handbook (2014, 2000+ pages); model for Basecamp, Doist.
Keywords
#handbook#documentation#writing#docs#وثائق#pyramid#minto#gitlab#onboarding#team#async#sid-sijbrandij#دليل تشغيل الفريق#عمل عن بعد#أسبوع أول للموظف#مراجعة ربعية للدليل#خمسة أقسام أساسية#basecamp-doist#خمس عشرة صفحة كحد أقصى#سبعة أيام إلى إنتاجية#2014-أول-شركة-عن-بعد#ألفا صفحة نموذج gitlab#معايير تفويض في الدليل#تحديث ربعي إلزامي#أي سؤال متكرر يجب دخول الدليل
Frequently asked questions
How long does "Team Handbook" take?
This exercise takes about 50 minutes, practiced with another person in a Creative format.
When will I notice the effect of "Team Handbook"?
Next new hire becomes productive in 7 days instead of 21. In the short term: In 3 months, "who do I ask about X?" drops 70%.
Is "Team Handbook" evidence-based?
Yes — it draws on GitLab Public Handbook (Sid Sijbrandij, GitLab (2014)). GitLab — first fully-remote company with public handbook (2014, 2000+ pages); model for Basecamp, Doist.
Is "Team Handbook" suitable for beginners?
Its difficulty level is: Intermediate. No external tools required — it can be practiced directly inside the app.
Subscribe for full access
Subscribe to Plus for full access to this practice and the whole catalogue, or try first — free, no sign-in, no commitment.
7 complete practices (one per domain) are free forever, no sign-in.