Coca-Cola FEMSA — KOF
Designing internal enterprise experiences that bring clarity to complex operational workflows.
I contributed to internal enterprise platforms for Coca-Cola FEMSA, designing UX solutions for operational and business workflows within a complex product ecosystem. My work focused on understanding business logic, structuring flows, creating prototypes, aligning with technical teams, validating with functional users, and using AI-assisted workflows to explore visual solutions faster while staying grounded in KOF's Design System.
Company
Coca-Cola FEMSA — KOF
Industry
Enterprise / Operations / Consumer goods
Role
Product Designer / UX Designer
Product type
Internal enterprise platforms / Operational tools
Timeline
Jan 2025 – 29 Jun 2026
Team
UX, Business Analysts, Tech Leads, Developers, Functional Users, Client Stakeholders
Methods
Discovery, Benchmarking, IA, User Flows, Wireframes, Prototyping, Validation, Design System, Handoff
Tools
Figma, FigJam, Gemini, Figma Make, Jira / Confluence
Status
Delivered design initiatives / Under NDA
Some parts of this project are under NDA, so I'm showing a curated version of the process, artifacts, and outcomes. Sensitive product screens, operational logic, business rules, internal workflows, and client documentation have been blurred or simplified while keeping the design decisions, methodology, and my role clear. I'm happy to walk through more detail privately in an interview or portfolio review.
Sensitive product and operational details have been blurred or simplified to protect confidential business information.
Context
Coca-Cola FEMSA needed UX support for internal enterprise platforms used to manage operational and business workflows across a complex ecosystem. These initiatives required translating business rules, user needs, technical constraints, and Design System standards into clear, scalable digital experiences.
I worked on different initiatives such as Cockpit AdminPanel, MRK cell, Geofencing / Geocerca, Sales Leader Profile, and Command Center Image Bank. Each initiative had its own logic, stakeholders, and operational complexity, but all required the same foundation: clarity, consistency, validation, and development-ready UX decisions.
Why it mattered
Designing the screens was the easy 20%. The real work was understanding how internal users actually get things done, how the business processes behave underneath the interface, and turning that mess of requirements into flows people could follow, validate, build, and eventually scale.
My role
I worked as Product Designer / UX Designer, contributing to UX definition, product understanding, information architecture, interaction flows, prototyping, validation, and handoff within a larger enterprise ecosystem. My role connected business needs, functional user expectations, technical feasibility, and Design System consistency.
- Designed UX solutions for internal enterprise platforms and operational workflows.
- Worked on initiatives including Cockpit AdminPanel, MRK cell, Geofencing / Geocerca, Sales Leader Profile, and Command Center Image Bank.
- Translated business requirements into user flows, wireframes, prototypes, and documentation.
- Collaborated with Business Analysts, Tech Leads, developers, stakeholders, and functional users.
- Designed solutions aligned with KOF's Design System to maintain consistency and scalability.
- Conducted validation sessions with functional users and technical teams to reduce ambiguity before handoff.
- Used Gemini and Figma Make to explore visualization alternatives and accelerate context-based ideation.
- Rebuilt final solutions using existing Design System components or new structures based on its atomic foundations.
The challenge
The main challenge was designing clear, scalable UX solutions for internal platforms where the complexity lived behind the interface: business rules, operational workflows, user permissions, technical constraints, and multiple stakeholder expectations.
- User challenge: functional users needed tools that helped them complete operational tasks with clarity, confidence, and less cognitive load.
- Business challenge: KOF needed internal platforms that could support complex operational and business workflows while maintaining consistency, scalability, and readiness for development.
- Design challenge: the UX work required understanding complex logic quickly, aligning with multiple roles, validating assumptions, and designing within an existing Design System without losing flexibility.
Problem statement
How might we help functional users complete complex operational workflows through clearer internal tools, while supporting business logic, technical feasibility, and Design System consistency?
Goals & success criteria
User goals
- Help functional users understand and complete operational workflows more clearly.
- Reduce confusion caused by complex business logic or fragmented information.
- Improve confidence when interacting with internal enterprise tools.
Business goals
- Support internal operational and business workflows through scalable UX solutions.
- Reduce ambiguity before development.
- Align UX decisions with business rules, stakeholder needs, and product priorities.
- Maintain consistency across KOF's internal ecosystem.
Design goals
- Create clear user flows, wireframes, prototypes, and documentation.
- Use the existing Design System to support consistency and scalability.
- Validate proposed solutions with functional users and technical teams.
- Use AI-assisted workflows to explore alternatives faster without replacing UX judgment.
Process
01 — Discover
Understanding the business logic before designing the interface
I started each initiative by understanding the business context, the operational workflow, the users involved, and the constraints behind the request. In enterprise UX, the interface is only the visible layer; the real challenge is understanding the logic behind every decision.
- Reviewed business requirements, user stories, and available documentation.
- Clarified the purpose of each initiative with Business Analysts and stakeholders.
- Identified user roles, operational needs, dependencies, and technical constraints.
- Mapped current or expected flows to understand how the experience should behave.
- Used benchmarks and references when the team needed early visualization or alignment.
- Identified assumptions that needed validation before detailed design.
How I used AI
I used Gemini to organize the case context, user needs, business problem, stakeholders, process, and available files. This helped me create more precise prompts for Figma Make and explore early visualization alternatives faster. Final decisions stayed grounded in UX criteria, stakeholder feedback, product constraints, and KOF's Design System.
Discovery structure used to align business logic, user needs, and technical constraints before designing the interface.
02 — Define
Turning complex requirements into clear UX direction
After understanding the context, I translated requirements into a clearer UX direction. This helped align UX, BA, technical teams, and stakeholders before moving into detailed design, especially when the feature needed early visualization or the logic was difficult to understand through written requirements alone.
- Synthesized requirements into user flows and interaction logic.
- Defined information architecture and screen structure for each initiative.
- Identified which parts of the flow required validation with functional users.
- Prioritized clarity, consistency, and development readiness.
- Aligned the UX direction with BA, tech, and stakeholder expectations.
- Used FigJam flows and conceptual explorations to clarify the product logic before final execution.
How I used AI
I used Gemini to transform project context into structured prompts for Figma Make. AI helped generate visualization ideas, but I used those outputs only as exploration. The final UX direction was rebuilt with my own design judgment, stakeholder feedback, and KOF's Design System components.
User flow used to align product logic and reduce ambiguity before moving into wireframes and prototypes.
03 — Develop
Exploring solutions with Design System consistency
Once the UX direction was clear, I explored interface structures, flows, and prototypes. The goal was to design solutions that were understandable for users, realistic for development, and consistent with the broader KOF ecosystem.
- Created wireframes and prototypes for internal platform initiatives.
- Explored different ways to structure information, actions, filters, states, and operational data.
- Used KOF's Design System components to maintain visual and functional consistency.
- Built new structures when needed, using the atomic foundations of the existing system.
- Iterated based on feedback from BA, technical teams, stakeholders, and functional users.
- Balanced business complexity with usability and implementation feasibility.
How I used AI
I used Figma Make as an ideation accelerator after preparing prompts with Gemini. The generated explorations helped me see possible structures quickly, but I did not use them as final design. I rebuilt the final solutions using KOF's components, UX criteria, accessibility considerations, and feedback from the team.
Wireframe exploration used to test structure, hierarchy, and Design System alignment before detailed handoff.
AI-assisted exploration used as a starting point, later rebuilt with KOF's Design System and UX decision criteria.
04 — Deliver
Validating and handing off development-ready UX solutions
The final work translated complex business logic into clear UX artifacts ready for validation and development alignment. I documented flows, prototypes, design rationale, and interaction decisions so the team could reduce ambiguity before implementation.
- Delivered user flows, wireframes, prototypes, and UX documentation.
- Validated proposed solutions with functional users and technical teams.
- Prepared handoff material for developers and product teams.
- Documented design rationale, states, interactions, and important business rules.
- Supported alignment between UX, BA, tech, and stakeholders before development.
- Helped maintain consistency across internal tools by applying Design System standards.
How I used AI
I used AI to support speed during exploration and documentation, but not to replace decision-making. The final handoff was grounded in validated flows, Design System consistency, technical feasibility, and functional user feedback.
Handoff documentation created to reduce ambiguity and support development readiness.
Before / after
Before
Complex requirements and operational logic could be difficult to understand through documentation alone, creating ambiguity between UX, BA, technical teams, stakeholders, and functional users.
After
The work translated business logic into clearer flows, prototypes, validation artifacts, and Design System-aligned solutions that improved shared understanding before development.
Final solution
The final work focused on three main experience improvements:
Clearer operational flows
I translated complex business logic into user flows and prototypes that helped teams understand how each experience should behave before development.
Design System-aligned solutions
I used KOF's Design System to create consistent, scalable experiences across internal tools, adapting or extending structures only when the product logic required it.
AI-assisted ideation with UX control
I used Gemini and Figma Make to accelerate early visualization, then rebuilt final solutions through UX judgment, stakeholder feedback, and Design System components.
Impact & results
User value
Functional users received clearer internal experiences designed around operational workflows and validation needs.
Business value
Supported internal business and operational initiatives by translating complex logic into actionable UX solutions.
Team / process value
Reduced ambiguity between UX, BA, technical teams, and stakeholders before development.
Product / system value
Maintained consistency across internal tools by designing with KOF's Design System and scalable interaction patterns.
Obstacles & trade-offs
This project required constant trade-offs between business complexity, user clarity, technical feasibility, and Design System constraints. In enterprise UX, the challenge was not to simplify the business too much, but to make the workflow understandable without losing operational accuracy.
- Understanding complex business and operational logic quickly.
- Working with changing scope, evolving requirements, and shifting priorities.
- Balancing Design System consistency with feature-specific needs.
- Aligning UX decisions with BA, tech, developers, stakeholders, and functional users.
- Designing for internal workflows where users, rules, and permissions can vary.
- Creating clear handoff documentation for development.
- Using AI as an accelerator without allowing it to drive final UX decisions.
What I learned
This project reinforced something I already suspected about enterprise UX: making internal tools look cleaner is the easy part. The real skill is understanding the business logic deeply enough to make it usable, scalable, and buildable.
- I learned how to move faster through complex enterprise contexts without skipping UX rigor.
- I strengthened my ability to translate business requirements into clear flows and prototypes.
- I improved how I validate solutions with functional users and technical teams.
- I learned how to use AI as an exploration partner while keeping UX judgment at the center.
- I confirmed that Design Systems are most valuable when they support consistency without blocking product logic.
- I strengthened my ability to collaborate with BA, tech, and stakeholders in complex delivery environments.
What leaders said about my work
Stephanie demonstrated a high level of commitment, professionalism, and responsibility, contributing across research, information architecture, experience definition, user flows, benchmarking, prototyping, and validation.
Diana Castillo Vargas
She maintained effective communication with stakeholders and collaborated actively with multidisciplinary teams, bringing a user-centered perspective to improve the product experience.
Diana Castillo Vargas
KOF is probably the clearest example of how I work in an enterprise environment I'm still learning: get under the interface to understand the business logic, use AI where it actually helps speed up exploration, and turn what starts as ambiguity into decisions the team can validate and build on.
Stephanie Cacheo — Senior UX Designer