UX Design Process: Unplugged Sandra Loop, Sybase iAnywhere <insert your name here>

UX Design Process: Unplugged High-level description of need … … to an application that meets the user and business needs with a fantastic user experience. Interactive & informative … covering the whole process in various depths.

High-level description of need …

… to an application that meets the user and business needs with a fantastic user experience.

Interactive & informative … covering the whole process in various depths.

Scenario Mobile trouble ticket application Appliances R Us , Repair & Maintenance Division “ Appliance Repair Engineer downloads the tickets to the mobile device. He reviews the tickets and reports what action was taken (eg. fixed, ordered part, replaced part). The status of the ticket can be sent to the back end so that the ticket dispatcher can track progress and assign/reassign tickets to the Appliance Repair Engineers. The updated tickets will be uploaded to the back-end for processing and immediate billing.”

Mobile trouble ticket application

Appliances R Us , Repair & Maintenance Division

“ Appliance Repair Engineer downloads the tickets to the mobile device. He reviews the tickets and reports what action was taken (eg. fixed, ordered part, replaced part). The status of the ticket can be sent to the back end so that the ticket dispatcher can track progress and assign/reassign tickets to the Appliance Repair Engineers. The updated tickets will be uploaded to the back-end for processing and immediate billing.”

Define boundaries of system Define business needs and ROI with specific metrics Understand users’ characteristics Personas (of users and clients) Job shadowing Document as scenarios or use cases Design Information Architecture Design lexicon Design User Interface / Experience (with increasing level of fidelity) Non-functional requirements Design branding / look and feel Write test cases Design for testability & supportability Document the system Involve the trainers Formal usability Design checkpoints Competitive benchmarking Beta Pilot Measure success against metrics What Activities Can We Do?

Define boundaries of system

Define business needs and ROI with specific metrics

Understand users’ characteristics

Personas (of users and clients)

Job shadowing

Document as scenarios or use cases

Design Information Architecture

Design lexicon

Design User Interface / Experience (with increasing level of fidelity)

Non-functional requirements

Design branding / look and feel

Write test cases

Design for testability & supportability

Document the system

Involve the trainers

Formal usability

Design checkpoints

Competitive benchmarking

Beta

Pilot

Measure success against metrics

Mockup: Stakeholder Review

Mockup: Stakeholder Review

Mockup v.2: User Review

Mockup v.3: User “in the Field”

Mockup v.3: User “in the Field”