Intern welcome week presentation where I got to see Clippy. If you don’t know who he is, look him up.
Picture with my design studio team!
I got to meet some Minecraft legends.
I was blown away by the amazing architecture all over Microsoft campus.
The Seattle view was amazing!
Designing adaptive, AI-driven experiences for enterprise workflows.
Microsoft, 2025
I spent 12 weeks developing common patterns and features for AI integration on an enterprise scale within the Dynamics 365 team. I was given full control to create an AI driven experience within the Project Operations product focused on optimizing workflows.
My work is confidential and protected under NDA. Please reach out to learn more about this project!
Exploring adaptive interfaces
Designing for adaptive UX meant stepping into a space where no one on the team had all the answers. We were all learning in real time what it means to design for AI‑driven experiences, not just AI‑assisted features. During my internship, I spent my time reading articles, studying emerging patterns, and exploring live AI products to fast‑track my understanding. The goal wasn’t to replicate what already existed—it was to understand how intelligence changes the relationship between user, interface, and system.
The challenge was building something more visionary than a traditional UI. Instead of designing another button or card, I had to question the patterns themselves. Titles, headers, containers—these familiar structures often assume static content and predictable flows. But adaptive UX requires an interface that shifts, anticipates, and responds. It’s the difference between building the Subaru you drive and imagining the Tesla that drives itself. The work demanded breaking the system in order to create a new one.
Enterprise design patterns
Designing adaptive experiences at the enterprise level meant thinking beyond a single product team. My work needed to scale across multiple groups, each with different needs but shared constraints. I explored how AI‑driven interactions—like contextual recommendations, dynamic layouts, and predictive workflows—could become reusable patterns rather than one‑off solutions.
This required building frameworks that were flexible enough for teams to adopt, yet opinionated enough to maintain consistency. I wanted to create AI patterns that could travel: interactions that could be lifted, adapted, and reused across the organization without losing their integrity.