THE DECISION BRIEF · NO. 2
When The Problem is Loud, but the Decision is Silent

Leaders don't skip decisions because they are careless. They skip them because the problem gets loud enough to sound like a decision.
Sales are down. Margins are tight. The team is overwhelmed. The pipeline is inconsistent. The client experience is messy. Those are real problems, and they deserve attention. But none of them tell you what choice actually needs to be made.
That gap is where money gets wasted.
The cost
A problem describes pressure. A decision defines movement. When those two get confused, the team starts solving whatever feels most obvious.
"Sales are down" becomes "we need more leads." That might be true. But it might also be wrong. The real decision could be whether to change the offer, narrow the market, fix the sales process, raise prices, stop serving a bad segment, or rebuild the follow-up system.
Same pressure. Completely different decisions.
"Margins are tight" becomes "we need to cut costs." Maybe. Or maybe the real decision is whether to change pricing, reduce scope, redesign delivery, renegotiate vendors, or kill a service line that looks good on revenue and terrible on economics.
"The team is overwhelmed" becomes "we need to hire." Maybe. Or maybe the business needs fewer exceptions, cleaner workflows, better automation, fewer bad clients, or a more honest service model.
This is how shiny thing syndrome sneaks into serious leadership. Not because the operator is distracted. Because the decision was never defined tightly enough to protect the team from the most available answer.
The first answer is rarely neutral. It usually reflects whatever the team already knows how to do, whatever someone has been wanting to do, or whatever feels easiest to defend in a meeting.
That is not strategy. That is momentum wearing a better suit.
This is the first discipline in the DARK Method: Define the Decision. Not define the frustration. Not define the pressure. Not define the symptom. Define the actual call.
What needs to be decided? Who owns it? By when? What options are on the table? What evidence would change the call? What happens if you are wrong?
Until that is clear, every recommendation is early.
The decision has to be translated
The practical move is simple: stop letting the problem enter the meeting unconverted.
Before anyone proposes a fix, force the problem through a decision translation. This does not need to be complicated. You are not building a consulting deck. You are taking the pressure and turning it into a usable decision statement.
Use this structure:
- Pressure: What hurts right now?
- Decision: What choice does this pressure require?
- Options: What paths are actually available?
- Inputs: What information would change the call?
- Threshold: What would make us move, pause, or walk away?
That is the whole drill.
Take "revenue is inconsistent." As a problem, it creates panic. As a decision, it becomes something more useful: "We need to decide whether our growth constraint is offer, audience, channel, sales process, or retention."
Now you have a real conversation.
You can look at lead quality, close rates, deal size, referral sources, sales cycle length, client fit, repeat purchase behavior, churn, and delivery drag. You are no longer throwing tactics at a vague business headache. You are deciding which constraint deserves attention first.
The way you name the decision controls the inputs you look for. The inputs change the whole sheet.
The Pressure Test: The Decision Translation Drill
Take one problem in your business right now and run it through these five questions before your team starts solving it.
1. Are we describing pain or defining a choice?
"Cash flow is tight" is pain. "We need to decide whether this is a pricing problem, collections problem, expense problem, or timing problem" is a choice.
The first version creates anxiety. The second version creates work.
2. What are the real options?
If there is only one option on the table, you are probably not deciding yet. You are drifting toward the first answer that sounded reasonable.
Name at least three paths. They do not have to be equally attractive. The point is to force the preferred path to compete with other possibilities before it gets protected by momentum.
3. What input would change the answer?
This is where a lot of meetings get exposed. People argue hard for answers without being able to name what evidence would change their mind.
Ask it directly: what would we need to know to choose one path over the others?
If no one can answer that, the team may not be evaluating. They may just be defending preferences.
4. What harder decision are we avoiding?
Problems are often named in a way that protects the comfortable fix.
"How do we get more leads?" may avoid "Are we selling the wrong thing to the wrong market?"
"How do we increase capacity?" may avoid "Which clients or services are creating most of the drag?"
"How do we improve profitability?" may avoid "Is this offer economically broken?"
The name of the problem can hide the real decision. That is why it has to be pressure-tested before the team commits resources.
5. What is the cost of being wrong?
Not every decision deserves the same level of scrutiny. Some calls can be made fast because the downside is small and reversible. Others deserve a slower definition because the cost of being wrong compounds.
If the cost is low, move. If the cost is high, define the decision before the business starts marching behind an answer.
The close
The problem is usually the loudest thing in the room. That does not make it the most important thing.
The decision is quieter. It takes more discipline to find because it does not announce itself as loudly as the pressure does. But once you name it, the conversation changes. The options get cleaner. The inputs get sharper. The team stops confusing activity with direction.
A described problem can fill a calendar.
A defined decision can change the business.
If you are carrying a decision that still feels foggy, use the FREE Decision Anatomy Worksheet. It helps you take one real decision apart before the meeting turns pressure into motion.
Use it before the fix becomes politically committed.
Originally published in The Decision Brief on LinkedIn.
