From Tracking to Decisions — Designing a Smarter Inventory System

Visit Website

Overview

Rio began as an internal tool to manage inventory, but the problem quickly proved to be larger than stock tracking. Small business operators weren’t struggling to see what they had — they were struggling to understand what to do next. Inventory decisions directly impact cash flow, margin, and purchasing risk, yet most tools separate these concepts across disconnected systems or bury them in reports. This project reframed inventory as a decision system, focused on helping operators connect daily operations to financial outcomes in a clear, actionable way. Rather than building another inventory tracker, I designed Rio to answer a more fundamental question: What do I need to do right now?

My Role

Sole product designer, end to end — research, IA, UX, visual design, and brand identity

I partnered with the founder to define the product concept and core thesis, then translated that into a cohesive system across product and brand.

Defined the system model, navigation structure, and primary user flows
Designed the full product experience across Overview, Inventory, Product Detail, Plan, and Reports
Established the visual language and design system to support a calm, decision-first experience

How might we help small business operators make confident buying and stocking decisions without requiring finance expertise, spreadsheets, or heavy ERP tools?

The Problem

Most inventory tools fall into one of two categories: Tracking tools — Easy to use, but limited to showing what exists (stock levels, SKUs, basic reports) ERP systems — Highly capable, but complex, rigid, and disconnected from how small businesses actually operate Neither approach solves the real problem: Operators don’t need more data—they need help making decisions. Key gaps identified: • Inventory, financial metrics, and purchasing decisions are fragmented • Users must interpret raw data to understand risk or opportunity • Planning workflows (like Open-to-Buy) are spreadsheet-heavy and inaccessible • Tools are designed around systems, not how people think or act • Users rely on intuition, spreadsheets, or delayed reporting to make high-impact decisions.

Key Constraints

1. Designed for non-experts The system needed to support financial decision-making without requiring formal finance knowledge. → Led to simplifying complex concepts like OTB into intuitive, editable assumptions 2. Balance clarity with flexibility Small businesses operate differently, but too much flexibility introduces complexity. → Required prioritizing strong defaults and guided decision-making over configurability 3. Avoid ERP-level complexity The product needed to feel lightweight and fast, while still supporting meaningful financial workflows. → Forced intentional scope reduction and careful information hierarchy 4. Real-time + planning in one system Inventory is both operational (today) and strategic (future), but most tools separate these. → Required designing across multiple time horizons without increasing cognitive load

Approach

I approached Rio by reframing inventory from a system of record into a system of decision-making. Rather than optimizing for completeness or flexibility, I prioritized clarity, speed, and actionability — designing the product to help users understand what matters and decide what to do next.

This led to shifting the interface away from dashboards and raw metrics toward signals and actions, where inventory issues are surfaced as interpreted, actionable insights instead of data to be analyzed. The goal was to reduce interpretation and make the next step obvious.

To reduce cognitive load, I structured the system around distinct time-based modes: Overview, Inventory, Plan, and Reports — each supporting a different type of thinking, from immediate awareness to longer-term planning and reflection. This separation allowed each surface to stay focused while still working together as a cohesive system.

Inventory was designed as the primary workspace, organized by behavior (At Risk, Overstocked, Healthy) rather than static categories. This aligns the interface with how users actually prioritize problems. Product detail was surfaced contextually through a drawer instead of a separate destination, keeping users in flow and reducing unnecessary navigation.

On the planning side, I reworked traditional Open-to-Buy workflows into a model of editable assumptions where users adjust sales, markdowns, and target inventory while the system calculates available budget. This makes financial planning more intuitive and accessible without requiring users to understand the underlying formulas.

Purchase orders were treated as an output of these decisions rather than a starting point, reflecting how operators naturally work. Financial context — cost, margin, and inventory value — was embedded directly into operational views, ensuring that every decision is made with full awareness of its impact.

Finally, I used progressive disclosure to manage complexity, making key inputs visible when needed, but collapsible once decisions are set, so users can move from understanding to execution without losing context.

Outcome

Rio validated a clear gap between inventory tracking and inventory decision-making. By reframing inventory as a system tied to cash flow, margin, and purchasing decisions, the work uncovered a broader opportunity beyond software. What began as an internal tool evolved into the foundation for a financial consulting practice, helping small businesses make more informed operational decisions.The product concept continues to be developed with plans to evolve into a standalone offering.