Plato Elevate Winter Summit has been announced (Dec 7th-8th)

🔥

Back to resources

Building a New Domain Team

Building A Team

6 April, 2021

Thomas Lamirault
Thomas Lamirault

Engineering Manager at Ubisoft

Thomas Lamirault, Engineering Manager at BlaBlaCar, shares how he built a brand new team by transforming an existing component-based team into a domain-based one.

Problem

I joined a startup that used to organize its teams around components. I strongly felt that organizing them around specific domains would be far more effective. Some domains were left unattended and without clear demarcation of ownership over domains, and therefore, teams were reluctant to take ownership.

My proposal was met with approval, and I was eager to roll up my sleeves and start building a new domain team. I was tasked to build it from scratch, drawing the team boundaries and attracting new team members.

Actions taken

To start with, I had to provide a solid explanation of why we were undergoing this change and reorganizing the teams. Engineers are not always willing to embrace a change, and they often demand to know why something like that is done. They need to hear compelling arguments; otherwise, they would push back. Therefore, I delivered some robust arguments and expanded on benefits making sure that they would embrace the upcoming change.

The next step was to formulate a team charter, define a team mission and key objectives. I made sure all our strategic documents were clear and concise, which made new engineers who were joining the team well-informed and motivated. Following on that, Product and Engineering sat together to precisely define a roadmap and prioritize features that we would be working on in the upcoming period.

We populated the team with engineers from the company first. We circulated the team charter around, which quickly brought us some volunteers. Clearly defined charter proved to be a great way to attract mission-driven and proactive people. We also added some senior people who had extensive knowledge of the domain, but we also had to fill in our ranks by hiring people externally.

As a result, our domain-based engineering team became more efficient, and Product was happier with the structure they found to be more logical. However, the domain itself (security) is notorious for its strict deadlines, which was generating a lot of tension and caused some junior people and those less attracted by new mission to leave.

Lessons learned

  • In retrospect, I feel that I should have aimed for different profiles more suitable for our specific mission. My original plan was to have people of various profiles, and I felt that it would benefit the team. However, some of the juniors simply didn’t fit in. If people, like some of our juniors, didn’t feel they were the right match for our mission, you should let them go.
  • Build a rapport with the team early on. Explain what you plan to do, what your expectations are, and use that to build cohesion around the shared goals and aspirations.
  • Start small. Let things roll, but start small. It’s easier to consolidate and set up for success on a smaller team than a large one.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Delegate successfully as a first time manager of Product Managers

24 November

Andrew Tsui, a Product Leader, works to build great teams that are independent, demonstrate mastery of their domain, and fully commit to their purpose.

Scaling Team
Building A Team
Delegate
Coaching / Training / Mentorship
Psychological Safety
Cross-Functional Collaboration
New Manager
Andrew Tsui

Andrew Tsui

Director of Product at Startup

Managing New Team Members

6 October

Harsha Shekar, Engineering Manager at Atlassian Corporation Plc, explains how he brought up and eased new members into his team, while navigating through multiple challenges.

Building A Team
Collaboration
Motivation
Harsha Shekar

Harsha Shekar

Engineering Manager at Atlassian

Building an Organization From the Ground Up

19 September

Arpan Dalal, Sr. Director Engineering at RepairPal, speaks of his effort to build an organization from the ground up in a brand new domain of the mom-and-pop gardening space.

Product
Building A Team
Impact
Arpan Dalal

Arpan Dalal

Sr. Director Engineering at RepairPal

Scaling Teams to Make Better Decentralised Decisions via Documents and Tenets

6 September

Kirsten Zverina, Head of Product at Abethos Ventures, shares some decision-making mechanisms like FAQs and tenets, that can help reduce the pain of scaling teams.

Product Team
Scaling Team
Building A Team
Team Processes
Kirsten Zverina

Kirsten Zverina

Head of Product at Abethos ventures

Getting Ready for a Cold Start

25 August

Alex Oleinikov, Software Engineering Manager at People.ai, shares how he started a team from scratch and what he had to put in place before the first hires began to arrive.

Mission / Vision / Charter
Building A Team
Alex Oleinikov

Alex Oleinikov

Software Engineering Manager at People.ai

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.