Unit 1: Foundations of Problem Solving and Design Thinking - Subjective Questions

Design thinking is a human-centered and iterative approach to solving problems creatively and effectively. It focuses on understanding people, identifying their real needs, generating possible solutions, and testing those solutions.

Key features include:

• Human-centeredness: Solutions are based on users' experiences, needs, and expectations.
• Structured process: Common stages include empathize, define, ideate, prototype, and test.
• Iteration: Ideas are repeatedly improved through feedback and learning.
• Creativity and analysis: It combines imaginative idea generation with logical evaluation.
• Practical experimentation: Prototypes help identify weaknesses before full implementation.

Thus, design thinking provides a systematic yet flexible way to address complex and uncertain problems.

The major stages of design thinking are:

• Empathize: Understand the users, their experiences, emotions, difficulties, and context through observation, interviews, and interaction.
• Define: Organize the collected information and clearly state the core problem from the user's perspective.
• Ideate: Generate a wide range of possible solutions without judging ideas too early.
• Prototype: Create simple and inexpensive representations of selected ideas so that they can be explored.
• Test: Obtain feedback from users, identify problems, and improve the proposed solution.

These stages are not always strictly sequential. Teams may return to an earlier stage when new information or user feedback reveals a better understanding of the problem.

Design thinking is iterative because the understanding of a problem and its possible solution develops gradually through repeated learning.

• Initial assumptions may be incorrect or incomplete.
• User feedback during testing may reveal unexpected needs.
• A prototype may expose technical, practical, or emotional problems.
• New observations may require the team to redefine the original problem.
• Several ideas may need to be compared and improved before selecting an appropriate solution.

For example, a team may move from testing back to defining when users reveal that the original problem was misunderstood. This repeated movement among stages reduces risk and improves the relevance, usability, and feasibility of the final solution.

Well-defined problems have clear objectives, known constraints, and a relatively specific method or set of methods for reaching a solution.

• The starting condition is clear.
• The desired outcome is measurable.
• Constraints are usually known.
• Solutions can often be evaluated objectively.
• Example: Calculating the shortest route between two fixed locations.

Ill-defined problems have unclear goals, incomplete information, changing constraints, and multiple possible solutions.

• The problem may be interpreted differently by different stakeholders.
• The success criteria may be subjective.
• The problem and solution often evolve together.
• Example: Improving the experience of patients in a hospital.

Design thinking is particularly useful for ill-defined problems because it helps teams explore needs, clarify the challenge, and develop solutions through iteration.

Problems can be classified according to the number of factors involved, the predictability of relationships, and the degree of uncertainty.

• Simple problems: The relationship between cause and effect is clear, and a familiar procedure can usually solve the problem. Example: Replacing a damaged light bulb.
• Complicated problems: They involve many parts or technical steps, but expert analysis can generally identify a reliable solution. Example: Designing a bridge.
• Complex problems: They involve interacting human, social, economic, or environmental factors. Cause-and-effect relationships may only become clear after action, and there may be no single correct answer. Example: Reducing urban poverty.

Design thinking is valuable for complex problems because it supports empathy, experimentation, collaboration, and adaptation.

Problem framing is the process of deciding how a problem should be understood, described, and approached. It identifies the relevant users, needs, context, constraints, and desired outcomes.

Its importance includes:

• Providing direction: It focuses the team on a meaningful challenge.
• Preventing premature solutions: It encourages understanding the problem before choosing an answer.
• Revealing assumptions: It makes hidden beliefs and limitations visible.
• Encouraging multiple perspectives: Different stakeholders may frame the same situation differently.
• Supporting innovation: A broader or more constructive frame can reveal new solution possibilities.

A weak frame may lead to solving the wrong problem, while a well-developed frame creates a useful foundation for research and ideation.

An effective problem statement should clearly express the challenge without prescribing a particular solution.

Important characteristics include:

• User-focused: It identifies the people affected by the problem.
• Need-oriented: It explains what users need rather than naming a product or technology.
• Specific: It provides enough context to guide investigation.
• Open-ended: It allows multiple possible solutions.
• Actionable: It is realistic for the team to investigate and influence.
• Evidence-based: It reflects observations and research rather than unsupported assumptions.

For example, instead of stating "We need a mobile application," a better statement is: "First-year students need a simple way to find reliable campus services because they often feel confused during their first weeks."

A solution-focused approach begins with a proposed answer or technology and attempts to fit it to a situation. A problem-focused approach begins by understanding the users, context, causes, and desired outcomes before considering solutions.

Design thinking generally favors a problem-focused approach because it delays commitment to one solution until the challenge is better understood.

Empathy is the ability to understand and appreciate the experiences, emotions, motivations, and difficulties of other people. In design thinking, it helps teams move beyond assumptions and view a problem from the user's perspective.

Empathy supports problem solving by:

• Revealing explicit and hidden needs.
• Showing how users behave in real contexts.
• Identifying emotional and social factors.
• Exposing difficulties that users may not state directly.
• Building respect and trust between designers and stakeholders.
• Preventing solutions from being based only on the team's preferences.

Methods such as interviews, observation, journey mapping, and contextual inquiry help develop empathy. The goal is not merely to feel sympathy but to gain useful, evidence-based understanding for designing a better solution.

Observation and interviews are complementary methods for collecting information about users.

Observation involves watching users perform activities in their natural environment. It helps reveal:

• Actual behavior rather than reported behavior.
• Workarounds and repeated difficulties.
• Environmental and social influences.
• Unspoken needs and frustrations.

Interviews involve asking users open-ended questions about their experiences, goals, feelings, and challenges. They help reveal:

• Personal motivations and expectations.
• Perceptions of existing services or products.
• Important events and pain points.
• Suggestions and desired improvements.

Researchers should avoid leading questions, listen actively, record evidence accurately, and compare what users say with what they actually do. Combining both methods produces a more complete understanding.

User needs are the functional, emotional, social, or practical requirements that help users achieve their goals. Pain points are the obstacles, frustrations, risks, delays, or negative experiences users encounter.

They influence problem definition by:

• Identifying what users are trying to accomplish.
• Showing where existing processes fail.
• Distinguishing important problems from minor complaints.
• Revealing opportunities for improvement.
• Helping teams state the problem in terms of outcomes rather than features.

For example, a commuter's need may be to reach work reliably, while a pain point may be uncertainty about delays. A useful problem statement would focus on improving reliable travel information rather than immediately proposing a specific application.

Reframing means examining a problem from a different perspective and expressing it in a new way.

A possible reframing process is:

• Collect evidence from users and stakeholders.
• Identify assumptions in the original problem statement.
• Ask who is affected and what outcome is truly desired.
• Separate underlying needs from visible symptoms.
• Generate alternative interpretations of the challenge.
• Select a frame that is meaningful, open-ended, and actionable.

For example, the question "How can we make customers wait less?" may be reframed as "How can we make the waiting experience more useful and comfortable?" The second frame allows solutions involving communication, entertainment, scheduling, comfort, or service redesign rather than only reducing time.

A symptom is an observable sign that a problem exists, while a root cause is an underlying factor that produces or sustains the problem.

For example, repeated customer complaints may be a symptom. The root cause could be unclear instructions, poor staff training, or a flawed process.

Identifying root causes is important because:

• Treating symptoms may provide only temporary relief.
• Root-cause analysis prevents the problem from recurring.
• It helps resources address the most influential factors.
• It improves the quality and long-term impact of solutions.
• It prevents teams from selecting solutions based on assumptions.

Tools such as the five whys, cause-and-effect diagrams, process mapping, and stakeholder interviews can help uncover deeper causes.

Stakeholders are people or groups who affect, experience, support, regulate, or are affected by the problem and its solution. Complex problems usually involve different stakeholders with different goals and constraints.

Considering multiple stakeholders is important because:

• One group's improvement may create difficulties for another.
• Stakeholders possess different forms of knowledge and experience.
• It reveals conflicts, dependencies, and hidden constraints.
• It improves acceptance and implementation of the final solution.
• It supports fairness and reduces the risk of excluding vulnerable groups.

A stakeholder map can identify primary users, secondary users, service providers, decision-makers, regulators, and affected communities. Effective problem framing balances these perspectives while keeping the needs of the most affected users visible.

Constraints are limitations such as time, budget, technology, laws, resources, safety requirements, or user abilities.

They can limit creativity when:

• They prevent exploration of potentially useful alternatives.
• They reduce available resources for research or prototyping.
• They create rigid rules that discourage experimentation.

However, constraints can also stimulate creativity by:

• Focusing attention on the most important needs.
• Encouraging simpler and more efficient solutions.
• Promoting the creative use of available resources.
• Making the problem more specific and actionable.
• Encouraging teams to challenge conventional assumptions.

Good design thinking does not ignore constraints. It makes them explicit, distinguishes fixed constraints from flexible ones, and uses them to guide realistic innovation.

The six questions provide a structured method for understanding a problem from multiple angles:

• Who: Identifies users, stakeholders, affected groups, and decision-makers.
• What: Defines the observed difficulty, unmet need, or desired outcome.
• Where: Examines the physical, digital, organizational, or social context.
• When: Identifies the timing, frequency, sequence, and conditions under which the problem occurs.
• Why: Explores motivations, causes, consequences, and the importance of solving the problem.
• How: Examines how the problem currently occurs and how improvement might be measured.

This sequence helps teams avoid vague statements and collect information systematically. It also highlights missing evidence and supports the creation of a clear problem frame.

Separating these types of information improves the reliability of problem solving.

• Facts: Information that can be verified, such as attendance records or documented response times.
• Observations: Directly noticed behavior or events, such as a user abandoning a form.
• Interpretations: Meanings or explanations assigned to facts and observations.
• Assumptions: Beliefs accepted without sufficient evidence.

If these categories are mixed together, teams may treat guesses as facts and define the wrong problem. For example, observing that users stop completing a form is different from assuming that they are uninterested. The observation should lead to further investigation through questions, interviews, or testing. This distinction promotes critical thinking and reduces bias.

Common barriers include:

• Personal bias: Designers may interpret needs according to their own experiences.
• Confirmation bias: Teams may seek only evidence supporting an existing idea.
• Limited user access: Important users may be difficult to reach.
• Time and budget pressure: Teams may skip research and testing.
• Overreliance on stated preferences: What users say may differ from what they do.
• Excluding minority or vulnerable groups: Solutions may work only for the majority.
• Premature fixation: Teams may commit to a solution too early.

Ways to overcome these barriers include using diverse research participants, asking open-ended questions, comparing multiple data sources, documenting assumptions, involving users throughout the process, conducting inclusive research, and testing prototypes early. Reflection and team critique can also expose hidden bias.

Design thinking and traditional analytical problem solving both seek effective solutions, but they differ in emphasis and method.

The approaches can complement each other. Design thinking helps identify the right problem and desirable solution, while analytical methods help assess feasibility, performance, and risk.

Divergent thinking expands the range of possibilities. It is used to explore different interpretations of a problem, generate ideas, and identify alternative approaches. Judgment is temporarily postponed so that unusual and varied ideas can emerge.

Convergent thinking narrows possibilities by evaluating and selecting options according to criteria such as desirability, feasibility, viability, safety, and sustainability.

A design thinking process alternates between the two:

• Diverge while exploring user experiences.
• Converge while defining the core problem.
• Diverge during ideation.
• Converge when selecting ideas for prototyping.
• Diverge again when testing reveals new possibilities.

Using both modes prevents premature judgment while ensuring that creativity leads to practical action.