Royal Caribbean
Overview
Shoreside employees
While at Royal Caribbean I was tasked with designing the Shoreside Crew app. The app would replace an outdated intranet platform that served to connect, assist, and engage the global land based employees of the massive cruise shipboard fleet . Shoreside represents all land-based employees; including everyone at the global offices, from IT professionals, to sales, to janitors.
Along with functional features like news, a digital key and wallet, the shoreside crew app presented an opportunity to engage and involve the entire employee base by having diverse and inclusive content from all satellite offices. We wanted to create a product that encouraged employees to engage and see themselves reflected in the experience . Content strategy needed to be visited and reworked, and not just duplicated from the company’s intranet.
Business goal: Enable full visibility to usage and performance of assets, prohibit costly and redundant content creation
User goal: Enable reusability and visibility of content and atomic assets across channels, authors and audiences.
UNIFYING THE VISION
In conjunction with product leaders, I facilitated discovery workshops to craft user stories from high level concepts. Conducted user research by contacting leaders from different lanes of business to schedule sessions with employees. These HCD workshops also allowed us to understand the how to prioritize the possible features that would benefit our user. Our team was not fully in agreement with the viability of all features so further workshops helped us to find middle ground. My role was mainly to advocate for the user while holding a firm understanding of business obligations obligations. These sessions served as a starting point for streamlined artifacts such as site maps and user flows which informed the deliverables in our agile sprints.
Provided expertise: User research | Service design | HCD workshop facilitation
Design System Contributions
I knew that when I joined the Excalibur team, I was jumping onto a speeding train. I connected with teams with more mature products to understand how the product I owned would fit into the ecosystem.
Along the way, each designer had the responsibility to audit the UI, vet patterns, and document them in our shared library. The design system was a living, breathing reference developed out of an emergent strategy.
OUTPUT
The following features were decided upon for our beta release: Home Feed, News, Resources, People Search, Meeting Scheduler, Ship Finder, Account.
These features allowed users to connect with one another, locate each other, access career advancement portals, find their way to a meeting, schedule meetings and more.
It was key to align very closely with QA and developers to make sure the builds matched the original intended designs. Through iteration, several stakeholder design reviews, some serious derailments and time constraints, a beta version was built over the course of my time at Royal Caribbean.