Building connections when joining a new remote team
Joining a new team can be a thrilling and transformative experience.
Recently, I joined a team of over 20 colleagues. Although they had been working together for some time, there had been a restructuring before my arrival.
This new team was organized into feature teams, each responsible for a specific set of features. Additionally, team members were grouped into squads based on their technology expertise.
In my team, we had two mobile and one backend developers, one designer, and a dedicated team manager.
In this blog post, I will share my personal experience with the onboarding process, building relationships, understanding team dynamics, and much more. All this was while working remotely, which always presents an extra challenge in creating connections.
Stepping into a new team meant immersing myself in a whole new world.
Getting to know my team members and the company culture were crucial steps. I actively engaged in conversations, asking questions and listening attentively. One experience that left a lasting impression was attending a product team day on my first day. A product team day is a day where we explore common points, preferred working styles, and also where we step out of the everyday professional reality and allow ourselves to get to know each other better. Through this, I was able to gain deeper insights into the team's dynamics and objectives.
Building strong relationships with my new team members became a top priority.
I sought common ground by finding shared interests, hobbies, or experiences. Taking the initiative to engage in informal conversations during virtual coffee breaks allowed me to connect on a personal level. I also sought mentorship opportunities, leveraging the expertise of my more experienced colleagues.
Furthermore, I made a point to familiarize myself with the team, ensuring I was aligned with the established workflow. For example, I discovered that many team members preferred 10-minute meetings over exchanging messages on Slack. Others enjoyed pair programming or at least having virtual company while programming.
I had to develop the skill of articulating my thought process while programming. Seeking feedback was also vital to my growth within the new team.
I sought constructive criticism from my peers and team leaders, valuing their insights as catalysts for improvement.
Embracing the team culture went beyond understanding it: it meant actively contributing to its growth and harmony. As you embark on your journey, remember that joining a new team is an opportunity for growth, learning, and lasting impact.
Happy collaborating!