# Onboarding Guide
## ✨ Welcome to `[Team Name]`
`[Explain the team: who you are, why you exist, and what you do!]`
## 👜 Some things you'll need first
In order for you to follow this guide it's going to be super important that you have some things ready
- [ ] `[List the most important items to start following the guide. Eg. an e-mail account, SSO access, an account for the version control repositories, an onboarding buddy]`
## 🛂 Getting your accounts ready
`[For each account explain what it's used for, and how their account is accessed (eg. via SSO, password manager, etc), or how to request access if it requires manual action]`
- Infrastructure accounts (eg. AWS, Azure, Snowflake, etc.) - Code and CI (eg. Github, Jenkins, Circle CI) - Observability (eg. Datadog, Rollbar, Crashlytics, Grafana) - On-Call Duty (eg. Pagerduty) - App Stores (eg. App Store Connect, Play Store) - Internal Tooling Access (eg. CRM management, feature flag toggles, etc.) - Analytics (eg. Amplitude, Posthog, Google Analytics) - Task Management (eg. Linear, JIRA, Asana) - Knowledge Management (eg. Notion, Confluence, Readthedocs, RapidAPI) - Communication (eg. Slack, include the main channels) - Package Management (eg. NPM, Crates) - P&O Tools (eg. Bamboo, Workday, Personio) - LLMs (eg. Claude, OpenAI) - E-mail (eg. Google Account) - Performance Management (eg. Leapsome) - Password Managers (eg. 1Password, Bitwarden) - Design Tools (eg. Figma, Sketch) - Localization Management (eg. Lokalise, Crowdin, WebTranslateIt)
## 🧐 The who's who of `[Team Name]` and friends
`[Introduce your team, who they are and what they can help you with. Include prompts on what to ask them about.]`
But we also have good friends that you should definitely reach out to!
`[Primary stakeholders, contact points in other teams, people we collaborate with often.]`
## 📕 Terminology
Here's a glossary of terms and acronyms that you'll be hearing a lot. `[If there's a general glossary, link to it here. Introduce terms that are used often in your team: Acronyms, project names, etc.]`
## 🔬 Cloning Projects
So, lets get you started with the projects you should start cloning:
### ❤️ Our Projects
`[List and Link to the projects that your team actively works with.]`
### 🧡 Good Projects to Know About
`[List and link to projects that your team might not maintain but are useful to read to get context, or will come in handy later]`
## 🗓 Adding Some Important Things to your Calendar
There's always something going on in the office, so make sure you're aware of all the important events.
### 🕯 Our Rituals
If you haven't received the invites already, make sure to ask your teammates about: `[List your ceremonies, or recurring events so they can double cheeck their calendar. Include frequency and purpouse]`
``` Daily Standup Sprint Review Retrospective Sprint Planning Refinement ```
### 🤝 Company-wide Rituals
There are also some company-wide events that you might want to join:
`[Link to company-wide events. Include whether they're mandatory, recommended, optional. If not mandatory, explain under which conditions you recommend they attend]`
## 👩💻 Internal Communities
Ask some team members about these communities and the regular events:
`[Include chapters, communities of practice, but also social interest groups that can help your teammate form connections.]`
## 🔰 Onboarding Events
You should have some invites to some onboarding and training invites, the ones that are required are marked as such, for the other ones you can decide whether it's relevant for you: if you're unsure you can ask us about it.
`[If you have already set up some onboarding events, or the company has a set process for new joiners. Mention this here]`
## Some Tasks To Get You Started
### Meet the team, set up your environment (1st week)
Here's some tasks you can do to get started on the right foot. Ask your teammates if you're not sure about any of these!
- [ ] Schedule a chat with the following people. - [ ] Meet with **[Line Manager]** to learn more about the team setup, our way of working, etc. and set times together for: - [ ] Regular 1:1s - [ ] An initial expectations setting session - [ ] `[List who they should meet in the first week, clarify whether they're expected to set up the meeting or if the other person will. Include prompts of what they can expect the other person to tell them]` - [ ] Some initial reading - [ ] `[List and link to important documentation, such as infrastructure diagrams, employee handbooks, working agreements, architectural decision records, your team's knowledge base.]` - [ ] `[Create a small task that includes environment set up and a good "first target". Try to get a task that is completable in the first week and focused on their primary role]` - [ ] High Five everyone around you!
### Let's get some context (1st month)
- [ ] `[List who they should meet in the first month, clarify whether they're expected to set up the meeting or if the other person will. Include prompts of what they can expect the other person to tell them]`
- [ ] `[List more tasks that should be done in the first month, try to cover a broad area so they have an opportunity to explore different areas of your team. If tasks aren't set up, add the prompts on how to choose a task during the team planning sessions ]`
## ✨ Learning More
There's a lot of stuff in this guide, and not enough guide to go in depth into all topics! If you want to learn more, here's some links you might be interested in!
`[Link to any relevant documentation: Team agreements, practices, guides, documentation, etc.]`