Problem Solving vs. Solution Finding
Open more possibilities with a change in words
In product design and development, we talk a lot about "problem solving," but I recently wondered about the worldview encapsulated in this term — and whether things might be better if we talked more about "solution finding" instead.1
Designers and developers often describe the detailed work of conceiving and building products and services as "problem solving." I've certainly used the term more times than I can count! Upon reflection, though, the term seems more aligned with science-based disciplines such as engineering.
Problem-solving explicitly centers our focus on some issue(s) that need to be eradicated. It says, here is a conundrum we need to break down into its constituent parts, which we can solve like a math problem. In applied science fields such as engineering, there is always some technical problem that needs solving. How do we span a reliable steel bridge across the river? How do we create a secure service that stores personal health data? How we prevent memory leakages in our web app?
Solution Finding is about Possibilities
What happens if we shift our language away from this structured, scientific viewpoint? What if we don't center our minds on the problem, but rather the goal?
When we are "solution finding," we're exploring the world around us in various ways, engaged in a creative process of building something that provides value. A solution can be any one of the ways we might address an opportunity (and yes, often we are solving a problem of some sort too, it’s almost inescapable). Usually, however, there isn't some singular answer waiting to be determined in the way that an engineer building a bridge must handle steel's coefficient of linear expansion, or a software developer has to define the exact path for saving a health record in the properly configured database.
When finding solutions, we're consciously enabling ourselves to play with what's possible. Although "problem solving" pleasantly evokes puzzles, it continues to imply there's a defined, correct answer. Instead, typically there are many possible answers for any given opportunity. When we are solution finding, we will identify and evaluate a variety of solutions. We'll determine their fitness for the matter at hand based on our values, judgment, and other tangible and intangible measures. One solution may be a good option in a world with expansive amounts of time; another solution may be better when time is limited. One solution could offer a potential alternative benefit; another may present a lower risk.
A solution is something that adds value, above all else. And creating solutions can be many-layered, even at the “superficial” yet meaningful level of adornment. For example, devising a new protocol to help a patient know when to schedule their next medical exam is a solution — and so is the way that scheduling prompt gets presented as a timely software interaction to the patient — and so is the polished visual language that is applied to this interaction.
Possibility Starts with a Word
There's an artful awareness involved in the act of finding: the search for something having its desired result. When we begin to search for solutions, even our initial utterance helps us move towards places where we’re generating ideas good enough to pursue building. (This is also why the “how might we…?” formulation is so incredibly powerful: it creates an opening for possibilities!) Finding solutions happens through our idea-filled conversations, then moves on to sifting through various possibilities and evaluating solution candidates at increasingly higher levels of fidelity.
A solution-finding mindset is the province of the Possibilitarian. The art of the possible involves "finding solutions" more than it does "solving problems." Try this linguistic shift on for size yourself the next time you're engaged in building something great!
Lizz at Devise is a publication exploring the space of design and product management through the lens of heart-centered values and teamwork. Thanks for reading along! Lizz leads Devise Consulting, where we do cool stuff involving Product Management, UX Design, Strategy, Customer Research, Team Development, and Product Operations. Our availability is going fast at the moment, so schedule time now if you would like to find solutions together: chat with Lizz.
Although you may come at me with your "it's just semantics" finger-wagging, I have always found great value in using language clearly and investigating our working nomenclature to reveal any hidden or implicit meanings. Take a moment to explore with me: how might the words we use affect our perspectives and outcomes?
Insightful! Thanks lizz ❤️