Wednesday Jan 08, 2014

Designing the Language Experience of the User Interface

When you think about any user interface (UI) guideline and you hear “language of the user,” what do you think?

  • I should be able to understand the words I see on the UI.
  • The words I see on the UI should be meaningful to the work that I do.
  • The words I see on the UI should be translatable and localizable.

The usability of business applications has evolved, and business applications have become more consumer-focused. The average user’s understanding of business applications has evolved as well. Technology and know-how now allow us to build contextual user experiences into applications and to design language experiences for the UI—with style, tone, terms, words, and phrases—that resonate with real users and their real, every day work experiences in the real world, across the globe.

For example, on the Oracle Human Capital Management Cloud My Details page, notice how the sections are organized, how they use real-world terms in headings and field labels, and how they use real content, such as personal and biographical details instead of placeholder text, which cannot be evaluated for its meaning or translation or localization needs.

Oracle Human Capital Management Cloud My Details page

Choosing which terms, words, and phrases to include on the UI is as important as choosing the right terms to use in code. In code and on the UI, the terms and words should be accurate in context and enable the successful completion of a task in context, whether the context is the processing of an event in the code or the user adding information to a contact record on a form in the UI.

37signals book, Getting Real, dedicates a short essay, Copywriting is Interface Design, to the importance of copywriting in UI design and how important every single word choice on is for the UI.

There are also numerous resources that support that choosing terms, words, and phrases for the UI that accurately represent real-world concepts in their source language often enables the translation and localization experiences. For examples, see Ultan Ó Broin’s Blogos entry Working Out Context in the Enterprise: Localize That! and Verónica González de la Rosa and Antoine Lefeuvre’s slideshare ‘Translation is UX’ Manifesto.

So how do we design a rich, context-aware UI language experience for today’s user?

  • We use accurate terms to represent concepts that are well-established in the real world by real users. These are the terms that users use frequently, terms such as team or shopping cart.
  • We use terms consistently to represent the same concepts across applications. We wouldn’t use location in one place and party site in another to represent the same concept, or save and submit to represent the same concept.
  • When we need to use these terms in context of phrases on the UI, we do so with a style and tone that resonates with users and yet is still translatable and localizable. This means that we don’t introduce nonsensical words or instant messaging-speak. We offer phrasing that is simple and clear: Add a new customer record.
  • We stop surfacing the language of the application on the UI, for example, code-specific terms. When we use a term like worker in the code as an abstraction or a superclass to represent the concept that a person can assume the role of “employee” or “contractor” in the system, this use makes sense in context of where and how it is used in code. When we surface the term worker on the UI to represent either or both roles, we introduce a context-independent use of this concept and one that when tested, we learn is not necessarily translatable or localizable in such a context.

Jakob Nielsen in his 1995 article 10 Usability Heuristics for User Interface Design identified a need for this practice of using language choices that resonate with real users: “The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.”

A simplified UI is simple to build, simple to extend, and simple to use. Use and context awareness require us to build applications that focus equally on code, visual design, and language (UI) design. Every page that we surface to the user should make sense to the user in context of his work and the real world. The practice of designing the language that is used on the UI offers us an extraordinary opportunity to evolve how we communicate with users to enable their work everywhere.

Wednesday Jul 31, 2013

User Interface | Design Considerations

When it comes to creating superior applications, the central design considerations remain the same, no matter whether you’re building interfaces for desktop or mobile workers. Karen Scipi explores user interface (UI) design for enterprise applications, an area even more prescient as cloud-based applications offer opportunities for optimized UIs of different types using the same data. 

You must understand who your workers are, what work they do, and the functionality that will most enable them and their productivity in their specific work environments.  

  • A desktop user interface refers to an interface that’s optimized for tasks that are performed over extended periods of time, usually in an office.  
  • A simplified user interface refers to an interface that’s optimized quick access, high-volume, self-service tasks that can be completed on any device and from any location.

For example, the task flow for an accounts payable clerk who typically works in an office would differ from the sales manager who travels and works mostly on his mobile device. Which user interface design would work best in each of these scenarios? The answer depends on several heuristics and data points.

When considering which user interface to design, think about multiple aspects of the workers, their roles, and their tasks. 

Workers

Consider how workers’ experiences can vary. Keep in mind that the one-size-fits-all analogy doesn’t work when it comes to designing a user interface. 
Even those who use desktop interface functionality for the majority of their tasks can benefit from simplified user interface flows. But getting a sense of who your workers are and how they are working most of the time will help you better understand what Oracle Fusion Applications functionality they will most benefit from and which user interface might better enable their work and productivity. 

When you think about workers’ experiences, ask yourself questions like these:

  • Where in the world do these workers work? 
  • What do workers’ work environments look like? For example, do they work primarily in an office, on a train, or in a warehouse?
  • With whom do the workers engage, and how to they engage with others? For example, do they use collaboration tools or social media?

For example:

 Worker Role  Typical Work Environment
 Order Processor  Office
 Sales Representative  On the go

Tasks

Identify tasks that are central to workers’ roles. But what constitutes a central task? Central tasks are typically the 10% of tasks that 90% of the workers spend 90% of their time performing.

When you think about worker tasks, ask yourself questions like these:

  • What specific tasks do workers’ perform? 
  • Are the tasks self-service tasks for all workers?
  • Which tasks are central to workers’ roles?
  • How do workers perform these tasks? 
  • How frequently are these tasks performed?
  • Do the tasks require short or long periods of time to complete?
  • Do the tasks require significant or minimal data entry activities?
  • Where do workers work? On a bus, a train, in a warehouse?
  • Based on workers’ roles, work environments, and tasks, which applications, devices, and tools best support their work? 

For example:

Worker Role  Typical Work Environment  Typical Work Tasks Example Applications, Devices, and Tools
 Order Processor  Office Data entry

  • Order management and email applications
  • Computer with keyboard
  • Phone

 Sales Representative  On the go Engages with existing and prospective customers to maintain and establish relationships and to sell products and services

  • CRM and email applications
  • Mobile and tablet devices
  • Phone, collaboration, social media tools

Information and information design

When you think about information and design considerations for different types of information, ask yourself questions like these:

  • What types of information, such as customer or vendor records, accounting data, trends, issues, news, ratings, and so on do workers need access to? 
  • How would information best be displayed to enable the interpretation of it? In a workbook, in a form, in a list, in an analytic? 
  • What key information does the worker need in a specific task flow?
  • Can the information be simplified by reducing data and features, or by eliminating corner cases that are displayed in the user interface?

For example:

 Worker Role  Typical Work Environment Examples of Information and Information Display Types
 Order Processor  Office

  • Existing and new customer order records
  • Forms, lists, workbooks

 Sales Representative  On the go

  • Existing and new customer records, including customer contact, ratings, and qualification information
  • Sales, trends, and issues analytics
  • Lists, notes

Interested in learning more?

See:

About

Welcome to the Usable Apps blog.

Learn more about us at
Usable Apps

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today