Defining Problem Statement

Collaborate reflect on the simulation discover where the persona encounters the problem, document events that precede, and proceed the customers frustration.

Defining Problem Statement

Step 1. Let's explore the users' timeline, document events preceding the problem, the frustrations related to the problem, and how or where they might seek a solution.

Step 2. Let's develop our problem statement. Define the problem; what group of people suffer from the problem? How is the problem being addressed, and why does the problem persist?

Defining Problem Statement

Reflect on the empathizing persona, discover where the persona encounters the problem, document events that precede, and proceed the persona's frustration. Then define the problem.

Group Size: 4-5

Materials Needed: Print Defining Problem Statement, Pens, Markers and Post-its

Duration: 30-120 mins

Defining Problem Statement

A defining problem statement summarizes how the user/customer suffers from the problem, deeply analyzing their frustration, how they cope with the problem, how market forces have addressed it, and why it persists.

  • Drafting a Problem Statement

    Understanding when the user encounters the problem.

    Develop insights into the problem and possible solutions.

    Understand how the user copes with the problem.

  • Work together in 4-6 member teams to document the where the problem is encountered in the user timeline. Then use the prompt to craft a problem statement.

  • Step 1. Let's explore the users' timeline, document events preceding the problem, the frustrations related to the problem, and how or where they might seek a solution.

    Step 2. Let's develop our problem statement. Define the problem; what group of people suffer from the problem? How is the problem being addressed, and why does the problem persist?

  • Our goal here is to pinpoint where the user experiences the problem in the timeline.

    Document the user's frustration in dealing with the problem.

    Detail where they might go to find a solution to the problem.

    Define the problem. How big is the problem? By defining how big the problem is, we also define the opportunity to solve it.

    Define the problem within the user story; your problem statement should be familiar and compelling.

    Document ways the customer copes with the problem.

    Document quantifiable information, like how long it takes the customer to complete a task.

Validation for Defining Phase

Interviews can be a valuable method for validating the need in design thinking. Here are some approaches to effectively validate the need through interviews:

Interviews can be a valuable method for validating the need in design thinking. Here are some approaches to effectively validate the need through interviews:

Define the Interview Objective: Clearly articulate the purpose of the interview and the specific need you are seeking to validate. This helps you structure the interview questions and focus the conversation.

Select Interview Participants: Identify individuals who represent your target audience or end-users. Ensure a diverse sample that includes different perspectives and potential user segments. Seek out individuals who have experienced the need firsthand.

Prepare Interview Questions: Develop a set of open-ended questions that encourage participants to share their experiences, challenges, and needs related to the problem you are addressing. Start with broad questions to establish rapport and gradually delve into more specific aspects.

Active Listening: During the interview, actively listen to the participant's responses. Allow them to express their thoughts fully and avoid interrupting or leading the conversation. Pay attention to their tone, emotions, and non-verbal cues to gain deeper insights.

Probe for Details: Ask follow-up questions to explore participants' responses in more depth. Encourage them to provide specific examples or anecdotes that illustrate their needs and pain points. Probing helps uncover hidden insights and ensures a comprehensive understanding.

Avoid Leading Questions: Frame your questions neutrally and avoid leading participants toward a particular answer. This ensures that their responses are genuine and not influenced by your preconceived notions.

Seek Specifics: Encourage participants to provide specific details about their needs, preferences, and challenges. Ask for examples of situations where the need arises and how it impacts their lives. Specifics help you validate the need more effectively.

Validate and Clarify: Summarize and repeat the participants' responses to ensure accurate understanding. Seek clarification if needed to avoid misinterpretation. This validates that you are correctly capturing their needs.

Look for Consistent Patterns: Analyze the interview data collectively to identify consistent patterns and recurring themes across participants. This helps validate whether the need is widespread and shared by a significant portion of your target audience.

Triangulation: Combine interview data with insights from other research methods, such as observations, surveys, or data analysis. Triangulating multiple data sources provides a more comprehensive and robust validation of the need.

Iterate and Refine: Use the insights gathered from interviews to iterate and refine your understanding of the need. Continuously validate and update your findings as you progress through the design thinking process.

Validating the Market

Validating the market in design thinking involves assessing the viability and demand for your product or solution within the target market. Here are some approaches to validate the market during the design thinking process:

Market Research: Conduct thorough market research to gather information about the industry, market trends, target audience, and competitors. Analyze industry reports, market studies, and available data to gain insights into the size, growth potential, and dynamics of the market.

Customer Surveys: Develop surveys to collect feedback directly from your target audience. Ask questions about their needs, preferences, and willingness to adopt new solutions. Survey responses can provide quantitative data to validate market demand and identify potential customer segments.

Competitor Analysis: Analyze your competitors to understand their offerings, market positioning, pricing strategies, and customer base. Assess their strengths and weaknesses, and identify any gaps or unmet needs in the market that your solution can address.

Proof of Concept: Develop a minimal viable product (MVP) or a proof of concept to demonstrate your solution's core features and value proposition. Test it with a select group of potential customers or stakeholders to gather feedback and assess their interest in adopting the product.

Pilot Programs or Trials: Conduct small-scale pilot programs or trials to test your solution in a real market setting. Gather feedback and data from these trials to evaluate user acceptance, measure customer satisfaction, and validate market demand.

Pre-sales or Crowdfunding: Offer pre-sales or crowdfunding campaigns to gauge market interest and validate demand. If customers are willing to pre-order or invest in your product or solution, it indicates a level of market validation.

Key Opinion Leaders: Engage with industry experts, influencers, or thought leaders who have influence and credibility within your target market. Seek their opinions and validate your solution's potential in the market based on their insights.

Partnerships and Alliances: Explore opportunities for partnerships or alliances with established organizations in the industry. Their willingness to collaborate or support your solution can serve as an indicator of market validation.

Early Adopters and Beta Testers: Identify and engage with early adopters who are enthusiastic about trying new solutions. Allow them to test your product or solution in exchange for feedback. Their positive reception and adoption can validate market demand.

Sales and Revenue Generation: Track sales and revenue generation once your solution is launched in the market. Consistent sales and revenue growth over time indicate market validation and customer acceptance.

It's important to approach market validation iteratively and adapt your solution based on the feedback and insights gained. Regularly revisit and refine your market validation strategies throughout the design thinking process to ensure that your solution aligns with market needs and preferences.