How to Turn Developer Team Friction Into a Positive ForceHow to Turn Developer Team Friction Into a Positive Force
Friction is a force that surrounds everyone all of the time. For developer teams, it can be a source of both inspiration and irritation for IT leaders.

Teams occasionally generate a certain amount of internal friction, and development staffs are no exception. Yet, when managed properly, team friction can actually be turned into a motivating force.
Developer team friction can become a positive driving force when it encourages diverse perspectives, promotes critical thinking, fosters innovation, and improves communication skills, observes JB McGinnis, a principal with Deloitte Consulting. "Constructive disagreements can lead to more robust solutions, continuous improvement, and stronger team cohesion," he explains in an email interview. "By tapping into and exploring this friction positively, teams can enhance performance and drive innovation."
Friction can be a fantastic driver for positive change, states Andy Miears, a director with technology research and advisory firm ISG. "When members of a development team are at odds with each other, it often indicates some degree of inefficiency, lack of work product quality, a poor working environment, or unclear roles and responsibilities," he says via email. "Using friction as a compelling way to identify, prioritize, and address pain points is a healthy behavior for any high-performing team."
Multiple Benefits
Developer team friction, while often seen as a negative trait, can actually become a positive force under certain conditions, McGinnis says. "Friction can enhance problem-solving abilities by highlighting weaknesses in current processes or solutions," he explains. "It prompts the team to address these issues, thereby improving their overall problem-solving skills."
Read more about:
InformationWeekAbout the Authors
You May Also Like