Challenge

There is a category of operational problem that rarely appears in management reports: the tool that works, but gets in the way. It doesn't fail enough to generate support tickets, nor does it noticeably paralyze operations. Still, it creates constant friction: an extra click, information that's hard to find, an interface that requires effort to interpret each time it's used.

For the warehouse clerk, this translates concretely to: impaired readability due to small fonts under artificial lighting, difficulty locating actions on the screen, and time spent finding the correct field. When multiplied by the volume of SKUs per shift, it ceases to be an ergonomic detail and becomes an invisible operational cost.

This was the point where LinkedBy's inventory app found itself. It worked, but it didn't help those who depended on it.

LinkedBy develops solutions for complex logistics operations, such as ERP, WMS, route planning, and fleet management. Its inventory app is used by checkers in Heineken distributor warehouses, where the context imposes clear demands: variable lighting, dynamic operation, time pressure, and a high volume of SKUs with subtle variations. A system designed outside of this environment fails not due to technical limitations, but due to misalignment with real-world use.

The request for Evo Systems was straightforward: redesign the experience so that the app would keep pace with the operation.

The analysis revealed a set of decisions that, individually, would be acceptable, but together created an interface that was difficult to read in the context of use.

The header followed the Android standard, in navy blue, without any client branding. The cards displayed only code and name in text, without visual support, which, in a scenario with similar packaging, transferred the responsibility of differentiating items to the operator. The typography was minimal and the layout dense, without a clear hierarchy. The editing modal, a critical step in the counting process, did not reflect the operational logic in the organization of the fields. The absence of a brand filter made navigation dependent on scrolling and continuous reading. The buttons followed the system standard, without indicating priority or consequence.

All of this together demanded a constant effort of adaptation from the operator, an effort that does not contribute to the task.

Transformation_

The redesign was conducted in Figma over the course of a week. The starting point wasn't the interface, but the context of use: who operates the app, in what environment, under what time pressure, and with what volume of SKUs. Each design decision only entered the project after having an operational reason to justify it.

• Visual identity on the login screen:  The login screen now displays Heineken branding, logo, and green color palette. In multi-client operations, the visual identity at the entrance eliminates ambiguity about which instance the operator is accessing and positions the product as a solution belonging to that operation, not as a generic tool.
• Product cards with integrated image: The cards now display a photograph of the product alongside the code and name. In a warehouse with variations in packaging by brand, size, and type, the image serves as an immediate visual verification. The checker confirms the product by its appearance before reading the code, reducing reliance on memorization and the margin for confusion between similar SKUs.
• Filters by brand at the top of the list:  The filter bar segments the product list by manufacturer with a single tap. In a count that traverses physical sections of the warehouse organized by brand, the filter mirrors the logic of the physical space in the interface logic. The checker does not need to scroll through the entire list to find the products in the section they are in.
• Visual hierarchy in operational fields: The redesign established a clear reading order: code and name highlighted at the top of the card, followed by the fields for counting by physical category, Pallet(s), Box(es) and Loose(s), and then by the control fields, Expiry Date, Lot, Stock Location and Stockout. This sequence replicates the order in which the checker verifies the product in the field, reducing the need for visual searching at each record.
• Editing mode reorganized: The release correction modal received a field organization that reflects the same logic as the main card. Fields are grouped by type, and buttons have a clear visual distinction between confirm and cancel, reducing the risk of editing in the wrong field.
• Handling system states: The app began displaying explicit confirmation and error messages for submissions. In an operation where silent failures—data recorded locally but not synchronized—can lead to recounts or inventory discrepancies, status feedback ensures that the operator knows what the system has done.
• Count history: The history screen now records the date, start time, end time, and total number of items counted per session, enabling basic operational traceability.

Benefits_

The redesign did not produce measurable impact data within a week of implementation, and it would be incorrect to claim error reductions or speed gains without structured measurement. What the redesign delivers is the viability of a more reliable operation.

A clerk operating with product images, brand filters, and a clear visual hierarchy can perform the count with fewer workflow interruptions. An interface that confirms submission and alerts about failures gives the operator visibility into the status of the data they recorded. A session history provides management with traceability that the previous system did not offer. These are the conditions that the redesign creates: not guaranteed results, because results depend on operation, training, and process. But without these conditions, the results are limited by the interface.

The app is in production. LinkedBy now has a tool that treats the work of the checker with the seriousness that the operation demands.

Tools used_

• UX/UI Design

The project was conducted in Figma, used as the central environment for exploring, validating, and prototyping the interfaces. More than just a design tool, Figma served as a collaborative space for structuring decisions based on the operational context, allowing for rapid iteration on flows, visual hierarchy, and information organization.

The approach was guided by UX/UI principles applied to the real-world usage environment, focusing on readability, reducing cognitive effort, and aligning the interface with field operations. The result did not depend on complex technology, but on the rigorous application of design as a tool to solve operational problems.