160 likes | 509 Views
ISE 298 Professional Seminar San Jose State University October 22, 2003 Jeff English & Scott Robinson PeopleSoft Supply Chain Management. UCD at PeopleSoft. Enterprise Software. Initially focused on: Desktop client software Domain experts are users Complicated back-end processes
E N D
ISE 298 Professional Seminar San Jose State University October 22, 2003 Jeff English & Scott Robinson PeopleSoft Supply Chain Management UCD at PeopleSoft
Enterprise Software • Initially focused on: • Desktop client software • Domain experts are users • Complicated back-end processes • But evolved to: • Web-based UI • “Self-service” interactions • Off-loading work of experts to novice users • This transition has been relatively successful from a technology point of view, but a challenge from a usability perspective
User Experience at PeopleSoft • Central team • Product “pillar” teams • Tools team
How do we get user input now? • Previously: heuristic reviews • Testing without context • Shoot-from-the-hip guidance
Getting user input moving forward… • Iterative prototypes w/ testing • Market + user research • Card sorting and tasks analysis • Developing a partnership with customers and product users through a “UE Partners Program”
What are barriers to change? • Difficulties include: • Legacy organization • Legacy technology • Legacy UI layout and presentation issues • No validation of user assumptions
The Enterprise Development Pyramid Roles it affects: (Who needs to sign off) • CTO • VP of Products & Technology architectural • Tools Group: across all products • Central UE Team behavioral visual Central Team: committee • Development (Programmers) • Strategist (Product Manager) linguistic These roles build on top of one another.
Pyramid: Linguistic Example • What am I supposed to do here? • Language & button text are relatively easy to change
Pyramid: Visual Example • Visual grouping of content on this page is overly complex.
Pyramid: Behavioral Example • Checkboxes are grayed-out, breaking Web conventions. • PeopleSoft “grid” or view of database rows is confusing to new users.
Pyramid: Architectural Example • Application is broken into Components & Pages … • Pages are represented by Tab Navigation.
Pyramid: Architectural Example • Why do I see Bill To Options and its sub-page on the same hierarchical level? • No way to flexibly present secondary navigation. • Instead, this part of the application was broken into separate Components, creating user navigational complications.
Building a New Process and Team… • Team expanded to 3 Interaction Designers and 4 Usability Engineers • Focus on strategy and innovation over incremental improvement • Forging relationships with customers and product users
Questions Thank you! Jeff English Scott Robinson jeff_english@peoplesoft.com scott_robinson@peoplesoft.com