Case Study / Web App Design / Froth

Upgrading a Project Management for Better Focus, Structure, and Usability

My role

  • Product designer
  • Problem solving
  • User testing

Platform

  • Customer app
  • Merchant app

Product

Robotico Digital

Year

2024

Froth Web App Interface

↑ Sneak peek of Froth Web App interface

Introduction

Froth is a fast-growing marketplace platform bridging merchants and customers across regions. After a 300% growth spike in 18 months, the internal dashboard—originally designed for a leaner operation—couldn’t keep up with the complexity of scaling teams and workflows. Operations, support, and merchant success teams—over 50 users—were slowed down by fragmented data, inefficient navigation, and delayed insights. Routine performance checks became time-consuming, requiring manual digging across tools and spreadsheets. We saw an opportunity to redesign the dashboard into a more focused, scannable, and decision-ready interface—one that reflects how teams actually work at scale.

Problems

  • Data Accessibility Issues → Performance metrics were difficult to locate. Teams spent excessive time identifying what needed attention.
  • Operational Inefficiency → 40% of operations productivity was consumed by cross-platform data gathering. Simple queries took 15–20 minutes.
  • Decision-Making Delays → Fragmented information slowed down strategic decisions, affecting fulfillment and customer satisfaction.

Solution

After auditing workflows and analyzing internal feedback, we opted for a strategic redesign that restructured the layout without rebuilding the backend. This allowed for faster deployment and lower disruption to daily operations.

  • Streamlining critical workflows
  • Grouping related metrics for at-a-glance insights
  • Reducing clutter with modular design components

Key Improvements

  • Enhanced Visual Hierarchy → Priority-based layout that highlights the most critical data first
  • Modular Card System → Grouped related performance metrics with trends and status indicators
  • One-Screen Context → Consolidated actions and data on fewer screens to minimize context switching

What I Learned

This project taught me how to simplify internal tools without oversimplifying. I gained experience designing scalable UIs for high-pressure environments and learned the importance of structuring data for clarity and speed. It reinforced the value of tight developer collaboration and stakeholder alignment throughout the product lifecycle.