THE PROJECT:

Complete redesign of administrative event request management system in web application.

THE PROBLEM: Users were running into roadblocks trying to use a very popular but dated tool in a web application. Feature requests and support tickets were growing steadily.

THE SOLUTION: Development time was slated to rework the tool from the ground up, to make the tool easy to use and learn, while meeting the needs of a varied customer base.

STEP 1: Establish project goals.

between admins, admin reviewers, reviewer element reviewers, and the requestor (student)

COMMUNICATIONimprove 1STEP 1:

Establish project goals.

between admins, admin reviewers, reviewer element reviewers, and the requestor (student)

COMMUNICATIONimprove 1

HISTORY2to maintain and conveyactions and commentson the request

record

STEP 1: Establish project goals.

STEP 2: Define the users who would be interacting with the tool.

STEP 2: Define the users who would be interacting with the tool.

UmbrellaAdmins

STEP 2: Define the users who would be interacting with the tool.

UmbrellaAdmins

AdministrativeReviewers

STEP 2: Define the users who would be interacting with the tool.

UmbrellaAdmins

AdministrativeReviewers

Reviewer Element Reviewers

STEP 2: Define the users who would be interacting with the tool.

UmbrellaAdmins

AdministrativeReviewers

Reviewer Element Reviewers

Students(Requestor)

STEP 3: Interview current customers to gather their feedback, wants, and needs for a better system.

STEP 3: Interview current customers to gather their feedback, wants, and needs for a better system.216 form reviewers

• not ordered•not sent automatically on submission

3 notified admins1 Reviewer-element reviewer (sometimes)

UMBRELLA ADMIN VIEW

STEP 3: Interview current customers to gather their feedback, wants, and needs for a better system.216 form reviewers

• not ordered•not sent automatically on submission

3 notified admins1 Reviewer-element reviewer (sometimes)

UMBRELLA ADMIN VIEW

10 form reviewers2 notified admins1 Reviewer-element reviewer (sometimes)

UMBRELLA ADMIN VIEW

STEP 3: Interview current customers to gather their feedback, wants, and needs for a better system.216 form reviewers

• not ordered•not sent automatically on submission

3 notified admins1 Reviewer-element reviewer (sometimes)

UMBRELLA ADMIN VIEW

10 form reviewers2 notified admins1 Reviewer-element reviewer (sometimes)

UMBRELLA ADMIN VIEW UMBRELLA ADMIN VIEW

3 form reviewers ✓ ordered ✓ start on submission1 notified admin1 Reviewer-element reviewer

STEP 4: Run complete heuristic evaluation of the current tool, acting as each defined user.

STEP 4: Run complete heuristic evaluation of the current tool, acting as each defined user.

STEP 4: Run complete heuristic evaluation of the current tool, acting as each defined user.

I want someone to review event requests. Why did I have to go to a form builder? I should be adding event request reviewers.

STEP 5: Compile results from • heuristic testing• direct user feedback • support tickets• idea board requests and create extensive list of desired system behavior.

STEP 5: Compile results from • heuristic testing• direct user feedback • support tickets• idea board requests and create extensive list of desired system behavior.

STEP 5: Compile results from • heuristic testing• direct user feedback • support tickets• idea board requests and create extensive list of desired system behavior.

STEP 5: Compile results from • heuristic testing• direct user feedback • support tickets• idea board requests and create extensive list of desired system behavior.

STEP 5: Compile results from • heuristic testing• direct user feedback • support tickets• idea board requests and create extensive list of desired system behavior.

STEP 6: Develop use cases for a variety of scenarios and involved users.

Include user behaviors that could throw roadblocks into the flow.

STEP 6: Develop use cases for a variety of scenarios and involved users.

Include user behaviors that could throw roadblocks into the flow.

STEP 6: Develop use cases for a variety of scenarios and involved users.

Include user behaviors that could throw roadblocks into the flow.

STEP 6: Develop use cases for a variety of scenarios and involved users.

Include user behaviors that could throw roadblocks into the flow.

STEP 6: Develop use cases for a variety of scenarios and involved users.

Include user behaviors that could throw roadblocks into the flow.

STEP 6: Develop use cases for a variety of scenarios and involved users.

Include user behaviors that could throw roadblocks into the flow.

STEP 7: Build wireframes and user flows to depict interaction for specific use cases.

STEP 7: Build mockups and user flows to depict interaction for specific use cases.

STEP 7: Build mockups and user flows to depict interaction for specific use cases.

STEP 7: Build mockups and user flows to depict interaction for specific use cases.

STEP 7: Build mockups and user flows to depict interaction for specific use cases.

STEP 7: Build mockups and user flows to depict interaction for specific use cases.

VALARIE MARTIN STUARTuser interface and experience design

After mockups were passed to development,layout and design iteration continued

throughout the building process.

VALARIE MARTIN STUARTuser interface and experience design

And the process as it looks today…

user interface and experience designVALARIE MARTIN STUART

dallas, texas, usa • 972-762-4360 • www.valarie.info