Apologies! but as per the Non-Discloser Agreements (NDA) between me and the client (Pycube) I can't use business name, logo and any kind of brand identity. So! here I am going to name this app 'Field Tracker'.
The client planned for some pilot app for different industries. One of those is 'Field Tracker' focusing the backend tracking for logistic industry.
They have separate parallel app for customers and support.
Problem Statement:
Enhancing the enterprise application’s usability to provide a smooth and intuitive experience for users (every employee).
Project Summary:
This UX case study focuses on optimizing the enterprise application’s interface and interactions to better serve its users.
Goals and Objectives:
Improve user engagement and retention by simplifying navigation and incorporating intuitive features. Reduce user frustration by addressing pain points in the existing app.
Target Audience:
Employees aged 20–60 with varying levels of tech-savviness, seeking a seamless and hassle-free user experience.
Research Methods:
Conducting contextual interviews and usability testing to gather insights into user needs and pain points within the app.
Design Process:
Applying user-centered design principles to redesign key app screens, validating changes through user testing and feedback.
Users of FielTracker application are limited and restricted. And because of that, all most every situation was certain.
The kick-off meeting served to establish the scope and objectives of the project. Following this, we had a series of stakeholder interviews to better understand the context of the project. We interviewed the CEO, the Head of Marketing, and the Head of Product, who provided us with their understanding of the market and long-term vision for the bank. On top of that, the Business Owner provided information on technical limitations and design restrictions, while sales and customer support employees shared the knowledge, they had accumulated on interacting with the beta application as end-users.
We had our kick-off meeting. We collected materials from the previous researches, such as personas, jobs to be done, and usability tests.
In order to better understand where potential pain points were likely to arise, we ran workshops for each segment with the teams, ultimately mapping out the user journey.
A research plan was created with the objectives and the research questions. In total, 15+ interviews and usability tests were conducted.
Empathy map is used in design thinking to gain a deeper understanding of a user's perspective, thoughts, feelings, and behaviors, helping to identify their needs and motivations.
What they Say: Direct quotes or paraphrased statements from users about their experiences.
What they Think: Users' thoughts, motivations, and needs, framed in first-person statements.
What they Do: Typical or observed user behaviors and actions.
What they Feel: Users' emotional states during the process.
Helped team understand user needs, behaviors, and motivations.
Provided insights to inform product development and design decisions.
Helped teams communicate user insights effectively, especially to stakeholders.
Encouraged teams to "get inside the heads" of users.
At first, we kept our designer ego aside. We had no taste-choice-option. All that only users had authority to possess.
Our research suggested that the major problem for employees trying to view all the necessary data on clicks.
In the second part of our sessions, we gave our participants a few tasks in order to test the usability of the beta application. This was the point where we uncovered the problems those were mostly design-related (mostly contrast, alignment and proximity). All the findings were collected, processed, and presented to Business owner.
Contrast: Can never see all the data clear. Background and font color difference is low. Too many colors irritate users.
Repetition: Can never see the uniformity within the app or even a page.
Alignment: Can never find data with in content. Positioning not done properly.
Proximity: Can never understand the subject and body. Not grouped properly.
Hit the image to view larger in modal
Inside CMS a total of 300+ pages are there. Only (Search > Loan >) Loan Master is explored.
Functional testing is important. But how the application looks in addition to how it works is also important. Often times, the UI of an application can pass a functional test, while design elements that are visually defective can go under the radar. Visual bugs can be annoying or unpleasant to users, but they can go beyond inconvenience to be more severe. In fact, visual inconsistencies can affect the user journey in a way that makes it difficult or even impossible to complete their intended actions even though the test is functionally proficient.
Every page, every element was checked one for one in different operating systems and devices. Uniformity and look & feel verified. On finding of any design issue, development team was requested to make changes and returned us a newer copy. This loop continued till 100% accuracy reached. Related production redlines and mockups are always suggested to them.
This heat map is a graphical representation of user activity on CTO app for initial 14 days after successful deployment.
New & Imaginative Ideas. View things in new ways. Generate new possibilities and alternatives. Solution is guaranteed.
People talk a lot about and I do it, that make my Client feel proud. It makes the Brand easier to remember and for longer time.
It turns a very ordinary thing into more Attractive one. Kind of a magic it works like but not an illusion.