Firefighting in Product Development: Understanding the Tipping Point

Firefighting is a common problem in product development, where team members try to fix problems as they arise, often at the last minute. This could start a domino effect of issues and consume significant time and resources that weren’t anticipated. This blog article will discuss the problem of firefighting, how it affects the creation of new products, and how to prevent the tipping point.

The Cycle of Firefighting
Usually, the development team has gotten into the habit of fixing problems at the last minute, leading to a cycle of fixing one problem and discovering more. This is frequently brought on by a lack of communication and an optimistic attitude of wanting to solve problems on their own. The design process often involves fixing unexpected problems, causing extra work and delays in the project. As the problems pile up and the deadline approaches, the pressure to solve them increases, leading to longer hours and more stress for the team. This is known as the “Work Harder Loop.” The longer the team works this way, the more tired they get, making more mistakes, and creating more problems.

Eventually, the team reaches a tipping point, where they can no longer keep up with the problems and things start to get worse. This is a typical issue in companies that manage several projects at once, resolving issues but never preventing them. People become firefighters as it can be exciting and bring recognition, but it can cause more problems in the long run. The Beavertail project at Harley-Davidson was a prime example of this, with multiple problems that needed fixing, causing the whole company to focus on fixing them and putting other projects on hold.

The Root Cause of Firefighting
When a company experiences problems with their product development, it is often because there is something wrong with the system, not just the individuals working in it. However, leaders and managers might blame the workers instead of examining the system, causing frustration and making the problem worse.

Finding a Solution
A study by MIT students helped to shed light on the problem and find ways to improve the system. The study found that having a good flow and cadence in the development process is crucial to avoiding problems in the future. System maps were used to see the cause and effect of problems, helping the team to understand the issue better.

In conclusion, firefighting is a common problem in product development, causing a chain reaction of problems and taking up valuable time and resources. To avoid reaching the tipping point, it is important to examine the system and find ways to improve the development process, such as having a good flow and cadence. By doing this, organizations can prevent problems from arising and focus on delivering a successful product.