Recall the checks for writing a strong How-Might-We prompt.
Does the prompt name a real user and moment? Strong prompts point to a situation: first-time admin connecting live data, nurse preparing handoff, manager before corrective feedback. This keeps ideation anchored in empathize and define evidence. Does the prompt preserve the customer's job? Use progress language: feel safe, prove value, recover confidence, decide what to do next. Avoid product-area language alone. JTBD keeps the prompt from becoming a disguised feature request. Could three different solution types answer it? If only one feature can answer, the prompt is too narrow. Reopen the solution space before ideation. The second diamond needs divergence.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in