Screenshot of wireframes for the desktop based application I worked on at Lloyds Register
Wireframe of the 'My Service Requests' page - bringing a usable, logical, actionable layout to the engineer's to-do tasks was a crucial element in getting this complex project to work.
Screenshot of wireframes for the desktop based application I worked on at Lloyds Register
Wireframe of the 'Scope' page - simplifying the complex task of scoping a ship to be surveyed was one of the most complex tasks to design for - creating a 3 step system allowing engineers to manage their surveys made this once complex task easy with a step-by-step process.

Designing a desktop app

I was hired by InfoSys Lodestone as the Senior UX on a project for their client Lloyds Register. I was responsible for every aspect of UX - user journeys, site architecture, experience design and additionally the UI design and I created digital brand guidelines.

Lloyds Register needed a new and modern desktop-based online/offline capable app that would allow maritime engineers to evaluate ships whilst out in the field. It needed to work seamlessly in an offline capacity while deep in a ships bowls as well as in a connected office environment.

I designed user flows that catered to this online/offline requirement along with other documentation to suit the client's needs. This meant producing interactive Axure wireframes, a sitemap, user flows and annotated still wireframes for the various page templates that made the many user journeys.

Complexities and roadblocks

The project wasn't big in size but it was complex. Lloyds Register is an old company with some entrenched working practices which was highlighted when interviewing engineers in the company. It was discovered that for the most part, that the engineers preferred pen and paper rather than tablets and laptops and that they weren't overly keen on using software to enter their data. This was partly as a result of their experience with the current systems that Lloyds Register's were using. Software that was very clunky and repetitive to use and seemingly without consideration for the user. So the new application had to be intuitive and friendly, easy to use and be straight forward. No 'IT-speak', ill-thought through user journeys or even poorly worded system alerts. And no endless menu-based navigation to complete their tasks, something they currently had to endure.

The project was run in waterfall methodology with requirements being gathered via Use Case documents that were fleshed out in more detail during workshops. I had to encourage the team and the client to try not to 'solutionise' their problems, but instead lay them bare so they could be captured and turned into requirements, allowing for proper UX thinking to be applied across the board.