Portrait of Brian Bradshaw

About

Senior product designer, Portland Metro

I love people. In college, at the University of Utah, I studied psychology, and most of what held my attention was decision making: why people choose what they choose, how influence actually works on a person, and what happens in the space between what someone means to do and what they end up doing. Thirteen years later, I am still circling that same question. I just carry a different set of tools now.

Since then I have worked across health, fintech, and software as a service, sometimes as the only designer in the building, but always on fast, agile teams, which meant I could not hide behind a narrow job description. I have run the research myself, built the design system myself, and more than once sat down and written the front end code myself, because that was the fastest way to find out if an idea actually worked once a real person touched it. I like that whole arc, start to finish. Research tells you what is true. Design turns that truth into something a person can use. Code is where you find out whether you were right.

AI has been part of that process since 2023, and not as something I bolted on to sound current. It changed how quickly I could move from a decision to something shipped. I have designed AI features that reached real patients, and I used that same AI assisted way of working to design and build the site you are reading right now, the same day, beginning to end, the way I try to work on everything.

Most recently, at Habit Layer, I have owned the design of a patient app and the dashboard the coaches and providers use to support them, including a system that helps make sense of health data without burying anyone in it. Before that, the work took me through a company built around genetics and methylation, into the specific and strange psychology of a workforce that spends eight hours a day transcribing song lyrics, and even into the middle of a crowd at a concert, trying to understand why people show up in the first place. Each of those projects looked completely different from the outside. Underneath, they were always the same question. What does this person need to understand right now, and what is the smallest number of steps between them and doing something about it.

I have a degree in psychology, not design, and I think that shows up in how I work more than any tool I use. I still read a room before I read a Figma file. If any of this sounds like a project you are working on, or a team you are building, I would like to hear about it.

Tools and methods

Design
Figma, including design systems, component libraries, variants, auto layout, and prototyping. Design tokens and token management for multi-brand consistency. Responsive web and mobile, interaction and visual design, information architecture, developer handoff.
Research and analytics
FullStory, Hotjar, Pendo, Amplitude, Mixpanel, PostHog, Google Analytics. Usability testing, moderated and unmoderated interviews, journey mapping, behavioral cohorts, design sprints, prototype validation.
AI
Claude, Claude Code, Claude Skills, ChatGPT, Gemini, Cursor. Research synthesis, qualitative pattern finding, content and terminology consistency across product surfaces, AI assisted front end implementation, prompt design and evaluation for user facing features.
Build
Next.js, React, HTML and CSS, REST APIs, FHIR R4B, no-code and low-code platforms.
Education
Bachelor of Science in Psychology, University of Utah, with a focus on decision making, influence, and cognition, including contributions to academic research. Certified SAFe 4 Agilist, Scaled Agile Inc.