Site map and data page hierachy
Teams was an internal security tool used across Amazon to manage team-based permissions. The original system required manually adding people to groups and was difficult to navigate, especially for new users. Managers and individuals both needed to use it, but the experience lacked clarity and didn’t scale well for growing teams.
As the second designer on the team, I owned the Teams product and led UX for redesigning the dashboard. My goal was to make the workflow intuitive and reduce the burden of managing access across teams.
What the current designs looked like
Led end-to-end UX for the Teams dashboard
Collaborated with TPMs and engineers to align on what was possible for MLP
Focused on making the system role-based and easier to self-serve
Worked with the broader team to align on interaction patterns and consistency
The existing tool was fragmented and hard to navigate
No clear path for managers to add or remove team access
Users varied widely, from senior managers to individual contributors
Needed to ensure the experience worked within the technical limitations for launch
Replaced a manual, unclear process with a cleaner, role-based workflow
Enabled self-service access management for both individuals and managers
Created a clearer path through the dashboard that reduced friction for first-time users
Helped the team ship a focused, MLP-ready version while setting the stage for future improvements
Alongside my work on Teams, I partnered with the other designer to improve how permissions were modeled and grouped across multiple tools. I also contributed to broader design alignment across the security org, helping refine interaction patterns and working closely with TPMs and engineers to keep product direction focused and feasible for launch.
