Coca-Cola Enterprise AI Use Cases Dashboard
Project Summary :
I redesigned an enterprise platform serving three audiences at once (employees submitting AI use cases, the review team evaluating them, and executives tracking adoption), accelerating Coca-Cola's AI adoption process and cutting operational task time by 34%.
Designing for Employees
Employees came to do two things: submit an idea, and keep track of it afterward. The redesign carries that across two pages, the home page and the submission.
The Home Page - Prioritize Actions and Updates
Employees come to the portal to act, so the new home page opens with their work, not the company's mission. Submission status and pending tasks now sit on the landing page, which removes the trip to a separate tab just to see where an idea stands. I held the layout to the two things an employee returns for, current status and the next action they owe, and kept everything else off it.
Poppy Agentic Chatbot - Simplified Q&A Support
Most tickets came from employees stuck somewhere in the submission process. Poppy answers those questions on the spot, so an employee can keep moving without opening a ticket or pulling a reviewer off their work. By handling the repetitive questions behind the 10 to 20 monthly tickets, it frees reviewers for the cases that actually need them.
Submission Form — Staged, Not Stacked
The new form breaks submission into stages and shows only the fields that fit the current step. I moved the questions people can't answer yet to the stage where they belong, and dropped any stage that doesn't apply to a use case. Each step stays short, so the form carries an employee toward submitting instead of wearing them down before they start.
Designing for Employees
Employees came to do two things: submit an idea, and keep track of it afterward. The redesign carries that across two pages, the home page and the submission.
The Home Page - Prioritize Actions and Updates
Employees come to the portal to act, so the new home page opens with their work, not the company's mission. Submission status and pending tasks now sit on the landing page, which removes the trip to a separate tab just to see where an idea stands. I held the layout to the two things an employee returns for, current status and the next action they owe, and kept everything else off it.
Poppy Agentic Chatbot - Simplified Q&A Support
Most tickets came from employees stuck somewhere in the submission process. Poppy answers those questions on the spot, so an employee can keep moving without opening a ticket or pulling a reviewer off their work. By handling the repetitive questions behind the 10 to 20 monthly tickets, it frees reviewers for the cases that actually need them.
Submission Form — Staged, Not Stacked
The new form breaks submission into stages and shows only the fields that fit the current step. I moved the questions people can't answer yet to the stage where they belong, and dropped any stage that doesn't apply to a use case. Each step stays short, so the form carries an employee toward submitting instead of wearing them down before they start.
Designing for Employees
Employees came to do two things: submit an idea, and keep track of it afterward. The redesign carries that across two pages, the home page and the submission.
The Home Page - Prioritize Actions and Updates
Employees come to the portal to act, so the new home page opens with their work, not the company's mission. Submission status and pending tasks now sit on the landing page, which removes the trip to a separate tab just to see where an idea stands. I held the layout to the two things an employee returns for, current status and the next action they owe, and kept everything else off it.
Poppy Agentic Chatbot - Simplified Q&A Support
Most tickets came from employees stuck somewhere in the submission process. Poppy answers those questions on the spot, so an employee can keep moving without opening a ticket or pulling a reviewer off their work. By handling the repetitive questions behind the 10 to 20 monthly tickets, it frees reviewers for the cases that actually need them.
Submission Form — Staged, Not Stacked
The new form breaks submission into stages and shows only the fields that fit the current step. I moved the questions people can't answer yet to the stage where they belong, and dropped any stage that doesn't apply to a use case. Each step stays short, so the form carries an employee toward submitting instead of wearing them down before they start.
Designing for Employees
Employees came to do two things: submit an idea, and keep track of it afterward. The redesign carries that across two pages, the home page and the submission.
The Home Page - Prioritize Actions and Updates
Employees come to the portal to act, so the new home page opens with their work, not the company's mission. Submission status and pending tasks now sit on the landing page, which removes the trip to a separate tab just to see where an idea stands. I held the layout to the two things an employee returns for, current status and the next action they owe, and kept everything else off it.
Poppy Agentic Chatbot - Simplified Q&A Support
Most tickets came from employees stuck somewhere in the submission process. Poppy answers those questions on the spot, so an employee can keep moving without opening a ticket or pulling a reviewer off their work. By handling the repetitive questions behind the 10 to 20 monthly tickets, it frees reviewers for the cases that actually need them.
Submission Form — Staged, Not Stacked
The new form breaks submission into stages and shows only the fields that fit the current step. I moved the questions people can't answer yet to the stage where they belong, and dropped any stage that doesn't apply to a use case. Each step stays short, so the form carries an employee toward submitting instead of wearing them down before they start.
Designing for The Review Team
The review team built the old tool and worked around its flaws, so they never asked for a redesign. My job was to improve their workflow without taking away the control they were used to.
The New Review Workspace - Everything Side by Side
I pulled the whole case onto one workspace where a reviewer can read any stage next to another without leaving the page. A collapsible submission list keeps the queue one click away, then folds out of the way for a focused read. Reviewers kept the depth they relied on and lost the page-hopping that slowed their reviews.
Additional foldable side bar provides maximum review workspace when desired.
Designing for The Review Team
The review team built the old tool and worked around its flaws, so they never asked for a redesign. My job was to improve their workflow without taking away the control they were used to.
The New Review Workspace - Everything Side by Side
I pulled the whole case onto one workspace where a reviewer can read any stage next to another without leaving the page. A collapsible submission list keeps the queue one click away, then folds out of the way for a focused read. Reviewers kept the depth they relied on and lost the page-hopping that slowed their reviews.
Additional foldable side bar provides maximum review workspace when desired.
Designing for The Review Team
The review team built the old tool and worked around its flaws, so they never asked for a redesign. My job was to improve their workflow without taking away the control they were used to.
The New Review Workspace - Everything Side by Side
I pulled the whole case onto one workspace where a reviewer can read any stage next to another without leaving the page. A collapsible submission list keeps the queue one click away, then folds out of the way for a focused read. Reviewers kept the depth they relied on and lost the page-hopping that slowed their reviews.
Additional foldable side bar provides maximum review workspace when desired.
Designing for The Review Team
The review team built the old tool and worked around its flaws, so they never asked for a redesign. My job was to improve their workflow without taking away the control they were used to.
The New Review Workspace - Everything Side by Side
I pulled the whole case onto one workspace where a reviewer can read any stage next to another without leaving the page. A collapsible submission list keeps the queue one click away, then folds out of the way for a focused read. Reviewers kept the depth they relied on and lost the page-hopping that slowed their reviews.
Additional foldable side bar provides maximum review workspace when desired.
Designing for Executives
Why It Matters
Executives had no view of their own. The only dashboard belonged to the review team, so when leadership wanted to know how AI adoption was tracking, they asked the review team to pull it together. Each request took a reviewer away from their work to answer a question that a dashboard should have handled.
The New Executive Dashboard - Adoption at a Glance
I built executives their own dashboard: a live view of AI adoption they can read without asking anyone. Search, filter, and sort let them drill into use cases by status, impact, risk, audience, and org unit independently. Leadership gets answers on demand, and the review team gets those hours back.
Designing for Executives
Why It Matters
Executives had no view of their own. The only dashboard belonged to the review team, so when leadership wanted to know how AI adoption was tracking, they asked the review team to pull it together. Each request took a reviewer away from their work to answer a question that a dashboard should have handled.
The New Executive Dashboard - Adoption at a Glance
I built executives their own dashboard: a live view of AI adoption they can read without asking anyone. Search, filter, and sort let them drill into use cases by status, impact, risk, audience, and org unit independently. Leadership gets answers on demand, and the review team gets those hours back.
Designing for Executives
Why It Matters
Executives had no view of their own. The only dashboard belonged to the review team, so when leadership wanted to know how AI adoption was tracking, they asked the review team to pull it together. Each request took a reviewer away from their work to answer a question that a dashboard should have handled.
The New Executive Dashboard - Adoption at a Glance
I built executives their own dashboard: a live view of AI adoption they can read without asking anyone. Search, filter, and sort let them drill into use cases by status, impact, risk, audience, and org unit independently. Leadership gets answers on demand, and the review team gets those hours back.
Designing for Executives
Why It Matters
Executives had no view of their own. The only dashboard belonged to the review team, so when leadership wanted to know how AI adoption was tracking, they asked the review team to pull it together. Each request took a reviewer away from their work to answer a question that a dashboard should have handled.
The New Executive Dashboard - Adoption at a Glance
I built executives their own dashboard: a live view of AI adoption they can read without asking anyone. Search, filter, and sort let them drill into use cases by status, impact, risk, audience, and org unit independently. Leadership gets answers on demand, and the review team gets those hours back.
AI-Augmented Process
Unravel User Needs & Team Alignment
What AI did:
Synthesized 10+ data points
What I do:
Planned actions from insights
Iterative Design Process
What AI did:
Converted sketches and ideas into prototypes
What I do:
Refined details and ensured consistency
Made data-based design decision
Design Hand-off
What AI did:
Evaluated technical feasibility through React
What I do:
Handed design off with clear communication
AI-Augmented Process
Unravel User Needs & Team Alignment
What AI did:
Synthesized 10+ data points
What I do:
Planned actions from insights
Iterative Design Process
What AI did:
Converted sketches and ideas into prototypes
What I do:
Refined details and ensured consistency
Made data-based design decision
Design Hand-off
What AI did:
Evaluated technical feasibility through React
What I do:
Handed design off with clear communication
AI-Augmented Process
Unravel User Needs & Team Alignment
What AI did:
Synthesized 10+ data points
What I do:
Planned actions from insights
Iterative Design Process
What AI did:
Converted sketches and ideas into prototypes
What I do:
Refined details and ensured consistency
Made data-based design decision
Design Hand-off
What AI did:
Evaluated technical feasibility through React
What I do:
Handed design off with clear communication
AI-Augmented Process
Unravel User Needs & Team Alignment
What AI did:
Synthesized 10+ data points
What I do:
Planned actions from insights
Iterative Design Process
What AI did:
Converted sketches and ideas into prototypes
What I do:
Refined details and ensured consistency
Made data-based design decision
Design Hand-off
What AI did:
Evaluated technical feasibility through React
What I do:
Handed design off with clear communication
Background
A Tool Built by Backend Reviewers, for Reviewers
The AI use case portal launched in 2023, built entirely by the review and engineering teams with no design input. It worked the way reviewers work: dense and technical, and they didn't mind. As the company scaled its AI adoption, submissions grew, and so did complaints and abandonment rates. The portal worked for the people who built it and failed everyone else. I picked up the redesign using the feedback backlog the team had already gathered.
Why the Redesign Matters
300+
AI use cases submitted through the portal in two years
50+
Support tickets employees opened (last 3 months before this project)
2-4
Executives reached out for analytic info update monthly
Internal AI is a major company initiative, and this portal is where every idea starts. As submissions and tickets climb, employees wait longer to get started and reviewers lose hours to avoidable questions, so the redesign protects both the AI pipeline and the team's time.
One Portal Serving Three Workflows
Employees
Employees submit AI use cases through the platform for review.
Current Challenges:
High Abandonment: The form asked review-stage questions that employees couldn't answer at that point, so they left before submitting.
Missing Updates: No notifications or clear next steps, so employees missed actions they owed on their submissions.
Review Teams
The Review team evaluates submissions and approves or requests additional actions on each case.
Current Challenges:
Scattered Information: Reviewers had to jump between multiple pages to assemble a single case.
Unplanned Support Load: Confused employees brought questions straight to reviewers, who ended up doing work outside their job.
Executives
Executives review AI use cases to track progress in enterprise AI adoption.
Current Challenges:
No Executive View: Leadership got the same interface as the review team. No summary, no way to see adoption at a glance.
Background
A Tool Built by Backend Reviewers, for Reviewers
The AI use case portal launched in 2023, built entirely by the review and engineering teams with no design input. It worked the way reviewers work: dense and technical, and they didn't mind. As the company scaled its AI adoption, submissions grew, and so did complaints and abandonment rates. The portal worked for the people who built it and failed everyone else. I picked up the redesign using the feedback backlog the team had already gathered.
Why the Redesign Matters
300+
AI use cases submitted through the portal in two years
50+
Support tickets employees opened (last 3 months before this project)
2-4
Executives reached out for analytic info update monthly
Internal AI is a major company initiative, and this portal is where every idea starts. As submissions and tickets climb, employees wait longer to get started and reviewers lose hours to avoidable questions, so the redesign protects both the AI pipeline and the team's time.
One Portal Serving Three Workflows
Employees
Employees submit AI use cases through the platform for review.
Current Challenges:
High Abandonment: The form asked review-stage questions that employees couldn't answer at that point, so they left before submitting.
Missing Updates: No notifications or clear next steps, so employees missed actions they owed on their submissions.
Review Teams
The Review team evaluates submissions and approves or requests additional actions on each case.
Current Challenges:
Scattered Information: Reviewers had to jump between multiple pages to assemble a single case.
Unplanned Support Load: Confused employees brought questions straight to reviewers, who ended up doing work outside their job.
Executives
Executives review AI use cases to track progress in enterprise AI adoption.
Current Challenges:
No Executive View: Leadership got the same interface as the review team. No summary, no way to see adoption at a glance.
Background
A Tool Built by Backend Reviewers, for Reviewers
The AI use case portal launched in 2023, built entirely by the review and engineering teams with no design input. It worked the way reviewers work: dense and technical, and they didn't mind. As the company scaled its AI adoption, submissions grew, and so did complaints and abandonment rates. The portal worked for the people who built it and failed everyone else. I picked up the redesign using the feedback backlog the team had already gathered.
Why the Redesign Matters
300+
AI use cases submitted through the portal in two years
50+
Support tickets employees opened (last 3 months before this project)
2-4
Executives reached out for analytic info update monthly
Internal AI is a major company initiative, and this portal is where every idea starts. As submissions and tickets climb, employees wait longer to get started and reviewers lose hours to avoidable questions, so the redesign protects both the AI pipeline and the team's time.
One Portal Serving Three Workflows
Employees
Employees submit AI use cases through the platform for review.
Current Challenges:
High Abandonment: The form asked review-stage questions that employees couldn't answer at that point, so they left before submitting.
Missing Updates: No notifications or clear next steps, so employees missed actions they owed on their submissions.
Review Teams
The Review team evaluates submissions and approves or requests additional actions on each case.
Current Challenges:
Scattered Information: Reviewers had to jump between multiple pages to assemble a single case.
Unplanned Support Load: Confused employees brought questions straight to reviewers, who ended up doing work outside their job.
Executives
Executives review AI use cases to track progress in enterprise AI adoption.
Current Challenges:
No Executive View: Leadership got the same interface as the review team. No summary, no way to see adoption at a glance.
Background
A Tool Built by Backend Reviewers, for Reviewers
The AI use case portal launched in 2023, built entirely by the review and engineering teams with no design input. It worked the way reviewers work: dense and technical, and they didn't mind. As the company scaled its AI adoption, submissions grew, and so did complaints and abandonment rates. The portal worked for the people who built it and failed everyone else. I picked up the redesign using the feedback backlog the team had already gathered.
Why the Redesign Matters
300+
AI use cases submitted through the portal in two years
50+
Support tickets employees opened (last 3 months before this project)
2-4
Executives reached out for analytic info update monthly
Internal AI is a major company initiative, and this portal is where every idea starts. As submissions and tickets climb, employees wait longer to get started and reviewers lose hours to avoidable questions, so the redesign protects both the AI pipeline and the team's time.
One Portal Serving Three Workflows
Employees
Employees submit AI use cases through the platform for review.
Current Challenges:
High Abandonment: The form asked review-stage questions that employees couldn't answer at that point, so they left before submitting.
Missing Updates: No notifications or clear next steps, so employees missed actions they owed on their submissions.
Review Teams
The Review team evaluates submissions and approves or requests additional actions on each case.
Current Challenges:
Scattered Information: Reviewers had to jump between multiple pages to assemble a single case.
Unplanned Support Load: Confused employees brought questions straight to reviewers, who ended up doing work outside their job.
Executives
Executives review AI use cases to track progress in enterprise AI adoption.
Current Challenges:
No Executive View: Leadership got the same interface as the review team. No summary, no way to see adoption at a glance.
Design Strategy
The original portal tangled three jobs into one interface. I pulled the threads apart and built each group a path shaped around what they came to do. The constraint was to separate those experiences without breaking the single system that connects them, so one submission still moves cleanly from employee to reviewer to executive.
Design Strategy
The original portal tangled three jobs into one interface. I pulled the threads apart and built each group a path shaped around what they came to do. The constraint was to separate those experiences without breaking the single system that connects them, so one submission still moves cleanly from employee to reviewer to executive.
Design Strategy
The original portal tangled three jobs into one interface. I pulled the threads apart and built each group a path shaped around what they came to do. The constraint was to separate those experiences without breaking the single system that connects them, so one submission still moves cleanly from employee to reviewer to executive.
Design Strategy
The original portal tangled three jobs into one interface. I pulled the threads apart and built each group a path shaped around what they came to do. The constraint was to separate those experiences without breaking the single system that connects them, so one submission still moves cleanly from employee to reviewer to executive.
Validation
Validated through usability testing with employees, reviewers, and executives
34% reduction in operational task time
Employees and reviewers completed core submission and review tasks 34% faster than with the original tool during moderated testing. The sample was small (n=8), so I read it as a strong directional signal.
100% stakeholder approval
The review team built the original and never asked for any changes to the review structure. After testing both versions, everyone agreed that the redesign works better.
Ready to build
I worked with the React engineering team from day one, so they could build straight from the designs instead of waiting on a handoff.
Scalable design system
I built a design system the team still uses, so they build new dashboards faster and keep them visually consistent.
What I'd Measure After Launch
I designed the redesign around the outcomes it needed to move. Once it's live, these metrics show whether it worked:
Submission abandonment
Whether staging stops the drop-off before submit.
Support tickets per month
Whether the new platform pulls the number down.
Time from submission to decision
Whether the consolidated review workspace speeds up reviews.
Executive dashboard use
How often leadership checks it instead of asking the review team
Validation
Validated through usability testing with employees, reviewers, and executives
34% reduction in operational task time
Employees and reviewers completed core submission and review tasks 34% faster than with the original tool during moderated testing. The sample was small (n=8), so I read it as a strong directional signal.
100%
stakeholder approval
The review team built the original and never asked for any changes to the review structure. After testing both versions, everyone agreed that the redesign works better.
Ready to build
I worked with the React engineering team from day one, so they could build straight from the designs instead of waiting on a handoff.
Scalable design system
I built a design system the team still uses, so they build new dashboards faster and keep them visually consistent.
What I'd Measure After Launch
I designed the redesign around the outcomes it needed to move. Once it's live, these metrics show whether it worked:
Submission abandonment
Whether staging stops the drop-off before submit.
Support tickets per month
Whether the new platform pulls the number down.
Time from submission to decision
Whether the consolidated review workspace speeds up reviews.
Executive dashboard use
How often leadership checks it instead of asking the review team
Validation
Validated through usability testing with employees, reviewers, and executives
34% reduction in operational task time
Employees and reviewers completed core submission and review tasks 34% faster than with the original tool during moderated testing. The sample was small (n=8), so I read it as a strong directional signal.
100% stakeholder approval
The review team built the original and never asked for any changes to the review structure. After testing both versions, everyone agreed that the redesign works better.
Ready to build
I worked with the React engineering team from day one, so they could build straight from the designs instead of waiting on a handoff.
Scalable design system
I built a design system the team still uses, so they build new dashboards faster and keep them visually consistent.
What I'd Measure After Launch
I designed the redesign around the outcomes it needed to move. Once it's live, these metrics show whether it worked:
Submission abandonment
Whether staging stops the drop-off before submit.
Support tickets per month
Whether the new platform pulls the number down.
Time from submission to decision
Whether the consolidated review workspace speeds up reviews.
Executive dashboard use
How often leadership checks it instead of asking the review team
Validation
Validated through usability testing with employees, reviewers, and executives
34% reduction in operational task time
Employees and reviewers completed core submission and review tasks 34% faster than with the original tool during moderated testing. The sample was small (n=8), so I read it as a strong directional signal.
100% stakeholder approval
The review team built the original and never asked for any changes to the review structure. After testing both versions, everyone agreed that the redesign works better.
Ready to build
I worked with the React engineering team from day one, so they could build straight from the designs instead of waiting on a handoff.
Scalable design system
I built a design system the team still uses, so they build new dashboards faster and keep them visually consistent.
What I'd Measure After Launch
I designed the redesign around the outcomes it needed to move. Once it's live, these metrics show whether it worked:
Submission abandonment
Whether staging stops the drop-off before submit.
Support tickets per month
Whether the new platform pulls the number down.
Time from submission to decision
Whether the consolidated review workspace speeds up reviews.
Executive dashboard use
How often leadership checks it instead of asking the review team