Working in a group of five, under a Tech Lead, the author decided to dip toes into the waters of collective ownership and embrace a feature or service/microservice-based approach.
The goal was for every team member to be equally knowledgeable about every nook and cranny of the project, providing a wellspring of expert opinions to tackle bugs and roll out new features.
This approach ignited the team’s commitment and sense of ownership towards the project, providing unique opportunities for some team members.
Breaking down silos led to standardization and harmonization of best practices across different technologies and scopes, providing a common language for effective communication.
Collective ownership meant everyone was empowered to handle user stories from end to end, segment them better, and understand their impacts collectively.
This experiment led to erasing the need for a single point of contact and training team members to attend all project meetings and voice decisions.
However, it is essential to find and accept compromises, as everything in the organization must evolve together, not just one piece of the puzzle.
The importance of promoting autonomy and initiative, eliminating rules, fostering internal mobility and collective ownership, which disrupts the Tech Lead's roles, is vital to create a successful team.
The article concludes with celebrating small victories and contributing to the gradient descent.