Swedavia Alarm and Firefighter Management System

Full UX / Ui System Redesign

Dashboard, User Management System, Alarm Report Creation Forms, Alarm Management System, Alarm Response Environmental Report System, Firefighter Training Management System, Firefighter Work Schedule System

Swedavia Alarm and Firefighter Management System

Full UX / Ui System Redesign

Dashboard, User Management System, Alarm Report Creation Forms, Alarm Management System, Alarm Response Environmental Report System, Firefighter Training Management System, Firefighter Work Schedule System

Swedavia Alarm and Firefighter Management System

Full UX / Ui System Redesign

Dashboard, User Management System, Alarm Report Creation Forms, Alarm Management System, Alarm Response Environmental Report System, Firefighter Training Management System, Firefighter Work Schedule System

Project Summary

Role


UX Lead


Role


Ux Researcher

Product Designer

Duration


16 weeks


Duration


16 weeks


Year


2024


Year


2024


Program


Figma


Program


Figma


Category


SAAS


Mission


To increase easy and speed of use throughout the system, alongside allowing simple and direct access to required information to allow for faster task completions.

Mission


To increase easy and speed of use throughout the system, alongside allowing simple and direct access to required information to allow for faster task completions.

Mission


To increase easy and speed of use throughout the system, alongside allowing simple and direct access to required information to allow for faster task completions.

User Pain Points


  1. Convoluted flows to complete central tasks.

  2. Difficulty finding required reports - reports sorted arbitrarily between multiple databases, each assessed through a different path.

  3. Hard to scan report forms for information.

  4. Training schedule hard to use, unable to be displayed in entirety, have to tip head to read column titles.

  5. Within training schedule, hard to see which firefighter had not completed which training.

User Pain Points


  1. Convoluted flows to complete central tasks.

  2. Difficulty finding required reports - reports sorted arbitrarily between multiple databases, each assessed through a different path.

  3. Hard to scan report forms for information.

  4. Training schedule hard to use, unable to be displayed in entirety, have to tip head to read column titles.

  5. Within training schedule, hard to see which firefighter had not completed which training.

Solutions


  1. Redesign of systems structure and Ui components to create simple single function flows.

  2. Merge reports storage system into a singular searchable and filterable database.

  3. Introduce informational hierarchy, standardise placement of common fields between forms, simple, visual data representation.

  4. Redesign form Ui with responsive vertical colour sizing.

  5. Present current and previous years training data on different schedules so current missed training can easily be identified.

Solutions


  1. Redesign of systems structure and Ui components to create simple single function flows.

  2. Merge reports storage system into a singular searchable and filterable database.

  3. Introduce informational hierarchy, standardise placement of common fields between forms, simple, visual data representation.

  4. Redesign form Ui with responsive vertical colour sizing.

  5. Present current and previous years training data on different schedules so current missed training can easily be identified.

Main Problems Faced in Design


  1. No discovery or research stage to the project.


  2. Understanding use cases for systems' functions.


  3. Duplicate form fields - understanding which duplicates are a result of mislabeling and hence require relabelling; and which are unintentional duplicates.


  4. Designing a standard form layout allowing consistence of specific input field placement.


  5. Client's familiarity with and high acceptance of old systems flaws.


  6. Shifting and unclear expectations, system goals and use case scenarios from client.


  7. Keeping the ux considerations embedded within the ui present after implementation from the development team.

Main Problems Faced in Design


  1. No discovery or research stage to the project.


  2. Understanding use cases for systems' functions.


  3. Duplicate form fields - understanding which duplicates are a result of mislabeling and hence require relabelling; and which are unintentional duplicates.


  4. Designing a standard form layout allowing consistence of specific input field placement.


  5. Client's familiarity with and high acceptance of old systems flaws.


  6. Shifting and unclear expectations, system goals and use case scenarios from client.


  7. Keeping the ux considerations embedded within the ui present after implementation from the development team.

Solutions


  1. Understanding the purpose of each system requirement through client and product owner contact and meetings;, and reference to the clients requirement specifications (kravspecifikationer)


  2. see a

  3. see a


  4. 1st.Identifying fields common to all and placing them on the form in appropriate grid place based on input order and informational importance,

    2nd Identifying and mapping the relationships between fields appearing on more than one form.

    3rd Developing a layout guide that allows for the maximum amount of standardisation whilst maintaining a compact, above the fold, layout.


  5. Utilising as much of the old systems structure and flow initiation points so the changes although visually drastic still feel intuitive to those used to the old system.


  6. Regular client meetings combined with taking meeting notes for accountability and reference.


  7. Work in conjunction with development team, explain rational behind design decisions.

Solutions


  1. Understanding the purpose of each system requirement through client and product owner contact and meetings;, and reference to the clients requirement specifications (kravspecifikationer)


  2. see a

  3. see a


  4. 1st.Identifying fields common to all and placing them on the form in appropriate grid place based on input order and informational importance,

    2nd Identifying and mapping the relationships between fields appearing on more than one form.

    3rd Developing a layout guide that allows for the maximum amount of standardisation whilst maintaining a compact, above the fold, layout.


  5. Utilising as much of the old systems structure and flow initiation points so the changes although visually drastic still feel intuitive to those used to the old system.


  6. Regular client meetings combined with taking meeting notes for accountability and reference.


  7. Work in conjunction with development team, explain rational behind design decisions.

User Discovery & Empathising

Being brought onto the project at a late stage, in order to lead the existing design team, I was not involved in the discovery stage.

Within my review of the project I found that no investment had been made into research. The projects direction had solely been driven based on the clients specification document, however this approach provides no clarity or insight on optimal execution. I had to proceed with design decisions based on my understanding of UX heuristics and user optimisation.

Due to this, I planned to do early usability tests on our reviewed designs in order to anchor them within real world data.

Being brought onto the project at a late stage, in order to lead the existing design team, I was not involved in the discovery stage.

Within my review of the project I found that no investment had been made into research. The projects direction had solely been driven based on the clients specification document, however this approach provides no clarity or insight on optimal execution. I had to proceed with design decisions based on my understanding of UX heuristics and user optimisation.

Due to this, I planned to do early usability tests on our reviewed designs in order to anchor them within real world data.

Ideation

Due to the redesign nature of the work, the required functionality of the design was predefined. For this reason the ideation phase was concerned with finding the optimal implementation of these functions.

Initially, this took the form of understanding the previous systems user flows in order to improve the information architecture and system navigation.

Through this work we streamlined the system, reducing clicks to access central functions, merging several flows that provided the same functionality and unified parts of the system that provided similar functions.

We also conceived of a standardised form layout that placed common information in the same place within each form and displayed this information so it could be more easily visually scanned.

We also tackled the scheduling system, prioritising placement of required information on the parent page and deprioritising less important information to child pages.

Due to the redesign nature of the work, the required functionality of the design was predefined. For this reason the ideation phase was concerned with finding the optimal implementation of these functions.

Initially, this took the form of understanding the previous systems user flows in order to improve the information architecture and system navigation.

Through this work we streamlined the system, reducing clicks to access central functions, merging several flows that provided the same functionality and unified parts of the system that provided similar functions.

We also conceived of a standardised form layout that placed common information in the same place within each form and displayed this information so it could be more easily visually scanned.

We also tackled the scheduling system, prioritising placement of required information on the parent page and deprioritising less important information to child pages.

Design, & Prototype

Design, Prototype & Tests for Mobile

Having used Ux principles to identify the previous systems weaknesses, we proceeded to build a testable prototype which solved these issues whilst adhering to the clients requirements and attempted to maintain as much consistency with the old system to allow for easy adoption.

Redesigning the landing screen to house a dashboard displaying key information on firefighters training and alarm trigger information so that admins can better process and make more use of the information held within the system.

Redesigned the navigational system so that all aspects of the system can be accessed from a singular side bar. This was done to reduce the space needed on the screen for navigation, which in turn allowed more space for data display; reduced the distance the mouse had to travel and the amount of clicks need to access different areas of the system.


The all of the windows and forms were redesigned so that they could be displayed 100% above the fold, allowing all information to be seen at the same time.

Merged the alarm creation tab and the alarm storage tabs into a singular alarms tab. During this process we also placed all alarms within the same database so that all alarms could be accessed or searched for from the same place.


This reduces the necessary of prior knowledge of the systems structure hence reducing onboarding times. It also increased speed of use as it is no longer necessary to leave one databank and enter another in order to view information on different alarm types.


We also introduced an advanced search function to allow specific data to be accessed quickly.

Created a standardised form layout which places common fields in the same position across all forms to increase speed and ease of completion.


This form layout also places the most predominant information in the most prominent place and represents information where possible in a more visual way.

These two changes, combined with the standard layout allow for quicker scanning and comprehension of information.


We also used click boxes rather than typing or drop down menus to reduce clicks and increase speed of filling out each form.


The final major change was to Add a 'saved feedback screen' so users can be sure their work has been saved, not that the page timed out or a similar fault occurred on saving the filled in form.

Separated current year and previous years trainings into two separate tables, making it more clear and easier to see which firefighter has yet to complete a necessary training.


We also introduced a filtering system, active on both current and previous training tables so that admis could quickly access the data they needed within an information heavy table.


We also removed the red representing a non completed trainings and instead left a blank space to reduce visual stimulus overload.


We also grouped the firefighters into their work groups to make finding a particular firefighter much easier.

Reworked a new form layout again so that 100% of the form is above the fold.


Divided the form into two functions, one to provide information on the training overview and another to allow management of the specific training days/times.

Reworked a new form layout again so that 100% of the form is above the fold.


Divided the form into two functions, one to provide information on the training overview and another to allow management of the specific training days/times.

Created a more prominent profile section to reduce mistakes misidentifying which firefights trainings is being viewed.


The previous version was very hard to read and understandi the presented information. We streamlined this information into a table display information clearly.


Furthermore we Isolated important data with a highly visual presentation format, eg ability to see progression through EASA training, making vital information easily accessible.


And again the entirety of the form is above the fold.

New feature - Working day schedule


Opens on on the primary function page, the current days schedule.


Has a monthly calendar overview displaying which firefighter group is working on which day to allow each firefighter to plan into the future. This function is made easier through a function which highlights their work days based on their working group.

Initial Design Changes

Usability Testing

Usability test write up and data will follow shortly.

Have a look at a few full case studies.

Have a look at a few full case studies.