Challenge
The visible request was to replace dedicated handheld scanners. Discovery revealed a deeper operational problem: store teams depended on fragmented tools, disconnected workflows, and limited visibility to complete everyday work.
I recommend viewing case studies in landscape orientation.
Retail Operations Platform
Turning a scanner replacement initiative into a scalable operating platform for store execution, inventory workflows, task management, and manager visibility across 900+ retail locations.
- client
- LOTUS'S
- year
- 2025
- role
- Product Design Lead
- scale
- 900+ stores
- platform
- Android + desktop
- focus
- Product Strategy, IA, Design Leadership
Solution
We reframed the initiative as a platform transformation. Instead of recreating scanner behavior on a phone, the product unified task management, scanning, inventory workflows, and operational oversight within a shared mobile architecture.
BUSINESS PROBLEM
The challenge was not hardware. It was the way operational work was organized.
Daily execution was split across separate tools. Employees switched context to finish routine tasks, while managers could see individual processes but not the full operational picture. As new workflows were added, complexity grew faster than the platform could support.
DISCOVERY INSIGHTS
Discovery changed the product from a scanner app into an operating system.
We studied complete store journeys rather than isolated interface moments: how employees start a shift, receive tasks, scan products, resolve exceptions, and return to the next priority.
Four insights shaped the platform: scanning was part of larger workflows, roles needed different operating models, employees needed direction more than personal analytics, and consistent patterns would scale better than locally optimized screens.
The product strategy shifted from tools to operating model.
The goal became one device, one application, and one operational platform: a system that could absorb new workflows without increasing cognitive load for store teams.
OPERATIONAL MODEL
The platform was organized around how work unfolds during a shift.
We separated urgent system-initiated work from employee-initiated operations. Tasks became the primary entry point, while scanning, inventory checks, price verification, and logistics tools stayed available inside the flow.
01
North Star on the home screen
Customer Happiness and Daily Revenue became shared operational indicators, helping employees connect daily execution with business performance.
02
Tasks before navigation
Associates entered a prioritized queue instead of a generic menu, reducing the effort needed to understand what mattered now.
03
Operational tools inside workflows
Scanning, inventory checks, label printing, and price verification became steps inside work rather than separate destinations.
04
Manager oversight by exception
Managers received a dashboard focused on workload distribution, bottlenecks, and unresolved operational issues instead of raw activity noise.
CONSTRAINTS & LEADERSHIP
The product had to improve operations without disrupting them.
As Product Design Lead, I shaped the product architecture, facilitated discovery, aligned product decisions with business goals, and helped move design discussions from interface preferences toward operational efficiency.
The strongest design work happened inside constraints: legacy processes could not all be redesigned, business KPIs had to stay visible, and AI-assisted automation had to wait until the organization was ready to support it.
ConstraintDesign Response
Legacy hardware mindsetReframed the work around platform strategy
Busy shop floorPrioritized short flows and clear task states
Role differencesDesigned separate entry models for associates and managers
Existing processesSupported current operations while leaving room to simplify later
Future automationPrepared the architecture for AI-assisted workflows without forcing premature features
PLATFORM ARCHITECTURE
A scalable structure for operational work.
Instead of organizing the product around isolated features, we defined operational domains that gave users and product teams a shared mental model. This made the platform easier to learn, maintain, and extend.
Core domains
Dashboard, Tasks, Operations, Inventory, Scanning, Performance, Notifications, and Profile gave every workflow a clear place in the system.
Reusable interaction patterns
Recurring execution patterns were standardized so new operational workflows could be added without retraining employees on every process.
Design system foundations
Shared components and interaction rules across Android and desktop reduced implementation ambiguity and supported a consistent operational experience.
Automation readiness
The architecture was prepared for future process automation and AI-assisted operations without adding disconnected AI features too early.
OUTCOMES
- Unified scanner replacement, task management, inventory workflows, and operational processes into one platform direction.
- Established a scalable product architecture prepared for company-wide rollout across 900+ stores.
- Created a shared design language and delivery process that could be transferred to the client team.
- Defined a foundation for future process automation and AI-assisted retail operations.
Product architecture has a longer-lasting impact than individual interface decisions.
Discovery is most valuable when it challenges the original brief and changes the product strategy.
Operational products should follow how work is performed, not how internal systems are organized.
The most scalable solutions balance user needs, business priorities, and organizational readiness.
More Projects
Let's Connect
Feel free to contact me if having any questions.
I'm available for new projects or just for chatting.
Herman Lewandowsky, 2026