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

Managing remote first organization

4 January

I was hired at HUMAN in 2021 to manage a team that went from hybrid to completely remote working environment because of COVID.

Building A Team
Company Culture
Ahsan Habib

Ahsan Habib

VP Software Engineering at human

Myth Busting

10 December

Supporting principles on why being data led (not driven) helps with the story telling.

Alignment
Managing Expectations
Building A Team
Leadership
Collaboration
Productivity
Feedback
Psychological Safety
Stakeholders
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero

The Not-So-Easy Guide on How to grow and develop an Amazing A-Team

5 December

Your Org Team may as well be a Sports team. Let's explore how this cohesive, multi-skilled team can be optimized for Great Group Playoff.

Alignment
Building A Team
Company Culture
Sharing The Vision
Embracing Failures
Team Processes
Jaroslav Pantsjoha

Jaroslav Pantsjoha

Google Cloud Practice lead at Contino

DevSecOps: Why, Benefits and Culture Shift

29 November

Why DevSecOps matter and what's really in it for you, the team and the organisation?

Innovation / Experiment
Building A Team
Leadership
Ownership
Stakeholders
Cross-Functional Collaboration
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero

The Growth Mindset in Modern Product Engineering

28 November

The impact you can have with a Growth Mindset' and the factors involved in driving orchestrated change.

Building A Team
Leadership
Collaboration
Feedback
Ownership
Stakeholders
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero