Seahawk is a comprehensive messaging system designed to handle all messaging needs across 48 bases. Currently used for various purposes such as callouts, announcements, and marketing, Seahawk aims to streamline communication processes efficiently.
To enhance Seahawk's capabilities, the project will focus on several key areas. Firstly, we'll prioritise integrating essential functionalities like DV Locate and overdue vessel management. This integration will ensure that critical messages related to vessel positions and overdue statuses are efficiently managed within the Seahawk system. Additionally, we'll implement features that allow base profiles to create user groups and lists. This will enable more targeted and organised message distribution, improving overall communication efficiency across the 48 bases.
Next, we'll address the complexities of managing non-critical communications. By creating separate databases and tailored delivery methods for non-critical messages, we'll ensure that mission-critical messages receive priority within Seahawk's framework. This approach will streamline communication processes, allowing users to distinguish between urgent and routine messages effectively. Furthermore, enhancements such as scheduling SMS and template creation functionalities will be developed. These features will optimise communication processes, allowing users to schedule messages in advance and create standardized templates for common communication scenarios.
Lastly, we'll focus on user management to ensure efficient message distribution while maintaining data security. Implementing tiered access levels will enable us to cater to different user groups' needs. Regional managers, for example, will have access to multiple bases within their region, while base members will only access their own base's information. By addressing user management complexities, we'll create a user-friendly experience that promotes effective communication and collaboration across all bases. Through iterative development and user feedback loops, Seahawk will evolve into a robust messaging solution tailored to diverse communication needs.
The target for MR SMS portal is their internal team, age range is 40+ and training sessions will be required to teach them how to use the portal, understanding the needs and behaviours of members was undergone by interviews with members, competitor research and observation sessions to gather insights into their navigation habits, pain points, and preferences.
As there was no existing web app, the previous user research step was vital to designing the right system for MR. To help visually present to the product to the board at MR HQ, micro user flows were identified and mapped out so they could easily understand how it will work, how their organisation will us it and the benefits that come from that. This will help later on to identify key touchpoints, any possible routes or steps a user may take and how to use the SMS portal emotions, and potential friction points to optimise the user experience.
When starting to build out the hierarchy of the page, we wanted to ensure that we developed a clear and intuitive information architecture that organises the system's features and functionalities logically. In particular, prioritising essential elements such as SMS sending, Template creation, multiple access levels within members, trip monitoring, SKED alerts, and emergency protocols for easy access. Before starting to build out wireframes and designs in Figma, sketches were done to understand the desired hierarchy of each page.
From here, we applied a cohesive visual design language that aligns with the MRNSW brand identity while promoting usability and engagement. Colour, typography, and imagery were strategically used to convey important information and guide users through their journey. A design library was built out in order to build a cohesive design system. Figma was used for both the design and prototyping of key features. This makes the project easier to walk through with the developers and ensure that I can present and explain my designs effectively. I worked alongside the developers to get to the end product that we were able to launch.
In the 2 months post launch I conducted iterative rounds of user testing with members to gather feedback on the prototype's usability, effectiveness, and overall user experience. This allowed us to identify areas for improvement and refine the design based on these user insights. Due to the age range of the intended users, certain accessibility considerations were taken to ensure the system adheres to accessibility standards and guidelines. This way we ensure that we accommodate users with diverse needs and abilities. We did this my implementing features such as keyboard navigation, screen reader compatibility, and high contrast modes for enhanced accessibility. Responsive design did not need to be considered for this product as it is intended to be desktop only within HQ. We maintained a continuous feedback loop with members and stakeholders to address evolving needs and opportunities for enhancement. And regularly analysed user feedback, metrics, and usability testing results to inform iterative improvements to the UX design.
