FEDERAL AVIATION ADMINISTRATION.
Building the next generation web-based Aerospace Medicine Safety Information System (AMSIS). A platform that guides over 4 million external and internal users through medical certification and drug test protocol for air safety.
Lead a team of 2 designers
Project Management: TFS
Prototyping: Axure, Figma
Project duration + Team
4 UX Designers
2 Business Analysts
6 Development Teams
Retire 5 FAA legacy systems into one to maximize efficiency and minimize paper handling for sixteen diverse business units.
Wireframe of new external-facing landing page for applicants and medical personnel.
User Research + Business Analysis.
FAA (client) provided over 2,000 system and business requirements. Our team analyzed and decomposed the requirements into design and technical specifications for the AMSIS delivery teams. To further understand the end-users' needs, the UX team conducted ethnographic studies at the FAA (CAMI) headquarters in Oklahoma City. To continue the stakeholder and end-user feedback loop, the UX team organizes and facilitates monthly engagement workshops to validate business processes and screens.
Below is a snapshot of example user flows and workflows co-created with SMEs during one of the user engagement events.
There are over 47 user-roles that fall under one of two main AMSIS portals, Drug Abatement and Medical. In place of traditional personas - the team uses the 'Jobs-to-be-done' framework. Where we analyze each specified role and define their situations and motivations. This is an important step to take in order to develop accurate user-flows and screen interactions.
Internal users: manage registrations and conduct annual reviews on airline employers of essential workers who have direct access to US planes and air time.
External users: Upload documentation and evidence for review.
External users: submit applications and medical exam information.
Internal users: review and allocate medical certification and clearance.
Airmen (pilots / air traffic controllers)
Due to FAA brand and visual specifications. The AMSIS team architects guided us on determining the use of PrimeNG as the main UI component library. This gives the UX team some visual and functional constraints which allow us to determine quickly what is feasible from an interaction perspective.
Figure Description: Wireframe of the scheduler's dashboard when logging into AMSIS.
Here is a glimpse of the interactive prototype created to follow the Scheduler's 'job-to-be-done' story mentioned above. As you can imagine this is a beast of a project and does contain classified information therefore this prototype has been scrubbed for public viewing. Please keep this in mind when previewing.
Integrating into the Agile process.
The overall process of user research and screen validation is a reoccurring activity. The static wireframes and interactive prototypes that are produced during this time are used to guide business analysts when creating the backlog user stories. It also provides a visual guide for dev and testing teams. As the UX lead I helped guide the team in integrating into the SCRUM team to explain UI interaction decisions and observe functional constraints that may influence future screen designs.
Creating these screens/prototypes helps expedite the agile development process and has allowed for the team to continue to create visually consistent UI and a 508 compliant web-app.