Context

In software development projects involving multiple teams, there's often a misalignment between engineering practices and business goals. This misalignment can lead to delays and inefficiencies, particularly when working with external teams or new team members who may prioritize code perfection over business needs.

‍

Problem Identification and Consequences

Upon joining a project involving a large team of 50+ engineers, we encountered a situation where a member of our Client’s team was overly focused on code perfection. This led to:

1. Constant requests for minor, subjective code improvements during reviews
2. Delays in delivering an experimental product
3. Potential financial losses due to these delays
4. Misalignment with the project's experimental nature and timeline

The core issue was a disconnect between coding practices and business objectives, particularly for a short-term experimental project.

‍

Solution Implementation

To address this misalignment and improve collaboration, we implemented a multi-step approach:

1. One-on-one conversation: Initiated a dialogue with Tom to understand his perspective and explain the business context.
2. Educational document: Prepared and shared a document outlining the business aspect of code reviews.
3. Team meeting: Organized a discussion to align the team on code review practices, resulting in a "Team Agreements" document.
4. Personal development: Worked with Tom's team leader to set personal goals for his growth as a software engineer.

Throughout the process, we maintained a focus on team success rather than individual blame, adhering to our value of "Be a team player. We succeed and fail as a team."

‍

Business and Product Gains

This approach yielded several positive outcomes:

1. Faster product delivery: The experimental product was completed more quickly.
2. Improved team focus: The entire team became more attuned to business problems and objectives.
3. Maintained team dynamics: Relationships between team members remained positive.
4. Individual growth: Tom developed his skills as a more well-rounded software engineer.
5. Knowledge sharing: The experience led to the creation of "Code Review - Team Agreements," an article that helps other engineers become more business-aware.

By aligning external teams with business objectives, we not only resolved immediate project challenges but also created lasting improvements in collaboration and efficiency.