Surface unmet user needs and creative improvement ideas through open-ended sentence completion at scale.
"I Wish That..." captures unmet user needs and desires through an open-ended sentence completion technique that surfaces honest, creative feedback.
"I Wish That..." is a lightweight feedback technique where users complete the sentence stem "I wish that..." on cards, stickers, or digital forms to express unmet needs and desires in their own words. UX researchers, service designers, and product teams use it for ongoing feedback collection at service points, within apps, or during events to maintain a continuous dialogue with customers. The method's power lies in its simplicity: the open-ended format encourages honest, creative responses that go beyond what typical satisfaction scales can capture. Users naturally frame their feedback as forward-looking aspirations rather than backward-looking complaints, which makes the data inherently actionable for design teams. Because the barrier to participation is so low — completing a single sentence — the method reaches people who would never sign up for an interview or complete a lengthy survey. Teams typically deploy it over days or weeks, collecting responses continuously and clustering them into themes through affinity mapping. The resulting insights often surface unexpected improvement ideas and reveal the language users actually use to describe their needs, which directly informs messaging, feature naming, and content strategy. When combined with structured research methods, "I Wish That..." provides the emotional context that quantitative data alone cannot deliver.
Explain the purpose of the 'I Wish That...' method to participants. This method encourages creative thinking by framing problems as opportunities, helping participants openly and constructively express their desires for improvements.
Invite a diverse group of stakeholders, such as users, designers, and product owners, to participate in the session. Provide pens, sticky notes, or a digital tool for documenting ideas.
Define the specific challenge or problem that the group will be focusing on. Ensure that the problem is clear and understood by all participants.
Instruct participants to individually generate as many 'I Wish That...' statements related to the problem as they can, without considering feasibility or constraints. Encourage creativity and free-thinking.
Ask participants to share their 'I Wish That...' statements with the group. Encourage open discussion, addressing each idea without judging or dismissing them. Explore potential challenges, benefits, and implications.
Group similar ideas together, and refine statements by discussing potential improvements and adjustments. Encourage collaboration and constructive feedback.
Ask participants to individually or collectively rank the 'I Wish That...' statements based on their perceived importance, impact, and feasibility. This will help identify which ideas to focus on in further development.
For each prioritized 'I Wish That...' statement, create an action plan detailing the steps needed to turn the idea into reality. Assign specific tasks, responsible parties, and milestones, if possible.
Continually monitor and evaluate the progress of each action plan, adjusting as needed based on feedback, changes in context or priorities, and newly discovered insights.
After running the "I Wish That..." method, the team will have a substantial collection of user-generated statements that articulate unmet needs, desires, and improvement ideas in authentic user language. Through thematic analysis, these statements will reveal recurring patterns about what users most want changed or added, often surfacing needs that formal surveys and analytics miss entirely. The prioritized wishlist serves as direct input for product roadmap discussions, feature ideation sessions, and content strategy work. Teams also gain the specific vocabulary users use to describe their needs, which informs messaging, navigation labels, and marketing copy. The ongoing nature of the method builds a feedback culture where users feel heard and engaged.
Seed the collection point with at least one example card to reduce embarrassment and show what kind of responses are welcome.
Use simple, branded graphics on the cards that respect the visual identity of the company or organization.
Turn data collection into a dialogue — answer questions, comment on proposals, and explain decisions via social media or a public board.
Place cards and pens at natural pause points in the user journey where people have a moment to reflect.
Collect responses over an extended period (days or weeks) to capture diverse perspectives and seasonal patterns.
Combine physical card collection with a digital version for users who prefer typing over handwriting.
Cluster responses weekly using affinity mapping to identify emerging themes before the collection period ends.
Share back what you learned and what you acted on to encourage ongoing participation and build trust.
Gathering wishes and never responding or taking visible action erodes user trust. Close the feedback loop by sharing what you learned and what changes you made based on the input.
Adding restrictive qualifiers to the sentence stem (e.g., 'I wish the checkout page...') limits the range of responses. Keep the prompt open enough to capture unexpected needs.
Running the collection for just a few hours misses the diversity of users who visit at different times. Extend the collection period over days or weeks to capture a representative range of perspectives.
Reading wishes casually without structured thematic analysis leads to cherry-picking. Use affinity diagramming or coding frameworks to identify genuine patterns rather than just the loudest voices.
Wishes are aspirational by nature. Teams that take every wish at face value without considering feasibility and strategic fit create unrealistic expectations. Prioritize wishes against business constraints.
Collection of all gathered statements summarizing user needs and desires.
Ranked list of statements from most to least significant user needs.
Participant descriptions with demographics, preferences, and pain points.
Summary of key patterns and opportunities from collected statements.
Visual maps of participant thoughts, feelings, and experiences.
Clustered statements organized into related themes and categories.
Actionable recommendations for product enhancements based on insights.
Visual summary of process, insights, and recommendations for stakeholders.