How Restructuring Can Help Your Team to Claim Ownership
19 October, 2020
I was managing a team of five people and whatever task we would be given, it would be picked by an IC who would be most available at the moment. They would work on a task and once completed, they would move to the next one. This approach didn’t allow people to build strong domain knowledge and they would often complain about lacking the purpose and motivation.
I decided to split the team into two sub-teams. The team consisted of four back-end engineers who were split into two subteams and one front-end engineer who would be added to a subteam that needed them the most at the moment. Two subteams would have their own area that they would be focused on and have ownership of. That helped them gradually develop their subject matter expertise and position themselves as knowledgeable individuals who can be respected because of their competencies. Claiming ownership happened as a natural consequence of that approach -- they became more connected with the domain and therefore, more responsible and concerned about all details of whatever would fall in their area of interest and expertise.
Their competencies soon became known to people outside the team. They would be reached out to as domain experts by people across the company. Also, it became widely known what was the area they owned and what they were responsible for.
The team underwent restructuring two quarters ago and the feedback from the team was tremendously positive. These changes allowed us to move faster because people were able to develop specific expertise and focus on things they felt confident about. Besides the evident improvement in velocity, we noticed the improvement in collaboration -- members of two subteams were much more eager to share information from their area of expertise and enhance cooperation when working on the common task.
- It is hard to enforce accountability without establishing ownership first. People tend not to care about things they don’t own and that are outside of their area of expertise.
- Before going forward with a reorg, make sure to talk to ICs and understand their wants and preferences.
- We were concerned that the reorg would eventually lead to isolation but in the long run, it enhanced cooperation. However, you have to ensure that knowledge sharing happens early on before two subteams become siloed.
Nimrod Perez, CTO and VP of Engineering at Wobi LTD., explains how he solved a long-troubling problem of disproportionate workload by his simple and egalitarian approach.
CTO and VP of Engineering at Wobi LTD.
Ido Cohen, Head of Product at Permutive, shares how he approaches communication with different stakeholders who more often than not have different -- and conflicting -- goals.
Head of Product at Permutive
Ido Cohen, Head of Product at Permutive, discusses the importance of solving the right problems and how failing to identify them can lead to misuse of resources and lost opportunities.
Head of Product at Permutive
Fei Xu, Engineering Manager at Square, Inc., recalls how he approached the restructuring of his team with an intent to have them claim ownership and develop subject matter expertise.
Engineering Manager at Square Inc.
Jeffrey Wescott, Director of Engineering at Splunk, describes how he introduced clarity on ownership between four disparate teams by drafting a charter that precisely demarcated who owned what.
Director of Engineering at Splunk
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.