Event Manager
Summary: A web-application that allows for tracking of events was designed and developed. This project took an idea and turned it into an application using UX methodologies, working closely with stakeholders, performing user testing, and collaborating with developers. Development went smoothly and a beta version of this product is currently being used within the organization. There are plans to expand this product to over 150,000 users, allowing for a dramatic reduction in licensing costs, and removing the need for third-party support.
-
Both Business Requirements and User Requirements were collected during a three day event. This event included a wide-range of stakeholders across multiple sub-organizations. Collected requirements were grouped in a similar fashion to a MosCow model, allowing us to determine prioritization . This allowed us to create User Stories quickly and ensure that all necessary requirements were met upon our first release.
-
User personas were created according to theoretical users that were hypothesized during initial requirement gathering. Initial and theoretical user personas were compared with a sample of potential users and edited accordingly.
-
Card sorting was utilized to ensure that the appropriate grouping and sub-categories made logical sense and that this product could be scaled for future use.
-
A diagram of User Flows was created that utilized the Infrastructure Diagram and Business Requirements previously gathered. This User Flow allowed us to test mockups through the user flows to ensure that goals could be met.
-
Once mid-level-fidelity was completed. Interactive features were added in. This allowed for additional user testing. Most user testing was completed using prompt-based methodologies. Users were asked to perform a certain task and then asked to explain their though process as they completed that task.
After initial tests were completed, users were given the ability to ask any questions, This data was gathered and summarized, allowing for design modifications to resolve issues found during user testing
-
Beta testing is nearing completion and we have made the application available for specific use-cases. We are currently working on adding features that were outside of the MVP scope. Once the selected use cases have been run successfully, we plan to scale-up to 150,000 users.
Requirement Gathering
Both Business Requirements and User Requirements were collected during a three day event. This event included a wide-range of stakeholders across multiple sub-organizations. Collected requirements were grouped in a similar fashion to a MosCow model, allowing us to determine prioritization. This allowed us to create User Stories quickly and ensure that all necessary requirements were met upon our first release.
User Personas
User personas were created according to theoretical users that were hypothesized during initial requirement gathering. Initial and theoretical user personas were compared with a sample of potential users and edited accordingly.
Infrastructure Architecture
Card sorting was utilized to ensure that the appropriate grouping and sub-categories made logical sense and that this product could be scaled for future use.
User Flow Diagrams
A diagram of User Flows was created that utilized the Infrastructure Diagram and Business Requirements previously gathered. This User Flow allowed us to test mockups through the user flows to ensure that goals could be met.
User Testing
Once mid-level-fidelity was completed. Interactive features were added in. This allowed for additional user testing. Most user testing was completed using prompt-based methodologies. Users were asked to perform a certain task and then asked to explain their though process as they completed that task.
After initial tests were completed, users were given the ability to ask any questions, This data was gathered and summarized, allowing for design modifications to resolve issues found during user testing.
Results
Use of this tool has expanded beyond the initial set of beta testers and we have made the application available for specific use-cases. We are currently working on adding features that were outside of the MVP scope. Once the selected use cases have been run successfully, we plan to release the application to specific groups within the company and then scale-up to 150,000 users.