48% of leaders want to move quickly when something is not working. 38% step back first. 29% lost more than $10,000 before realizing the fix had not resolved the problem.
← All researchwant to move quickly to fix it when something is not working
step back to understand what is happening first
lost more than $10,000 before realizing the fix did not work
When something is not working, 48% want to move quickly to fix it and 38% step back to understand what is happening first. 13% feel pressure to make the right decision. 1% say they are unsure what the real issue is.
Asked about a recent solution that did not fix the real problem, 61% estimated they spent or lost up to $10,000 before realizing it. 13% estimated $10,000 to $50,000, 11% estimated $50,000 to $100,000, and 5% estimated $100,000 to $400,000. 10% were not sure or did not track it.
What this suggests: the most common first reaction is speed, and 29% put the cost of a fix that missed above $10,000. That figure counts money only. The survey did not ask about time, delay, or decisions made in the meantime, and 10% could not put a number on it at all.
Share of 100 respondents. The three blue bars add up to 29%. No one reported more than $400,000.
48% want to move quickly when something is not working. In Study 03, 64% took significant action within three months of feeling stuck.
Responding quickly is not the same as solving the deeper problem. It means responding quickly to something that may or may not be the actual problem. It is like repairing the same pipe again when the pipe needs replacing, or the whole piping system needs to change. The leader is confidently repairing the pipe. The problem is not resolved.
Each study surveyed a separate group of 100 decision-makers, so this comparison is my interpretation, not a single measured result.
The full report is still being written. Leave your email and I'll send it to you the day it's out.
100 decision-makers in businesses of 2 to 50 people. Independent research by Julia Berger.
The talk: how founders burn time and money fixing symptoms instead of causes.
See the talk →The analysis platform I built so a diagnosis rests on performance data.
See the framework →