Coca-Cola

Global Supply ChainBenchmarking CMS

Designing a structured survey platform for Coca-Cola's global bottling network

ROLE

Lead UX Designer

SCOPE

Workflow design, role-based UX, prototyping, usability validation

PLATFORM

PowerApps (Enterprise CMS) · Figma (Design Systems, Prototyping)

KEY OUTCOME

Scalable, centralized workflow

Coca-Cola global supply chain benchmarking CMS on a laptop

Coca-Cola operates a global supply chain with hundreds of bottling facilities, each with its own equipment, workflows, and reporting needs. But the system used to collect benchmarking data across those facilities was far less sophisticated than the operation it supported. Surveys were created in spreadsheets, reviewed through email threads, translated inconsistently, and in some cases printed, mailed, scanned, or faxed back.

What should have been a structured operational process had become a fragile collection of workarounds.

I was brought in to design a content management system that could bring order to that complexity. The goal was to help teams create, approve, translate, and publish surveys more efficiently, while giving leadership a centralized way to understand how facilities were performing and where action was needed.

Built in PowerApps, the solution had to work within platform constraints while still feeling intuitive to users who were deeply accustomed to Excel-based workflows. The challenge was not just to improve the interface. It was to replace an unreliable process with a system people could actually trust.

Executive Summary

The Business Problem & The User Problem

Coca-Cola lacked a centralized, scalable way to manage benchmarking surveys across its global bottling network. Content was created and maintained through spreadsheets, emails, and manual publishing steps, which created version confusion, slowed approvals, and made multilingual distribution difficult. At the user level, creators, approvers, translators, and facility managers were all working through disconnected processes that introduced friction, delays, and avoidable errors.

The Strategic Solution

I designed an enterprise CMS in PowerApps that transformed a fragmented survey process into a structured, role-based workflow. The platform enabled teams to build modular surveys, route them through approval queues, support translation workflows, and publish content without relying on developers for every update.

My Role & Leadership Scope

I led UX strategy, interaction design, workflow modeling, and usability validation across the product. I worked closely with stakeholders, developers, and QA to align the system around real operational needs while ensuring the final solution could be implemented effectively within the chosen platform.

Impact

The new CMS replaced ad hoc manual processes with a structured system for survey creation, approval, translation, and publication. It reduced dependency on engineering, improved clarity across user roles, and created a more scalable foundation for collecting global operational data.

40%Reduction in survey publishing time

100+Global facilities rollout

Business Outcomes

ADOPTION

90%+

Platform adoption across target users

Strong uptake after rollout

APPROVAL VELOCITY

50–75%

Faster approval workflows

Reduced delays and bottlenecks

OPERATIONAL EFFICIENCY

Reduced dependency

Less manual coordination and fewer engineering handoffs

Simplified operational flow

Replaced fragmented spreadsheet and email workflows with a centralized CMS

Improved consistency across survey creation, translation, and approval

Enabled more scalable multilingual distribution across global facilities

Gave leadership clearer visibility into performance trends and operational priorities

Outcomes based on stakeholder reporting, workflow analysis, and post-launch operational trends.

System Transformation

From fragmented workflows to a structured, scalable platform

Before

Fragmented workflows

Manual coordination

No visibility

Version control issues

After

New centralized CMS platform with structured workflow

Structured CMS workflow

Defined roles & automation

Centralized visibility

Version-controlled content

Structural Bottlenecks

Five critical operational friction points compounded across the global organization, creating measurable productivity loss and delaying strategic decision-making.

File Chaos

Multiple uncontrolled versions of surveys created inconsistency and confusion across teams.

Engineers as Publishers

Content updates required developer intervention, creating bottlenecks and delays.

Translation Without Structure

There was no formal localization workflow, leading to inconsistent and unreliable translations.

Wrong Questions, Wrong Facilities

Facilities sometimes received questions that did not apply to their machinery or operating context, hurting data quality.

Static Data, Limited Insight

Leadership had access to information, but not in a form that supported timely decision-making.

Detailed Process

To address these systemic bottlenecks, I designed a structured workflow transformation spanning research, modeling, and implementation.

Research & Discovery

I conducted interviews across stakeholder groups and time zones to understand how content moved through the organization in practice.

Workflow Modeling

I translated findings into user flows and future-state workflows that could be validated with stakeholders.

Wireframing & Prototyping

I started with low-fidelity wireframes and then created Figma prototypes tailored to the realities of PowerApps.

Familiarity Without Chaos

The interface needed to feel more structured than Excel, but not so unfamiliar that adoption became its own barrier.

Documentation & Handoff

I created detailed design specifications and worked closely with engineering and QA to ensure the experience translated accurately into the shipped product.

Who's Who (And What They Needed)

Content Creator

Core Job: Create structured survey modules

Pain Point: Previously relied on spreadsheets and email with no clear system or structure

Content Approver

Core Job: Review and approve survey content

Pain Point: No visibility into approval status and no reliable review queue

Translator

Core Job: Localize finalized content

Pain Point: No formal translation workflow or dedicated tools

Publisher (Executive)

Core Job: Publish finalized content globally

Pain Point: Dependent on developers for routine content updates

Facility Manager

Core Job: Complete relevant surveys in the right language

Pain Point: Often received mismatched or unclear inputs

My Design Moves

1. Mapped the Existing Workflow

I created before-and-after workflow models to visualize how survey content moved through the organization and where delays and handoff failures were happening.

2. Designed a Modular Survey Builder

I designed a structured content system that preserved useful Excel familiarity while eliminating version chaos and manual workarounds.

3. Created Role-Based Experiences

I tailored workflows and interfaces for creators, approvers, translators, publishers, and leadership so each group had the right information and controls.

4. Introduced AI-Assisted Translation

I incorporated AI-assisted translation as a first-draft mechanism with human review built into the workflow.

5. Aligned Design with Platform Constraints

I designed the system to work within PowerApps limitations while still improving usability, structure, and clarity.

6. Partnered Closely Through Delivery

I collaborated with development and QA throughout implementation and created detailed specifications to support accurate delivery.

BeforeAfter

Before

Survey requests started informally
Creators built content manually in spreadsheets
Approvals moved through scattered email threads
Translation had no formal workflow
Publishing required developer intervention
Surveys could be printed, mailed, scanned, or faxed
Facility managers completed mismatched or unclear forms
Leadership received fragmented data with little actionable clarity

After

Survey content moved through a structured CMS
Creators built modules using templates and defined inputs
Approvers reviewed content through visible queues
Translation became a supported step in the workflow
Publishing became a controlled user action, not a developer task
Surveys were distributed digitally and matched to facility context
Facility managers completed relevant content in the appropriate language
Leadership gained centralized visibility into trends and priorities

Interactive Comparison

Admin-Only Tool

Not accessible to end users

Shared Web Interface

Accessible to creators, approvers, and publishers

BeforeAfter

Previously, publishing required access to an internal admin tool. The redesigned system introduces a shared web interface that enables creators, approvers, and publishers to manage the workflow independently.

What I Learned

This project reinforced that enterprise design is often less about novelty and more about replacing fragile habits with systems people can trust.

The best solution was not the one with the most dramatic interface. It was the one that gave each role a clearer path forward without asking users to completely reinvent how they worked overnight.

It also reminded me that operational complexity tends to hide inside familiar tools. A spreadsheet can look harmless on the surface, but when an entire workflow depends on it, it is often carrying far more risk than anyone wants to admit.

Global Supply Chain CMS

Retail Rx Fulfillment

Video Broadcasting Platform

Global Supply ChainBenchmarking CMS

Executive Summary

Business Outcomes

System Transformation

Structural Bottlenecks

File Chaos

Engineers as Publishers

Translation Without Structure

Wrong Questions, Wrong Facilities

Static Data, Limited Insight

Detailed Process

Research & Discovery

Workflow Modeling

Wireframing & Prototyping

Familiarity Without Chaos

Documentation & Handoff

Who's Who (And What They Needed)

Content Creator

Content Approver

Translator

Publisher (Executive)

Facility Manager

My Design Moves

1. Mapped the Existing Workflow

2. Designed a Modular Survey Builder

3. Created Role-Based Experiences

4. Introduced AI-Assisted Translation

5. Aligned Design with Platform Constraints

6. Partnered Closely Through Delivery

BeforeAfter

Admin-Only Tool

Shared Web Interface

What I Learned