Pika View Dashboard

FMCG teams were working with large, fragmented datasets across brands, SKUs and regions. The data comes from informal retail: the Pika mobile app, used by 6,000+ traders, captures it in the field.FMCG teams were working with large, fragmented datasets across brands, SKUs and regions. The data comes from informal retail: the Pika mobile app, used by 6,000+ traders, captures it in the field.

Existing tools made it difficult to explore that data confidently, compare performance, or extract actionable insights quickly.Existing tools made it difficult to explore that data confidently, compare performance, or extract actionable insights quickly.

The questions executives brought were specific: market share, pricing shifts, distribution gaps and brand concentration. They needed the answer before the evidence, and each question needed a different slice of the same data.The questions executives brought were specific: market share, pricing shifts, distribution gaps and brand concentration. They needed the answer before the evidence, and each question needed a different slice of the same data.

So the job wasn’t a report per question. It was one system flexible enough to answer any of them.So the job wasn’t a report per question. It was one system flexible enough to answer any of them.

I designed and co-developed Pika View, and owned the UX architecture for its filters, comparisons, trend analysis and performance breakdowns.I designed and co-developed Pika View, and owned the UX architecture for its filters, comparisons, trend analysis and performance breakdowns.

As Technical Project Manager I coordinated engineers, designers, data teams and stakeholders, and delivered 95% of milestones on schedule using Jira.As Technical Project Manager I coordinated engineers, designers, data teams and stakeholders, and delivered 95% of milestones on schedule using Jira.

Every business question needed a different slice of the same data, so I designed one flexible filtering system across brands, SKUs and regions rather than a fixed report per question. Because data is sold and accessed by region, the filters also had to respect what each customer could see.Every business question needed a different slice of the same data, so I designed one flexible filtering system across brands, SKUs and regions rather than a fixed report per question. Because data is sold and accessed by region, the filters also had to respect what each customer could see.

I prioritized progressive disclosure: summary metrics up front, comparisons and performance breakdowns one level down. The overview stays readable without hiding depth.I prioritized progressive disclosure: summary metrics up front, comparisons and performance breakdowns one level down. The overview stays readable without hiding depth.

Usability testing with internal stakeholders and external users shaped both decisions, with each round aimed at clarity and trust in the data.Usability testing with internal stakeholders and external users shaped both decisions, with each round aimed at clarity and trust in the data.

The constraints shaped the design as much as the questions did:The constraints shaped the design as much as the questions did:

• Large datasets with performance costs
• Several user roles with different needs
• Data sold and accessed by region
• Engineering limits on data loading and state management

This project reinforced the importance of designing systems, not screens, especially in data-heavy environments where clarity directly affects decision quality.This project reinforced the importance of designing systems, not screens, especially in data-heavy environments where clarity directly affects decision quality.