← Selected work

AI platform

AI Hub

A curated, role-based hub where Customer Service teams discover AI tools and learn how to use them.

Final design · The hub home page, organized around what employees need to do.
My role
UX lead: research, UX/UI design, and front-end updates
Collaborated with
Product manager, project team, software engineers
Audience
Customer Service teams worldwide
One trusted place Employees discover relevant AI tools and learn how to use them in a single hub, backed by an admin review flow for adding new tools.

Context and role

The AI Hub serves Customer Service teams worldwide. My part covered research, design, and implementation, working alongside the product manager, project team, and software engineers.

As an enterprise tool used across the organization, it had to meet accessibility requirements, and I accounted for accessibility throughout the design.

Role
UX lead: research, UX/UI design, and front-end updates
Collaborated with
Product manager, project team, software engineers
Year
2026

Responsibilities

  • Gathered user feedback and researched Customer Service job roles
  • Designed the complete feature suite for the hub
  • Designed the admin flow for reviewing and approving new tools
  • Presented the designs to leaders for final approval
  • Stayed involved through implementation with software engineers
  • Took over front-end updates to implement the design
  • Designed for accessibility, in line with enterprise requirements

Problem

Too many new tools, too little clarity.

New AI tools were being introduced company-wide almost every week. Employees in Customer Service struggled to find the right tool for their job and were unsure what to use.

The starting point was broad: tool overload and confusion. I created the AI Hub platform and owned the user experience end to end, from user feedback and research through design to implementation, for a worldwide audience.

The problem surfaced in two places: in leadership programs, and in feedback users shared with facilitators. Agents, tools, and apps were being created across the company, often duplicating each other, and people weren’t sure what to use whenever a new one appeared in their team or elsewhere.

UX process

Start from the job, not the tool.

I gathered user feedback and researched Customer Service job roles to define which tools and content each audience needed. That work shaped the structure of the hub around roles.

  1. ResearchFeedback and roles

    User feedback and a study of Customer Service job roles.

  2. DesignHub and tool pages

    A role-based hub with tool pages, use cases, and training videos.

  3. IterateRefined designs

    The designs refined over several rounds of feedback.

  4. ApproveLeadership review

    Designs presented to leaders for final approval.

  5. BuildWith engineers

    Built with software engineers, with front-end updates I implemented myself.

I stayed involved through implementation to keep the build aligned with the approved design, and briefly took over front-end updates to implement the design myself.

Solution

One hub, familiar patterns.

I designed the complete feature suite for the hub. Employees can find a curated list of tools for their role, open tool-specific pages with use cases and training videos, read reviews, and collaborate in community spaces.

I designed the experience to be relatable to existing hubs while staying distinct and specific to the organization and its needs.

Final design · Browsing tools, with space for each tool’s details.
Final design · Training content to help employees learn how to use the tools.
Final design · Community discussions, where users share how they use the tools.

Tool pages

Each tool has its own page: setup steps to get started, key features, supported use cases, success stories, and training resources. Ratings, target roles, and related tools sit alongside, so people can judge quickly whether a tool fits their work.

Final design · A tool page, from setup steps to training. Example tool shown.

About the hub

An About page sets out the hub’s mission and vision, and what it offers: curated AI tools, a community of people sharing what works, practical guidance for each tool, and a quality bar every tool is evaluated against.

Final design · The About page, with the hub’s mission, vision, and what it offers.

Trade-offs

Branding. The hub had to stay within the Customer Service branding, so I worked within it rather than giving the hub a look of its own.

The built-in assistant. An assistant built into the hub was explored as an experiment. The team later decided it wasn’t necessary, which kept the hub focused on helping people find and learn the right tools.

Engagement

Recognize the people who share what works.

An AI Champions leaderboard celebrates contributors. People earn points for reviews and the tools they use, collect badges such as Community Champion, AI Pioneer, and Tool Master, and can view the rankings for all time, by month, or by week, for technical and non-technical roles. A nomination button invites people to recognize a leader who inspires them. These features came out of wider team discussions, and I designed how they work in the hub.

Final design · The AI Champions leaderboard and Hall of Fame. Placeholder names.

A later home page

A later version of the home page brings points, a community pulse with the topic of the week, AI events, and learning paths onto the first screen.

Final design · Home page, version 4, with community pulse, AI events, and learning paths.

Responsible AI

Help people use AI well, not just find it.

A Responsible AI page explains why AI ethics matters and sets out clear do’s and don’ts, such as fact-checking outputs, combining AI with human judgment, and never sharing sensitive data. It links to the internal AI policy resources for anyone who wants more detail. The idea came out of wider team discussions, and I designed the page.

Final design · Responsible AI guidelines, with do’s and don’ts.

Governance

A way to add tools with care.

A hub stays useful only if new tools are added thoughtfully. The project manager and project team defined the governance model, including a request-and-review mechanism with approval criteria.

I designed the in-product flow that supports it: a smooth path for admins to review submitted tool requests and approve them against the criteria, including role eligibility approvals.

  1. SubmitTool request

    A tool is submitted for the hub.

  2. ReviewAgainst criteria

    Admins check it against the approval criteria.

  3. ApproveRole eligibility

    Admins approve it, including which roles it applies to.

Shaping this flow alongside the governance model influenced how new tools are introduced and reviewed.

Outcome

A trusted place to start.

The AI Hub gave the worldwide Customer Service organization one trusted place to discover relevant AI tools and learn how to use them.

Leaders approved the designs before handoff, and the build was developed with engineering to match them.

What this project shows

End to end ownership, research-driven design, leadership buy-in, and hands-on collaboration with engineering to deliver a curated, governed tool hub for a global audience.