- Heroing in Software Development. Blog

---

In software development, "heroing" refers to a scenario where a team member, often a senior developer or a lead, discovers a critical defect right before a release and makes a "diving catch" to save the project from potential failure. While this may seem admirable, it represents a deeper issue within the team's dynamics and workflow.

Though a last-minute save can be better than a failure, heroing tends to cultivate unhealthy team dynamics and encourages undisciplined programming practices. Here's a closer look at the implications:

Unhealthy Dependency

When heroing becomes a norm, other team members may begin to rely on the hero to fix issues, undermining their responsibility and ownership of the code. This dependency discourages proactive problem-solving and fosters complacency.

Overwork and Burnout

Heroes often work under immense pressure, leading to overwork and burnout. The constant need to be on high alert and ready to fix critical issues at the last minute can be exhausting and unsustainable.

Undermining Trust

Trust issues may arise if team members feel their work is not trusted until validated by the hero. This lack of trust can stifle creativity and innovation, as engineers may hesitate to take risks or make decisions independently.

Stunted Growth and Learning

Heroing short-circuits the feedback loop essential for learning and growth. When the hero swoops in to fix problems, other team members miss out on valuable learning opportunities, leading to stagnation in their professional development.

Recognizing Heroing

Identifying heroing involves monitoring specific behaviors and metrics within the team:

 - Check-In Spikes: Look for spikes in the "help others" metric in Flow, particularly those involving late check-ins. This indicates that a team member is frequently intervening to fix issues at the last minute.

 - Self-Merging PRs: Observe if pull requests (PRs) are being self-merged, especially close to deadlines. This suggests that the hero is bypassing the review process to implement urgent fixes.

 - Low Review Activity: Monitor the code review activity. A pattern of low engagement in reviews until the end of a sprint or deadline could signify heroing behavior.

Addressing Heroing

Instead of managing the symptoms of heroing, focus on refining the code review process and promoting healthier team practices:

 - Encourage Frequent Commits and Interim Reviews: Aim for small, frequent commits and regular interim reviews for larger projects. This practice helps catch issues early and distributes the review workload evenly throughout the development cycle.

 - Early Feedback: Involve the hero in providing feedback early in the process, even before the code is completed. This preemptive approach can prevent last-minute crises and ensure continuous improvement.

 - Lower Barriers to Participation: Cultivate a habit of early and frequent feedback within the team. Reducing the size and frequency of PRs can make the review process more manageable and encourage broader participation.

 - Actionable Feedback: Coach the hero to transform their last-minute fixes into actionable, sustainable feedback for their teammates. This approach not only addresses immediate issues but also empowers the team to avoid similar problems in the future.

Cultivating a Healthier Team Environment

To foster a more collaborative and disciplined team environment:

 - Promote Ownership: Encourage all team members to take ownership of their code. This can be achieved by setting clear expectations, providing necessary resources, and recognizing individual contributions.

 - Balanced Workload: Ensure that no single team member, including the hero, is overburdened. Distribute tasks and responsibilities evenly to prevent burnout and maintain a sustainable pace.

 - Transparent Communication: Maintain open lines of communication within the team. Regular check-ins, retrospectives, and one-on-one meetings can help identify and address issues early, before they escalate into emergencies.

 - Continuous Learning: Invest in the professional development of all team members. Providing training, mentorship, and opportunities for growth can enhance their skills and confidence, reducing the need for heroing interventions.

By addressing the root causes of heroing and promoting a more structured and collaborative workflow, teams can improve their efficiency, resilience, and overall satisfaction in their work.