Power user

User testing for software often focuses on inexperienced or regular users.[12] Power users can require different user interface elements compared to regular and minimal users, as they may need less help and fewer cues. A power user might use a program full-time, compared to a casual or occasional user, and thus a program which caters to power users will typically include features that make the interface easier for experts to use, even if these features might be mystifying to beginners.

A typical example is extensive keybindings, like Ctrl+F or Alt+Enter; having keyboard bindings and shortcuts for many functions is a hallmark of power-user centric software design, as it enables users who put forth more effort to learn the shortcuts to operate the program quickly without removing their hands from the keyboard. Power users typically want to operate the software with few interactions, or as fast as possible, and also be able to perform tasks in a precise, exactly-reproducible way, where casual users may be happy if the program can be intuitively made to do approximately what they wanted. To aid in the automation of repetitive tasks during heavy usage, power-user centric interfaces often provide the ability to compose macros, and program functions may be pre-conceived to with the intention that they will be used programmatically in scripting.

In general, the notion is that interface design may have to make trade-offs between the acceptability of confusing beginners and minimalists versus the acceptability of annoying experts or power users. These concerns may overlap partially with the blinking twelve problem, a well-known conundrum of interface design in which engineers who design computer programs often have a poor grasp what users do and don't know about their software: because the implicit goal of bringing a software product to market is to ensure most users will always be beginners (as implied by the hope that the product's market share will continually grow), it may be extremely difficult to both appease lesser knowledgeable and naive users who want software to be intuitive-to-understand, and power users, who want software which, once well-understood, enables them to leverage the greatest use out of it.

However, there are solutions for these problems, such as:

• Product variations
• Operation modes
• More advanced features, options and settings logically separated in submenus.

A 'simple' intuitive interface often increases the complexity of a program and impedes its efficient use, while a 'complex' interface may be more efficient if it does a better job of exposing the functionality of the program and make it quicklier accessible. For example, a program with huge numbers of keyboard shortcuts may seem to be needlessly complex, but may in fact be much easier to use for an experienced power user, since keyboards have far more buttons than mice, and a program where most of its behaviour is exposed via the keyboard will require fewer total button pushes than a program in which all functions and behaviour are only accessible via long sequences of mouse clicks to navigate menus. Providing both interfaces simultaneously is an option, but in turn this requires greatly extended development time, and so trade-offs are often made.

SAP and Oracle are well known enterprise systems which often require a complex set of training in order to gain professional certification. Because of this, and also to encourage engagement with the systems, many companies have created a "Super User Model" (also called Power User, Champion) in order to take regular users and raise them to a level of leadership within the system. Doing this accomplishes three objectives:[7][8]

1. More engaged use of the system as there is a personal face assigned to champion the system and make acceptance of the technology less challenging.
2. A significant time and cost reduction as companies are not seeking or hiring new or temporary resources for the purposes of developing and/or delivering documentation, training, and support.
3. ROI or proof of concept of the SAP investment should be more easily achieved as users are directly involved, thereby using the system invested in, which benefits the company overall.

Extensive research has been done with the Super User Model in SAP, specifically in regard to the role they take in training and supporting end users. Currently, more than 70% of SAP companies utilize a form of the Super User Model.

In Microsoft Windows 2000, Windows XP Professional, and Windows Server 2003, there is a "Power Users" group on the system that gives more permissions than a normal restricted user, but stops short of Administrator permissions. If a user is a member of the Power Users group, they have a greater chance of exposing the system to malware over a normal user and can promote their account to an Administrator by purposely installing malware.[13] Thus, the Power Users group should be used with trustworthy and knowledgeable users only; it is not suitable to contain untrustworthy users. The Power Users group has been deemed obsolete in Windows Vista as part of the consolidation of privilege elevation features in the introduction of User Account Control.[14] In Windows Vista Business l or higher, you can still create a "power user" via local users and groups, but there is no difference from a standard user because all the ACL entries of the file system are completely removed.