Outside Help · Symptoms · Business problem

Three Proposals, Three Different Problems.

Three proposals can look like three ways to solve one issue. Often they are three different definitions of the issue.

Part of the Outside Help Market hub · Decision Atlas · Developed by Stan Tscherenkow

Three Proposals, Three Different Problems infographic thesis opener A page-specific thesis card showing the visible pressure, hidden layer, and correction. Proposal problem map Core claim
A proposal comparison is fake if the proposals are not solving the same business drag.
Business decision map Situation One businesspressure Proposal lens Agencycoachoperator Route Compare the problembefore scope Owner memory: name the layer before the proposal names it for you.
A proposal comparison is fake if the proposals are not solving the same business drag.
Text version: One business pressure can produce different proposals because each role names a different problem. The buyer must compare the problem before comparing scope.
Section 1 · Definition

I.Definition

Three proposals, three different problems is what happens when each outside-help role translates the same situation into its own scope.

The agency sees demand generation. The consultant sees process. The coach sees leadership behavior. The fractional leader sees ownership and cadence. The business coach sees a decision layer.

The proposals may all be competent. That is what makes the situation dangerous. Bad proposals are easy to reject. Good proposals pointed at different problems create expensive fog.

Section 2 · Where it fits

II.Where it fits

This pattern is a buying-market symptom. The buyer is trying to compare offers but the offers are not answering the same question.

It links directly to Hub 2 because proposal disagreement usually reveals role bias. It also links to Hub 7 because no proposal comparison works until someone names the decision the business is actually making.

Three Proposals, Three Different Problems infographic A four-step map showing one situation turning into three different proposals because each proposal defines a different problem. Proposal problem map Decision rule
A proposal comparison is fake if the proposals are not solving the same business drag.
Mechanism map 01 Situation One businesspressure 02 Proposal lens Agencycoachoperator 03 Problem named Three differentproblems 04 Route Compare the problembefore scope Repeatable ruleIf the layer is unnamed, the role defines it.
A proposal comparison is fake if the proposals are not solving the same business drag.
Text version: One business pressure can produce different proposals because each role names a different problem. The buyer must compare the problem before comparing scope.
Section 3 · When it works

III.When it works

This page works when the proposals are specific, serious, and incompatible. One recommends a campaign. One recommends a process redesign. One recommends executive coaching. One recommends interim leadership.

It works when each proposal reflects a real part of the truth. The agency may correctly see weak positioning. The consultant may correctly see broken handoffs. The coach may correctly see avoidance. The fractional leader may correctly see ownership gaps.

This page is especially useful when a team keeps arguing about which proposal is best while quietly skipping the harder question: which problem are we solving first?

Section 4 · When it does not work

IV.When it does not work

This page does not apply when one proposal is simply poorly scoped or factually wrong. That is not a market-map problem. That is a quality issue.

It also does not apply when the company intentionally needs several coordinated workstreams. Some situations need legal, operational, financial, and leadership support. The trap is pretending those workstreams are substitutes.

It fails when the buyer asks the cheapest proposal to do the work of the highest-consequence one. That is not resourcefulness. That is budgeting with a blindfold.

Section 5 · Common misuse

V.Common misuse

The first misuse is forcing proposals into one comparison grid. A neat grid can make incomparable things look comparable. The grid feels mature. The decision remains confused.

The second misuse is asking the last seller to interpret the earlier sellers. This usually produces a miracle. The last seller discovers that the correct answer is the thing they sell. History is stunned.

The third misuse is buying the proposal with the clearest deliverables. Clear deliverables matter, but a clear deliverable attached to the wrong place only gives the mistake better packaging.

Section 6 · Related roles

VI.Related roles

Too Many Kinds Of Help names the confusion before proposals arrive.

Three Advisors, Three Checks is the business coaching version of this proposal pattern.

Why This Decision Is Stuck helps when proposal disagreement points to a decision layer.

Section 7 · Decision test

VII.Decision test

  1. Do the proposals solve different versions of the problem?
  2. Can every proposal be partly right?
  3. Has the team named which problem comes first?
  4. Are deliverables being compared before the problem is compared?
  5. Would one decision owner be able to sequence the proposals rather than rank them?
Section 8 · Next route

VIII.Next route

Check How To Choose Outside Help if the next move is selection. Check Role Bias Explained if the disagreement is coming from professional lenses.

Choose by pressure

Use the next page only when the decision points there.

Use the next page only when it clarifies the next real decision.

Related pages

Choose the next decision layer.

RouteDecision Atlas hub RouteThe private company glossary, organized by the pressure behind the term.