61% of leaders say their first assumption about a problem turns out incomplete or wrong at least sometimes. 41% diagnose by talking with their team. 10% start with metrics, dashboards, or reports.
← All researchsay their first assumption about a problem turns out incomplete or wrong at least sometimes
rely most on talking with their team to work out what is not working
rely most on metrics, dashboards, or reports
When something feels off, 31% notice team performance or morale first and 24% notice their own workload or stress. 17% notice revenue or pipeline changes first. To work out what is not working, 41% rely most on talking with their team and 25% step back and map what is happening. 10% rely most on metrics, dashboards, or reports.
61% say their first assumption about the problem turns out incomplete or wrong at least sometimes: 47% sometimes, 10% often, and 4% almost always. When deciding what to fix next, 29% are driven most by urgency or immediate pressure and 28% by expected impact. 24% say they fix the most visible issue first.
What this suggests: the first read on a problem comes from people and pressure more often than from data, and 61% say that first read does not always hold. A first assumption works better as something to test than as something to fund.
Share of 100 respondents. The three blue bars add up to 61%.
61% say their first assumption is incomplete or wrong at least sometimes. In Study 03, 53% said they are very confident they know what is holding their business back.
Put together, leaders may be confidently misdiagnosing. And in Study 02, 29% lost more than $10,000 before realizing their fix had not resolved the problem.
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 →