§ 00 / ABOUT

Serial problem solver.

Fixated on optimizing systems.

Obsessed with structure and flow.

Unapologetic technology geek.

Naturally, a UX designer.

§ 01 / BIO

Want a bit more?


I'm a product designer working on AI experiences inside Windows at Microsoft. My job sits at a strange and exciting intersection: operating systems, agents, enterprise workflows, trust, orchestration. All the messy, high-stakes problems that show up when software stops being a tool and starts acting on your behalf.

The more honest version is that I'm wired to solve problems. I don't really know how to turn it off. If something feels inefficient, structurally off, or just vaguely wrong, I will keep pulling on it until I understand it. Sometimes that means building prototypes late at night. Sometimes it means mapping systems no one asked me to map.

I have a habit of obsessively researching the "right" solution to things most people would settle on in an afternoon. I like constraints. I like tradeoffs. I like figuring out what the real problem is underneath the surface problem.

FIG. 1.1
Bryce Henthorn at altitude on a hike, smiling toward the camera with a green valley and clouds behind
Field site, summer 2024.

§ 02 / 04

Experience

§ 02 / EXPERIENCE

Building systems at scale since 2018


MICROSOFT

2025 – PRESENT

Windows Agent Platform

Led agent visibility and orchestration design across Shell, Copilot, and M365 integration surfaces. 3 engineering partner teams.

2025 – PRESENT

Copilot Actions

2023 – 2025

Windows Recall

Designed semantic search experience for Copilot+ PCs. Shipped at Build 2024. Navigated privacy redesign after public launch.

2022 – 2023

File Explorer Modernization (Windows 11)

2020 – 2021

Teams for Education

Led interaction design for virtual classroom experience serving 150M+ users. Reframed team strategy from growth metrics to engagement architecture.

2018 – 2020

Microsoft Education

PRIOR

AMAZON
Contract
NORDSTROM
Contract
§ 03 / PHILOSOPHY

Good design should feel inevitable in hindsight


Design, for me, is structure. It's the quiet architecture that makes complexity feel obvious. I care about progressive disclosure. I care about removing noise. I care about building systems that scale without collapsing under their own weight.

In the AI space especially, I think we're in a moment where clarity matters more than novelty. Agents that interrupt at the wrong time. Automation that feels unpredictable. Those are structural problems, not styling problems.

I'm not trying to design isolated features. I'm trying to design how systems behave over time. How they learn. How they earn trust. How they stay in flow instead of fragmenting it.

I'm ambitious about the impact of the work, but I'm pretty grounded about the craft. I still sweat alignment, hierarchy, edge cases, and empty states. The details matter because they're where trust is won or lost.

If you're building something that sits at the edge of what software can do, especially where AI and real human workflows meet, that's where I'm most energized. I like hard problems. I like unclear terrain. And I like turning chaos into something that feels simple and durable.