/ Opening
The brief is a request—not automatically the problem
“We need awareness,” “fix the messaging,” and “launch a campaign” are proposed actions wrapped around an untested diagnosis.
REQUEST
What are they asking for?
The visible deliverable or action.
SYMPTOM
What is going wrong?
The observed business or human effect.
CAUSE
What produces the symptom?
Communication, structure, incentives, product, capacity, trust.
TAKEAWAYDo not solve the requested action until the problem class is clear.
PRODEVXQXQ1
/ Quick Test
Is this a communication problem?
Sales teams are not using a new product narrative.
MESSAGE-FIRSTRewrite the deck
Rewrite the deck
Train sales again
Create more materials
SYSTEM DIAGNOSISIncentives still reward the old product
Incentives still reward the old product
Proof is missing
Product cannot deliver the claim
Managers disagree on priority
TAKEAWAYCommunication may cause, expose, or amplify the problem without being the root cause.
PRODEVXQXQ2
/ Model
Move from brief to root-cause hypothesis
Keep the layers separate.
01Visible requestWhat solution was requested?
02Observed symptomWhat evidence says something is wrong?
03Problem classCommunication, capability, incentives, product, process, resources?
04Root-cause hypothesisWhat mechanism predicts the evidence?
TAKEAWAYA useful diagnosis changes the kind of solution the team considers.
PRODEVXQXQ3
/ Distinctions
Communication breakdowns have several forms
Name the specific failure rather than saying “alignment.”
INFORMATION
People never received what they needed
Access or timing failure.
MEANING
People interpreted the same signal differently
Frame, language, or context failure.
EXPECTATION
Roles, standards, or outcomes were unclear
Commitment failure.
COORDINATION
People knew but could not act together
Decision rights, process, or incentive failure.
TAKEAWAYClear communication cannot repair a system the organization refuses or lacks capacity to operate.
PRODEVXQXQ4
/ Team Challenge
Autopsy: “We need more awareness among small businesses”
Work backward from the requested media solution.
Low qualified demandHigh site traffic, weak conversionStrong interest, low sales follow-upExisting customers do not expand
OUTPUT: request · symptom · 5 whys · communication failure · structural constraint · root-cause hypothesis · evidence needed
TAKEAWAYThe right diagnosis should predict what evidence will appear and what action will change.
PRODEVXQXQ5
/ Pressure Test
Does the diagnosis survive new information?
A root-cause story must remain revisable.
1.What evidence supports the symptom?
2.What competing explanation fits the same facts?
3.What structural condition could messaging not fix?
4.What observation would falsify the preferred diagnosis?
TAKEAWAYThe diagnosis earns confidence by surviving pressure—not by sounding decisive.
PRODEVXQXQ6
/ Example
From awareness brief to adoption diagnosis
The problem class changes the solution.
LAYERREADDECISION
RequestBuy more small-business awarenessDo not accept yet
SymptomTraffic and inquiries already existAwareness may not bind
CauseBroker proof and follow-up path are weakTrust + process problem
ActionBuild proof and response systemFix adoption before scale
TAKEAWAYThe best diagnosis can make the requested deliverable unnecessary.
PRODEVXQXQ7
/ Close
Solve the cause that changes the decision
Communication makes systems legible; it does not replace structure.
SEPARATERequest from problem
TESTCompete explanations
ACTMatch solution to cause
TAKEAWAYDo not call every business problem a messaging problem—or ignore the communication system inside it.
PRODEVXQXQ8