Write the Insight Statement
Write an insight statement that is evidence-backed and action-oriented without prescribing an untested solution.
Kai has a vague finding: users are frustrated with setup. The team cannot act on it because the statement lacks situation, evidence, and job pressure. Insight statement: When [situation], users [behavior] because [need], so test [implication] The common trap is writing either a mood label or a solution. Mood labels are too vague to design against. Solution statements hide the inference and make the research sound more certain than it is. Name the situation When first-time admins are about to invite employees... The situation anchors the finding in a moment, not a general persona. Add observed behavior ...they delay launch…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in