Using everything we know about how people gather information, think, understand, remember, and act to design effective technology.
Our approach recognizes that the human is an integral part of the system. If the pilot can't use the control stick effectively or gather information from the flight displays efficiently, the flight won't be a good one.
Characteristics of human perception, cognition, and motor response determine your success with any piece of technology.
Applying scientific knowledge to the design of technology. Dropping a log across a creek isn't the same as building a bridge. Effective technology optimizes user performance, appeals visually, and minimizes costs.
Yes we can. Both in terms of quality of the user experience and the cost of a bad experience.
In 2006, the International Organization for Standardization (ISO) published its standard for usability test reports (ISO/IEC 25062). Three measures of usability are required: Efficiency, Effectiveness, and Satisfaction. These measures can be made on any technology that a human uses. We have been using the standard since it was released in draft form (1998) as part of the Industry USability Report (IUSR) Project.
How productive is the user in accomplishing a goal? Measuring time, physical effort, trips to help resources. Design for less time, less effort, and less variability from one user to the next.
How good is the outcome? Measuring accuracy and completeness with which users achieve specified goals. Design for fewer errors and a better result.
How satisfied are the users? Measuring ratings to standardized surveys that go beyond "did you like it". Design for user confidence, understanding, interest, and independent action.
A bad user experience is a cost. Here are three perspectives on the cost of poor usability
Bad review by Walt Mossberg in the WSJ? Analysts at USC and University of Miami put big $ values on poor quality (The Value of Quality). The difference between a bad review and a good review can swing investors toward or away from the producing company.
Compare the cost of Human Factors Engineering to the revenue to be gained. Discover and eliminate roadblocks to successful use. A back-of-the-envelope formula can scope the ROI.
When chasing time-to-market, don't forget that immature (unusable) products are slow to gain market acceptance. The cost of correcting usability issues and providing customer support push the breakeven point out even further.
Usability follows from knowing what "work" the user will do to achieve what "goal". Design to aid the user, not to force the user to expend superhuman effort. Human Factors involvement at product definition is the most efficient use of everybody's time.
Do you need a Human Factors Engineer (HFE) for every technology project? Probably not - but the smarter you are about usability, the better you'll do at picking a log to drop across the creek. The following are two good rules of thumb for where an HFE really makes a difference.
The value of user performance increases with the cost of the technology and the cost of a failure resulting from using the technology. That's why there are lots of HFSs in aerospace and power systems design. What will your technology cost you or your customer? What will it cost you or your customer if the technology fails to execute its mission?
The value of user performance increases with the difficulty of the task and frequency of execution. That's why there are lots of HFEs around phone companies. Managing complexity (and the errors that go with complex tasks) reduces the cost per task and the costs of cleaning up errors. How complicated will the user find your task? How many times a week/day/hour will the user have to deal with that complexity?
Human Factors Engineering happens right along with the rest of the product development cycle.
Gathering information about the end goal and the work required. Documenting the perceptual, cognitive, and motor response requirements. Then rebuilding the task with technology that transforms the user's ability to reach or go beyond the goal.
Putting the user in direct contact with the transformed task. Optimize rate of learning, ease of performing, and accuracy of execution. Design of methods, displays, and controls for use across the system. Mapping tasks to methods, displays, and controls.
Measurements with or without a working system. Formal usability testing puts potential users in the task using the design. Analytical models such as keystroke-level models (KLM) and GOMS models predict user performance based on know performance characteristics and mathematical equations. What's the cost of omitting tab-between-fields in a standard address entry block? A 10% increase in completion time.
O’Brien Consulting is a human factors engineering firm. The business was incorporated in 1998 in Cupertino, California - the heart of Silicon Valley. We moved to Leawood, Kansas, a suburb of Kansas City, in 2002.
Our business is human factors engineering - applying the science of human performance to the design of technology. The founders, Kevin and Kim O’Brien, have a combined 40 years helping teams build the processes, information displays, and input methods that make up a product's user interface.
Ph.D., Applied Experimental Psychology, Rice University
Co-founder of O’Brien Consulting, Kim was a staff engineer at Sun Microsystems for eight years. While with Sun, Kim evaluated and designed software and documentation across Sun’s product line. Projects included UNIX desktop applications, system administration tools, and web-based e-commerce applications.
Prior to Sun Microsystems, Kim did human factors work for Lockheed Engineering & Sciences at Johnson Space Center and Canon Information Systems.
Ph.D., Experimental Psychology, University of Kansas
Kevin has over 20 years experience providing human factors expertise in consumer computing, network administration, customer care systems , human resource and medical records systems, and on-line help.
Prior to forming O’Brien Consulting, Kevin was a senior human factors engineer in the telecommunications industry (Pacific Bell) and aerospace industry (Lockheed Engineering & Sciences at Johnson Space Center).