Don't Change Multiple Variables at Once
This is the cardinal rule of all troubleshooting, from fixing a car engine to debugging a line of code. It’s a foundational principle of the scientific method for a reason: to understand cause and effect, you must isolate variables. When you alter several
things simultaneously—like changing a marketing campaign’s ad copy, its target audience, and its budget all in one go—you create a fog of confusion. If performance improves, you won’t know which change was responsible. If it gets worse, you can’t pinpoint the new problem. The impulse to 'try everything' feels productive, but it destroys the very knowledge you need to solve the issue. A systematic process, where you change only one thing and then re-test, is the only way to get a clear signal. It may feel slower, but it’s infinitely more efficient than creating more chaos and having to backtrack.
Don't Immediately Blame Individuals
One of the core tenets of Root Cause Analysis (RCA) is to focus on the 'how' and 'why' a problem occurred, not 'who' was responsible. Shifting immediately to blame creates a culture of fear, where team members become hesitant to report issues or provide the transparent data needed for a real diagnosis. Problems in a business context are rarely the fault of a single person. They are more often the result of a flawed process, a broken system, a miscommunication, or an unforeseen external factor. Before you look for a person to blame, map out the process. Gather all the relevant information, from system logs to customer feedback, and look for systemic failures. By treating the problem as a system issue rather than an individual failing, you encourage collaboration and get a much more honest and complete picture of what truly went wrong.
Don't Redefine the Project's Core Goals
When a project hits a major roadblock, it can be tempting to move the goalposts. Stakeholders might suggest changing the objective to something more easily achievable, effectively declaring victory over a different battle. This is a critical mistake. Changing the project’s fundamental goals before you understand why the original ones aren’t being met is a form of surrender, not a solution. It prevents the organization from learning from the failure. A problem should first be clearly defined and understood in the context of the original goals. Only after a thorough analysis reveals that the initial goal was genuinely unattainable or misguided should you consider adjusting it. Until then, hold the objectives steady. They are the fixed point against which you measure the problem. Changing them is like changing the location of the finish line halfway through a race—it doesn't fix the runner's performance.
Don't Discard Your Established Processes
In a crisis, formal processes like change management, documentation, and communication protocols can feel like bureaucratic hurdles. The urge is to go rogue, make quick changes, and inform people later. Resist this. Your established processes are there for a reason—they provide stability, predictability, and a record of what was done. Abandoning them during troubleshooting is a recipe for disaster. Good documentation becomes even more critical when things go wrong; you need a log of what you've tried and what the results were. A systematic approach, guided by your existing workflows, ensures that any solution is implemented safely and that the fix can be understood and replicated later. Ignoring process turns a single problem into two: the original issue and the new, undocumented, and potentially unstable state you've just created.
