August 2024 - February 2025
team of 6
remote
Figma
web & mobile
AMOS — while robust — was never built for today’s distributed, mobile workforce. Crew members had no direct access to their personal or job-related data. Every change, from bank account updates to new travel documents, required manual entry by office-based administrative staff using a legacy desktop system. The workflow was slow, error-prone, and overly reliant on human intermediaries.
Seafarers taking control of their own data
The Crew Portal was designed for active crew members working aboard vessels or traveling between contracts. These users needed a secure, self-service platform to view and manage:
Pay slips and
earned leave days
AMOS ERP: the user experience
BEFORE
Translating legacy logic into intuitive, responsive UX
I was responsible for shaping the Crew Portal experience from the ground up - translating AMOS’s legacy logic into a modern, user-friendly interface. I created a responsive design system that supported both the initial web app and the upcoming native mobile rollout.
... my responsibilities included:
Researching and mapping legacy workflows to inform UX decisions
Developing a component-based UI kit for scalable design delivery
Desinging responsive UI designs for desktop and mobile
Creating clickable Figma prototypes for testing and engineering handoff
Coordinating implementation with frontend/backend developers
Designing for progress inside a legacy-bound product ecosystem
While the Crew Portal was new, it wasn’t built from a blank slate. It had to mirror AMOS’s backend behavior and preserve UX patterns that originated in a 1980s desktop architecture. Admins still relied on concepts like manual submission validation, so the interface needed to reflect those workflows clearly.
On top of that, the product was to be deployed on-premise, requiring close collaboration with developers in order to navigate infrastructure limits and system access protocols.
Research
Research & reverse-engineering legacy workflows
Started by analyzing how AMOS handled crew data - translating legacy desktop workflows into actionable UX patterns.
IA & User flows
Designing for clarity within technical boundaries
Mapped new user flows that respected AMOS’s structure while simplifying tasks for crew members and admin reviewers.
UI design
Component system & responsive UI in Figma
Built a reusable component library in Figma and designed screens across desktop and mobile viewports, laying the foundation for future modules.
Collaboration
Handoff, development & iteration
Worked closely with frontend and backend engineers during implementation, supporting with QA feedback, design fixes, and layout adjustments.
A responsive tool that reshaped how crews engage with their data
Delivered in 6 months and adopted by 2 clients operating 60+ vessels
Clients reported notable reduction in administrative workload, freeing staff for review instead of data input
Used in SpecTec sales demos and helped secure follow-up projects, including a native mobile app and integration with the onboard Security of Crew (SoC) module
Design system reused in the next product module (Procurement) to ensure UI/UX consistency
Successfully deployed on-premise, tailored to client infrastructure constraints
Designing around legacy logic requires strategy, not resistance
Legacy UX patterns often carry invisible logic — sometimes requiring adjusting of design instincts to accommodate how legacy systems expect data to flow.
My engineering background helped bridge technical understanding across design, frontend, and backend teams.
Helping non-technical users means thinking beyond product UI; designing a guided help chatbot showed me the power of lightweight support layers.
