top of page
Frame 1.jpg
Connecting workflows within a complex maritime platform.
and validating the need for an improved platform communications and notification system/product to support it!​ 
 
Group 30.jpg
presentation_download.jpg
​

Context

​

Our mission was to roll out a complete digital transformation for a well-known private maritime company over a 2 - 4 year period. This included providing a complete suite of cloud-based products, tools and services (via a single platform called Open Ocean Studio) to replace numerous outdated and disconnected tools, processes and manual ways of working.

This also included dozens of software solutions and products to be built across the broader organisation, including iOT, shore and vessel based software and hardware, auditing, crewing and dozens of operational management tools.

​

This specific study fast forwards one year, when a number of products had already been designed, dev'ed and delivered. However there was still a major problem which we estimated accounted for approximately 30-50% of their "spent" time during an average working day. (based on our teams qualitative research). So essentially we need to bridge the workflows gaps with triggers, notifications, and better cross department methods of communication.

OOS Product Ecosystem

Problem / Opportunity

​

The problem was initially hidden from plain sight. Over the course of dozens of discovery workshops with different teams during the first couple of years, we began to notice there was a few issues that continually resurfaced during our user interviews = which was 'transparancy and accuracy of information. Every team shared similar feedback, however when talking with the teams one by one over nearly 2 years, it only account for about 10% of the feedback each time, so it wasn't proritised as a problem that needed solving immediately.

​

However, by the end of the second year, that ten percent feedback had come up so many times, if you added them all together - became a serious problem for the business.

 The challenge for me in this case, was how do I present this issue and demonstrate it to our leadership team,

​

This presentation was created in order to demonstrate to our internal teams and customer, the impact from a single change in decision to an itinerary and it's impact to all the workflows already in place. Also to highlight the dependancies between teams on workflow hand offs between departments.

 

Towards the end of the presentation, we took the opportunity to identify and conceptualise the need for a solution which aggregated all relevant information together for the required users in the form of a dashboard - where they could monitor activity and action tasks relevant to their roles. (This screenshot shown towards the end).

​

(example from presentation below shows the domino effect of a cancelled port call on multiple teams within the organisation a the high level of interoffice communications surrounding it)

cs1_scenariosbusy.png

Discovery

​

Once support from the rest of the business was achieved, the team began conducting a number of workflow mapping and collaborative discovery/ design sessions with department heads. This was done in an effort to understand how their existing enterprise workflows looked and how they worked when they also intersected with one another. The Image below is one of the these mapping sessions used to identify the workflow for onboarding for a new member of crew.

​

​

workflow mapping (2)_edited.jpg

​

Definition

​

After a number of collaborative design sessions. with the teams, this resulted in the creation of a new product called ‘OnRadar’. OnRadar worked in a similar way to a task management system and 'live actions' board for the company.  

(below highlights the "OnRadar" product - an eventual outcome of the above attached workflow presentation).

​

OnRadar was successful in providing various departments and teams, improved communication workflows, transparency and trust in data. A huge win for the target audience and bold step towards providing a new default "view" of their daily workflows.

onradar.jpg

Case-study on request.

​

Unfortunately, not everything can be shared in public.  If you'd like more information around any of the below, please get in touch.

​

  • How we identify the problem and communicated the opportunity

  • The opportunity, empathy and problem statement to testing, measuring and optimising workflow optimisation

  • Design systems / scaling horizontally.

  • Collaborated on this project with multiple teams across the organisation

​

Group 30.jpg

get in touch

mailbox

E: daniel@dccwhite.com

W: dccwhite.com

M: +49 15206386916

  • LinkedIn
bottom of page