Originally posted on my Twitter in Indonesian 👉🏻 Link to thread
When I first joined my current company, there was one thing that was very helpful and I could used it as a survival book, it's the Onboarding Doc.
Sharing a bit about why this Onboarding Doc helped me personally 👇🏻
Previously, in 8 years of career, I had never received an onboarding doc as detailed as this, I hope this can be an insight for those who have never done it and want to try to make something like this in your company.
I can say it's a kind of guide to pass the probation period haha. And it's really useful, so I don't feel clueless. I can understand how can I pass the probation period. If I achieve all of their expectations, it should be safe, right?
a little breakdown of the expectations in each month:
Not too many hands-on projects, heavier in product knowledge and building relationships with the team members. There is 1 design task in the first month, it's design audit. I really like this, so I can learn how the product works.
Connect to leadership roles in the office. This is something I've never experienced as well. So the program manager help me to setup the schedule with the leadership (head & VP) of all divisions. And so I can get a lot of wide insights too.
The most memorable insight I got was, when I spoke with VP of JP Media, He told me about how the media in Japan works, the flow of information and where the revenue comes from. It's interesting to discuss this sometime in a separate thread 🤔
In 60 days, I started to receive some hands-on expectations too, which have been broken down by each PM from the each squads I've been assigned to. Also started syncing a lot and participating in related team meetings too.
At this stage, it is full hands-on. Every docs has been broken down by PM. Neat and comprehensive. And from me personally, in the third month I have enough basic knowledge and ready to full hands-on.
In this doc, I am also given a breakdown for any meetings that repeated every week, two weeks, or monthly from each level such as: 1on1, Design team meetings, pillar/squad meetings & Company-wide meetings.
Its contents are like this:
- Core values
- Org chart
- Company history
- And other company regulations
This is important, so you know where to ask if you have question. Now, the contents are more like this:
- Joined in any squad details with the docs
- Who is the leadership?
- List of each individual in his squad. Not only the product team, but also the business etc. Again, so you know who you want to ask.
This helps a lot too. It contains this information:
- Week 1 checklist
- Design principles (mindset design)
- Kanban design (to know the progress of other designers)
- Design onboarding system
- Outline general deliverables (how to deliver to the engineer here)
It's been broken down, what slack channel should I join, PM also help with this for squads level channels. No need to ask here and there, you already know where you should go.
All the links you need from company-wide such as roadmaps etc., product teams, design teams to personal docs such as individual OKR, are all here. Including links to teams that are directly related to us when we work, such as PM, Data science, Ops, etc
This is simple but very useful. You have to install any tools, how to install them, and how if you want to request a new tools or apps, it's all here. Including how to see the data, how to see the research findings that have been done, etc.
When I just joined, the calendar for the first week has been filled for 1on1 with each individual in the design team for the introduction. So, the design team is encouraged to set 1 on 1 to introduce theirselves to the new comer. This is because the team is still small, so it's doable, if it's as big as Indonesian unicorn design team with hundreds people, it seems difficult.
I myself still like amaze with the neat and structured documentation in my current company. Here all use Notion. If you want to read it, the info is there.
End of thread. Hopefully it can be an insight for those who want to try it 🙏🏻