Understand the Problem Before Solutions

#133 - Software Requirements Essentials - Karl Wiegers

Topic 4 of 12

Published May 15, 2023 · Clip 22:07–26:19 (4:13)

Karl explains practice one: when handed a problem or a solution, think backward. Use root cause analysis (fishbone/Ishikawa diagrams) to find contributing causes, and when given a solution, ask what problem it's meant to solve — not to challenge, but to reach a shared understanding. He warns about achieving project success (on time, on budget) while suffering product failure because the solution doesn't actually solve the right problem.