Security On-board
Our core Security team and its sister team, XWT, were in the process of merging into a single unified organization. A researcher and I were assigned to support this transition by assisting with feature development, identifying redundancies between the two teams, and helping establish a shared understanding of the evolving security space. One of our key objectives was to create a unified security administrator persona that both teams could align around.
Overview
The initial task was to create a visual map outlining the reporting structures of both teams, their primary focus areas, and the technologies they had each worked with. This helped identify where Canvas components could be introduced and revealed opportunities for future system contributions or component rebuilds.
Impact at a Glance
Process
Problem
Teams frequently chose an over-powered multi-select component even when it was unnecessary, leading to friction, inconsistency, and code sprawl across the platform.
- A swap from Sketch to Figma had been well received internally but the older XpressO toolkits had been abandoned during this transition period
- Product Designers had been showing up to reviews with their PM’s and Developers with designs, flows, and assets that were not buildable
- An unclear understanding of how Core platform tooling works in relation to our Design System. How enhancements get funded or how to present contributions
- Which UI kit to use based on the development team I’m working with
Approach
My initial task was to create a visual map outlining the reporting structures of both teams, their primary focus areas, and the technologies they had each worked with. This helped identify where Canvas components could be introduced and revealed opportunities for future system contributions or component rebuilds.
- Audit legacy prompt implementations across repos
- Define atomic → compound variant taxonomy
- Tokenize interaction + visual states
- Ship docs, decision trees, and examples
Project Gallery
