The tension between rapid iteration and deep problem framing

Some designers argue that the most effective way to solve complex problems is to treat framing and solving as the same cognitive process (A Failure To Disagree). By building precise mental models of a problem, the solutions often reveal themselves as obvious, transforming a vague challenge into a simple question of execution (A Failure To Disagree). This approach prioritizes understanding the underlying structure of a situation before any design work begins, as research into solution fixation warns that people often diagnose a problem only briefly before lingering on the fix (Edtech Partnerships).

Others prioritize rapid prototyping to stay close to the problem, treating failure as essential data rather than a sign of poor framing. Felix Brooks-church, for example, developed his technology by working directly in small workshops, building prototypes, and testing them in real-world environments to ensure they functioned before scaling. This perspective suggests that the most useful insights emerge from the friction of building, rather than abstract reflection on the problem space (Edtech Partnerships).

These positions pull in different directions regarding whether design should prioritize the speed of implementation or the depth of inquiry. While one side warns that jumping to solutions leads to unintended consequences, the other maintains that staying in the problem space without building can lead to paralysis. Both agree that the core risk is settling on an answer before the context has been fully examined.

• Henrik Karlsson suggests that writing down every possible alternative, including impossible ones, helps break defaults and prevents settling for the first idea (Escaping Flatland).
• Janine Rosado notes that designers gain influence by translating user-centric usability issues into business-centric metrics like abandonment rates and revenue impact (UX Jobs).