1 / 9

User Experience Development Process

User Experience Development Process. Gary Macomber ERCOT User Experience Architect. Agenda. Background Expectations of Market Participants and ERCOT The Pieces Background information, team, materials, methods, and results The Full Process All of the steps

duff
Download Presentation

User Experience Development Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. User Experience Development Process Gary Macomber ERCOT User Experience Architect

  2. Agenda • Background Expectations of Market Participants and ERCOT • The Pieces Background information, team, materials, methods, and results • The Full Process All of the steps • The Plan - Part 1, Initial Evaluations What are we doing and when by project • The Plan - Part 2, Integrating UIs Across Projects Looking across projects to UIs in the context of jobs • The Plan - Part 3, Long Range Plan • What’s Happening Where are we and some important caveats UI Development Process

  3. Background Market - TPTF • Existing ERCOT applications have different user interface styles • Market is discontented with existing user experience provided by ERCOT – ease of use, consistency, and integration across applications • TPTF is emphatic aboutthe need for an improved and integrated user experience • Wants to see ERCOT’s plan • Expects ERCOT to follow the plan • Market wants to see emerging designs and to have the opportunity to influence the final products ERCOT – Nodal Program • ERCOT has established User Experience and Visual Design Guidelines and provided these to the vendors • Guidelines establish the UI Development Process as well as expected results in style and design approach This briefing describes the plan for ensuring MPs have adequate opportunity to review market-facing user interfaces UI Development Process

  4. The Pieces User Experience Background Information Project Teams Usability Testing Use Cases Visual Design Guidelines/Industry Standards MPs ERCOT Test Cases User Descriptions Methods Expert Evaluation Materials Card Sort Testing by Users Results Testing by Surrogates Cards Prototypes Wireframes Priority/Impact Live Interfaces Annotated Screens Revised Process Flows Redesigned Screens Revised Visual Design Team UI Development Process

  5. The Full Process Information Architecture Prototype Eval 1 Eval 2 Wireframes Use Cases Production Evaluation Post Production Evaluation Part 2 Part 3 Part 1 • Use Cases/Task Analysis – define activities and order required to perform the activities • Information Architecture – define structure of information across the activities, establish information organization • Wireframes – provide a low fidelity method to evaluate task flow and organization • Prototype – provides a visual representation of the user interface, allows more extensive testing, may involve more than one iteration • Production Evaluation – evaluate the performance of the interface by the intended users performing • Post Production Evaluation – evaluate the performance of the interface after the users have had several weeks to use it This process will be applied to each User Interface, modified based on what the vendor provides UI Development Process

  6. The Plan - Part 1, Initial Evaluations • Goal: ensure individual projects follow user experience and visual design • guidelines • Basis: Design artifacts and individual software evaluation indicates reviews by ERCOT indicates reviews by MPs Not being Performed ERCOT facing UIs only UI Development Process

  7. The Plan - Part 2, Integrating UIs Across Projects • Goal: provide a consistent user experience across applications as users perform their tasks • Basis: end-to-end test cases, user roles UI Development Process

  8. The Plan - Part 3: Long Range Plan • Make User Experience an essential element of the Change Process • Iterative process • Evolutionary process • Goal directed • Form the User Interface Design Council • Market Participant focused, extension of MIS subgroup • Collaborate on designs • Provide means for getting feedback • Structured • System reviews • Surveys • Unstructured • Help Desk ticket analysis • “Comment Box” UI Development Process

  9. What’s Happening • Finishing first round of internal UI evaluations • Readying Market testing of redesigned MMS and first build of MIS • NMMS, CRR and MMS –Testing system in Fall • Starting work on OS • Caveats • Budget impacts may restrict how much a Project does • Where we are at in aggressive schedules may impact amount and timing of updates • COTS software UIs may be more difficult to modify • What do we need • Support for plan • Access to users to test UIs UI Development Process

More Related