Avanade Agentic Platform
Role
Product Designer
Duration
Active Engagement
Team
Product Design
tl;dr
I'm currently a product designer on the Avanade Agentic Platform team, owning UX and visual design for the Asset Library from ideation through final specs. This is my first project working directly on an AI product, and it's given me a chance to work AI into my own design process, using it to accelerate prototyping and ideation.
Screens are currently under NDA, but I'm happy to walk through the work in more detail.
Context
The Avanade Agentic Platform (AAP) is Avanade's internal AI platform that enables consultants to discover, build, and deploy agentic AI workflows across client engagements. I'm the product designer on this team, currently owning the design of the Asset Library, the platform's central surface for managing and discovering agentic solutions.
The Two Sides of the Asset Library
The Asset Library looks different depending on who you are.
For admins, the previous experience was a simple card grid where each asset had to be opened and published individually.
Before
That works at low volume, but the platform is scaling and admins needed a way to process a high volume of incoming solutions efficiently. We designed the admin view around batch publishing and modification, surfacing all relevant metadata inline so admins could make namespace and license decisions without having to open each asset individually.
After
Given that this was a UX improvement pass rather than a full redesign, we leaned heavily on existing design system components to keep implementation scope tight.
For non-admin consultants, the focus was on discovery. Rather than dropping users into an undifferentiated list of assets, we introduced curated category views that let consultants browse by theme, for example all assets related to customer service, alongside direct search across solutions, individual agents, and artifacts.
Where it's Going
This iteration was intentionally scoped as a bridge, improving the experience for both admins and browsing consultants within existing infrastructure constraints while buying the platform time until there's capacity for a more substantial redesign. The work is currently slotted for development, and I'm continuing to design across other areas of the platform.
The work has continued to evolve considerably since this writing. Several new surfaces have been introduced across the platform, each bringing its own set of constraints and decisions around hierarchy, state, and interaction model.
Working through development alongside engineering has surfaced edge cases and implementation nuances that have continued to shape the design in meaningful ways. More on that soon.
I'll update this as my time on the project goes on!