You’re staring at a whiteboard full of sticky notes. Your team has been in this conference room for two hours. Everyone agrees something is wrong — revenue is flat, the product launch missed its window, turnover on the engineering team is climbing. But when you ask the room to state the actual problem, you get five different answers.
This is the moment most leaders get wrong. Not because they lack intelligence or experience, but because they skip the single most important step in solving any business problem: defining it with precision.
As Drago Dimitrov writes in Instant Competence, “Defining the problem is half of solving it.” That’s not a motivational platitude. It’s a structural truth about how problem-solving actually works — and most business leaders violate it daily.
Why Most Business Problems Stay Unsolved
Here’s what typically happens when a business faces a challenge. Someone identifies a symptom — declining sales, missed deadlines, customer complaints — and the team immediately jumps to solutions. “We need to hire more salespeople.” “We should redesign the onboarding flow.” “Let’s switch project management tools.”
The solutions feel productive. They generate action items, timelines, and budgets. But six months later, the original problem persists, often wearing a new disguise. The reason is straightforward: the team solved the wrong problem, or more accurately, they solved a vague approximation of the real problem.
Vague problems produce vague solutions. And vague solutions waste time, money, and trust.
How to Define a Business Problem: The Gap Between Two States
The Instant Competence framework begins with a deceptively simple definition: a problem is the gap between your current state and your desired state. If your current state equals your desired state, there is no problem. If a gap exists, that gap — precisely measured and described — is the problem.
This sounds obvious until you try to apply it rigorously. Consider a CEO who says, “Our company culture is broken.” That statement feels true. It carries emotional weight. But it tells you almost nothing about what to fix. What is the current state of the culture? What would the desired state look like, specifically? Where exactly is the gap?
Without answering those questions, “fix the culture” becomes a black hole that absorbs resources without producing measurable change.
The Two Flavors of Every Problem
The framework introduces another clarifying lens: every problem can be expressed as either “not enough of a good” or “too much of a bad.” This reframe forces you to identify the specific variable that’s out of balance.
- “Our culture is broken” becomes → “We don’t have enough cross-team collaboration” (not enough of a good) or “We have too much siloed decision-making” (too much of a bad).
- “Revenue is flat” becomes → “We don’t have enough new customer acquisition” or “We have too much churn in our existing base.”
- “The product launch failed” becomes → “We didn’t have enough market validation before building” or “We had too much scope creep during development.”
Notice how each reframed version points toward a specific system variable you can investigate and adjust. The original statements pointed nowhere.
The Upgraded Resolution: From Fuzzy to High-Definition
Dimitrov calls this process of sharpening a problem statement the “Upgraded Resolution” — borrowing from the idea of image resolution. A standard-definition problem statement is blurry. An upgraded, high-definition problem statement is sharp enough to act on.
Here’s what the upgrade looks like in practice:
Standard resolution: “We need to improve our sales process.”
Upgraded resolution: “Our average deal cycle has expanded from 45 days to 78 days over the past two quarters (current state). We need to return to a 50-day average within the next quarter (desired state). The gap is 28 days of unnecessary friction, primarily concentrated in the proposal-to-contract phase.”
The second version doesn’t just describe a problem — it locates it within a system, quantifies the gap, and identifies where in the process the breakdown occurs. A team working from that statement will converge on solutions far faster than a team working from “improve sales.”
Three Questions That Upgrade Any Problem Statement
You can apply this technique immediately using three questions:
- “What is the current state, measured as specifically as possible?” — Force yourself to describe reality without judgment or interpretation. What do the numbers say? What does the situation look like if you remove all emotional language?
- “What is the desired state, and how will we know when we’ve reached it?” — The desired state must be concrete enough to recognize. “Better culture” is not a desired state. “90% of employees report feeling heard in quarterly surveys, up from 62%” is.
- “Is this ‘not enough of a good’ or ‘too much of a bad’ — and which specific variable?” — This question prevents you from staying at the symptom level and forces you down to the variable level, where solutions actually live.
Why Leaders Resist Defining Problems Clearly
If precise problem definition is so powerful, why do smart leaders skip it? Three reasons come up repeatedly:
Urgency bias. When something feels broken, the pressure to act is enormous. Defining the problem feels like delaying the solution. In reality, a well-defined problem dramatically accelerates the solution — but that’s counterintuitive when the building feels like it’s on fire.
Comfort with ambiguity. Vague problems are politically safe. “We need to improve collaboration” offends no one. “The VP of Engineering and the VP of Product have not aligned on feature prioritization criteria, causing an average 3-week delay per release cycle” names specific people and specific failures. Precision creates accountability, and accountability creates discomfort.
Confusing symptoms with root causes. Customer complaints are a symptom. High employee turnover is a symptom. Declining margins are a symptom. Leaders who treat symptoms as problems end up in an endless cycle of firefighting. The Instant Competence approach forces you to look beneath symptoms to find the actual system variables — the “knobs” — that are producing the unwanted outcomes.
The Body Temperature Test
One of the most effective illustrations of this approach comes from an analogy Dimitrov uses throughout Instant Competence: body temperature.
Imagine you feel cold. That’s your discontent — the vague sense that something is wrong. Now define the problem precisely: your current state is a body temperature of 96°F. Your desired state is 98.6°F. The gap is 2.6 degrees.
But here’s the critical insight: you can’t change your body temperature directly. Temperature is an outcome — the result of multiple variables (clothing, room temperature, activity level, hydration, health). To close the gap, you need to identify which variables (which “knobs”) to adjust. Put on a sweater. Turn up the thermostat. Drink something warm.
Every business problem works the same way. Revenue, culture, product quality, customer satisfaction — these are all outcomes. You can’t change them directly. You change the system variables that produce them. But you can only identify the right variables once you’ve defined the problem with enough precision to see the system clearly.
Putting It Into Practice: A 15-Minute Exercise
Take the biggest challenge your team is currently facing. Then work through this sequence:
- Write down the problem as your team currently states it. Don’t edit it. Capture the vague, standard-resolution version.
- Separate the current state from the desired state. Write each on its own line with as much specificity as you can. Use numbers where possible.
- Identify the gap. What is the measurable distance between the two states?
- Reframe using “not enough of a good” or “too much of a bad.” Which specific variable is out of balance?
- Rewrite the problem statement incorporating all of the above. This is your Upgraded Resolution.
If you do this exercise honestly, you’ll likely discover that your team has been debating solutions to a problem nobody had properly defined. That realization alone is worth the 15 minutes.
The quality of your solution is bounded by the quality of your problem definition. A perfectly executed solution to the wrong problem is still a failure.
Ready to Think Differently?
The approach described in this post is just Step 1 of the Instant Competence system — a complete 7-step methodology for solving any problem with clarity and confidence. The framework continues with clarifying your values, mapping system variables, developing solution templates, and stress-testing your decisions before committing.
Read Instant Competence to get the complete system, with real case studies and practical exercises.
Or start with the free Clarity Worksheet — a guided tool for defining and solving your most pressing challenge.
And if you’re an investor or operator who wants to see this problem-definition approach applied specifically to understanding businesses, check out What Does This Company Do? — where 32 qualitative spectrums give you high-definition clarity on any company.