User experience design is a subset of the field of experience design which pertains to the creation of the architecture and interaction models which impact a user's perception of a device or system. The scope of the field is directed at affecting 'all aspects of the user’s interaction with the product: how it is perceived, learned, and used.'
Because user experience has become so important to organizations’ success in the marketplace and, thus, their revenue, it is now part of their overall business strategy. Organizations should plan how to manage and measure user experience. Therefore, most organizations have some system for managing their strategy and measuring their progress toward achieving their goals. One popular system for managing and measuring strategy is Balanced Scorecard.
Creating usable systems that people intuitively understand is not just a technical issue. It is about understanding how people engage with each other, and how we can support this through clear, simple, comprehensible interface design.
Is it more important for your web site to be desirable or accessible? How about usable or credible? The truth is, it depends on your unique balance of context, content and users, and the required tradeoffs are better made explicitly than unconsciously.
User experience design is a subset of the field of experience design which pertains to the creation of the architecture and interaction models which impact a user's perception of a device or system. The scope of the field is directed at affecting "all aspects of the user’s interaction with the product: how it is perceived, learned, and used." User experience design, most often abbreviated UX, but sometimes UE, is a term used to describe the overarching experience a person has as a result of their interactions with a particular product or service, its delivery, and related artifacts, according to their design.
Over the last few months, as 2010 started winding down, we had the good fortune to travel around Asia to places that included Nanjing and Guangzhou, in China; Singapore, for UX Singapore; and Taipei, Taiwan. We ran workshops, gave presentations, met with members of the local UX communities, and of course, enjoyed the good Asian food that usually gets wrapped around our travel experiences in Asia. Our experiences have given us a deeper understanding of the state of UX design in Asia. Now that we’re back in Hong Kong—to refresh before our travels start again in 2011—we’ve taken the time to reflect on the people we’ve met and the conversations we’ve had over the last few months.
Easy task completion (traditional usability) is not enough in the Web world. Appealing visual site design is not enough. A site visitor needs to not only be attracted to a site and able to figure out how to buy (or register, sign up, etc.)-they need in addition to be able to tell quickly that a site will meet their needs, and they need to want to buy from this site, as opposed to a competitor's site. This is a key aspect of overall Web site success.
Using a self-designation with a certain amount of specificity sacrifices practicality to accuracy. Individuals who have been hired as a single-function specialist may have the luxury of presenting as a “usability engineer” or “information architect”. For the independent consultant, this strategy can have definite negative consequences.
When a company wants to make a certain segment of the organization better, usually they 'throw more money at it' and hire more employees. The problem with doing this for a UX team is that people with overlapping skills and ideas usually end up hindering user-centered design rather than helping. Conflicting design decisions will soon turn into a design by committee situation that won't help the consumer nor expose individual expertise (Brown 2004). User experience groups need to be flexible, agile, and scalable, and should only expand if the projects they work on are sufficiently large. The following is an overview of skills and disciplines needed for a successful user experience group.
User Experience (UX) design is traditionally seen as the domain of user interface (UI) design, but within a software development team it should mean so much more! UX should permeate through the whole development team. It should influence the way middle tier developers' craft their components and the way database administrators create their tables, stored procedures and views.
Brazil was the site of the seventh International Conference of Ergonomics and Usability, Interface Design, and Human Computer Interaction. Held in the seaside city of Balneario Camboriu in the southern Brazil state of Santa Caterina, the conference was hosted by the Universidade do Valle do Itajai (UNIVALI). I was fortunate to be invited to participate in the conference.
The usability and user experience communities of practice are experiencing great growth and have emerged in countries throughout the world. These developing practices have brought about a huge economic boom in the UX market as both customers and clients are beginning to understand the business benefits they bring. In India, we have undoubtedly seen the growth of these practices. Indian UX companies are delivering designs that satisfy users' needs to their clients.
Presents a strategic roadmap for user experience design. Combining usability with the science of persuasion, learn how you can: impact online decision-making and user motivation; create a dashboard-based framework to measure and track user experience; integrate your customer channels and internal-facing systems; and help executives appreciate and understand the value of user-centered thinking and design.
Over the past twenty years, the field of user experience has been fortunate. Software and hardware product organizations increasingly have adopted user-centered design methods such as contextual user research, usability testing, and iterative interaction design. In large part, this has occurred because the market has demanded it. More than ever, good interaction design and high usability are part of the price of entry to markets.
I can’t tell you how many frustratingly unusable enterprise Web applications I’ve encountered during my 12 plus years in corporate America. As important as the user experience of enterprise software is to a business’s success, why isn’t its assessment usually a factor in technology selection?
User interface mockups are an important tool in software engineering. During the requirements phase they serve as prototypes that elicit feedback from stakeholders and end users, and they’re an integral part of any functional specification.
Of all the user research methods that have emerged over last few decades, why did some catch on and become renowned, while others are still waiting for their big break or have declined from their previous glory to has-been status? By comparing the user research methods that never really caught on to those that have become popular, we can determine what it is that makes user research techniques valuable to UX professionals.
A collaborative approach enables clients to actively participate in the process, increasing the likelihood of achieving a collective vision for the project. This article focuses on the first step in the journey towards collaboratively developing a User Experience Strategy and is concerned specifically with how user stories are generated, themed and prioritized.
A complicating factor in UX analysis and design is that people starting with the same goal can often pursue different strategies in achieving that goal. I once experienced this complication when conducting generative user research prior to designing a user interface. Once I had collected data from one group of participants, I decided to collect additional data from a second group to extend and validate the initial data. To my consternation, the data from the second group was strikingly different. Far from providing guidance for designing the user interface, this additional data left me feeling like a person with two clocks that tell different times. Further analysis revealed that, through some fluke, people in the first group tended to work in one type of situation, while those in the second group tended to work in another type of situation. This research led to the insight that our user population uses two different strategies depending on their work situation. This example represents just one of the many times when I’ve had to account for multiple user strategies in a UX project.
This article is based on the research and feedback I received from a number of user experience designers, usability specialists, product developers and writers, which led me to engage in a dialogue with the users.
User experience professionals can also learn some lessons from and find potential recruits in technical communicators as they have skills that can be applied directly to the design process.
To better manage interactions with such large datasets, we’ve incorporated the concept of views, in the same way that Microsoft Outlook and SQL Builder use them. However, my initial usability testing has found that the concept of views is escaping most people, and I think it often boils down to the term itself. Even if I show users what the software does—and they pretty much always like it when they see it—they still often cannot get over the initial hurdle of the naming convention.