Pika Dashboard

Project Overview

This project was a milestone: our team had never worked directly with FMCG clients before. As we approached onboarding our first enterprise customer, we were tasked with creating a foundational dashboard UI, one that could not only support their immediate data needs but also demonstrate that our product was ready for scale.I wasn’t the lead on this project, but I worked closely with the other designer to co-design the dashboard and supporting flows (e.g., settings and password recovery). We prioritized clarity, responsiveness, and scalability, ensuring the design could grow with customer demands.The dashboard you see here was part of the proof, a working UI delivered swiftly, with strong fundamentals that helped leadership see our product’s potential in the FMCG space.

‍

Overview

More on this project

🧩 The Challenge

We were entering a new vertical (FMCG) with no prior enterprise-facing interface. Our goal wasn’t to solve edge cases or deep insights just yet, it was to prove product readiness with a clean, data-friendly dashboard UI that could handle the basics well.

We needed a layout that would:

Be flexible enough for future feature expansion.

Make it easy for non-technical users to explore and interpret data.

Reinforce trust and professionalism in the eyes of a prospective client.

Help our leadership close the deal confidently.

🎯 The Goal

To design and implement an FMCG-ready dashboard UI that could support our first customer’s needs while acting as a visual proof-of-concept for enterprise adoption.

This meant delivering:
A modular, scalable layout.
‍
Smooth flows for settings, account access, and recovery.
‍
Clear organization of KPIs, user access, and controls.

An interface clean enough to be demoed, and solid enough to scale

✅ The Solution

We designed a streamlined, enterprise-facing dashboard with key supporting flows:

A data overview section with room for account summaries, user tracking, and metrics.
A flexible settings panel for team access, profile changes, and account management.

A lightweight password recovery flow to keep friction low for enterprise users.

This solution is now in front of our first FMCG customer and has already helped leadership build trust and gain momentum toward signing. It’s our first entry into the space, and a great UI foundation for more advanced features down the line.

[digital project] image of creative illustrations on a laptop screen

🔁 Design Process

Our approach followed a clear progression:

Business Requirements: We worked with internal stakeholders to understand the data points FMCG clients care most about (sales performance, distribution heatmaps, category trends, etc).
UI Design: We designed modular dashboard components, summary cards, filters, table views, and visualizations, in collaboration with a second designer.
Internal Review: We conducted iterative internal testing to refine clarity, responsiveness, and design consistency.
Live Enterprise Testing: We’re currently testing the dashboard with our first major enterprise partner in the FMCG space. This test will drive the next round of product improvements and future enterprise growth.

‍

Information Architecture

What Determined the IA and Structure

1. Business Requirements from FMCG Stakeholders
  - The FMCG company we signed was clear: they needed visibility into sales trends, product performance, and trader activity across different regions.
  - This meant the IA had to prioritize top-level KPIs (total sales, top products, active traders) with drill-down capability for managers.
2. Internal Data Team Input
  - The data department guided us on what data was reliable and available in real time, which directly shaped the dashboard modules.
  - For example, sales insights and stock movement were prioritized because they had consistent pipelines, while more advanced predictive analytics were scoped for later iterations.
3. Hierarchy of Enterprise Users
  - We accounted for different user roles: FMCG managers, analysts, and executives. Each required different levels of granularity.
  - This informed the structure: high-level summary cards for quick decisions, and deep-dive tabs for analysts.
4. Testing with Internal and Pilot Users
  - Early walkthroughs revealed that stakeholders preferred fewer tabs but deeper context in each section (e.g., combining Sales + Customer Behavior rather than splitting).
  - That led us to streamline the IA into 3–4 primary sections instead of 7–8 fragmented ones.
5. Enterprise UX Best Practices
  - We followed patterns like progressive disclosure, sticky filters, and exportable reports because these are critical for enterprise adoption.
  - The structure mirrored the workflow of FMCG managers: monitor → compare → drill down → export/share.

Selected work, simply displayed

Clean Design. Clear Impact.

[digital project] image of a graphic design on a screen (for a web design agency)

Design System

To bring order to the evolving Pika experience, I created a design system tailored for informal retailers. It was built to be intuitive for first-time smartphone users, with clear contrast, accessible font sizes, and repeatable patterns across screens. The system allowed us to scale from agent tools to inventory and insights without redesigning from scratch every time.

Work That Speaks for Itself

A look at the solution for the Pika Dashboard MVP

image of signature dishes for a japanese restaurant

image of ramen bowls (for a japanese restaurant)

image of a main course assortment for a chinese restaurant

image of traditional chinese medicine ingredients

Final Thought

Enterprise UX is about alignment, not just features: I learned that designing for enterprise clients requires as much attention to stakeholder needs as to end-user flows. Every feature we designed, from sales insights to trader performance, was required to directly support business objectives and ROI discussions.‍
Data storytelling is critical: Unlike consumer products, where simplicity is king, enterprise dashboards must balance complexity with clarity. I had to design visual hierarchies that made raw numbers meaningful, turning data into insights that decision-makers could act on quickly.
The value of trust in early-stage enterprise adoption: Since this was our first major FMCG client, I learned how crucial polish and professionalism are in building confidence. A clean UI, consistent design system, and reliable flows weren’t just cosmetic, they helped secure and retain a two-year contract.
Design systems save time and scale faster: Working with another designer, I saw firsthand how aligning on a shared design system (components, typography, colors, data tables) ensured consistency, faster iterations, and a scalable foundation for future clients.

‍

Designing a Functional FMCG Dashboard for Our First Enterprise Client

Role

Project Owner

Duration

Tools Used

Design Process