IDYeah Labs - Concept Contest

IDYeah Labs is an initiative by IDYeah Creations. We invite you to uncover the FACE of our Labs by giving your best guess as the Concept Contest Entry, on our Facebook Page Wall.

Usability Watch - Tuborg Beer

In pursuit of looking at all dimensions and examples of usability around us (mostly in software world), we're committed to bring you readers some focused reviews and experiences on real-world products. Products that have innovated to achieve a long-lasting user experience. The case in question today is: Tuborg Beer.

I have been a delighted consumer of beer since 1997, and have experienced the taste of many brands over the years. With evolving taste buds and changes in company at the tables, I have shifted loyalties too; some due to geographical constraints of unavailability of few brands. Anyways, no beer has caught my fancy to the extent of a not-so-far-ago launched brand in India - Tuborg, a beer of Denmark. The main reason of my fascination was beyond its soothing mild flavor; it was the usability innovation in its packaging! And it hit me and my close friends that all these years, we'd never "missed" this neat little way of opening the bottle like a beverage can. The very apparatus that makes drinking a beverage in a can more fun and manageable as compared to a bottle, was simply introduced in the bottled drink.



Wow! The expression is also about the experience you get by the sound made. It's not just a convenience about managing without hunting for an opener. It's the ambiance this creates. Almost invisible cold white fumes emitted after a "puckk!" - just setting the tone right, even for teetotalers. And the makers must have known indeed one of the immediate promotion benefits - the strong recall value about this unique mechanism. The word-of-mouth viral effect I hear was very strong, naturally.

A good watch on usability and user experience - from a beer maker (Tuborg).

Thoughts?

We'll be posting similar features, taking on examples of singular products - opining about the user experience. If you wish to contribute any such reviews/experiences, please get in touch - we would love to feature them on our blog, post-moderation of the content.

WATCH THIS SPACE!

Visibility Principle

A user interface is only valued when the user interactions achieve their purpose. The first element of user interaction is what the user sees in the interface. Visibility is all about how clearly the user sees the state of the interface and all the possible actions. If the users cannot "see" how to use the interface, it is not adhering to the visibility principle of user interface design. Let's dive into some real-world examples and then follow-through with web examples.

 

Good visibility - car dashboard that is designed with everything positioned in a way that can be easily found and used.

 

Sleek design in this case compromises usability - auto-faucets have a great advantage of saving water, but its common challenge is "where to put our hands" to ensure timely hand-wash.

Style yes, visibility of main functions - a big NO! One of the most complex wrist-watch dial ever designed.

How many combinations!? Phew!

 

Most straightforward with high visibility - ATM.

Over to few web examples:

• google


• dropbox


• business catalyst


• high rise


• fidelity


• acosmin


• justdial

Employ commonsensical ideas like highlighting important parts of your web page on top center, avoiding dead-ends, and always suggesting users the 3 answers: "where he is", "what there is", and "where can he go next".

Suggestions?

Case Study: Reaching Wider Audience with Enhanced Visibility

Background

Founded in 2005 with 3 partners, Vector Consulting Group is now the leading player in the area of Theory of Constraints consulting in India and South East Asia. Vector employs TOC philosophy to bring about quantum jump in performance of organizations in its target industry clusters. They partner with clients till they realize the targeted benefits.

Web marketing being inexpensive, yet sophisticated and effective if done right – made Vector hunt for a suitable vendor in IDYeah Creations to relook at their corporate branding and communications through public domain: web site.

Challenge

Vector’s main objective behind its recent site revamp was to position the company as the leader in the space of “Theory of Constraints” based management consulting. Vector’s key differentiator from competitors is their array of “guiding principles” on which they base their business operations:  Benefits Sharing; Ownership of Results; Trust; and Respect for the Individual.

In order to successfully convey the Vector way of messaging, it was essential that the new site design maintain a steady balance between both the “serious” consulting and the “innovative” engagement aspects of Vector’s services and products.

IDYeah worked with Vector Consulting Group’s founder members to keep the overall tone and structure of site content in line with the corporate brand and offerings strategy. From a design perspective, IDYeah established a consistently innovative visual tone for the site that could be complemented with various graphic elements to infuse a much-needed dynamism without losing the overall intent – of connecting better with the visitors and inspiring trust and confidence as a brand.

Launched in June 2009, the new web site clearly establishes Vector as the leader in its category and provides web site visitors with company, solutions, and industry information that is structured for easy access to the content that they seek.

User & Task Analysis

IDYeah’s User Profiling and Task Analysis served as the foundation for the establishment of the global site architecture and use case workflows. The range of user needs for access to information (i.e. CIO seeking consulting case studies vs. CTO seeking product features) required a detailed “user to task” analysis exercise to determine what online functionality was most valuable to each identified user type. By focusing on functionality and key features for particular user groups, IDYeah was able to identify and quantify at a granular level the key tasks and valued content areas across a wide range of Vector’s site visitors.

Expert Evaluation

 

• Top Navigation not prominent


• Industry clusters/focus not visible


• Logo and symbol eating up precious real estate on screen


• Not scalable to accommodate increasing number of case studies


• Not scalable to highlight the authored media materials on the competence and success stories


• Overall tone and structure either leaving the visitor without much information or taking repeated and prolonged efforts


• Visual appeal of a leader in its space missing


• Corporate logo and product logos not consistent and progressive


• Over-design and excessive use of Flash – hampering the effectiveness of SEO

Information Architecture

Vector’s priority requirement in establishing the information architecture for site content areas was to establish clear, visitor-specific paths to site information. To achieve the balance between product/service promotion and communication of expertise, IDYeah created a meaningful taxonomy for the site that divided the information into 3 Industry Clusters to help direct the users to relevant content. In tandem with developing the site architecture, IDYeah also developed a crisp information workflow on the Home page providing information seekers with an “at-a-glance” reference to core space and expertise of Vector. Per Industry cluster, following workflow was suggested, designed, and implemented:



 

IDYeah Creations employed DesignWave Consultancy as the Design Partner and Inkey Solutions as the Technology Partner to arrive at the desired outcome.

User Interface Design

 


 
After generating wireframes on the initial concept, and having them in place, IDYeah began applying visual design treatments to the UI foundation to create a look and feel that would support Vector’s repositioning goals. An initial set of digital mockup directions that spanned a range of tone and attitude. From this set, a single direction was chosen and refined to become the new outline face of Vector.

Benefits

• Strong re-branding and re-positioning


• Increased site traffic and qualified set of business inquiries


• Platform for sharing expertise through expert literature


• Improved in-bound marketing and sales

Staying Live with SAP

You cast off all legacy systems and installed SAP; SAP ties it all together – but it costs. And did you achieve answers to your problems? Or are you contemplating to look for an alternative, because the migration introduced new problems?

ERP-centric companies are missing out on the full potential of a solution as rich as SAP, because they are failing to appreciate the implications – and continuing to make the mistakes of traditional systems development and integration. SAP implementation projects are suffering from ‘undue focus’ on technology, lack of user interface, lack of attention to human and organizational needs, lack of evaluation, and very little integrated working – internally between systems.

Measuring RoI is an essential prerequisite of any IT investment today. But the big problem is that it is far from quantifiable. And if the investment is as huge as an SAP implementation, the aforementioned problem becomes magnified. Spending on IT is no longer identified as an expense, but as an investment. And RoI is based on cash flow analysis. It is also true that management, and not technology, will ensure success or failure. Integration of business objectives with IT solutions succeeds only when management if committed to ensure a smooth transition of change management. “Leveraging staff and current investment” is the biggest faced challenge.

Most commonly posed questions:

• Can we reuse current investment?


• Can we simplify increasingly complex business processes?


• Can we increase productivity?


• Can we lower maintenance costs?

Until the early nineties, the relationship between an organization’s investment in IT and its impact on the performance and productivity was never seriously measured. Perhaps, the most critical reason was one’s inability to segregate the benefits based on ‘Deployment of IT’ vis-à-vis ‘Deployment of robust processes.’ Only if an organization has the latter approach to an SAP implementation, will it see the value and reap the benefits in the longer run. In accordance with the above approach, it must be added that SAP demands a fundamental change in the processes followed by business and the people who work those processes.

Change, being painful by nature, discourages many to take the second approach. However, if you install SAP as software without changing the ways people do their jobs, you may not see any value at all – and the new software (SAP) could slow you down by simply replacing the old legacy software that everyone was used to. On the other hand, if you are able to use SAP to improve ways your people take orders, manufacture goods, fill timesheets, for example, you will see value from it.

SAP, in spite of being one of the largest and most successful vendors of enterprise resource planning (ERP), ironically is a misnomer. For one, it DOES NOT help your planning. Resource – and the ownership of that resource in any business – is a hazy term. What is right about it is the enterprise part. It successfully integrates all departments and functions across a company onto a single computer system that serves the particular needs of different departments. Organizations opting for SAP as their ‘back-office software’ have one or more of the following reasons – to integrate financial information; integrate customer order information; standardize and speed up core business processes – manufacturing, financial services – but whatever be the case; reduce inventory, non-performing assets – as the case may be; and standardize HR information.

Business benefits aside, SAP as an ERP delivers well on three necessary objectives – consistency and reliability of data across the organization; streamlined transaction processing; and operations-level reporting.

Which is a better approach – Going for an ERP vendor like SAP or going for specialized point products? Opinions vary, based on a survey of several successes and failures in either case. Important is to base your evaluation on your business case, the strength of transaction processing backbone, and the desired room for sophistication. At times, an ERP like SAP is not able to handle a function vital for the company. In such cases, a specialized third-party product can be interfaced to deliver the result. For example, Mohan Breweries and Distilleries Ltd implemented SAP R/3; they found that they needed far superior functionality in the insurance area. They opted for IVL’s iNSUR/3, a comprehensive add-on package with SAP R/3 ERP solution that addresses the needs of enterprises in the areas of insurance and claims management. The company was able to authenticate information on numerous critical data of the insurance processes and cut down nearly 50% of excess manpower costs. It could increase the efficiency of the supply chain by integrating the routine insurance related activities into SAP R/3 Business Framework.

SAP is generic enough to cater to 24+ industries. As much as this being a strong point in favor, it introduces a major limitation – Usability! And this compromise cannot be escaped from, internally. The reason is commonsensical – in making itself applicable to diversified industries, diversified processes, SAP was forced to provide innumerable data elements packaged logically in discrete screens and transactions; terminology used on-screen is also generic in nature for the same reason. Following table captures the common ‘effects’ faced by most customers, and the ‘causes’ leading to those symptoms.

EFFECTS

• Tedious and error-prone data entry


• Users spending more time on SAP than their primary tasks


• Steep learning curve


• High costs in training and re-training

CAUSES

• UI peppered with inconsequential data elements


• SAP by nature is more transaction-driven than process-driven


• Complex and excessive navigation to perform a task


• Imprecise and confusing terminology for your industry

Whatever industry you are in, “it’s all about productivity!” Productivity suffers if end-users are not comfortable with ‘what they see’ on screen and ‘how they interact’ with the screen. SAP evolution from R/2 to R/3 to Frogdesign look (EnjoySAP) has made a conscious effort to bring home better usability. However the spectrum traversed on this front is and is going to be limited because of the earlier mentioned fact – the generic nature.

Better usability can be achieved by internal and/or external customization and consolidation. For example, ABAP, the architectural language of SAP, can be used to re-configure, modify UI screens based on specific business process needs. Similarly, an external program (third-party) may be used to integrate with SAP in order to better the user experience. Or a combination of both! Important factors helping evaluate the approach are captured in the following points.

The solution:

SHOULD NOT

• change the underlying business logic of SAP


• incur extra overhead in terms of heavy maintenance and upgrade costs


• reduce system performance


• affect data integrity

SHOULD

• increase productivity and efficiency


• minimize or eliminate training and maintenance costs


• allow users to focus on their primary tasks


• provide flexibility in terms of deployment and configuration

For example, Rexam Beverage Can Americas implemented SAP R/3 to use its PM (Plant Maintenance) module for mapping their processes, for example – creating a maintenance work order; releasing the work order; and printing the work order – all of which they wanted to happen within 30 seconds. The Plant Manager of Rexam, New Jersey, Mr. Steve Foster and his team of professionals, during SAP training, found the interface neither simple enough nor fast enough to enable what they had in mind. “We had this idea of creating a maintenance system that looked like an ATM (automated teller machine),” says Foster. “No one’s ever been trained on how to run an ATM, yet everyone can use one. Why should it be any more difficult to create a work order in SAP?”

Foster and team found what they needed in a then little known product called GuiXT (software bundled within SAP R/3), developed by Synactive GmbH. With the help of a Synactive consultant, a Rexam programmer was able to use GuiXT to create an SAP PM interface that does, in fact, resemble an ATM in its simplicity. The basic menu screen contains just 10, touch-screen, function push buttons, each of which triggers a series of standard SAP functions that run in the background, but are transparent to the user. In some cases, a single button launches SAP transactions that would have otherwise required the user to navigate 12 to 15 separate screens using standard SAP interface, Foster says.



The result, according to Foster, is that Rexam training requirements for the SAP PM system were cut from an estimated 40 hours per machine operator – which would have been required using a standard SAP interface – to 4 hours with the simplified GuiXT enabled SAP interface. Multiplied times the 1,500 plant operators who would be using the system, that’s a savings of 54,000 hours. “We more than recovered the cost of GuiXT license in the training savings alone,” Foster observes. Moreover, the simplicity of GuiXT interface enabled Rexam to largely meet the 30-second goal for its users. “I’d say we’re hitting that 30-second goal about 80% of the time, and for the other 20%, it’s less than 45 seconds,” Foster notes.

Conceptually, from a CIO’s perspective, the perfect system would be one in which one could reuse invested software, describe software architecture so that a non-expert could successfully execute and simplify complex business modeling, and automate user tasks – all of the above with no or least maintenance.

Can you find or build one? Are you willing to Change?

 

Boorish behavioral patterns

To many coders, application development is the more glamorous part of software development, as compared to building the user interface for the same. What most of coders ignore however, is that to the end-user, the user interface IS the system. And what most end-users want is a system, which is functional, intuitive, easy to use and has sensible defaults. Humans during their evolution from cavemen to the current society have come up with a number of rules, governing various aspects of social behavior. These are the rules that are commonly referred to as social manners. We argue that a large number of the behavioral patterns classified as “good manners” apply to software application interfaces also. Consequently, user interface designers who tend to ignore “good manners” run the risk of making their applications as bad or rude software citizens.

But what are good manners? Simply put, good manners can be summarized as show consideration, respect and care for others.  It is somewhat surprising then that, whereas most of the creators of various software and web applications are well behaved and possess good social ettiquettes, some of their creations are truly rude and obnoxious in their interactions with end-users. It seems that many computer applications do not follow the basic tenets of social interactions which are common knowledge. The disconcerting fact is that some of the usability issues that underly such rude behavior has been identified and understood for decades.

Some examples of rude interfaces are summarized below:

1. Irrevocable Steps: This typically refers to instances when the system decides to take some irrevocable steps, with or without user consent. Automatically applying patches and rebooting the system is a concrete example. This is seen on windows environments, wherein the OS is configured to automatically download some patch from windows update without informing/intimating the user, and after the patch is installed, auto-rebooting the system. This is the physical equivalent of your futuristic car deciding to clean itself, suddenly change directions from your current destination to the carwash, throwing all the users out of the car and washing itself.


2. Pushy Behavior: Application developers want end-users to use their software as much as possible. But when their desire to promote their software to desktop users translates to the software adding itself in a number of places, including the startup menu, desktop icon, task bar, right click context menu and changing the default application for a number of file types to use itself, it can be termed as pushy behavior. Real player, and before that Paint Shop Pro was notorious for such behavior.


3. Pot calling Kettle black: While doing application design, it is the responsibility of the programmer to not just anticipate, but even expect incorrect inputs from the end-users, who often are not technically savvy. In a lot of cases, however, instead of designing the software to be robust and fault tolerant, the programmers blame the end-users via vague and rude error messages. An example of such is when the application attempts to confirm some obvious condition from the end-user eg - The infamous DOS error Abort, Retry, Fail?


4. Cryptic error messages: The HTTP status codes comprise of a list status codes that webservers return as a response for any HTTP request. In fact, all the HTTP status codes are very terse and to-the-point, but what is more puzzling is when website designers directly throw these cryptic error messages to end users. A very common example is, when a web server throws a “404 - page not found” error. It is fairly trivial for the website designers to put out a more graceful error message, or even re-direct it to a generic error page having a more polite error message.


5. Threatening error messages: These are error messages that threaten the end-user with some sort of destructive behavior (typically data loss). That this is a very rude behavioral pattern for the application goes without saying, but what is worse is that the programmer has anticipated the condition that causes this error message, and instead of fixing the root cause, added a threatning error message to the end-user. eg - “Continuing with the operation may cause permanent data loss and cannot be undone. Yes/No?”


6. Contract breaker: Windows GUI applications (typically) have a contract with the end-user that exiting the main window will close the applications. Applications that fall in this category satisfy the exit contract but keep running in the background hogging memory or CPU. Adobe is a prime example of such behavior.

We will be exploring some more such examples and analyzing their underlying patterns in upcoming posts. Please watch this space for more details.

Simplicity Principle

SIMPLICITY.

We saw few examples and points on one of the principles of user interfaces - structure. This features focuses on Simplicity.

Why do you need your site to be simple?

Site visitors will rarely visit your site to "enjoy" the design. The design should be very transparent and complementary to the content. From the visitor's point of view, the best design is pure text that echoes the content they're looking for. Nobody really has the time and patience to interpret your design. Remember, the complexity and abstractness that some design concept introduces does not command any appreciation for the hard work that's perhaps gone into creating the design. Strive for simplicity - easy to comprehend layout and text.

How can you achieve simplicity in your web site?

The idea is to achieve a perfect blend of details and their presentation on screen.

• Use graphics sparingly and meaningfully; also make sure it's light on size.


• If short text is sufficient, avoid having complex wordings. For ex: Use "Search" instead of "Quick Keyword Search" for your search functionality.


• Use suggestive and direct icons that are consistent with web terminology and use less space on screen.


• Use colors and fonts sparingly.


• Do not use jarring animations and advertisements.


• White/Blank Space is underrated; use it effectively.


• Use elements that work consistently across all browsers (HTML + CSS); avoid elements that cause issues across different environments (JavaScript, Flash).

Few examples of Simple web sites:

• blejskam


• enso


• artypapers


• distinct


• symphony cms


• opened hand


• jgm


• open communications

KISS philosophy has been around since the dawn of web site design. KISS does not mean boring and dull sites. It is possible to create great looking sites and still keep it simple using simple techniques, as exemplified in the above list of sites. Concept of simplicity is more complex than it may seem; but achievable.

Stay on for more discussions and examples on principles of user interfaces.

Structure Principle

STRUCTURE.

In my blog post, Principles of User Interface Design, we touched on various aspects of user interfaces. This feature will discuss few specific points of one of the aspects - Structure - followed by few examples.

Why do you need your site to be structured?

Well, you need your customers/prospects to understand quickly what need of theirs will your product/service fulfill. It is important for the visitors to find relevant information quickly, and get easy access to additional information if necessary. Your public domain, which is the place for introducing all that you do, can and will change in the future. Having a good and expandable structure would make this job easy and seamless. Having a good structure (which also means not random, but structured set of keywords) will also make the site findable on search engines. The customer also needs to have alternate paths to key areas and information on the site for better decision-making.

How can you achieve structure in your web site?

Main idea is to establish the information architecture for site content areas in providing clear, visitor-specific paths to useful and relevant information.

• Internal site linking structure - have logical grouping/linking between main navigational elements (either left or top) and secondary/direct navigation (right, center, or bottom).


• Linking between sections - have good cross-linkages and quick jumps to important sections of your site (for example: customer stories, case studies, thought-leadership blogs).


• Page-specific navigation - it is not a bad idea to design page-specific navigation and access to information. In fact, each page has to serve a specific purpose and it's a mistake to have all pages behave the same in a large site. For example, "About us" section needs to be very different than a section about "Products/Services" not just in presentation and writing style, but also in flow.


• Keywords as sections - site visitors will feel at home with the structure of the site, if we make user keywords as section names.


• Site Exits - design specific click-to-action elements for a logical exit from your site. For example: Inquiry Forms, Downloads, Feedback, Sign-ups, Share/Like.

Few examples of sites with good structure:

• mozilla


• vector consulting


• protolize


• sumagency


• greenpepper


• bearskinrug


• bbc


• usa gov


• abebooks


• rotten tomatoes

Structure it now; structure it well.

Stay with us for more features on other principles with more examples.

Reasons for Branding Usability Revamp

Branding and Usability

The visual identity created for a brand translates the brand strategy into clear, distinctive messages. Strategic identity stems from the core values of the company, expressing a consistent and unique vision. This ensures strong associations in the mind of the customer, inspiring trust and respect in the long term; beyond the life of any single product or service.

Rationale and Advantage

• Bring out Conceptual Message and USP


• Fulfill business inquiries with ease


• Reduce maintenance costs


• Increase customer satisfaction


• Grow competitive advantage


• Eliminate over design


• Increase accessibility to relevant information


• Increase sales and revenue


• Share right content in the right form


• Showcase Products, Solutions, Services, and Customers

It is far too important for your brand identity and brand strategy to be consistent and complementary. Make sure you use your public domain (logo, web site, social media, blogs, etc.) in high synchronization with your brand. Knowing your current and future audience (customers, employees, partners, investors) is very important while achieving consistency in branding revamp.

Good luck!

Principles of User Interface

This article simply lists down in brief the few principles that need to be adhered to and kept in mind, while creating or analyzing user interfaces. Following this, we'll take a look at few examples for each points in question, as series of features.

Principles

• structure
  
  
  
  • organize user interface purposefully
  
  
  • make it meaningful and useful based on clear, consistent models apparent and recognizable to users
  
  
  • put related things together; separate unrelated things
  
  
  • differentiate dissimilar things, make similar things resemble one another
  
  
  
  


• simplicity
  
  
  
  • make simple, common tasks simple to do
  
  
  • communicate clearly and simply in user's own language
  
  
  • provide good shortcuts that are meaningfully related to longer procedures
  
  
  
  


• visibility
  
  
  
  • keep all needed options and materials for a given task visible
  
  
  • do not distract user with extraneous and redundant information
  
  
  • do not confuse user with too many alternatives for performing same task
  
  
  
  


• feedback
  
  
  
  • inform actions or interpretations
  
  
  • inform changes of state or condition
  
  
  • inform errors or exceptions
  
  
  • keep model of communication - relevant, clear, concise, and in language familiar to user
  
  
  
  


• tolerance
  
  
  
  • reduce cost of mistakes and misuse by allowing 'undo' and 'redo'
  
  
  • prevent errors by tolerating varied inputs and sequences and by interpreting reasonable actions
  
  
  
  


• reuse
  
  
  
  • reuse internal and external components and behaviors; maintaining consistency with purpose
  
  
  • reduce the need for users to rethink and remember
  
  
  
  

Watch this space for some concrete examples...

SAP R/3 Customization with GuiXT

Preamble

This feature examines some of the major challenges faced by industries running on SAP in leveraging their staff and existing investment in an era of constrained budgets and expanded demands. The article is predominantly written from the perspective of the C level executive with some reference to the technical, distinguishing points of the solution. GuiXT product suite is very innovative and readily delivers 4 key economic advantages:

• Reuse of current investment;


• Simplification of increasingly complex business processes;


• Increase in productivity; and


• Lower maintenance costs.

We describe some of the challenges created by the current trends in ERP implementation, specific to SAP, and the potential solution.

Executive Summary

CIOs face the challenge of adapting to an increasingly complex software world with yesterday's tool sets. The Internet, e-commerce, internal integration demands, supply chain re-engineering, and customer relationship management are all contributors to the growing demands on today's developer. How does one deal with all this complexity and the difficulty in employing the necessary IT talent to successfully wade through this quagmire? Conceptually, the perfect system would be one in which we could reuse our software, describe software architecture so that a non-expert could successfully execute and simplify complex business modeling, and automate most user tasks.

Synactive is a products company, always at the forefront of technology since its inception, developing and providing user-friendly solutions, adding exponential value to customer businesses. Synactive GmbH is a member of SAP's Complementary Software Program. Their product GuiXT enables easy reuse of existing SAP investments.

GuiXT Software Suite allows corporations to adopt a user-friendly and intuitive SAP by introducing a modular scripting technology that dramatically increases productivity with its powerful automation and customization features. Web interactivity and external application interactivity with SAP is introduced; which takes business processes to an entirely new level. Repetitive processes cease to be painful with excessive data entry and navigation, and instead become automated and accelerated workflows. All of the above is  achieved without adding to or modifying the underlying business layer (ABAP code) of SAP. Core runtime engine of GuiXT is a part of SAP Front-end and hence is present at every client installation.

End users have realized in years that with complete training and adoption of customized processes throughout an organization, they experience total ROI gains for SAP's past infrastructure investment of 50% plus.

GuiXT layers into an organization's existing SAP implementation to seamlessly bridge together disparate technologies available for enterprise implementation. Most organizations have made significant investments in existing SAP model to achieve the benefits of user-friendly and intuitive interface to simplify their processes; however, these investments have not produced the expected results. This is because they are either difficult to develop using or they achieve the results by altering the business logic of SAP, making it difficult to maintain and change. GuiXT shields the developer from ABAP and allows them to focus on writing business logic.

Challenges

With ever increasing changes, CIOs of companies are acutely aware of the need to choose the right technologies that will enable them to remain agile and to respond rapidly to the changing demands of the marketplace. The pace is demanding with changing distribution patterns, globalization of commerce, and mergers and acquisition activity allowing little time for reflection.
Recently, the push has been for user interfaces to be simple, clear, and intuitive. Users want a system that is easy to learn and use, and is flexible. Challenges faced by CIOs of SAP customers are, having:

• User-friendly screens,


• Error-free and tedium-free data entry,


• Low training and maintenance costs,


• Automated business processes, and


• Integration with web and other applications.

GuiXT solutions have multi-dimensional value, which addresses and overcomes the aforementioned challenges, both in less time and less cost.

Reuse of current investment

With the growth of the Internet and interdependent software systems, the need to leverage existing systems has grown enormously. Call of the hour is ‘reusable’ systems. Solutions that are reusable and scalable to prevent or minimize costly upgrades would be ideal.

GuiXT solution not only ensures reuse of current investment, but also spares future recurring investments, in terms of training and retraining SAP users. Ease of use; scalability; reliability; manageability; and flexibility are some of the highlights of GuiXT solutions.

Solution Overview

You can use GuiXT components to implement a whole range of screen customization options. With GuiXT components, you can:

• Combine and consolidate SAP screens to reduce the number of screens users have to wade through; in most cases up to a single screen,


• Change the layout (i.e., refine terminology or delete/move screen elements) of any SAP screen to improve productivity and reduce errors in data entry,


• Add relevant documentation by integrating web based help within SAP Front end itself, and reduce training costs,


• Add automation driven by one-click process; hence simplifying the business processes.



Inside GuiXT Components

• GuiXT (Shipped with SAP GUI) – Allows you to change text and remove redundant data-entry fields in R/3 without touching core R/3 data. The runtime engine is bundled with SAP GUI.


• InputAssistant – InputAssistant allows you to streamline business processes by combining stock R/3 screens and transactions into a customized, personalized, error-free data-entry screen.


• Designer – Allows you to add or change R/3 text and remove redundant data-entry fields in R/3 by simple mouse ‘click-drag-drop’ operations, without touching core R/3 data. The result of the screen modifications as GuiXT scripts.


• Viewer – Allows you to embed any HTML or RTF page inside any R/3 screen for Help or Internet lookup.

Strengths

• Ease of use – Screen customizations are done using Designer, a WYSIWYG tool that empowers users to click-drag-drop elements in an editable SAP GUI screen.


• Scalability – GuiXT supports wide range of implementation sizes; from small businesses to large corporations. GuiXT supports R/3 installations 3.x to 4.x.


• Reliability – Since GuiXT is bundled within SAP, it eliminates the need of any additional development activity within SAP.


• Manageability – Personalization and customization are script-driven. GuiXT scripts (simple ASCII text files) can be stored and managed within R/3 database.


• Flexibility – Once GuiXT is activated, all SAP transactions become candidates for simplification and personalization. All it takes is additional GuiXT scripts.

Benefits For Users

• Intuitive R/3; Easy to understand and use


• Process automation; Minimal errors


• Tedium-free; Smart and quick data-entry


• Huge time savings; Allows them to focus on their actual tasks

Benefits For Management

• Proven and scalable (bundled by SAP AG)


• Data consistency and integrity


• No ABAP necessary; Ensures swift implementation


• Transparent deployment


• Low cost; Less training for users


• Error-free, streamlined processes; Increased productivity

For further details, you can visit: GuiXT Site and get in touch.

Business Applications Usability & Recurring Benefits

In your business environment and the spread of IT landscape comprising of huge distributed business applications like ERPs, what are your primary goals when it comes to assessment of the entire system metrics?

Primary Goals

• Reduce training time and increase user comprehension;


• Increase productivity, efficiency, and data integrity;


• Increase speed, ease of navigation, and ensure a comprehensive data footprint.

Depending on specific platforms and technologies in use, without compromising on their internal functionalities and rich features, what are the few generic and common customization approaches to achieve the above goals?

Few ways to achieve customizations in business applications

• Change standard terminology to those your organization's pervasive business terms thus eliminating ambiguity and uncertainty;


• Reduce manual data entry by automating redundancies;


• Rearrange your tabs, buttons, workflow elements and fields to match those of your internal processes;


• Hide unused workflow elements and fields and create validations for all of the fields necessary to achieve a complete set of mandatory data;


• Consolidate multiple tabs, screens within your workflows and create a streamlined and easy to navigate environment;


• Consolidate multiple workflows and shortcuts in a dashboard and one-click interface if feasible and ensure that users provide all necessary data and jump across relevant areas without expending extra effort.

A summary of recurring benefits

• Increase in productivity creates direct full time employee benefits thereby enabling a redeployment of resources to other areas of business;


• Increase in efficiency improves employee experience and reduces training and retraining burden from the company and management;


• Speed, clarity and easy navigation creates enhanced customer satisfaction and leads to more happy and reference-able clients;


• Automation and validation reduces the time required to navigate through systems and ensures a more comprehensive data set for management reporting;


• Consolidation and streamlining creates a cleaner and more scalable environment that is more conducive to retention of existing workforce without the need for additional resource expenditure;


• Survival of enhancements through upgrades ensures that your investment is preserved and additional resources are used for additional enhancements;


• Ease and speed of deployment ensures that you can create a multitude of enhancements in a very short time with near immediate results.

Thoughts?

Techniques/Guidelines for User Interface Creation

GRAPHICAL USER INTERFACE - visualizes complexity to make confusing and business technology issues clear, concise and concrete; helping people to make better, faster decisions, leading to action and results.

We've discussed examples of many principles and concepts of usability and user interface design in the previous blog posts. This feature lists down several concrete techniques and steps to be followed while creating a user interface. Future posts will cover most of these guidelines in depth with live examples.

• Consistency
  
  
  
  • Buttons/Menus in consistent places on all screens
  
  
  • Same wording in labels/titles and messages
  
  
  • Consistent color scheme
  
  
  
  


• Standardization
  
  
  
  • Setting standards and sticking to those; for example: Agile Modeling Standards
  
  
  
  


• Holding the line
  
  
  
  • Control over “unusual ideas” on how the screen should look like, by re-iteration of corporate goals, application needs and standards
  
  
  
  


• Explanation of rules
  
  
  
  • Application to “explain” rules to end-users to perform their tasks
  
  
  
  


• Navigation (external)
  
  
  
  • Easy access to relevant functional screens, from all screens
  
  
  
  


• Navigation (internal)
  
  
  
  • Co-relation of logical eye movement of user and the functional flow within a screen
  
  
  
  


• Terminology
  
  
  
  • Text (primary source of information for users) – proper choice of words
  
  
  • Less abbreviations; more complete words/sentences
  
  
  • Informative error messages
  
  
  
  


• Understanding UI widgets
  
  
  
  • Right widget for the right task
  
  
  
  


• Drawing parallel
  
  
  
  • Looking at other similar applications for standards/guidelines of usability
  
  
  • Avoiding imitation of user interface
  
  
  
  


• Color
  
  
  
  • Sparing use
  
  
  • Secondary indicator
  
  
  
  


• Contrast Rule
  
  
  
  • Dark text on Light background
  
  
  • Light text on Dark background
  
  
  
  


• Alignment
  
  
  
  • Organization of UI elements (left justified, right justified, etc.)
  
  
  
  


• Expecting mistakes
  
  
  
  • Designing for users to recover from their mistakes
  
  
  
  


• Intuitive design
  
  
  
  • Empowering users to make educative guesses for using the application
  
  
  
  


• Evolutionary approach
  
  
  
  • Mock-up, prototype leading to final output
  
  
  
  


• Grouping
  
  
  
  • Grouping logically connected items
  
  
  • Separating disconnected items
  
  
  
  

Remember, in order to reduce operating and opportunity costs, it's better to build it right the first time. More to follow on this subject...

Confusing Interface (Dilbert)

Usability Characteristic: "Easy To Learn"

The last feature in Usability Characteristics. An easy to learn site/product is one that supports both the initial orientation and continued learning throughout the complete lifetime of use.

Most usability exercises applied to sites and products achieve an end result that assures low entry barrier, i.e., initially easy to learn. However, very few result in having the same ease of learning in a sustained usage. In other words, we need to exercise usability in anticipation of future directions of the product to see that it's not just easy to learn, but easy to master as well.

Few examples of products that are easy-to-learn:

• google sketchup


• solidworks


• yahoo! messenger


• adept tracker


• microsoft sql server 2005 express


• neopaint


• alice


• real software

Generally, easy to learn interfaces allow users to build on their prior knowledge. Also, it allows them to build on any interaction patterns they have learned through use in a predictable way. Consistency in user interfaces drives predictability. Software products that achieve and maintain consistency even across years of upgrade are the easiest to learn and master. For instance, keeping terminology unchanged, having design elements and controls in familiar location, maintaining similar behavior for similar functions, and so on. Users see what they expect to see. This philosophy lays the foundation for the process of user observation and task analysis, leading to superior usability and user experience from a learning angle.

Watch this space for more discussions and guidelines around usability.

Usability Characteristic: "Error Tolerant"

Error Tolerant User Interface.

Your site/application ideally needs to prevent user errors and provide easy means to recover from them if they occur. This characteristic is also far too critical to be ignored or taken lightly. For achieving this, your current site or application may need a strong revamp, focusing on all critical tasks and paths of the user; the steps involved; the language used; alternate and recovery paths available; error message structuring; guiding tips and instructions; memory features; and so on. Basically, everything that makes the intended audience to explore and make optimum use, without fear - about loss of time and effort.

An error-free system, while being the ultimate desire, is far from being a reality. It may be far more usable, if the system considers comprehensible error-messages as part of its user interface, and with possible inclusion of a clear description and direct links to correct the problems. Some guidelines based on Whitney Quesenbery's theory and research, to make your interface error-tolerant are:

• Make it difficult to take incorrect actions; Design links and buttons to be distinctive, use clear language, avoid technical jargon, and make dependent and relevant fields appear together


• Make it difficult to take invalid actions; Limit user choices, provide clear examples for data entry, present appropriate navigation options


• Make it difficult to take irreversible actions; Provide back-tracking capability, provide undo/redo, avoid dead screens, don't indiscriminately use confirmations


• Plan for the unexpected; Allow user to add new entries, take exceptional routes through the interface, make choices you did not predict

It is important for the interface to be polite about correcting mistakes that typical arise from lack of foresight - that of the designer/developer.

I'm hunting for some good examples to add to this post, as done in my previous features. Feel free to contribute if you have any thoughts and suggestions. I'll update this feature with examples, very soon.

Next Characteristic: Easy To Learn.

Usability Characteristic: "Engaging"

The previous two posts saw examples of effective and efficient sites. This feature focuses on the "engaging" characteristic of a user interface.

An interface that's confusing or difficult to read; that fails to draw users into their tasks - generally fail in the "engaging" department from a functional aspect. Apart from this, an interface should be pleasant and satisfying to use, to qualify as engaging. Clearly, visual design and communication is the key here. The style, presentation, colors, fonts, graphic images, illustrations, etc. invoke immediate user reaction. Readability of content and clarity in interaction styles also matter a lot in an engaging relationship between the user and the site/application. Also, certain deterrent elements like an abstract image or an audio/video clip or a peel-away banner can add up to the engagement quotient.

At the risk of sounding repetitive about something painfully obvious - just like other usability characteristics, this aspect also demands that the design meet the expectations and needs of the people who must use the interface. In some ways, this post echoes some principles of the desirable philosophical dimension discussed in an earlier post.

Few examples:

• thomson reuters


• sap


• adidas


• sony style


• harley davidson


• accenture


• dell


• facebook


• google

Apparently, most well-known brands as above pay sincere attention to this aspect of usability - as an integral contributor towards brand loyalty and retention. A scientific approach towards achieving and measuring the engagement quotient is to conduct user satisfaction surveys and psychological interviews - aiming to gauge the patterns of user acceptance and user attitude. More detailed view of achieving this and other characteristics of usability will be discussed in a separate series of blog articles soon.

Please share your opinions.

Next topic: Error Tolerant User Interfaces.

Usability Characteristic: "Efficient"

Of the usability characteristics, effectiveness is often confused with efficiency; but they are not the same. Efficiency is concerned primarily with how quickly a task can be completed. Whereas effectiveness, as we saw in the last feature, concerns itself with completeness and accuracy of a task.

ISO 9241 defines efficiency as:

The total resources expended in a task.

Measurable parameters of efficiency are the number of mouse-clicks and keystrokes required or the total time on task. Layouts with visual elements that are designed with visible contrast, with proper text, and good logical placement - define clear user actions and choices, resulting in an efficient user interface. Also keyboard shortcuts, alternate menu navigational paths, and buttons all contribute towards efficiency.

The most common example of efficiency is the design and use of CTRL+C, CTRL+X, and CTRL+V in case of Windows - respectively the shortcut keys assigned to Copy, Cut, and Paste data. Though it may seem like portions of seconds or a few seconds saved while doing this operation, imagine the repeatability of these functions, which add up to a huge time-saving. Having FAQ sections on complex sites also lead to efficiency of use, where the recipe is to provide some quick answers/guidelines to common queries and doubts, rather than only keeping them embedded inside an ocean of content.

Few examples of efficiency:

• google


• godaddy


• northern light


• dropbox


• sofa


• gettyimages


• moneycontrol


• justdial

For sites and products to be more efficient, the focus in the iterative design process should be on the time taken for achieving the goal by the intended audience. It can be clicks, keystrokes, page views, search results...anything that has a quantifiable co-relation with time.

Thoughts?

Next 'E' to follow after this feature - Engaging.

Usability Characteristic: "Effective"

The first of the five usability characteristics - EFFECTIVE.

Effectiveness is measured by the completeness and the accuracy with which the intended users achieve their specific goals. The typical characteristics of an effective user interface are:

• clear terminology - in the user's language and appropriate to the task


• good, comprehensible choices on screen


• easy navigation; alternate means of navigating to an outcome, in complex situations (unfamiliar domain)


• quality user assistance/instructions

ATM machine and Calculator are perhaps two greatest examples of an "effective" system user interface.

Few web examples of effective design:

• eleven2


• enso


• finch


• amazon


• arstechnica


• mashable


• 37signals


• traffik


• wordpress


• readwriteweb


• crunchbase

The examples can continue to flow; but basically we need to appreciate the overlaps between various philosophical and practical dimensions of usability that are apparent in the examples. These are a blend of focusing on being effective, and striking some balance amongst other characteristics like useful, usable, findable, and so on.

Generally, usability and user-centered design is an iterative process and finding a balance between different characteristics for the specific design context is an important part of the user and task analysis. For sites and products that need to have greater emphasis on being effective, the iterative process should evaluate tasks for how accurately they are completed, and how often they produce errors.

More to continue as we move on to the second characteristic of usability in the next feature - Efficient.

The Five Es of Usability

PREAMBLE.

We saw the philosophical angle to various dimensions of usability in previous blog posts, with several examples. This series will focus on the practical dimensions - another, deeper view of the characteristics of usability: Whitney Quesenbery's Five Es of Usability. With examples, of course.

ISO 9241 defines usability as:

The effectiveness, efficiency and satisfaction with which specified users achieve specified goals in particular environments.

effectiveness: the accuracy and completeness with which specified users can achieve specified goals in particular environments; efficiency: the resources expended in relation to the accuracy and completeness of goals achieved; satisfaction: the comfort and acceptability of the work system to its users and other people affected by its use.



Extending the concept, and narrowing it down to fundamental elements, experts suggest the following five characteristics that are necessary to be met for the users of a product or a web site:

• Effective


• Efficient


• Engaging


• Error Tolerant


• Easy to Learn

Watch this space as we dig into each individual 'E' with some relevant examples.

Usability Dimension: "Valuable"

VALUABLE.

The 7th and last feature in the series of Usability Dimensions. For earlier features, kindly follow the following links: useful, usable, desirable, findable, accessible, and credible.

Depending on the specific case, all previously discussed dimensions need to be balanced in varying degrees, and not treated as mutually exclusive. However, the aspect of "valuable" is commonsensical and must. On one hand, it should relate to and contribute towards the company's ROI. On the other hand, it should also equate itself to ROE (User's Return on Experience). The user-interface design of your site or product should in effect result into one or more of measurable and sustainable benefits like:

• increase in sales


• increase in operational efficiency


• increase in productivity


• decrease in operational/maintenance costs


• re-use of existing components and infrastructure


• increase in brand awareness/networking outreach

This makes your site/product valuable. Only "shared" value (between Business community and User community) is the key to long term sustainability. I'm struggling to list down the examples of "valuable" websites, primarily because the "value" can be really diverse based on specific businesses, specific user community etc. For example, Technical Developers may find technology forum sites really valuable, much different than a teenager finding value in gaming or music sites, and so on. I'll attempt to list down few generic valuable sites that most end-consumers today from any category, qualification, or industry would not live without. Yes, it's easy to guess a few at least...as they would definitely echo your own choice too.

Here goes:

• google (Need I give a link for you to navigate?)


• youtube


• wikipedia


• facebook


• gmail (Isn't this a new term for email?)


• ebay


• linkedin

I encourage you to share your views and few more additions to the list, as comments to this post.

In conclusion, our sites and products must deliver value to the customers and sponsors. For non-profits, the user experience must advance the mission; for profits, it must contribute to the bottom line and provide customer delight.

Watch this space for more example-oriented features (please expect some overlaps in discussion points) through another series of the Five-Es of Usability - another view of usability dimensions: Effective, Efficient, Engaging, Error Tolerant, Easy to Learn.

Usability Dimension: "Credible"

CREDIBLE.

Sixth feature in the series of dimensions of usability.

Stanford's Persuasive Technology Lab investigates topics such as:

• what causes people to believe (or not believe) what they find on the web


• what strategies do users employ in evaluating the credibility of online resources


• what contextual and design factors influence these assessments and strategies


• how and why are credibility evaluation processes on the web different from those made in face-to-face human interaction, or in offline contexts

What makes your web site, your product more credible than others? We should focus on and understand the design and visualization elements that influence whether users trust and believe what we tell them.

I personally trust online presence that are sincere and honest representation of products, services, whatever is out there. A polished content/representation that's simply too perfect, coming from the desk of a copywriter or a marketer - is a complete turn-off and introduces a bias. I tend to stay away from companies, whose sites claim to do it all, have the most flattering testimonials from "unnamed" sources, and have impeccable language splashed - all of which usually is in complete contrast to the imperfect human owner. We should avoid pretense in all context. Credibility cannot be faked, cannot be purchased. A sincere, honest approach that's consistent, even if with flaws, would inspire much more trust and a following that lasts long, if not forever.

Lately, blogs as a platform are being used more for promotion of products or services of a company. Hence, the level of trust is taking a dive, since lesser and lesser blogs are in a non-commercial and honest writing form. A company, whose blog is more about thought-leadership, building awareness, or sharing knowledge, is bound to come across as credible. I'll in near future dedicate a specific feature on "usability of a blog" - where the attempt will be to extrapolate this example and cover more aspects with examples.

Few credibility guidelines:

• proof of a company: about us/contact details page


• explanation of how sensitive data will be used (credit card, phone numbers, email, etc.)


• proof of third-party evidence of your product/service quality (testimonials)


• professional design


• regular site updates, keeping it fresh and alive


• avoidance of errors and coming soon...

The above guidelines - are they enough to establish credibility in today's time of gazillion channels flooded with untrustworthy content mostly? We should do more. We should create valuable, useful and honest content, whether it be in form of articles, reviews, guides, white papers, blog entries or forum posts. We should keep marketing messages out of our content; add them separately, and keep them separate. Ditto with advertisements and videos. We should link out to other credible web sites from our site - probably the best way to establish the existence of your own company - by linking to other sites that reference you. Like press articles, affiliation listings, professional membership details, directory listings, etc. Here's a link to a slightly old presentation from Stanford about Web Credibility.

Few Non-Credible examples:

• shards of glass


• flik fx


• ucsofa


• guinea worm


• clones-r-us


• driver's license


• vampires & zombies

Likewise, there are tons of examples of credible sites; large corporations like: Google, SAP, IBM, Microsoft, Sony, ICICI Bank, and many many more. We should however be cautious of site-clones of these big brands; there's usually some obvious give-away in recognizing the fake from genuine. Web 2.0 trend has added discredit to noble initiatives such as Wikipedia and Ask.com - since any user can submit/edit any information on these platforms, regardless of the quality and authenticity of their sources. In that respect, both "Wikipedia" and "Ask" fall under the category of Non-credible sites.

In conclusion, what you do categorically does not matter. It's all about being there, being honest, being accountable, personally. Putting yourself upfront, writing the site in your own words, making your own promises, one-on-one. This way, you separate yourself from all competitors.

Watch this space for a feature on the last dimension: Valuable.

Usability Dimension: "Accessible"

ACCESSIBLE.

We discussed findable a couple of days back in our series of features on various dimensions of usability. We arrive at a lesser adopted yet very important aspect of "accessibility."

Wikipedia defines Web accessibility as the inclusive practice of making websites usable by people of all abilities and disabilities. All users should have access to information and functionality. For example, a good site/app with textual equivalents for images and with meaningful links would help blind users using text-to-speech software. Sufficiently large text/images or enlargeable makes it easier for users with poor sight to comprehend. Making hyperlinks prominent with underline and not just by a color change, would help color-blind users. Similarly, making clickable areas large enough would help users who cannot control mouse with precision. Users with dyslexia and learning difficulties would appreciate when content is presented in plain language and illustrated with instructional diagrams and animations.



If some practices are followed, all users in fact can be accommodated while not sacrificing the overall usability of the web site. The needs that accessibility aims to address include:

• Visual: Visual impairments - blindness, low vision, color blindness;


• Motor/Mobility: Difficulty/inability to use hands, muscle slowness, lack of muscle control;


• Auditory: Deafness, hard of hearing;


• Seizures: Caused by visual strobe or flashing effects;


• Cognitive/Intellectual: Developmental disabilities, learning disabilities, poor memory, lack of problem-solving and logic skills.

Few examples of almost accessible sites:

• texas a&m


• state of california


• enabled online


• one day films


• genasys


• einfach-fuer-alle


• open web


• keep austin beautiful


• hoehner music

This site exemplifies how web elements can be designed to be accessible. It puts forth the most common items together on one site that can make a site accessible. Things like: choosing a proper color contrast, alternative text for images, separating the structure (navigation, heading, subheading) and presentation (words, fonts, images), allowing users control over re-sizing of content, etc. For overall guidelines, please refer to: WCAG 2.0.

Just as our buildings have elevators and ramps, our web sites and products should be accessible to people with disabilities (10% of the population). Today's it's good business and ethical thing to do. Eventually, it will become the law.

Next dimension in line: Credible.

Usability Dimension: "Findable"

FINDABLE.

Fourth feature in our series: Dimensions of Usability. First three posts discussed the dimensions - useful, usable, and desirable.

Peter Morville says: "Findability precedes usability, in the alphabet and on the Web. You can't use what you can't find."

For your web site, there are two aspects of findability: how well your site can be found on the Internet, and how well information can be found on your site. While the former aspect is very important and concerns itself with concepts like search engine optimization and marketing techniques, we're going to restrict this feature to the latter aspect of findability. The issues that affect findability are: organization of the web site, representation of the user interface, web standards, user interaction, navigation, and content. Achieving a good design and score in these parameters would actually directly contribute to having a higher SEO too.

A standard way of measuring this dimension: "findable" for your web site is usability testing methodologies such as: Tree Testing or Reverse Card Sorting. It's all about focusing on the user's ability to identify and navigate  through your site/application to find and retrieve information and sources relevant to his needs. Things like: navigation, sub-navigation, placement of content, choice of words and phrases, information-flow, search functionality...contribute towards making your web site findable or not.

Few examples of highly findable sites:

• opera


• hbo


• chandra harvard


• fwa


• questacon


• ted


• brainpop


• penguin classics


• stimulus

Simply put, we must strive to design navigable web sites, products, and locatable objects, icons, user interface elements, so users can find what they need. Few things to keep in mind:

• avoid having no way of going back to home


• don't have illogically named links


• have consistent navigation across different pages


• don't have too many sub-navigation levels/hierarchy


• use breadcrumbs and sitemaps


• make states of hyperlinks different and noticeable

Next usability dimension topic: Accessible.

Usability Dimension: "Desirable"

DESIRABLE.

We saw few examples of useful and usable sites and applications. This feature is on "desirable".

"Form follows function" is an age old principle. Everyone is up for beauty. Good looks (form) works like a charm, in any industry, at times even at the expense of function. You may be witness to a great looking movie star, less on acting skills gather more fan following than an average looking, but great actor. Likewise, you would find a person going for a used car, more interested in examining the exterior/body of the car than the functional parts like engine. What about an architect paying more attention to colors and symmetrical dimensions in space, rather than focusing on the lifelines of the household system - electrical and plumbing lines?

Same applies to software and internet world. Not many achieve the balance of their site/app being desirable, at the same time high on usability: useful, usable, etc.

Few examples of beauty that doesn't work:

• verbatim


• creative with a k


• real casual


• jones...


• got milk?


• record tripping


• lego


• echo genesis


• incredibox


• there studio


• coca cola light


• google gravity


• on toyota's mind

If the primary function/industry of your web site is to convey beauty, one should design for beauty. Else, beauty should be a by-product, still essential, but not at the expense of functionality and ease of use. A desirable site may attract more visitors in the short-term, but the visitors are unlikely to revisit as they would find it difficult to achieve their desired goals; in which case, a more functional site will score in the long-term.

Typical user echoes the following while using any of the above sites:

"where do i look?" "where do i click?" "what do i do?" "how long does this take to load?" "where's the navigation?" "how do i scroll?"

The sad part about these sites is that there's undoubted creativity and plenty of ideas that's gone into the concept and production. But, like most real things, a tool is no good unless you can figure out how to use it. There are multiple ways the sites fail to function. It can be visual clutter, slow loading time, navigation issues, archiving issues, visibility/scrolling issues, etc. Instead, direct the users to certain sections/pages of the site; make your navigation clear; make menus and icons self-explanatory; use proper contrast ratio for higher visibility; and have a clear "call-to-action". More...

Few brands like: Sony, Apple, Microsoft - achieve form without sacrificing function.

Watch this space for the next usability dimension: Findable.

Usability (Dilbert)

Usability Dimension: "Usable"

USABLE.

Last feature discussed few examples and theories about a useful interface. This feature will focus on "usable" aspect of user interfaces. Often, we focus too much on our sites and applications being functionally useful and perfect; also making it very desirable and attractive, but losing focus on the vital concept: ease of use. One reason maybe because the interface-centered methods and perspectives of human-computer interaction do not address all dimensions of website/product design.

Of all dimensions of usability, usable is perhaps one of the closest attributes that is a direct contribution towards user productivity gains. Ease of use minimizes:

• erroneous actions


• need of training


• time spent on tasks

A useful and simple website is going to yield more repeat traffic in long term, even if it's not good to look at.

Few examples of a good balance between "useful" and "usable" and not categorically "desirable":

• gmail


• ebay


• youtube


• wikipedia


• amazon


• imdb


• myspace

The above list, you shall agree consists of few of the most used internet sites and these belong to this category of being usable and useful, but not visually appealing or desirable.  A couple more examples of relatively unknown sites that are "ugly" and still work like a charm because of being usable:

• Plenty of Fish - a very plain looking website that offers a free online dating service much like Match.com (but without the subscription fee). There is nothing specifically impressive about the website that stands out, in fact the site is actually rather ugly. A second look at the website on its reported earnings revealed that it brings in over $10,000 from Adsense – in one day. For those of you counting, that is $300,000 per month and nearly one million dollars in just three months.
  (borrowed from this site)


• Ryanair - audible gasps are possible when you see this site, for its ugly nature. However, Ryanair experiences online bookings to the tune of several millions a year.

Not making your interfaces usable is not a mistake, but outright blunder. Remember, if one of your users gets lost trying to navigate your website, check out of your web store, or finding simple contact information, then you unnecessarily are increasing the chances that this user will simply leave. This particular aspect of usability is best not kept optional. It is a must.

Watch this space as we discuss the next usability dimension: Desirable.

Usability Dimension: "Useful"

USEFUL.

It may be observed that when a website or product is usable, but not useful, it's unlikely to get off the ground. Useful is what generates the interest, serves a need, scratches an itch. Often useful can do without being usable. If your website page has large content that is "useful" for the user making an informed decision/action, you may have to sacrifice on the usability by allowing horizontal/vertical scroll and pop-up/navigation elements. Another standard usability principle suggests alphabetical order of drop-down menus, which is usable in nature, as the users can do without additional cognitive load in narrowing down their choice of action. However, if an unsorted but prioritized menu items are presented to the users based on the most useful options presented first; the system might prove to be more useful after all.

Few Examples of Useful but Low on Overall Usability:

• ecademy


• Most Torrent / Freeware Download sites


• craigslist


• experts-exchange


• only batteries


• flickr


• salesforce (App not Website)


• exactitudes


• igluski

As usability and UI practitioners, we cannot be content to paint within the lines drawn by customers and the known patterns of usability. We must courageously and creatively question the usefulness of the system and functionalities and the user interface elements. Thus, we seek to apply our deep knowledge of craft and medium to define innovative solutions that are more useful.

Watch this space for examples of next usability dimension: Usable.

Dimensions of Usability

Is it more important for your website/product 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 trade-offs are better made explicitly than unconsciously or subconsciously.

We'll attempt to discuss and exemplify various aspects and dimensions of usability and user experience - that should be actively considered for the visualization of our brand, product, website, etc. In a series of blog articles, we'll discuss the following dimensions of user interfaces, singularly:

• useful


• usable


• desirable


• findable


• accessible


• credible


• valuable

Watch this space as we explore the topics with appropriate examples.