ISIN Tool

Product Design

A large proportion of this project was based upon journey mapping techniques. This project involved a huge collaborative method between departments under very strict timeframe. To read more about the methods and processes involved scroll down

Introduction

This project was based on developing a platform to help in the purchasing of ISIN codes. ISIN (International Securities Identification Number) codes are identification numbers that companies can assign to assets. We started this project with the objective of creating a singular consolidated platform that would bring together multiple different products. The product would allow client-side users to approve or decline requests with end users by performing tasks. The project also allowed client-side users to communicate easily with the end user so that if there was an issue within the request they could be resolved efficiently. A large proportion of this project required using journey mapping methods and involved a huge collaborative method between departments in the company. A variety of developers and designers were in collaboration throughout the project under a strict timetframe.

Problem Solving

During our data collecting and research analysis phase of the project it was found that clients were currently using multiple plaforms to perform singular tasks. For example, they might move from their email to a spreadsheet based product, back to their email, then to a reference based product before moving back to their email. It was found that the client may have used several different patforms to perfom one task. Our aim was to centralise all data required to one space. In order to achive this we set upon designing one system that could support the multiple platforms currently being used by the client. This project involved using task analysis, user shadowing, user journey mapping and interviews with stateholders. Based on feedback we then evaluated the multiple products being used and evaluated how and why they were used. We also evaluated each task to determine those that were unnecessary or overly elaborate. This then allowed us to redesign the tasks to be more efficient in the new design.

My Role

My role in this product was as the lead product designer. My tasks involved working with the lead developer in collecting data. I gathered feedback from clients and carried out all UX and UI tasks throughout.

Research

The initial phase of the reserach began by interviewing the client alongside the lead developer, business analysist and project manager assigned to the project. Our aim was to gather as much data as possible during the initial meeting with the client and to figure out what aspects of the product they deemed most vital. It was also used to determine what could be achieved within the timeframe set out. Following the initial client meeting we started the user journey mapping phase. The clients then followed up with a step by step walkthrough of the tasks they were performing which we used to assist in the data collection during our task analysis phase. Other UX research techniques used during this project were user shadowing and storyboarding.

User Journey Mapping

After the initial meetings with the client we started with user journey mapping phase. We started by analysing each action the client was performing when completing a task. For example when the client wanted to respond to a query or when a new item was sent over via email. These were then added in and mapped out to see how we could introduce the tasks into the new design. Due to the complexity and volume of tasks that were being conducted by the client we decided to use a blended approach of skemma and journey mapping techniques to try and provide an overall view of the product we were designing. The skeema design provided us an architectural overview of the design while the journey mapping allowed us to view the processes that were required to be following when completing a tasks.

Concepts & Prototyping

Although the product is primarily used on a large desktop screens for the users, the End users (Clients users) would be using numerous types of media to access the product on there end therefore consideration needed to be given to this when designing the product. In starting to develop the concept and prototype I began at designing the initial wireframes for the project. After the designs for the first ‘clickable’ wireframe was completed I used the data collected from the journey mapping phase to build up the system using mock flow. The mock flow wireframes were sent over the client for internal testing. The wireframes phase allowed us to collect additional data from the internal users on the usability of the product. After this initial adjustments were made to the wireframes I started to design the min to high fidelity mock up’s of the product using Figma. Using Figma I developed prototypes for ourselves to internally test. Through this we could test for issues, errors and blocks within the product. I used a design system based on an atomic approach of atoms, molecules and organisms to build up the different modules. This design system allowed me to quickly prototype the remaining features of the product to give a consistent UI feel.

Figure: A Final concept of the Users Request Dashboard

Learnings

Due to the agile method of this project we were required to hand designs off for quick testing and development by our internal teams. Overall, I found the introduction of the design system really helped the developers and myself with this project. Wireframes gave a great insight into the most commonly used tasks that were completed by the internal users and end users. Finally, using Figma allowed for ease of hand over to developers and for fluid transitions for our team to go from concepts to working prototypes. It was found during the research phase that there was an enormous amount of information that the internal users had to be able to scan through with relative ease. Tables where the most obvious choice for displaying information although they have their limitations in terms of scalability. For example, the responsive requirements where partially hindered by the use tables. When attempting to design this project initially, due to the complexity, it was required to produce a project of robustness rather than an elaborately animated product. In this project I introduced the design systems described for the first time within the company. I think their introduction successfully assisted the developers and the development team when creating the live prototype as I was able to concurrently create the next features of the product. This improved efficiency within the project as it ensured that there was no variance between different developers and also helped to improve the speed at which the project could be completed. This project was successful in fulfilling its brief by using agile and consistent methodology between departments in the company.

About me

A little bit about myself. I have worked as a designer for the last seven years. Completed a Masters in Interaction Design from NCAD. I love working with people and in teams, and have a massive interest in design not just as a career but as a hobby. Outisde of work I like to be outdoors biking and hiking, and playing golf terribly.