Solutions, not Options
As a UX Designer, are you providing solutions or options?
The outcome of any problem solving exercise should ideally be a set of potential solution paths. That's the primary takeaway of any activity.
However, it's a common practice for designers to just change layouts, colours, fonts and copy to create so-called variants or options and call them different solutions for a problem. This is not a sensible approach by any means.
Options are just variants of a solution family, lacking any individual and inherent merit.
Think and work on strategic solutions, not random options.
As UX designers, we should present a range of solutions and not just options to clients or users. For example, testing is really not just about collecting data or feedback on those different button colours or copy. If they are different, you would obviously lead the participant to share a different response, however the response may not work as you're testing the taste for an option and not a solution.
Here is my hypothesis. If you present four options to someone, obviously there is a propensity to pick one, considering they don't have a choice to decline in a given scenario. Picking one makes other options insignificant and makes the mostly picked one the popular pattern, however it does not mean its the correct one.
The same logic applies to solutions as well.
However, it's not that easy to pick one based on taste alone and the evaluation process demands deeper processing and practical thinking by both participants and the tester. We moved from petty comparison to deeper evaluation in this context.
As designers, exploring diverse possibilities gives us the opportunity to draw insights from popular and diverse patterns. Once we identify merit in a potential route, we could expand further and test variants of the same.
Think solutions!
As UX designers, we should present a range of solutions and not just options to clients or users. For example, testing is really not just about collecting data or feedback on those different button colours or copy. If they are different, you would obviously lead the participant to share a different response, however the response may not work as you're testing the taste for an option and not a solution.
Here is my hypothesis. If you present four options to someone, obviously there is a propensity to pick one, considering they don't have a choice to decline in a given scenario. Picking one makes other options insignificant and makes the mostly picked one the popular pattern, however it does not mean its the correct one.
The same logic applies to solutions as well.
However, it's not that easy to pick one based on taste alone and the evaluation process demands deeper processing and practical thinking by both participants and the tester. We moved from petty comparison to deeper evaluation in this context.
As designers, exploring diverse possibilities gives us the opportunity to draw insights from popular and diverse patterns. Once we identify merit in a potential route, we could expand further and test variants of the same.
Think solutions!
