Unlock new features with tables

Context

Due to the orders increasing during the high season, most warehouse-related professions (managers or operators) need to optimize their daily operations in the RMS (Reuse Management System).

Some actions have to be handled in series, with no possibility of batch processing. Furthermore, some informations are not immediately visible; it is necessary to scroll the screen to consult them. The hierarchy of information is not always optimal, and it is not possible to sort it easily.

Problem understanding

🐳 What's the problem?

Tables are not very usable or configurable. We also have several types of tables.

🐼 Why do we want to solve this problem?

Standardized styles and use of tables.

To be able to filter and manage the columns you wish to display, their display order, etc. The aim is to personalize our working environment.

🐝 Who are we solving this problem for?

Mainly for the profiles that use the tool most often: warehouse operators and managers.

🦊 What are the use cases? JTBD ?

• As an RMS user, I want to be able to filter and sort in a table according to a particular criterion, to find information more quickly.
• As an RMS user, I want to be able to customize the columns I want to display, and the order in which they appear, so that I can go about my day-to-day work more quickly, and have data that is useful for my needs.
• As an RMS user, I want the customization I do on the tables to be persistent for my use, so I don't have to redo all the settings I've made each time I use it.

Stepping back

🤠 Customer's point of view : How important is the need? Is it something that needs to be addressed quickly? → the tables work today, but the infos displayed aren't necessarily useful for all users. 2/5

📏 Opportunity size : How many users are involved? How often? → 2/3 of users or more (only brand project managers are less concerned by this feature). 4/5

🌍 State of the art on the market : Could this opportunity bring about a change in our positioning? Would it make us stand out from the competition? → positioning more focused on tool customization. no real big differentiation there, other than supporting our UI/UX at a good level. 3/5

🥚 In-house : What impact would each opportunity have on the company? On the different teams? → Time and productivity savings for operators and managers, who will be able to focus on the right data. 4/5

The need to improve table customization seems moderate, with a widespread opportunity among the majority of users. As the internal impact on productivity remains one of our main pillars, we have decided to invest in this functionality.

KPI(s) to follow :

• Number of tables left as default vs. user-customized tables
• Number of custom tables per month
• Time spent customizing tables
• Table pages bounce rate
• Average number of table customizations per month (if users modify their tables every month, we may have missed a key point)

Wireframe and Prototype

After compiling the requirements, we focused on the most critical functionality based on feedback from our personas.

Feedback has been conclusive: the interface seems simple, but we need to convince you with Hifi mock-ups to get a better idea of the situation.

We decided to create the components in the design system and the mock-ups, and then present them to as many users as possible (mainly an internal panel) using Maze.

Progressive deployment

It takes several weeks of iterations to agree on a flexible component in the Design System that allows full latitude for composing tables in mock-ups.

Once the first mock-ups had been produced and validated, we were able to gradually implement the new tables in the application. This enabled us to be more reactive to any changes that needed to be made, while keeping on planning the next functionalities that would benefit from the redesign.

Results

Since implementation, feedback has been positive, because in addition to providing practical benefits, new functionalities have been unlocked thanks to the board's capabilities. What's more, other needs are emerging that are easier to implement thanks to all the work done previously.