PepsiCo's Galileo Architecture Rework

ROLE:

Product designer

DURATION:

Ongoing

Product Showcase

Introduction

Project overview

Galileo started as a diagnostic dashboard to help PepsiCo Retail eCommerce teams track profitability and market share. But as the platform evolved, it outgrew its original purpose. What was once a single-page dashboard turned into a chaotic, overstuffed tool trying to support multiple complex workflows — without the architecture to back it up.

I led the redesign of Galileo’s information architecture, transforming it into a scalable multi-app suite. This included defining the core structure for new apps like Business Hub, Events, Financial Trends, Marketing Automation, and Supply Chain.

My role

I was responsible for:

Redesigning the entire architecture and navigation system
Creating the drilldown methodology used across apps
Establishing layout patterns and interaction flows
Leading the design and implementation of the Events app as the first real-world application of this new structure

Context

The original design collapsed everything into a single page, with no clear hierarchy and no real path for growth. Information was cluttered, workflows were buried, and users — mostly financial analysts and executives — struggled to make sense of it all.

The redesign wasn’t just visual — it was structural. I reimagined how Galileo worked from the ground up, splitting the experience into modular apps and creating an architecture that could scale as the platform continued to grow.

Problem

What wasn't working

As new features were added to Galileo, its original single-page design quickly became unsustainable. What started as a lightweight reporting tool turned into a cluttered mess — forcing users to scroll through multiple unrelated tables, charts, and metrics stacked on top of each other.

Key issues

Cognitive overload: Everything lived on one screen, making it hard to focus or act on specific insights.

No clear hierarchy: Unrelated data competed for attention, with no way to drill into details.

Lack of segmentation: There was no structure to separate workflows or guide the user journey.

Unscalable architecture: Adding new features only made things worse — it was impossible to grow without making the experience more chaotic.

Weak navigation: The sidebar had only three static options and was hidden behind a hover interaction, which made switching apps or views confusing.

Inconsistent visual language: Layouts, colors, and components varied across the interface, making the platform feel fragmented and unpolished.

Research & Insights

After my own analysis, I needed to understand what users were struggling with — not just at a visual level, but from a cognitive and behavioral perspective.

Methods

Heuristic analysis of the existing Galileo experience
Interviews with financial analysts and platform users
Behavioral mapping to understand flow interruptions and friction
Competitive analysis to benchmark platform navigation models

Key insights that shaped the redesign

Cognitive overload was the #1 issue

Users frequently lost context mid-task. Too much information was presented at once, and there was no clear way to isolate or prioritize what mattered.

Lack of compartmentalization broke task flow

Users were forced to switch mental modes constantly — from analysis to action to searching for tools — all within the same chaotic view.

Navigation was not discoverable or meaningful
Most users didn’t even notice the original sidebar. Many relied on brute-force scrolling to find what they needed.

Users wanted to “zoom in” without getting lost
There was high demand for the ability to explore a specific product, time period, or unit without losing track of the bigger picture.

Table usage was high — but only in bursts

Users didn’t need everything all the time. They needed the right data in the right moment, with the option to go deeper when required.

Design Strategy

Where I wanted to take it

Instead of trying to simplify the single-page layout, I restructured the experience entirely. The new approach broke the platform into modular, purpose-driven apps — each with its own logic, layout, and flow — all connected through a consistent architecture.

Key shifts I introduced

From “everything in one place” → to dedicated apps

Business Hub, Events, Financial Trends, and more each became their own space, giving users clarity and focus.

Drilldown methodology

I introduced a drilldown approach that let users go deeper into specific business units, timeframes, or metrics — without overloading the main pages. Temporary tabs open as needed, then disappear when done.

Dynamic bottom navigation bar
The old sidebar was static and limited. The new bottom nav supports: Access to the app hub, Links hub (favorites, history, recent pages), Temporary drilldown tabs

Separation of concerns
Instead of cramming multiple workflows into one space, the new system cleanly separates exploration, monitoring, and action-taking.

Design Execution

Laying the foundation for a scalable system

With the architecture in place, I began designing wireframes and layout patterns that would support a range of apps — from high-level dashboards to deep-dive reporting tools.

The layout framework prioritized flexibility. Each app had its own content and use cases, so I focused on creating reusable structures that could scale and adapt.

Design principles I followed

Modular layout templates
I created page structures for:

Overview pages with KPIs + summary visualizations
Detail pages for drilldowns
Navigation hubs to jump between reports, views, and filters

Content follows structure, not the other way around

Since much of the content was still being defined, my goal was to build strong page logic first — then layer in content once we had clarity.

Bottom navigation + temporary tabs
Replaced the old sidebar with a more functional bottom nav that allowed access to:

App directory
Current section
Temporary tabs for specific actions (like time-based drilldowns or detailed records)

Click-to-drill interactions
In the Events app, users could click on a specific date in the chart and automatically drill into that period — no need to fumble with filter menus.

Key Screens Logic

Now that the structure and logic were in place, I focused on translating everything into real, usable screens. Below are final implementations showing how the redesigned architecture came to life — cleaner layouts, smarter interactions, and a system built for clarity, not chaos.

Business Hub – Before

The original Business Hub tried to contain everything — KPIs, charts, tables, filters — on a single page. There was no hierarchy, no breathing room, and no clear prioritization. The sidebar navigation was hidden, static, and often ignored.

What wasn’t working:

Content overload with unrelated metrics competing for attention
No clear entry points for users to take action
Sidebar acted more like a local page switcher than true navigation
Overlapping workflows made the interface difficult to scale or maintain

Business Hub – After

The new design embraces modularity. Features are broken into specific apps where they’re actually relevant. The layout prioritizes summary KPIs, visual context, and clearer navigation. The bottom nav replaces the sidebar and now supports drilldowns, links, and page history.

Why it works

Clear task-based structure: users see only what they need
Bottom nav gives access to links hub, current section, and temporary pages
Content is now structured across separate pages for better focus
Visual hierarchy makes key metrics stand out

Events App – Before

Events used to be just a massive table tacked onto the dashboard. It tried to show product rankings across different event periods — but it ended up overwhelming users with endless rows and raw numbers. There was no prioritization, no visual hierarchy, and no real insight — just data overload.

What wan't working

No separation between events and the rest of the dashboard
Table was dense, hard to read, and not actionable
Users couldn’t spot trends or shifts without manually scanning through dozens of rows
Everything was crammed into the same layout, with no context or flexibility

Events App – After

The Events section became its own app — no longer buried inside another page. It now tracks event-specific insights like competitor share, campaign reach, spend, and product performance. Users get visual context through charts, and when needed, they can drill down into a single product with a scoped table view.

Why it works

Dedicated space tailored for event-specific workflows
Visualizations show trends at a glance
KPI tiles at the top call out urgent shifts and guide users toward the next step

New System Features

The redesign wasn’t just about structure — it introduced new interaction patterns and features that made Galileo faster, more focused, and easier to scale.

Drilldown Methodology

Instead of dumping all details into a single view, users can now drill down into specific products, timeframes, or business units — and open those details in temporary, focused pages.

Why it matters:

Keeps high-level pages clean
Reduces context-switching
Lets users explore deeply without losing their place

Compartmentalized Tables

In the old design, massive tables tried to show everything at once — flooding users with irrelevant rows and no clear action path. In the redesign, tables are scoped and intentional. They show only what’s relevant in the moment, and are paired with supporting context or drilldown options.

Why it matters:

Reduces information overload
Makes tables easier to scan, understand, and act on
Supports a modular UI that adapts to the user’s current goal

Apps Hub

A centralized hub for recent pages, favorite links, and app shortcuts — accessible via the bottom nav. Built to help users jump between workflows without hunting through menus.

Why it matters:

Gives the whole platform memory
Personalizes navigation
Replaces the clunky static sidebar

Action-First Interactions

CTAs are now embedded directly into the UI — not buried in toolbars or side drawers. If a KPI tile shows low stock, users can click it to open a focused drawer with options to act immediately.

Why it matters:

Reduces decision fatigue
Makes insights actionable
Supports fast, task-driven UX

Results

The redesign of Galileo laid the groundwork for a more efficient, scalable platform — and the improvements were quickly visible in both user behavior and design velocity.

Platform Outcomes

The new structure directly impacted usability and task efficiency, especially in high-density apps like Events and Business Hub.

Team and system outcomes

Beyond the user experience, the redesign introduced structural clarity that sped up design, reduced friction, and made future expansion more sustainable.

Next Case Study

Next Case