The user experience process of redesigning a web application feature, from identifying the problem through delivery of mockups to development.

1. THE PROJECT:
Complete redesign of administrative event request
management system in web application.

2. 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.

3. 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.

4. STEP 1:
Establish project goals.

5. between admins,
admin reviewers,
reviewer element reviewers,
and the requestor (student)
COMMUNICATION
improve
1STEP 1:
Establish project goals.

6. between admins,
admin reviewers,
reviewer element reviewers,
and the requestor (student)
COMMUNICATION
improve
1
HISTORY
2to maintain and convey
actions and comments
on the request
record
STEP 1:
Establish project goals.

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

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

9. STEP 2:
Define the users who would
be interacting with the tool.
Umbrella
Admins
Administrative
Reviewers

10. STEP 2:
Define the users who would
be interacting with the tool.
Umbrella
Admins
Administrative
Reviewers
Reviewer Element
Reviewers

11. STEP 2:
Define the users who would
be interacting with the tool.
Umbrella
Admins
Administrative
Reviewers
Reviewer Element
Reviewers
Students
(Requestor)

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

13. STEP 3:
Interview current
customers to gather their
feedback, wants, and
needs for a better system.
16 form reviewers
• not ordered
•not sent automatically on
submission
3 notified admins
1 Reviewer-element reviewer
(sometimes)
UMBRELLA ADMIN VIEW

14. STEP 3:
Interview current
customers to gather their
feedback, wants, and
needs for a better system.
16 form reviewers
• not ordered
•not sent automatically on
submission
3 notified admins
1 Reviewer-element reviewer
(sometimes)
UMBRELLA ADMIN VIEW
0 form reviewers
2 notified admins
1 Reviewer-element review
(sometimes)
UMBRELLA ADMIN VIEW

15. STEP 3:
Interview current
customers to gather their
feedback, wants, and
needs for a better system.
16 form reviewers
• not ordered
•not sent automatically on
submission
3 notified admins
1 Reviewer-element reviewer
(sometimes)
UMBRELLA ADMIN VIEW
0 form reviewers
2 notified admins
1 Reviewer-element review
(sometimes)
UMBRELLA ADMIN VIEWUMBRELLA AD
3 form revie
✓ ordere
✓ start o
1 notified ad
1 Reviewer-

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

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

18. 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.

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

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

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

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

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

24. STEP 6:
Develop use cases for a
variety of scenarios and
involved users.
Include user behaviors
that could throw
roadblocks into the flow.

25. STEP 6:
Develop use cases for a
variety of scenarios and
involved users.
Include user behaviors
that could throw
roadblocks into the flow.

26. STEP 6:
Develop use cases for a
variety of scenarios and
involved users.
Include user behaviors
that could throw
roadblocks into the flow.

27. STEP 6:
Develop use cases for a
variety of scenarios and
involved users.
Include user behaviors
that could throw
roadblocks into the flow.

28. STEP 6:
Develop use cases for a
variety of scenarios and
involved users.
Include user behaviors
that could throw
roadblocks into the flow.

29. STEP 6:
Develop use cases for a
variety of scenarios and
involved users.
Include user behaviors
that could throw
roadblocks into the flow.

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

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

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

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

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

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

36. VALARIE MARTIN STUART
user interface and experience design
After mockups were passed to development,
layout and design iteration continued
throughout the building process.

37. VALARIE MARTIN STUART
user interface and experience design
And the process as it looks today…

43. user interface and experience design
VALARIE MARTIN STUART
dallas, texas, usa • 972-762-4360 • www.valarie.info