Thursday Nov 21, 2013

Dress Code 2.0: Wearables

It used to be that enterprises had this thing called a dress code to "inform" employees about what they could and couldn't wear in work. That's all changed these days, largely.

But now, enterprises need to react to what technology their employees will wear when working. Enterprises are about to take advantage of how the latest trend in technology, "wearables", will transform work and make workers smarter and enable them to complete their tasks more easily.


http://upload.wikimedia.org/wikipedia/commons/thumb/7/76/Google_Glass_detail.jpg/640px-Google_Glass_detail.jpg

The term "wearables" itself, for me, is too broad. We also have the Quantified Self arrivistes, and talk of "little data" or "the personal API" to contend with, so I'd prefer to think of wearables, in the enterprise context, as another optimized UI, part of an overall user experience.

Wearable technology, this way, might be best analyzed as being for a certain set of users to do certain tasks using certain devices. Using cloud-based data as the source of truth, all can be exchanged between other users and devices, meeting business objectives by solving business problems in an efficient, effective, and satisfying way (that's called "usability", folks).

We are past the fad stage, and real business cases are being identified (as this Wall Street Journal article, "Wearable Gadgets Transform How Companies Do Business" points out). Putting together the opportunities for integration of applications at the consumer level and those business services appearing, we can see an emergent technology and user experience roadmap for workers to be even more productive.

This is a fascinating area, and ironically IMO, again it seems that the enterprise offers more potential for realistic value-adds and faster adoption for wearables than the personal space does. Admittedly, it can be as hard to separate personal and work technologies from each other these days as it is to separate your work clothes from leisure wear, but does that really matter?

Talk of wearables is still dominated by a narrow range of devices, namely Google Glass and various smart watches, and most usage we see and hear about is of a healthcare, sporting, fitness, or just exploratory and fun nature.

However, thinking about wearables from a problem-solving perspective and taking in disparate technologies and use cases from the personal, enterprise, startup and open-source world is a more fruitful exploration, I think. And, we need to think beyond glasses and watches too, and think about what services, APIs, sensors, OpenCV (Open Source Computer Vision), voice, and more, can offer with integration and interconnectivity in the cloud.

The Oracle Applications User Experience team is up on the wearables technology and enterprise potential, so stay tuned. We've already shown off some early use cases in the CRM space for Google Glass, but there is a lot more coming.

We will bring a whole new dimension to the notion of "dress code" in work. Your participation and insight as Oracle customers and partners, and as users of our applications, has an open invitation, as always, to inform our innovations.

Exciting times.

Read more about wearables and the Applications User Experience team on Misha Vaughan's (@mishavaughan) VOX Blog.

Sunday Aug 18, 2013

Oracle BI Mobile App Designer and Dashboard UX Design Patterns and Guidelines

Just saw this cool video about the Oracle Business Intelligence Mobile App Designer. A great solution for mobile analytics that doesn't need an IT project to make it happen.




Oracle BI Mobile App Designer

Reminds me to tell you that the Applications User Experience team has made user experience design patterns and guidelines for Oracle Business Intelligence Enterprise Edition (OBIEE) available for free.


Information Display Decision Table

Information Display OBIEE dashboard design pattern helps you make decisions between alternatives

Use these resources to help build great-looking dashboard UIs, making sense of data in a sharp, consistently usable way. Whether it’s visually reviewing KPIs, metrics, reports, or analyzing aggregated data and drilling down to more detail, you can enable users to turn that breadth of insight into action, and all from the same UI.

You can access the OBIEE patterns and guidelines through the For Developer section of the Usable Apps website.

Related Visualizations?

Monday Nov 09, 2009

Error Messages - Everybody's Favorite

Generally when usability literature turns to the subject of error messages it concentrates on the physical manifestation of the error message rather than why the message happened at that point in the interaction (in application terms, the validation of the business rule). For example, usability experts often tell us to write helpful messages, not to scare the user with outrageous text and graphics, make the error message appear close to the problem area in the UI, and so on. Fair enough.

But, stopping just there, is for me a clue to one of the reasons error messages can be so annoying - they're more disruptive to the natural flow of a task than they should be. Really designers need to pay attention to how people work and design the validation points around that. For example, why design the input of data in fields across a series of tabs with the intention of validating all together at the end with a final submission (Scenario B)? It's a nightmare for users to then go back across the tabs, and revalidate fields on each tab. Instead, why not validate each tab's field data progressively as you go (Scenario B)? Makes much more sense from an interaction and productivity perspective.

validation_tabs2.png

Remember, error messages are there to support the user, not frustrate them further, so reduce the user's memory load by requiring them to go back a few steps and recommit data. Users want to commit correct data right way in a natural flow, not just complete fields for the sake of it. Granted, there can be some technical issues about committing data for validation that you may need to work on, but when designing messages start out by looking at a) how users work and then b) relating that to how your application validates data.

Of course, you may have a different idea. I'd love to hear it!

About

Oracle applications user experience (UX) assistance. UX and development outreach of all sorts to the apps community, helping to design and deliver usable apps.

Profile

Ultan Ó Broin. Director, Global Applications User Experience, Oracle Corporation. On Twitter: @ultan

See my other Oracle blog about product globalization too: Not Lost in Translation

Interests: User experience (UX), user centered design, design patterns, tailoring, BYOD, dev relations, language quality, mobile apps, Oracle FMW and ADF, and a lot more.

Search

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