design requirements
What the system
needed to support
Understanding the content
behind the visuals
The framework spanned Finance, Supply Chain, HR, Sustainability, Partners, and other areas. Each had its own content, stakeholders, and implementation needs.
My art director led working sessions with product experts, and I contributed across many of them. I used those conversations to understand which capabilities a page needed to communicate and translate complex product information into visual storytelling.
I also participated in regular check-ins with designers, web managers, and our developer to surface blockers and review implementation. For areas without embedded designers, I worked alongside my art director to create page designs and custom graphics directly.
These conversations shaped five requirements:
Maintain a recognizable direction across different product stories.
Give AI symbols and imagery a clear purpose.
Make the framework usable by designers working independently.
Account for accessibility, responsive behavior, and localization.
Keep designs practical to implement within the launch timeline.
[03]
solution
Agentic glass




Blur


Light Diffusion & Transparency




Layering


Color


Product UI


Key Features



Capabilities Section




Hero Graphics

Video Thumbnails

Product Trials & Tours


Hero
For animated heroes, we worked directly with our developer during design and iteration. The motion helped explain interactions such as Joule responding to a query or an agent completing a workflow.
Together we worked on refining visual treatments, reviewing responsive behavior, and preparing alt text for animated assets. Collaboration with the developer also brought loading behavior, contrast, and motion alternatives into the design process.
L1 Topic Overview
Joule
Line of Business (LOBs)
Business AI Platform (BAIP)
Industries
L2 Topic Pages


Resources


Types

Backgrounds

Web Page Color Pairings

Company logos

Types

Localization
I accounted for translated copy when adapting hero designs and kept text separate from graphics where possible.
For custom graphics that needed localization, I built a Figma-to-PowerPoint plugin. It allowed non-designer teams to adapt assets in a familiar tool. I also helped document the localization and developer handoff process.
This gave teams a way to work with delivered assets without relying on the design team for every language adaptation.






































