Scoping Pro

This project is password protected

Access details are provided with application materials.

Work About Resume
← Back to work

Product design + strategy / Enterprise scenario modeling

Scoping Pro

As PepsiCo’s Lead UX Designer, I partnered with Google Cloud to turn complex planning into a transparent production product that teams could understand, trust, and use.

Shipped to production ~3 days → <1 hour per location 2026 · Post-workshop through production

Role

Lead UX Designer

Partnership

PepsiCo × Google Cloud

Primary user

GTM Design team

Status

In full production

My design position

A technically powerful model only creates value when it reflects how people work, exposes its logic, and produces decisions they can defend.

The shipped product

From scenario setup to decision-ready results

The challenge

Planning was too slow for the decisions it needed to support.

Go-to-market teams relied on a resource-intensive spreadsheet process that could span roughly 40 tabs and take weeks. Modeling a new market could take even longer.

As PepsiCo brought food and beverage operations together, teams needed to reason across stores, SKUs, services, labor, mileage, vehicles, routes, facilities, and financial performance.

The product had to improve speed without becoming a black box. Users needed granular inputs, visible calculations, and enough control to determine whether a result made operational sense.

Speed

Leadership questions moved faster than manual analysis.

Precision

Broad averages hid store- and SKU-level opportunities.

Trust

Adoption depended on seeing the logic behind each result.

What I inherited

The strategy existed. The product experience still needed definition.

I joined after the innovation workshops had concluded. I inherited their research, prioritized opportunities, user journey, and strategic recommendations.

The workshop established what the product should accomplish. My work began with translating that direction into interactions, language, and product behavior that fit PepsiCo’s users and operating environment.

94opportunities surfaced
7strategic themes
5priorities selected
3use cases defined

My role in the partnership

I bridged Google’s product ambition with PepsiCo’s enterprise reality.

PepsiCo reality

Users, language, workflows, constraints

How GTM teams actually planned, evaluated results, communicated value, and built organizational trust.

My contribution

Domain translation

Identify gaps, challenge assumptions, and turn strategy into usable product behavior.

Google expertise

Product, data, AI, cloud, engineering

Scalable technical capabilities and design patterns developed with Google’s UX designer and cross-functional teams.

Google’s UX designer and I designed collaboratively. My domain knowledge helped the joint team recognize where a technically valid proposal needed to change to fit PepsiCo terminology, decision behavior, and operational expectations.

Consequential design decisions

We designed for informed judgment—not a single “correct” answer.

These decisions connected Google’s modeling capabilities with the way PepsiCo teams validate plans and communicate recommendations.

01 · Explainability

Expose the math behind the recommendation.

Experienced GTM users would bypass a faster tool if its output contradicted their operational knowledge and they could not inspect why.

We connected projected value to recognizable drivers such as labor, miles, assets, and service assumptions. Users could evaluate the logic instead of accepting a black-box result.

Design principle

Trust comes from making a result challengeable, not from asking users to believe it.

02 · Exploration

Separate full reruns from quick sensitivities.

Some changes alter the operating model and require a full simulation. Others—such as wage or efficiency assumptions—are questions users need to explore quickly while discussing tradeoffs.

We distinguished structural inputs from quick-toggle sensitivities so teams could test uncertainty without rebuilding the scenario every time.

Domain bridge

The interaction model reflects how planning conversations actually move between commitments and questions.

03 · Communication

Give experts depth and decision-makers clarity.

GTM Designers needed granular controls, saved scenarios, and detailed comparisons. Senior leaders, Finance, HR, and field partners needed a focused view of the selected option and its impact.

We separated the modeling workspace from the curated “from-to” story, allowing producers to explore broadly and publish only the evidence stakeholders needed.

Product principle

Do not expose every user to the entire sandbox.

The shipped experience

One continuous path from operating context to a defensible decision.

Scenarios became persistent product objects that could be configured, analyzed, saved, compared, and communicated—not temporary calculations scattered across files.

01

Define

Market, stores, facilities, products, services, and baseline.

02

Simulate

Adjust parameters and run the operational model.

03

Understand

Inspect P&L and operational value drivers.

04

Compare

Test sensitivities and contrast alternative futures.

05

Publish

Curate the recommendation for decision-makers.

Capabilities shipped

Granular market setup

Scenario library

Routing analysis

Versioning

Sensitivity testing

Side-by-side comparison

Value-driver explanations

Curated publication

Measured outcome

~3 days
to <1 hour

per location

Scoping Pro accelerated go-to-market planning while moving analysis from broad estimates toward store- and SKU-level precision.

Formula transparency helped eliminate the black-box concern and supported trust in scaling the product across North America.

Speed

Faster scenario creation and evaluation

Trust

Transparent assumptions and value drivers

Scale

A production foundation for North American planning

Reflection

Domain knowledge is a design capability.

In complex enterprise products, domain knowledge is not supplementary context. It is what helps a multidisciplinary team distinguish a technically possible solution from one people can understand, trust, and defend.

The partnership worked because neither organization designed in isolation. Google brought deep product and technical expertise; I helped ground that ambition in PepsiCo’s users, language, workflows, and organizational realities.

Let's Connect!