Shreeya Desai Portfolio

Back to home

Wibey — Rebuilt

Walmart Global Tech

In Progress

2026

Wibey — Rebuilt

Walmart Global Tech

In Progress

2026

Wibey — Rebuilt

Walmart Global Tech

In Progress

2026

Team

4 Designers (3 Staff Designers, plus myself as Product Designer), working alongside Engineering and Product Management.

Industry

AI / Developer Tools

Overview

I'm a Software Engineer / UX Designer II at Walmart Global Tech. Wibey is Walmart's internal AI assistant. Three staff designers had already researched one piece of its next version, the sessions panel and sidebar, and I was brought in to help alongside them.

The scope grew to Library, Documentation, Settings, Metrics, Catalog, and a new concept, Workspaces. With a background spanning engineering and design, once we started vibe-coding the prototype I was working directly in the codebase, not just the interface.

Outcome

Wibey is moving from a fragmented set of disconnected pages to one connected, workspace-driven experience, cutting the steps needed to switch context, create, and collaborate.

This work is still in progress, with impact measured against intended outcomes rather than live data yet.

Getting to know Wibey

Wibey is Walmart's internal AI assistant, used across all of Walmart Global Tech, from quick one-off questions to building and sharing AI-powered work. It's the tool engineers, designers, and other teams open daily to chat, create artefacts, discover reusable skills and agents, and now, with this redesign, organise that work as a team rather than individually.

Team

4 Designers (3 Staff Designers, plus myself as Product Designer), working alongside Engineering and Product Management.

Industry

AI / Developer Tools

Overview

Outcome

Wibey is moving from a fragmented set of disconnected pages to one connected, workspace-driven experience, cutting the steps needed to switch context, create, and collaborate.

This work is still in progress, with impact measured against intended outcomes rather than live data yet.

Getting to know Wibey

The challenge

A Product That Had Outgrown Itself

Wibey had grown feature by feature, and it showed. Screens were dense and hard to read, Chat and Sessions lived on separate pages with no shared space for a team's work, and creating anything meant leaving the product entirely, for Studio, for a separate Catalog platform, with no way to collaborate. This wasn't a fix for one broken flow, it was about making Wibey genuinely good to use.

Who are we designing for?

Target Audience

Designed for every employee across Walmart Global Tech, engineers, designers, product managers, people managers, and leadership alike.

ENGINEERS

DESIGNERS

PRODUCT MANAGERS

LEADERSHIP

PRODUCT MANAGERS

Getting started with design

Wireframes

Every solution below went through an earlier version before it shipped. These are the ones worth showing.

Solutions

Every solution below came out of the same rhythm: a stakeholder discussion, then one day to build a working version in code, using vibe coding, so the next review could react to something real instead of a slide. That speed came with real friction. Everyone worked in their own branch, in their own style, and merging separately-built explorations into one coherent product, once stakeholders approved a direction, was its own technical problem. We also ran through our AI credits faster than expected partway through and had to bring in additional agents to keep the pace up. Underneath all of it sat a quieter constraint: several parts of Wibey belonged to other teams, so what could be redesigned outright versus what had to be re-surfaced without disturbing ownership was a negotiation on almost every page.

Chat — Switch conversations without losing your place.

Merged two nav items, New Chat and Sessions, into one, since switching context meant fully leaving the current chat. Opening Chat now surfaces a sessions panel grouped by date or workspace, with a sources card, artefacts card, and timeline built in. Building this into the prototype meant working through how session state persists across the merged view, not just how it looks.

Workspaces — One shared home for the whole team's work.

A new concept: a shared home for a team's conversations, attachments, and artefacts. Built into existing surfaces rather than its own page, chats, Library, and CI/CD are all scoped to a workspace, so it doesn't add another destination to check. Creation and invite flows are still being defined.

Library — Everything you made, minus the clutter.

Attachments and artefacts existed before with no context, you couldn't tell where anything came from. Restructured to trace every item back to its origin, workspace and chat, with better filtering, more context per item, and a stronger visual quality bar than before.

Documentation — Answers, not another link to click.

Info used to be scattered across pages and external links with no single source of truth. Unified it into one page with everything a user needs. Pulled FAQs from real questions asked in page comments, Slack, and Confluence. Added a quick-ask feature, a page-scoped chat, for anything still missing.

Documentation — Answers, not another link to click.

Documentation didn't belong to anyone on the team going in, no one had asked us to redesign it, and there was no dedicated research behind it. I took ownership of it anyway, because it was clearly broken and no one else was going to fix it in this cycle. Info used to be scattered across pages and external links with no single source of truth. Unified it into one page with everything a user needs. Pulled FAQs from real questions asked in page comments, Slack, and Confluence. Added a quick-ask feature, a page-scoped chat, for anything still missing.

Metrics — The same data, finally easy to read.

The numbers belonged to other teams, not ours to change. What was ours: how people reach and explore that data. Redesigned filtering, layout, and pathways to related metrics, turning a noisy page into a navigable one.

Catalog — Try before you leave the page.

Was a read-only meta-registry pointing to a separate platform, users could look but never act. Rebuilt inside Wibey as fully interactive: try an artefact, duplicate it, or adopt it as-is, because passive discovery wasn't enough.

Create — Build together, without leaving Wibey.

Creating an artefact meant leaving for Studio, with no way to collaborate. Brought creation into Wibey and paired it with Workspaces, so teams build together in real time instead of across disconnected tools.

Quick Chat — A chat window that follows you, not the other way around.

Conversations felt locked to one screen. Hovering the sidebar chat icon now opens recent chats and a new chat button from anywhere, launching a floating window you can resize, drag, and dock.

Quick Chat — A chat window that follows you, not the other way around.

Conversations felt locked to one screen. Hovering the sidebar chat icon now opens recent chats and a new chat button from anywhere, launching a floating window you can resize, drag, and dock.

CICD

Engineers already had a tool for this, Pipeline Visualizer, but it lived outside Wibey on a separate platform. An earlier in-Wibey version, built by the senior designer who owns CI/CD, presented pipeline activity as a narrated agent trace, clear for a single incident, but with no sense of the pipeline's overall shape, five stages, some running in parallel, meant reading the whole trace just to see where things stood. A pipeline is spatial by nature, and a scrolling log flattens that. I rebuilt it as a visual, node-based canvas across the five real stages, each expandable into its actual steps, with a footer panel for Issues, Properties, Logs, Gatekeeper, and Analytics, so the depth is still there the moment you need it. Warnings and errors are highlighted directly on the canvas, visible before you even drill in.

Chat — Switch conversations without losing your place.

Workspaces — One shared home for the whole team's work.

Library — Everything you made, minus the clutter.

Documentation — Answers, not another link to click.

Metrics — The same data, finally easy to read.

Catalog — Try before you leave the page.

Create — Build together, without leaving Wibey.

Quick Chat — A chat window that follows you, not the other way around.

Conversations felt locked to one screen. Hovering the sidebar chat icon now opens recent chats and a new chat button from anywhere, launching a floating window you can resize, drag, and dock.

CICD

Overall Project Impact

Reduced tool sprawl.

Consolidating Studio and Catalog into Wibey means one less set of platforms to maintain and support.

Lower support burden.

Ask Wibey and page-level FAQs cut repeat questions reaching support teams.

Better cross-team reuse.

Workspaces and an interactive Catalog reduce duplicated work across teams.

Time saved at scale.

Small reductions in friction compound significantly across 10,000+ daily users.

Learnings

Speed and coordination pull in opposite directions. Vibe coding let us turn a stakeholder discussion into a working version in a single day, but everyone building in their own branch meant merging approved work back into one product was its own real technical problem, one I didn't fully anticipate going in.

Ownership shapes design as much as usability does. Several pages belonged to other teams before we ever touched them, so knowing what to redesign outright versus re-surface carefully was a constraint I had to navigate on nearly every page, not just Metrics.