01 / Vague askProperty: Symptom
Why are users dropping off?
Answer
They may be hitting friction. Review analytics, simplify the flow, and test clearer copy.
When the answer is generic, inspect the question first.
Prompting is not product thinking. Better wording will not save an unresolved decision.
A vague ask leaves too much room. It gives the model permission to produce almost anything coherent, which makes almost anything feel like progress.
The useful move is not a longer prompt. It is naming the judgment you expected AI to own.
A visible problem, but no boundary yet.
The answer must stay inside onboarding.
The answer must focus on new users.
The answer must relate to first value.
The answer must explain trust loss, not just friction.
The answer must say what would change the call.
The answer must point to a promise to remove or defend.
The answer must include what breaks if the decision is wrong.
If evidence shows it causes trust loss before the first useful result, remove or defend that promise before optimizing the flow.
Risk named. Evidence named. Decision owned.That question is the work. It turns the model from a decision-maker back into a tool for inspecting context, constraints, criteria, and consequences.
Same focus move, different object: an AI-built feature already works. The risk is mistaking a clean artifact for a reason to build.
The focused question asks what must change after use, what evidence would prove it, and what decision the team will own if the feature does not create that change.