Refactoring an app for Clock-in.
UX/UI Design
5 Persons
Web and Mobile
5 Weeks
How to improve the app to launch it as soon as possible?
Before I joined the team, the Mobteam app was developed exclusively by developers. The initial plan was to launch it internally first, followed by a general release. However, prior to the internal launch, the marketing team and the CEO reviewed the app to create an explanatory portfolio and discovered numerous areas needing improvement. Seeing the situation, I proposed conducting a usability test to identify key improvement points and refactor the application accordingly.
Acting as a UX/UI Designer, I applied a usability test, tabulated the data, and redesigned the application interface based on the collected data.
I worked on a team with other 4 people:
1 Back End Developer.
Including other areas in the Usability Test
Involving devs and QA in usability tests brought valuable insights and showed the importance of understanding user needs. After participating, they recognized the value of user feedback in the design process.
Talk, talk & talk!
Collaborating with devs from the start helped align design with technical constraints, avoid rework, and ensure a smooth handoff from prototype to development.
Working in an environment with low design maturity
I learned how important it is to advocate for UX by showing user reactions and clearly explaining the reasoning behind each design decision in a context with no established design culture.
Before starting the usability test, I talked a lot with the developers who created Mobteam to understand the concept of the product, the choice of features, and their operation. They didn’t have any designers on the team, so we went together, understanding everything we could improve. Then I started exploring the app, screen by screen, to understand each function. During this analysis, I identified points of improvement and started to raise the points that could be included in the usability test script.
I developed the usability test script, which specified specific tasks for users to perform. I recruited 4 internal employees from the company who would be the users of the app, and we conducted the test both online and in person, recording all sessions for further analysis. The Q.A. team and the developers who created the app participated as listeners in the test, noting all points relevant to the application. At the end of the test, I conducted a survey for my colleagues who participated as listeners to understand their perception of the test.
After the tests, I created a board on Figjam and asked the Q.A. team and the developers to add their notes, organized by each user, to facilitate the analysis of the data. I also included my own notes and compiled everything into a spreadsheet in Excel, highlighting the positive, negative, and intermediate points. Then we discussed in teams each highlighted point to elaborate on the backlog of the next version of the app, with the improvements to be implemented by both me and the development team.
With the backlog ready, I created a visual moodboard, analyzing some direct competitors. Then I talked to the developers to understand the components used in creating the application and introduced them to Material Design 3. We decided that, whenever possible, I would use the M3 components to refactor the app. I created the wireframes and validated them with the developers and my coordinator. During this validation, we identified the need to include biometrics in unlocking some functions.
