Restructuring products on app homepage

Restructuring products on app homepage

Restructuring products on app homepage

CLIENT

Ame Digital

ROLE

UX Designer

TIMELINE

6 months

RESPONSABILITIES

RESPONSABILITIES

Design and deliver new product

Organize the team

UX strategy for UK

Conduct the redesign

UX strategy for UK

From discovery to delivery

Context

The Ame app is a digital wallet focused on offering simplified forms of payment, in addition to facilitating people's daily lives through a variety of products and services.

Challenges

Some products will no longer be available; With the turn to IP (Payment Institution), we understand that the way we present products/services in the app is still very relaxed and informal.

We need to prepare the app for removing the products that are going to be withdrawn, and present the products in a more attractive, reliable, and objective way.

HIGH LEVEL GOALS

Generate better use of the tool by users

Automating work in the stone processing industry

Increase product relevance to customers

Increase product relevance to customers

impact

Unfortunately, I don't have any information about changes in performance.

DESIGN PROCESS

This is the design process that I created for this project.

DISCOVERING THE CHALLENGES

I had some hypotheses about the tool, which I then tried to validate through interviews with users.

The hypotheses were:

  1. There are many features and screens that the client is not using;

  1. The programming screens are not meeting the customers' needs, they are laid out in a way that is difficult to understand;

  1. We believe that the client has used other ways of organization (spreadsheets, papers, etc.), leaving the platform aside.

  2. Using a mobile device would make it easier to maintain the transmission data and record information.

I created a script and interviewed 8 workers who operate the cutting, polishing, and resin machines in the industry. The questions were focused on the routine of how they do it today, evaluation of the experience with the platform, and ideas for improvement.

The interviews were carried out in the industry, work environment of the interviewees.

Some points stood out in the interview:

All respondents use the platform on a daily basis in a common work day, the tool is extremely important in their routine, but they don't use all tools.

Elimination of paper

They still use a lot of paper to document processes. Transporting these forms to the platform could facilitate the routine and ensure more security for the information.

A mobile responsive version would not be helpful.

They deal daily with corrosive substances and a lot of dust, which would make it difficult to handle a cell phone or tablet to take notes on the desktop.

DISCOVERING THE CHALLENGES

I had some hypotheses about the tool, which I then tried to validate through interviews with users.

The hypotheses were:

  1. There are many features and screens that the client is not using;

  1. The programming screens are not meeting the customers' needs, they are laid out in a way that is difficult to understand;

  1. We believe that the client has used other ways of organization (spreadsheets, papers, etc.), leaving the platform aside.

  2. Using a mobile device would make it easier to maintain the transmission data and record information.

I created a script and interviewed 8 workers who operate the cutting, polishing, and resin machines in the industry. The questions were focused on the routine of how they do it today, evaluation of the experience with the platform, and ideas for improvement.

The interviews were carried out in the industry, work environment of the interviewees.

Some points stood out in the interview:

All respondents use the platform on a daily basis in a common work day, the tool is extremely important in their routine, but they don't use all tools.

Elimination of paper

They still use a lot of paper to document processes. Transporting these forms to the platform could facilitate the routine and ensure more security for the information.

A mobile responsive version would not be helpful.

They deal daily with corrosive substances and a lot of dust, which would make it difficult to handle a cell phone or tablet to take notes on the desktop.

building the persona

At that moment I already had the necessary information to start the ideation process, so I drew the persona, in order to summarize the knowledge acquired in the discovery, to then go on to create screens.

analyzing the process

In order to understand the process and possible bottlenecks, I built a complete flow of how the rocks that arrive in the industry are managed. Note the post-its in orange, they all report processes that are done through a printed form, thus corroborating the employees' main complaint.

building the style guide

I started creating the style guide, keeping the brand colors and creating auxiliary colors for feedback and alerts needed on the platform. I opted for Lato typography, for fluid reading and easy cognition. For the components, I used the icons and components provided by Material Design as a basis.

wireframing

I started creating sketches for the screens in medium fidelity, in order to validate the functionalities and flows before proceeding to create the prototypes. The main objective at that time was to transform the opportunities for improvement found into functional and simple-to-use screens.

  • Paper forms replaced by virtual forms on the platform;

  • More simplified screens in flows;

  • Text hierarchy and usability principles properly applied;

  • Guaranteed consistency.

prototyping

With all the specifications prepared, I started creating the prototypes, then applying the built styles and creating the components in their final version. These are some of the screens created (the brand was hidden to ensure customer confidentiality).

in retrospect

I planned to run a usability test, but I had some difficulties in the execution, such as:


  • The choice of the type of experiment was not the best for the scenario. I tried to meet the customers' requests and apply a test in Figma, providing the simulation of use in the navigable prototype. Today I would opt for the Maze tool to collect more assertive information about specific flows, not about all flows.


  • The budget cap had already been compromised by the other steps, so customers thought it best to carry on as it was, without running another test.

in retrospect

I planned to run a usability test, but I had some difficulties in the execution, such as:


  • The choice of the type of experiment was not the best for the scenario. I tried to meet the customers' requests and apply a test in Figma, providing the simulation of use in the navigable prototype. Today I would opt for the Maze tool to collect more assertive information about specific flows, not about all flows.


  • The budget cap had already been compromised by the other steps, so customers thought it best to carry on as it was, without running another test.