Solutioning
"We should build a RAG pipeline for better responses."
→
Leads with technologyNames the stack before naming the problem
→
Assumes the problemSkips asking what customers actually struggle with
→
Optimizes for impressivenessComplex answer signals technical fluency, not judgment
→
Closes the conversationLeaves no room to discover the real issue
Problem Definition
"What are customers doing right before they get stuck?"
→
Leads with the customerStarts with behavior, not infrastructure
→
Questions the frameTreats the prompt as a hypothesis worth testing
→
Optimizes for fitThe right answer might be a better help link
→
Opens the conversationCreates space to find what actually needs solving