You’re sitting in a meeting. The team has identified a problem — revenue is flat, a key client is unhappy, the product launch missed its window. Within minutes, solutions start flying. “Let’s hire more salespeople.” “We need a new CRM.” “What if we pivot the roadmap?”
Nobody pauses to ask the uncomfortable question: Are we even solving the right problem?
This pattern repeats across boardrooms, startups, and corner offices worldwide. Leaders jump from symptom to solution, skipping the diagnostic work that separates effective problem solving from expensive guesswork. What’s missing isn’t intelligence or effort — it’s a problem solving framework that forces clarity before action.
Why Most Problem Solving Fails Before It Starts
In Instant Competence, author and CEO Drago Dimitrov puts it bluntly: “Defining the Problem is Half of Solving It.” Yet most leaders treat problem definition as a formality — a quick sentence before diving into solutions.
Consider a real pattern Dimitrov describes: an app development firm cycling through three business analysts, each time hoping the next hire would fix recurring project failures. “If the problem was truly the analysts, replacing them should have worked. But it hadn’t. That meant one thing: the real issue was still hidden beneath the surface.”
The firm was solving the wrong problem brilliantly. They had a people solution for a process problem. This is not an edge case — it is the default mode of most organizations.
The Foundation: Every Problem Is a Gap
Before you can solve anything, you need a precise definition of what you’re solving. The Instant Competence framework starts with a deceptively simple insight:
“A problem is the distance between where you are now (your current state) and where you want to be (your desired state). It is the space between reality and desire.”
This isn’t philosophy — it’s a diagnostic tool. When you define a problem as the gap between current state and desired state, three things become immediately clear:
- You can change the current state — take action to modify reality
- You can change the desired state — reorient what you actually want
- You can do some combination of both
Most leaders only consider option one. They never question whether the desired state itself needs adjustment. A problem solving framework that ignores this flexibility is already working with one hand tied behind its back.
The “Not Enough / Too Much” Reframe
Vague problem statements produce vague solutions. “We need to improve culture” leads nowhere. “We need to innovate more” sounds urgent but means nothing actionable.
Dimitrov offers a practical reframe: describe every problem in terms of not having enough of something good or having too much of something bad.
Instead of “our culture needs work,” you might say: “There is too much miscommunication and team conflict” or “There isn’t enough support for remote working.” Instead of “we need to innovate,” try: “There isn’t enough innovative thinking to stay ahead in our market” or “There is too much resistance to new ideas and strategies.”
As the book notes: “By framing your problems in this way, your issues become less about nebulous dissatisfaction and more about concrete, addressable gaps.”
This isn’t just wordplay. When you force yourself to name what you have too much or too little of, you’ve already started identifying the variables you can actually change.
From Fuzzy to HD: The Systems Mapping Step
Here’s where most problem solving frameworks stop — they help you define the problem but leave you staring at it. The Instant Competence system goes further by mapping the system behind the problem.
The core insight is captured in a formula: Y = w1a + w2b + w3c + w4d + w5e. Your outcome (Y) is the weighted result of multiple variables (a, b, c, d, e), each with different levels of influence (w1, w2, etc.).
This might look academic, but the application is profoundly practical. Dimitrov illustrates it with the simplest possible example: feeling cold.
“I am cold. I want to feel warm. My problem is that the current state of my body temp feelz is different from the desired state.”
You can’t snap your fingers and stop being cold. You have to understand the system — the variables that influence body temperature: weather, air conditioning, clothing, food. These are the “knobs” you can turn.
“The individual variables are like knobs we can turn in the service of changing the status of our outcome variable,” Dimitrov writes. “We can’t change the outcome variable directly — if we could, we would.”
This is the critical mental shift. You stop trying to change the outcome directly and start asking: What are the knobs in this system, and which ones should I turn?
Not All Knobs Are Equal
Some variables have enormous influence on your outcome. Others barely move the needle. “For some variables, a very little turn of the knob will be enough to produce a giant change in the overall outcome. For other knobs, you have to really turn them all the way up to the max to get just a little change.”
This is why effort doesn’t always equal results. You might be pouring resources into a variable with a tiny weight while ignoring the one that would move everything. A good problem solving framework forces you to identify which knobs matter most before you start turning them.
Connected Knobs: The Hidden Complexity
Systems have another layer of complexity that most frameworks ignore: variables affect each other. “Sometimes knobs are connected to one another. You turn one and the other moves, too.”
In business, this shows up everywhere. You lower prices (one knob) and volume increases (another knob moves), but so does customer support load (a third knob turns). You hire aggressively (one knob) and productivity initially drops as the team absorbs new people (connected knob).
Leaders who don’t map these connections get blindsided by consequences that were perfectly predictable — if only they had looked at the system instead of the symptom.
Solution Templates: The Step Everyone Skips
Once you understand the system, the Instant Competence framework introduces a counterintuitive step: describe the solution before you develop it.
Returning to the body temperature example, Dimitrov explains: “We can say that we already know the solution, at a low-resolution level: ‘I will solve my problem of being cold by increasing heat generation and trapping existing heat in my body from leaving.’ That’s the solution template.”
A solution template is not a solution — it’s a filter. Any specific action you consider must fit within the template or it’s not addressing the actual problem. This prevents the common trap of falling in love with a clever solution that doesn’t actually solve what needs solving.
“The benefit of thoughtfully stating the obvious is a psychological one,” Dimitrov writes. “You will be confident that you didn’t miss something. You’ve now immunized yourself from fears of ‘Is my solution even in the ballpark?'”
In practice, this looks like: “We will solve our revenue problem by increasing the value delivered to existing customers and expanding our addressable market.” That’s obvious. It’s also incredibly useful — because now when someone suggests “let’s cut prices by 30%,” you can test it against the template. Does cutting prices increase value delivered? Does it expand the addressable market? Maybe. But you’re evaluating it against a clear standard instead of debating in a vacuum.
Putting the Framework to Work: A 5-Step Exercise
You don’t need to read the full book to start applying this thinking today. Here’s how to use the problem solving framework on your most pressing challenge:
- State the gap. Write one sentence: “My current state is ___. My desired state is ___.” If you can’t fill in both blanks with specifics, you don’t yet understand the problem.
- Apply the “not enough / too much” reframe. Rewrite the problem as either “there isn’t enough ___” or “there is too much ___.” This forces concreteness.
- Map the knobs. List 4-6 variables that influence your outcome. Don’t list actions — list variables. “Marketing spend” is a knob. “Run more ads” is an action.
- Weight the knobs. Which 2-3 variables have the most influence on the outcome? Where are you currently over-investing in a low-weight variable?
- Write a solution template. In one sentence, describe what any successful solution must accomplish — without naming a specific solution. Use this as your filter for every option you evaluate.
This exercise takes 20 minutes. It will save you weeks of pursuing the wrong solutions.
The Deeper Shift: From Things to Systems
The real power of a structured problem solving framework isn’t any single technique — it’s the mental shift from seeing things to seeing systems. As Dimitrov writes: “All expertise involves precision. Mastery of any endeavor means understanding what systems are involved and discerning how to change the configuration of the system’s variables.”
Music is a system of notes, scales, harmony, rhythm, and tempo. Chess is a system of openings, tactics, strategic motifs, and endgames. Your business is a system of variables with different weights and interconnections.
When you start seeing systems instead of symptoms, you stop cycling through business analysts hoping the fourth one will fix things. You stop throwing more salespeople at a revenue problem that’s actually a product-market fit problem. You stop treating every crisis as unique and start recognizing the patterns underneath.
That’s not just better problem solving. That’s a fundamentally different way of operating as a leader.
Ready to Think Differently?
The approach described in this post is part of Drago Dimitrov’s Instant Competence system — a battle-tested methodology for leaders who need to make the right call, even when the path isn’t clear.
Read Instant Competence to get the complete 7-step system, with real case studies and practical exercises for every step.
Or start with the free Clarity Worksheet — a guided tool for defining and solving your most pressing challenge.