Problem Articulation as a Skill
The 8 vectors that separate vague complaints from actionable diagnosis Part one of the Problem Articulation Series
Your company has a revenue problem. You know this. Your board knows this. Your CRO references it on every call. And yet — ask five leaders in the room to define it, and you'll get five different answers. One says pipeline. Another says conversion. A third points to the market. The fourth blames enablement. The fifth just wants more headcount.
They're not wrong. They're imprecise. And imprecision is where strategy goes to die.
Here's what nobody talks about: most revenue organizations don't fail at solving problems. They fail at naming them. They prescribe — new playbooks, new methodologies, new tools, new hires — without ever diagnosing what those prescriptions are meant to cure. The result is activity without coherence. Initiatives that sound right but connect to nothing.
A survey of 106 C-suite executives across 91 companies and 17 countries found that 85% agreed their organizations were bad at problem diagnosis — and 87% said that flaw carried significant costs.^1^ Eighty-seven percent. Not "we could be better." Nearly nine in ten executives admitting the thing they're worst at is the thing that determines whether everything else works.
Charles Kettering, who ran research at General Motors for 27 years, put it simply: "A problem well stated is half solved."^2^ That line has been repeated so often it's lost its edge. But sit with it. Half solved. Not ten percent. Not a good start. Half. Because a well-stated problem eliminates most of the options, narrows the search space, and makes the right answer almost obvious.
The inverse is equally true. A poorly stated problem multiplies options, diffuses effort, and guarantees that smart people will spend months solving the wrong thing.
Why This Matters Now
Revenue organizations have never had more data, more tooling, or more methodology. And yet: the median SaaS win rate dropped from 23% in 2022 to 19% in 2024.^3^ Only 24% of sellers met or exceeded quota last year.^4^ Forty to sixty percent of qualified pipeline ends in "no decision" — not because buyers don't care, but because nobody anchored the evaluation on a problem defined clearly enough to build consensus around.^5^
More pipeline isn't fixing it. More coaching isn't fixing it. The missing capability isn't execution. It's diagnosis.
Richard Rumelt, in Good Strategy Bad Strategy, argued that diagnosis is the first element of strategy's kernel — before guiding policy, before coherent action. Get the diagnosis wrong, and everything downstream is elegant motion toward the wrong destination.^6^ McKinsey built its entire intellectual foundation on structured problem decomposition, starting with Barbara Minto's MECE principle in the late 1960s — the idea that problems must be broken into pieces that are mutually exclusive and collectively exhaustive before they can be solved.^7^ The Challenger Sale showed that reframing a buyer's understanding of their own problem is the highest-leverage selling act — responsible for 53% of customer loyalty, more than brand, product, or service delivery combined.^8^ MIT Sloan called problem formulation "the most underrated skill in management."^9^
But each tradition keeps the skill in its own silo. Strategists treat diagnosis as internal analysis. Consultants treat it as decomposition for the team room. Sales methodologies treat it as a discovery technique for individual reps. Nobody has connected them into a single discipline where the quality of your problem articulation — how precisely you name what's broken, why, and what's at stake — is itself the competitive advantage.
This article builds that discipline. Eight vectors. One framework. The difference between "we have a pipeline problem" and a statement so precise that every downstream decision becomes obvious.
The Three Jobs of a Well-Defined Problem
Before the vectors, the standard. A well-defined problem does exactly three things:
1. Names the constraint. Not the aspiration. Not the symptom. The actual bottleneck limiting performance. "We need to grow faster" is an aspiration. "Win rates are declining" is a symptom. "58% of deals that reach proposal are single-threaded on a mid-level champion who lacks authority to push a buying decision" is a constraint.
2. Identifies the friction inside the system. Where behavior, incentives, or capability are misaligned — and why. Not "reps aren't productive enough." Rather: "The playbook tells reps what to do but not how to read the buyer — so the middle 60% default to one approach regardless of who's across the table."
3. Makes the stakes explicit. What happens if this isn't resolved. To whom. How fast. "If we don't fix this" is not stakes. "Every quarter this goes unaddressed, compensating with volume increases CAC by 12-15% while conversion stays flat — a margin compression spiral the board will notice in two quarters" is stakes.
Without all three, teams chase symptoms. They ship initiatives that generate activity reports but not results. They solve adjacent problems while the real one compounds.
When the problem is clear, it becomes a filter:
- Insights must explain why the problem exists.
- Choices must aim to resolve it.
- Actions must demonstrably reduce it.
- Outcomes should feel like the logical consequence.
If an initiative can't be traced back to the defined problem, it doesn't belong in the strategy.
The Eight Vectors of Problem Articulation
Every problem statement can be evaluated along eight vectors. Think of them as dials on a mixing board. Weak statements have most dials turned down. Strong ones have them up. The skill isn't knowing the dials exist — it's hearing which ones are low and turning them up.
The vectors follow a sequence in three phases that mirror how a listener actually processes a problem:
Phase 1 — Establish. Who cares and what's happening? Phase 2 — Diagnose. Why, where in the system, and how deep? Phase 3 — Stakes. How urgent, and who pays?
Skip a phase and you lose the room. Establish without Diagnose: "Interesting, but what do we do?" Diagnose without Stakes: "Makes sense, but we have other priorities." Stakes without Establish: "You're being dramatic — show me the data."
Vector 1: Relevance
From generic to "that's MY problem."
Relevance comes first because it determines whether the rest get heard. You can articulate a problem perfectly — specific, causal, quantified — and get nothing back. Not because it's wrong, but because it's framed for a different audience.
The same issue — "reps aren't engaging the buyer group effectively" — is a completely different problem depending on who you're talking to:
| Audience | The same problem, made relevant |
|---|---|
| CRO | "43% of your commit deals slip because there's no independent buyer signal validating deal readiness — your forecast is a confidence poll, not a data model." |
| VP Sales | "Your middle 60% of reps run single-threaded deals on junior contacts because the playbook tells them what to do but not how to read the buyer." |
| CFO | "Forecast variance has exceeded 15% for three consecutive quarters because the input is rep self-assessment, not buyer behavior data — every plan built on that number is wrong." |
Same root cause. Three framings. Each lands because it speaks in the language of that person's priorities, metrics, and daily reality.
The test: If you swapped the audience — gave the CFO version to the VP Sales — would it still land? If yes, it's not relevant enough.
How to dial it up: Know the archetype. Their KPIs. Their highest-severity pain. Frame in their metrics, their language, their consequences.
Relevance is the multiplier. The other seven vectors make the problem good. Relevance makes it land.
Vector 2: Specificity
From vague to precise. Name the segment, the metric, the timeframe.
| Level | Example |
|---|---|
| Vague | "Our pipeline isn't strong enough." |
| Moderate | "Our enterprise pipeline is underperforming this quarter." |
| Specific | "Enterprise pipeline above $100K has declined 22% quarter-over-quarter while SMB has grown 15%, creating a mix shift that drops average deal size and puts $2.4M at risk." |
Toyota's Taiichi Ohno developed the "5 Whys" technique precisely because vague problem statements led to shallow fixes.^10^ The technique's genius wasn't the number five — it was the insistence that you can't solve what you haven't specified. Every "why" forces another layer of specificity.
The test: Can someone who wasn't in the room understand exactly what's wrong, in what segment, by how much, and since when? If two people read your problem statement and picture different things, it's not specific enough.
Vector 3: Quantification
From qualitative to measured.
| Level | Example |
|---|---|
| Qualitative | "Reps aren't productive enough." |
| Directional | "Most reps are below quota." |
| Quantified | "34% of reps hit quota last quarter, down from 52% two quarters ago. The gap between top and bottom quartile win rates has widened from 1.8x to 2.6x in 12 months." |
Numbers do something adjectives can't: they eliminate ambiguity. "Most reps are below quota" lets every listener imagine a different severity. "34% of reps hit quota, down from 52%" creates a shared picture — identical in every mind that reads it.
A 1,000-employee organization wastes roughly $6 million per year on inefficient problem-solving — much of it because problems are described qualitatively rather than quantified precisely enough for everyone to agree on severity.^11^
The test: Could two people read this and arrive at the same understanding of how bad things are? Numbers create convergence. Adjectives create debate.
Vector 4: Causality
From symptom to root cause. The difference between describing what's wrong and explaining why.
| Level | Example |
|---|---|
| Symptom | "Win rates are declining." |
| Proximate cause | "Win rates are declining because deals stall in late stages." |
| Root cause | "58% of deals that reach proposal are single-threaded on a mid-level champion who lacks the authority to push a buying decision — and our process has no step requiring multi-threading before a proposal goes out." |
Blair Enns wrote it plainly: "Prescription without diagnosis is malpractice."^12^ In medicine, this is obvious. No doctor prescribes chemotherapy because a patient "doesn't feel well." But in revenue organizations, it happens constantly. Win rates decline, so leadership prescribes more pipeline. Deals stall, so they prescribe more training. The prescription addresses the symptom because nobody traced the symptom to its cause.
The test: If you removed the cause from the statement, would it still feel complete? If yes, you've described a symptom, not a problem.
Vector 5: Locus
From "it's happening to us" to "here's the system we built that creates this."
| Level | Example |
|---|---|
| External | "The market is more competitive." |
| Shared | "Competitive pressure increased and our approach hasn't adapted." |
| Internal | "We're losing competitive deals because our reps engage the buyer group the same way regardless of whether there's an incumbent — and we have no playbook for displacement deals, which now represent 40% of pipeline." |
External locus feels safe. It absolves. "The market is tough" is the corporate equivalent of shrugging. But it also removes agency. If the problem is out there, you can't fix it. Internal locus is uncomfortable — it means you built the system that's failing — but it's the only version that points to a lever you can pull.
The test: Does the statement point to something you can change? If the answer is no, it's not a problem statement. It's a weather report.
Vector 6: Systemic Depth
From isolated incident to structural pattern.
| Level | Example |
|---|---|
| Incident | "We lost the Acme deal because the champion left." |
| Pattern | "We've lost three enterprise deals this quarter when our primary contact changed roles." |
| Systemic | "78% of our enterprise deals are single-threaded. Our CRM, deal review, and methodology don't require or measure multi-threading — so we systematically build fragile deals and discover the fragility only when a person leaves." |
This is where the 5 Whys earns its keep — and also where it breaks down. Ohno's technique works brilliantly for linear causal chains: the machine stopped because the fuse blew because the bearing was insufficiently lubricated. But revenue problems are rarely linear. They're systemic. The issue isn't one cause — it's that the system was designed to produce the failure.^10^
The test: If you fixed this one instance, would the problem come back? If the answer is yes, you haven't gone deep enough. You're treating the symptom, not the mechanism that generates it.
Vector 7: Tension
From comfortable to urgent. What breaks if this continues?
| Level | Example |
|---|---|
| Low | "We should probably look at our sales process." |
| Moderate | "If deal cycles keep extending, we'll miss the annual target." |
| High | "Deal cycles have expanded 38% in four quarters. At this trajectory, we close 23 fewer enterprise deals this year — a $4.1M gap that can't be filled by adding pipeline because the bottleneck is conversion, not volume. Every quarter we wait, the gap compounds." |
Tension comes from three sources: trajectory (it's getting worse), compounding (delay increases cost), and irreversibility (the window is closing). The strongest problem statements invoke all three.
Without tension, a perfectly diagnosed problem sits in the backlog indefinitely. With it, the problem demands a response. This is not manufactured urgency — the "this offer expires Friday" tactic. It's surfacing the real cost of inaction using the buyer's own data.
The test: Does it create a felt need to act now? Not "eventually." Not "when we get to it." Now.
Vector 8: Stakeholder Consequence
From abstract to personal.
| Level | Example |
|---|---|
| Abstract | "Forecast inaccuracy creates planning challenges." |
| Departmental | "Forecast misses force finance to revise hiring plans mid-quarter." |
| Personal | "When the CRO's commit drops 20% in week 10, the CFO re-cuts the plan, the CEO re-sets with the board, and the CRO walks into the next meeting having missed two quarters in a row — a pattern that raises the question of whether the revenue function has the right leadership." |
This is where problem articulation becomes uncomfortable — and effective. Abstract consequences don't move people. Departmental consequences create concern. Personal consequences create action. Not because you're threatening anyone. Because you're making the stakes real.
The test: Can the person hearing this see themselves in the consequence? Can they feel what it costs them specifically — their credibility, their career, their ability to lead?
The Sequence at a Glance
| Phase | Vector | Question | Job |
|---|---|---|---|
| Establish | 1. Relevance | Is this their problem? | Target |
| 2. Specificity | What exactly? | Name | |
| 3. Quantification | How bad? | Size | |
| Diagnose | 4. Causality | Why? | Explain |
| 5. Locus | Can we fix it? | Locate | |
| 6. Systemic Depth | Pattern or one-off? | Depth-test | |
| Stakes | 7. Tension | How urgent? | Time-bound |
| 8. Consequence | Who pays? | Personalize |
The phases mirror how a listener processes information. First: "Is this about me? What is it? How big?" Then: "Why? Can we fix it? Will it recur?" Finally: "How urgent? What happens to me?"
The Scoring Rubric
Before presenting any problem statement, run it through this scorecard:
| # | Vector | Weak (1) | Moderate (3) | Strong (5) |
|---|---|---|---|---|
| 1 | Relevance | Generic or wrong audience | Touches their world but uses your language | Stated in their KPIs and consequences — would feel wrong delivered to a different role |
| 2 | Specificity | "We need to improve" | Named segment OR metric | Segment, metric, timeframe, and comparison |
| 3 | Quantification | No numbers | Directional: "most," "many" | Precise: percentages, dollars, trend lines |
| 4 | Causality | Symptom only | Proximate cause | Root mechanism — system design, incentive, or structural gap |
| 5 | Locus | "Market is tough" | "Market changed and we haven't adapted" | Specific internal system, process, or capability gap |
| 6 | Systemic Depth | Isolated incident | Recurring pattern | The mechanism that generates the pattern |
| 7 | Tension | No urgency | Implies risk | Trajectory + compounding + closing window |
| 8 | Consequence | "Creates challenges" | Departmental impact | Named role, specific personal toll |
32-40: Ready. Clear enough to filter every decision that follows. 24-31: Close. Identify which vectors are below 3 and fix them. 16-23: Not ready. Will generate debate about what the problem is rather than what to do about it. Below 16: That's a topic, not a problem. Start over.
Putting It Together: One Problem, Full Articulation
Here's what a fully dialed problem statement looks like — all eight vectors turned up — for a CRO:
"62% of our pipeline has no identified decision maker engaged. Our 3.2x coverage ratio masks a qualified-pipeline gap that puts the majority of forecasted revenue at risk. The system rewards pipeline creation — seller actions — but doesn't measure qualification against buyer actions. Reps are incentivized to fill, not qualify. Nothing in the process requires buyer-side validation before a deal counts as coverage. The CRO presents this pipeline to the board. When 40%+ of commit deals slip because no budget holder was engaged, credibility erodes. Two consecutive misses and the conversation shifts from pipeline to leadership."
Score that against the rubric. Relevance: CRO's top priority. Specificity: pipeline without a decision maker, named metric. Quantification: 62%, 3.2x, 40%+. Causality: system rewards creation over qualification. Locus: internal — CRM, incentives, review criteria. Systemic depth: nothing requires buyer validation at any stage. Tension: board credibility eroding. Consequence: the CRO personally.
That's a 38. That's a problem statement that doesn't generate a discussion about what's wrong. It generates a discussion about what to do.
Six Grammar Patterns
Once you internalize these structures, you generate problem statements fluently. Six patterns that cover most situations:
1. The Quantified Gap
"[Metric] is at [current] against [target], a gap of [X%], because [root cause]."
2. The Misaligned System
"We measure [X], but the outcome we need requires [Y]. The result is [consequence]."
3. The Invisible Cause
"[Symptom] is not caused by [common assumption]. It's caused by [hidden root cause] — which is why [standard remedy] hasn't worked."
4. The Compounding Trajectory
"[Problem] has moved from [past state] to [present state] over [timeframe]. At this trajectory, [future consequence]. The standard response — [current approach] — accelerates the problem because [why]."
5. The Capability Asymmetry
"[Top performers] achieve [result] because they [capability]. [Everyone else] cannot because [system gap]. The gap costs [quantified impact]."
6. The Structural Blindspot
"Our [system] captures [what it tracks]. It doesn't capture [what it misses]. This means [decision] is based on [incomplete input], producing [failure mode]."
Pick the pattern that fits your situation. Fill in the brackets with specifics. Score it against the eight vectors. Turn up the dials that are low.
What This Means for Revenue Leaders
The frameworks exist. MEDDIC. Challenger. Force Management. SPIN. Each improved some dimension of how revenue teams operate. But none of them start where strategy starts — with diagnosis.
Rumelt was right: the kernel of good strategy is diagnosis, guiding policy, coherent action. In that order.^6^ Skip the first, and the other two are sophisticated guessing.
Here's the practical implication: the next time your team says "we have a pipeline problem" or "win rates need to improve" or "we need to shorten deal cycles" — stop. Run it through the eight vectors. Ask: Which segment? How much? Why? What in our system produces this? How fast is it getting worse? Who specifically pays?
You'll find that the vague complaint contains a precise problem. And that the precise problem — once named — makes the solution almost obvious.
That's the skill. Not solving problems faster. Naming them better.
Next in the series: The Archetype Multiplier — the same problem articulated for CRO and VP Sales. Same root cause, completely different language. Because precision without relevance is insight that lands in the wrong inbox.
Endnotes
^1^ Thomas Wedell-Wedellsborg, "Are You Solving the Right Problems?" Harvard Business Review, January 2017. Survey of 106 C-suite executives across 91 private- and public-sector companies in 17 countries.
^2^ Attributed to Charles F. Kettering, head of research at General Motors, 1920-1947.
^3^ SaaS industry benchmarks: median win rate declined from 23% (2022) to 19% (2024). Sources include Forrester, Pavilion, and RevOps benchmarking surveys.
^4^ CSO Insights / Forrester, 2024 Sales Performance Study. Only 24% of sellers met or exceeded quota; 51% achieved 75% or less.
^5^ Matthew Dixon, citing Gartner research: 40-60% of qualified pipeline ends in "no decision." Gartner's own buyer surveys confirm nearly 40% of all B2B buying journeys end without a purchase.
^6^ Richard Rumelt, Good Strategy Bad Strategy: The Difference and Why It Matters (Crown Business, 2011). The "kernel" of good strategy: diagnosis, guiding policy, coherent action.
^7^ Barbara Minto developed the MECE (Mutually Exclusive, Collectively Exhaustive) principle while at McKinsey & Company in the late 1960s, later published as The Pyramid Principle: Logic in Writing and Thinking (1985).
^8^ CEB (now Gartner), The Challenger Sale research. Study of 6,000+ sales representatives found that teaching-led interactions — reframing the buyer's understanding of their problem — drive 53% of customer loyalty in B2B.
^9^ Nelson P. Repenning, Don Kieffer, and Todd Astor, "The Most Underrated Skill in Management," MIT Sloan Management Review, Spring 2017.
^10^ Taiichi Ohno, Toyota Production System. The "5 Whys" technique was developed as an iterative root-cause analysis method at Toyota Motor Corporation. Note: even Toyota's former managing director Teruyuki Minoura later acknowledged the technique can be "too basic" for complex systemic problems — hence the need for systemic depth (Vector 6) beyond simple causal chains.
^11^ Estimated organizational cost of inefficient problem-solving based on productivity research; cited in problem-framing literature including Wedell-Wedellsborg (2017) and subsequent analyses.
^12^ Blair Enns, The Win Without Pitching Manifesto (RockBench Publishing, 2010). "Prescription without diagnosis is malpractice."