top of page
thisisengineering-raeng-uOhBxB23Wao-unsplash.jpg

Oodles Dashboard: The Ultimate ERP Solution

  • Oodles Dashboard is an ERP solution designed to simplify and integrate business processes via artificial intelligence and machine learning.

  • The target audience for oodles dashboard was mainly internal users of Oodles technologies and clients from all across the globe.

  • As a UX writer and content specialist my role was centred around creating an effective flow via UX copies and compelling content that allows users to navigate through the tool, reduce intrusions and friction while using the Dashboard

  • For this project, I had to work closely with UI designers, frontend backend developers, QAs and product team.

Surveys

Objective: Dashboard is being developed on agile methodology of project development. Therefore after the first couple of scheduled releases I wanted to gather feedback from the existing users. Henceforth, I set up an online survey and asked existing users (internal users and external users) to fill it.

Detrimental factors and Course of Action:

  • The strategy followed a mix of in-depth, short, detailed and on-site surveys at different levels of the organisation and units to understand the quality of overall user-experience while using the Dashboard

  • 165 users (External and internal) out of 200 gave their valuable time and filled out the surveys

  • Some of the major insights and observations that I got from the survey are as follows:

    1. There were confusions and lack of awareness about the usability and features of the different functionalities incorporated within the dashboard

    2. Users complained about absence of a help centre within the tool

    3. Some of the design elements were unable to portray the required details and nuances which turned out to be a major downside.

    4. The user flow at some instances was not appropriate and created ambiguity amongst the mind of the users.

    5. Lack of appealing colours and aesthetic UI

     

  • The key decisions made based on the survey are as follows:

    1. Defining flow and creating UX copies for a help centre that would guide users in using the dashboard

    2. Compiling features to define the scope usability clearly amongst the mind of the users

    3. Identifying inappropriate design elements and their corresponding UX copies to edit, update or eliminate them from the flow

    4. Creating seamless User flows based on user centric approach

    5. Collaborating with designers to add appealing aesthetics and colourful UI

Personas

Objective: Based on the surveys/research and analysis we set up three personas groups. We referred to them throughout the entire product development process.

Driving Factors

  • During brainstorming for creating new and updating existing copies I decide to incorporate user personas in the process

  • The major methods that helped in the process of developing user persona were User research, involving stakeholders, and studying existing users to create a link between new and old users

  • The information provided for each persona group is as follows

    1. Location: where do people from this persona live?

    2. Age: what is the average age/age range of this persona?

    3. Gender: are people representative of this persona predominantly male or female?

    4. Relationship Status: Single? Married? Children?

    5. Interests: what are the general interests of people in this persona?

    6. Language: what is the primary language used by people in this persona?

    7. Favourite Websites: where do people in this persona go to learn new information?

    8. Education: what level of education do they have?

    9. Job Title: what is/are typical job titles for people in this persona?

    10. Responsibilities: what does a typical work day look like for people in this persona?

    11. Frustrations: biggest challenges for people in this persona?

    12. Motivations: what motivates people in this persona to be successful?

    13. Personal/Professional Goals: what do they wish to achieve?

 

Screenshot 2022-06-22 at 11.11.05 PM.png
Screenshot 2022-06-22 at 11.11.24 PM.png
Screenshot 2022-06-22 at 11.11.42 PM.png

Drafting Contours
 

Objective: At the beginning of the process I drafted contours to understand the requirements, align them strategically and move further.

Points to Ponder:

  • I always prefer drafting broad contours instead of creating copies immediately after looking at the design as it allows me to absorb and understand the design. Moreover, it gives me time to synchronise the copies with the design to come up with best results

  • I studied the problems faced by users while interacting with the dashboard and came up with the outline of the help centre

  • Before being finalised and approved it had to go through several changes, additions and improvements

  • I rigorously followed the practice of competitor analysis to come up with concrete concise and design friendly content

Help Center

The Help Center was the one most important and demand activity in the course of action from the design and product perspective. It encompasses detailed information and guides to help a typical user navigate through the tool effectively with minimal friction.

XD link: https://xd.adobe.com/view/532a8384-ea72-4a2c-9ac5-6d50e718e7a7-0679/?fullscreen

Screenshot 2022-06-22 at 11.24.07 PM.png

User Testing

Before launching the product, I did a testing round in order to reveal possible usability problems.
 

Guiding Points

  • The objective of conducting testing was to identify gaps and issues with language used in the app.

  • The testing was conducted after the QA release of the app.

  • The test subjects were children and students from different backgrounds who were using the app.

  • Testing was conducted in both remote and moderated modes.

  • The testing provided detailed insights about areas that were complex for the users to understand.

  • The insights helped me to change the language and voice of the application to enhance the quality of usage and user experience holistically.

 Key Learnings

  • Working on dashboard allowed me to overcome my fear of complex screen lineups and software development based projects. It played an extremely important role in helping me grow professionally.

  • Dashboard helped to understand the development cycle and process of software product even clearly

  • It has been one of the most challenging projects, but at the same time allowed me to learn new skills and polish my UX skills

Screenshot 2022-06-22 at 11.32.04 PM.png
bottom of page