Designing the Problem
In engineering, we often solve problems by breaking them down. Decomposition gives us clarity, focus, and manageable subproblems we can assign to teams, tools, or even entire disciplines. But decomposition comes with a cost: when functional requirements are tightly coupled, splitting a problem into independent parts can make some solutions (often the best ones) unreachable. The structure of the problem becomes the structure of the solution space. And that structure, more often than not, reflects historical accident more than deliberate design. This post explores how decomposition shapes design, using principles from axiomatic design and systems engineering. We’ll see how the act of breaking a problem into parts can inadvertently encode coupling that no amount of downstream optimization can fix; and how reframing the problem, and embedding expertise more interactively, can unlock better solutions. Axioms Picture using a water faucet. There are two things you want to control: the ...