Which five-step process best describes standard problem-solving methodology?

Which five-step process best describes standard problem-solving methodology?

• A. Brainstorm, select, implement, monitor, terminate.
• B. Define the problem, generate alternatives, evaluate options, implement a solution, review results.
• C. Define the problem, implement a solution, evaluate results, generate alternatives, review.
• D. Gather data, ignore it, act, reflect.

Answer: (B)

Defining the problem clearly, generating multiple possible solutions, evaluating those options with criteria, implementing the chosen solution, and then reviewing the results is a structured way to solve problems. Starting with a precise problem definition ensures you’re addressing the real issue and not chasing symptoms. Generating alternatives keeps you from settling on the first idea and increases the chance of finding a feasible, effective fix. Evaluating options using objective criteria—such as feasibility, cost, impact—lets you compare choices thoughtfully rather than guessing. Implementing the selected solution puts the plan into action, and reviewing the results checks whether it worked, reveals any unintended effects, and signals whether adjustments are needed. This sequence is widely taught because it keeps the process clear and helps you learn from what happens after implementation. Why the other sequences don’t fit: one approach starts with brainstorming and ends with termination, skipping problem definition and evaluation, which leaves you unclear about what you’re solving or how success is measured. Another sequence moves to implementation before generating and evaluating options, meaning you act without exploring better choices. The last option suggests gathering data and then ignoring it, which defeats the purpose of using information to guide decisions.

Defining the problem clearly, generating multiple possible solutions, evaluating those options with criteria, implementing the chosen solution, and then reviewing the results is a structured way to solve problems. Starting with a precise problem definition ensures you’re addressing the real issue and not chasing symptoms. Generating alternatives keeps you from settling on the first idea and increases the chance of finding a feasible, effective fix. Evaluating options using objective criteria—such as feasibility, cost, impact—lets you compare choices thoughtfully rather than guessing. Implementing the selected solution puts the plan into action, and reviewing the results checks whether it worked, reveals any unintended effects, and signals whether adjustments are needed. This sequence is widely taught because it keeps the process clear and helps you learn from what happens after implementation.

Why the other sequences don’t fit: one approach starts with brainstorming and ends with termination, skipping problem definition and evaluation, which leaves you unclear about what you’re solving or how success is measured. Another sequence moves to implementation before generating and evaluating options, meaning you act without exploring better choices. The last option suggests gathering data and then ignoring it, which defeats the purpose of using information to guide decisions.