In many respects, we have reduced the ambiguity in our world. We can now sample an entire music album before deciding to purchase it, use a smartphone app to learn what’s happening at home while we’re on vacation, or click a button to discover who has viewed our LinkedIn profile. However, while we might enjoy the occasional mystery/thriller novel or movie, in which the story’s outcome remains uncertain as we’re propelled through suspenseful twists and turns, we are becoming much less tolerant of mystery in our daily lives. We like to disambiguate the circumstances of our lives. We like to know things. This gives us comfort and favors predictability, which in turn reduces our anxiety and stress. Resolving uncertainty is actually something for which people are willing to pay.
But ambiguity is still alive and well in the work we do as UX designers. Those of us who design enterprise software should be very familiar with ambiguity. We encounter it often, whether in vague feature requirements, unfamiliar capabilities that derive from the acquisition of a new product or company, or the complex workflows that are characteristic of the highly specialized domains in which we work. Read More
Powered by WPeMatico