Brendan Kelly UX Site Logo
Back to top

Scroll to Top

icon
icon

Visit more pages:

Go to the Work page for brendankelly:

Go to the About page for brendankelly:

Read Brendan’s Cisco Case Study:

Read Brendan’s ExxonMobil Case Study:

Read Brendan’s Panasonic Case Study:

Read Brendan’s Verizon Case Study:

Read Brendan’s RWJF Case Study:

About Brendan

I’m the most interesting man you’ll read about on this whole website. Learn more about me, how I work, and what makes me tick.

Rubik's Cube
Brendan speaking on stage at Adobe Summit, microphone in hand, mid-gesture to the audience.

I'm Brendan, a UX designer and strategist based in Salt Lake City. I've spent about 15 years working on complicated digital experiences, and the part of UX I love most is the investigation: figuring out what people are actually trying to do, what's getting in their way, and how to make something complicated suddenly feel obvious.

​

My background is in computer science, but I've always been much more interested in the human side of technology.

​

Outside of work, I'm usually hiking somewhere in Utah, taking photos, spinning poi, spending time with my family, or hosting a game night.

​

I'm endlessly curious, I like learning things deeply, and I'm happiest when I have something new to figure out.

Stuff I wrote

An assortment of writings that help you get to know what’s happening in my brain

Dolly Parton Cubic Bagel
Dolly

I drive AI adoption...and I’m a friend of Dolly

Generative AI solutions have promised amplification: faster prototyping, richer insights, new creative possibilities. But amplification only works if people feel safe innovating. Too often, AI gets framed as a tool for cheating or being lazy. The real work is building a culture that removes that fear.

​

In my team, that began with socializing tools in a relaxed and welcoming environment. I started a weekly AI ‘Roundup,’ which began with sharing an image or short text I had made using AI, paired with two questions:

  1. “What do you think I tried to create?”
  2. “What do you think I wrote as a prompt?”

​

In the early weeks, the examples were absurd; and that was the point. One week, I showed a “cease and desist letter from Dolly Parton written without the letter ‘R’.” Another time, an AI-generated photo of a “cubist bagel.” The laughter lowered the stakes. After the guessing ended, I’d reveal my intent and walk through three evolving prompts that got me to the result I wanted, explaining what I changed each time and why.

​

The sessions caught on quickly, drawing people from other departments. Over time, the examples became closer to our real work. Beneath the humor, a tacit lesson emerged: this is how we use AI: iteratively, transparently, and as a creative partner, not a shortcut. The team learned by playing, and I made them co-authors of the message they were meant to absorb.

​

The result was a shared template for what it means to show your work when using AI tools and to do so without fear of overly zealous scrutiny. Transparency changed everything. Instead of wondering if it was “okay” to use AI, people started sharing discoveries, refining prompts, and learning from one another. It created a level playing field: everyone, regardless of experience, had something new to contribute. The tools amplified talent, but the culture amplified trust.

​

That’s what orchestration means to me: integrating new technology and creating the conditions that move barriers out of the way. Adoption alone isn’t progress. Progress happens when people feel empowered to use new tools openly, ethically, and together.

continue reading

Start the conversation

Case study collage

I delegate outcomes instead of tasks

When we manage by outcomes, we give our teams the autonomy, responsibility, and ownership to chart their own path.

- Teresa Torres

I set a direction, shine a light ahead, and then put trust in talented people to find the best path forward. It’s not an easy attitude to figure out, and loosening my grip on the reins was a challenge for me while growing in my career. When I began leading teams, I made a common leadership mistake: before assigning tasks, I would envision the steps I would take to complete them. When it came time to evaluate, I was just looking for ways the work differed from my expectations and I’d miss the merit of the way my teams would solve the problems their own way.

​

It took self-reflection, growth, and mentorship to learn an important lesson: Good leaders don’t assign tasks, they assign problems. If the navigation of a site isn’t working, I don’t tell a designer to “move a link” or “change a label.” I ask them to find out why people are getting lost. When you delegate the problem instead of the steps, you build ownership; and ownership builds momentum, creativity, and accountability.

​

Leadership, at its core, is trust paired with clarity. When people understand the goal and feel empowered to solve it, they don’t just follow, they lead. And there is no greater success as a leader than developing leadership in others.

continue reading

what-if?

I ask “what if...” to sell ideas

My dad often told me he could see me going into sales and I’d often reply with a scoff. I wanted to build things, solve real problems, turn chaos into something that actually worked. Sales was for people who didn’t want to create something. I had a plan, and it did not involve a quota.

​

Years later, deep into a career centered around craft, I had to reckon with something. The part of my job I had grown the most in and the part I looked forward to the most, was the part where I walk into a room, shine a spotlight on the work, and convince people. Convince them this idea is Worth pursuing. Worth fighting for. Worth making real. My work never saw the light of day if I couldn't get people excited enough to build it with me.

​

My dad was right. Turns out I went into sales after all.

​

I was terrible at selling ideas for longer than I'd like to admit. I remember a client meeting that went sideways from the first slide. I had everything: research, polish, a narrative that felt airtight. They questioned every single choice. I walked out deflated and went straight to my mentor. He heard me out, and told me: "You're approaching it like a lawyer. Trying to win. But your clients don't need to submit to you. They need to be on your side.”

​

That advice landed. I'd been designing with empathy for users and then walking into client rooms like I was there to prosecute them. The empathy just switched off.

​

So I changed my intent. Instead of trying to deliver a conclusion, I started trying to guide the room to one together. The simplest tool I found for doing that was to stop saying how things ought to be and start asking “what if we did it differently?”

​

What if it looked like this?

What would that mean for your users?

What would it take to get there?

​

Not "the data says we must do this."

Not "this is the right answer."

Just: what if...

​

If I ask you to picture a castle, yours won't look anything like mine. Different towers, different stones, different sky. And I don't need you to want my castle. I need you to want yours. When I open with mine, I've narrowed your imagination to fit around my vision, and something gets lost. ‘What if’ keeps the image open long enough for you to fill it in yourself.

​

It’s worked for me when leading teams towards change, too. But I want to be honest about how it actually works in practice, because organizational change doesn't happen because someone asked a good question in a meeting or an e-mail.

​

At one agency I worked at, the design team rarely shared work in progress. Unforgiving processes favored polished files, scheduled reviews, and work that had already calcified into something that felt difficult to challenge. Feedback became cautious. Revisions felt like admissions of failure. The work that made it to clients was fine, but it was rarely surprising, because we had optimized away the freedom to reach.

​

I didn't call a meeting and announce that we were doing things differently. That's not how people change.

​

Instead I started having individual conversations:With designers, I asked what it felt like to get feedback on finished work. Most of them, when given the space to be honest, admitted it felt like a verdict. With project managers, I asked what they thought they were actually seeing in those reviews, and whether they felt like they had any real influence on the outcome. With creative directors, I asked what it would mean for the quality of the work if they were seeing it three weeks earlier.

​

Nobody disagreed with the diagnosis. They just hadn't been asked to look at it directly.

​

From there it was incremental: A casual share here, an informal gut-check there. I framed early sharing not as a new process but as a favor: I'd love a quick gut-check before this goes too far in one direction. When it worked, people noticed. When a project came out stronger because a creative director had caught something early, I made sure that story got told.

​

Eventually it wasn't my idea anymore. That's how you know it worked.

​

The team trusted each other more because people had been invited into the work before it was finished, and that changed how we felt about it. Reviewers stopped feeling like judges. Designers stopped performing. The work got better, but the more lasting shift was that the team started thinking out loud together instead of presenting conclusions at each other.

​

Collaboration that happens in the open is how work moves forward.

​

The most useful thing I can bring into a room usually isn't an answer. It's a question that makes the answer belong to everyone.

continue reading

When I worked with Panasonic Connect, asking “what if...” helped move the needle for their business strategy.

See my work with Panasonic

Case study collage

More stuff I wrote...this time on LinkedIn

Core Principles

Empathy

Clarity

Culture

Energy

Growth

Curiosity

Let’s connect

LinkedIn
mail icon

Visit more pages:

Go to the Work page for brendankelly:

Go to the About page for brendankelly:

Read Brendan’s Cisco Case Study:

Read Brendan’s ExxonMobil Case Study:

Read Brendan’s Panasonic Case Study:

Read Brendan’s Verizon Case Study:

Read Brendan’s RWJF Case Study:

Brendan Kelly UX Site Logo

Let’s Connect

About Brendan

I’m the most interesting man you’ll read about on this whole website. Learn more about me, how I work, and what makes me tick.

Rubik's Cube
Brendan speaking on stage at Adobe Summit, microphone in hand, mid-gesture to the audience.

I'm Brendan, a UX designer and strategist based in Salt Lake City. I've spent about 15 years working on complicated digital experiences, and the part of UX I love most is the investigation: figuring out what people are actually trying to do, what's getting in their way, and how to make something complicated suddenly feel obvious.

​

My background is in computer science, but I've always been much more interested in the human side of technology.

​

Outside of work, I'm usually hiking somewhere in Utah, taking photos, spinning poi, spending time with my family, or hosting a game night.

​

I'm endlessly curious, I like learning things deeply, and I'm happiest when I have something new to figure out.

Stuff I wrote

An assortment of writings that help you get to know what’s happening in my brain

Dolly Parton Cubic Bagel
Dolly

I drive AI adoption...and I’m a friend of Dolly

Generative AI solutions have promised amplification: faster prototyping, richer insights, new creative possibilities. But amplification only works if people feel safe innovating. Too often, AI gets framed as a tool for cheating or being lazy. The real work is building a culture that removes that fear.

​

In my team, that began with socializing tools in a relaxed and welcoming environment. I started a weekly AI ‘Roundup,’ which began with sharing an image or short text I had made using AI, paired with two questions:

  1. “What do you think I tried to create?”
  2. “What do you think I wrote as a prompt?”

​

In the early weeks, the examples were absurd; and that was the point. One week, I showed a “cease and desist letter from Dolly Parton written without the letter ‘R’.” Another time, an AI-generated photo of a “cubist bagel.” The laughter lowered the stakes. After the guessing ended, I’d reveal my intent and walk through three evolving prompts that got me to the result I wanted, explaining what I changed each time and why.

​

The sessions caught on quickly, drawing people from other departments. Over time, the examples became closer to our real work. Beneath the humor, a tacit lesson emerged: this is how we use AI: iteratively, transparently, and as a creative partner, not a shortcut. The team learned by playing, and I made them co-authors of the message they were meant to absorb.

​

The result was a shared template for what it means to show your work when using AI tools and to do so without fear of overly zealous scrutiny. Transparency changed everything. Instead of wondering if it was “okay” to use AI, people started sharing discoveries, refining prompts, and learning from one another. It created a level playing field: everyone, regardless of experience, had something new to contribute. The tools amplified talent, but the culture amplified trust.

​

That’s what orchestration means to me: integrating new technology and creating the conditions that move barriers out of the way. Adoption alone isn’t progress. Progress happens when people feel empowered to use new tools openly, ethically, and together.

Try it with me! Send me a message and let me know you’d like to try the AI Roundup challenge.

Start the conversation

Case study collage

continue reading

I delegate outcomes instead of tasks

When we manage by outcomes, we give our teams the autonomy, responsibility, and ownership to chart their own path.

- Teresa Torres

I set a direction, shine a light ahead, and then put trust in talented people to find the best path forward. It’s not an easy attitude to figure out, and loosening my grip on the reins was a challenge for me while growing in my career. When I began leading teams, I made a common leadership mistake: before assigning tasks, I would envision the steps I would take to complete them. When it came time to evaluate, I was just looking for ways the work differed from my expectations and I’d miss the merit of the way my teams would solve the problems their own way.

​

It took self-reflection, growth, and mentorship to learn an important lesson: Good leaders don’t assign tasks, they assign problems. If the navigation of a site isn’t working, I don’t tell a designer to “move a link” or “change a label.” I ask them to find out why people are getting lost. When you delegate the problem instead of the steps, you build ownership; and ownership builds momentum, creativity, and accountability.

​

Leadership, at its core, is trust paired with clarity. When people understand the goal and feel empowered to solve it, they don’t just follow, they lead. And there is no greater success as a leader than developing leadership in others.

continue reading

what-if?

I ask “what if...” to sell ideas

My dad often told me he could see me going into sales and I’d often reply with a scoff. I wanted to build things, solve real problems, turn chaos into something that actually worked. Sales was for people who didn’t want to create something. I had a plan, and it did not involve a quota.

​

Years later, deep into a career centered around craft, I had to reckon with something. The part of my job I had grown the most in and the part I looked forward to the most, was the part where I walk into a room, shine a spotlight on the work, and convince people. Convince them this idea is Worth pursuing. Worth fighting for. Worth making real. My work never saw the light of day if I couldn't get people excited enough to build it with me.

​

My dad was right. Turns out I went into sales after all.

​

I was terrible at selling ideas for longer than I'd like to admit. I remember a client meeting that went sideways from the first slide. I had everything: research, polish, a narrative that felt airtight. They questioned every single choice. I walked out deflated and went straight to my mentor. He heard me out, and told me: "You're approaching it like a lawyer. Trying to win. But your clients don't need to submit to you. They need to be on your side.”

​

That advice landed. I'd been designing with empathy for users and then walking into client rooms like I was there to prosecute them. The empathy just switched off.

​

So I changed my intent. Instead of trying to deliver a conclusion, I started trying to guide the room to one together. The simplest tool I found for doing that was to stop saying how things ought to be and start asking “what if we did it differently?”

​

What if it looked like this?

What would that mean for your users?

What would it take to get there?

​

Not "the data says we must do this."

Not "this is the right answer."

Just: what if...

​

If I ask you to picture a castle, yours won't look anything like mine. Different towers, different stones, different sky. And I don't need you to want my castle. I need you to want yours. When I open with mine, I've narrowed your imagination to fit around my vision, and something gets lost. ‘What if’ keeps the image open long enough for you to fill it in yourself.

​

It’s worked for me when leading teams towards change, too. But I want to be honest about how it actually works in practice, because organizational change doesn't happen because someone asked a good question in a meeting or an e-mail.

​

At one agency I worked at, the design team rarely shared work in progress. Unforgiving processes favored polished files, scheduled reviews, and work that had already calcified into something that felt difficult to challenge. Feedback became cautious. Revisions felt like admissions of failure. The work that made it to clients was fine, but it was rarely surprising, because we had optimized away the freedom to reach.

​

I didn't call a meeting and announce that we were doing things differently. That's not how people change.

​

Instead I started having individual conversations:With designers, I asked what it felt like to get feedback on finished work. Most of them, when given the space to be honest, admitted it felt like a verdict. With project managers, I asked what they thought they were actually seeing in those reviews, and whether they felt like they had any real influence on the outcome. With creative directors, I asked what it would mean for the quality of the work if they were seeing it three weeks earlier.

​

Nobody disagreed with the diagnosis. They just hadn't been asked to look at it directly.

​

From there it was incremental: A casual share here, an informal gut-check there. I framed early sharing not as a new process but as a favor: I'd love a quick gut-check before this goes too far in one direction. When it worked, people noticed. When a project came out stronger because a creative director had caught something early, I made sure that story got told.

​

Eventually it wasn't my idea anymore. That's how you know it worked.

​

The team trusted each other more because people had been invited into the work before it was finished, and that changed how we felt about it. Reviewers stopped feeling like judges. Designers stopped performing. The work got better, but the more lasting shift was that the team started thinking out loud together instead of presenting conclusions at each other.

​

Collaboration that happens in the open is how work moves forward.

​

The most useful thing I can bring into a room usually isn't an answer. It's a question that makes the answer belong to everyone.

When I worked with Panasonic Connect, asking “what if...” helped move the needle for their business strategy.

See my work with Panasonic

Case study collage

continue reading

More stuff I wrote...this time on LinkedIn

Core Principles

Empathy

Culture

Growth

Clarity

Energy

Curiosity

Let’s connect

LinkedIn
mail icon

Visit more pages:

Go to the Work page for brendankelly:

Go to the About page for brendankelly:

Read Brendan’s Cisco Case Study:

Read Brendan’s ExxonMobil Case Study:

Read Brendan’s Panasonic Case Study:

Read Brendan’s Verizon Case Study:

Read Brendan’s RWJF Case Study:

Brendan Kelly UX Site Logo

Let’s Connect

About Brendan

I’m the most interesting man you’ll read about on this whole website. Learn more about me, how I work, and what makes me tick.

Rubik's Cube

I'm Brendan, a UX designer and strategist based in Salt Lake City. I've spent about 15 years working on complicated digital experiences, and the part of UX I love most is the investigation: figuring out what people are actually trying to do, what's getting in their way, and how to make something complicated suddenly feel obvious.

​

My background is in computer science, but I've always been much more interested in the human side of technology.

​

Outside of work, I'm usually hiking somewhere in Utah, taking photos, spinning poi, spending time with my family, or hosting a game night.

​

I'm endlessly curious, I like learning things deeply, and I'm happiest when I have something new to figure out.

Brendan speaking on stage at Adobe Summit, microphone in hand, mid-gesture to the audience.

Stuff I wrote

An assortment of writings that help you get to know what’s happening in my brain

Dolly Parton Cubic Bagel
Dolly

I drive AI adoption...and I’m a friend of Dolly

Generative AI solutions have promised amplification: faster prototyping, richer insights, new creative possibilities. But amplification only works if people feel safe innovating. Too often, AI gets framed as a tool for cheating or being lazy. The real work is building a culture that removes that fear.

​

In my team, that began with socializing tools in a relaxed and welcoming environment. I started a weekly AI ‘Roundup,’ which began with sharing an image or short text I had made using AI, paired with two questions:

  1. “What do you think I tried to create?”
  2. “What do you think I wrote as a prompt?”

​

In the early weeks, the examples were absurd; and that was the point. One week, I showed a “cease and desist letter from Dolly Parton written without the letter ‘R’.” Another time, an AI-generated photo of a “cubist bagel.” The laughter lowered the stakes. After the guessing ended, I’d reveal my intent and walk through three evolving prompts that got me to the result I wanted, explaining what I changed each time and why.

​

The sessions caught on quickly, drawing people from other departments. Over time, the examples became closer to our real work. Beneath the humor, a tacit lesson emerged: this is how we use AI: iteratively, transparently, and as a creative partner, not a shortcut. The team learned by playing, and I made them co-authors of the message they were meant to absorb.

​

The result was a shared template for what it means to show your work when using AI tools and to do so without fear of overly zealous scrutiny. Transparency changed everything. Instead of wondering if it was “okay” to use AI, people started sharing discoveries, refining prompts, and learning from one another. It created a level playing field: everyone, regardless of experience, had something new to contribute. The tools amplified talent, but the culture amplified trust.

​

That’s what orchestration means to me: integrating new technology and creating the conditions that move barriers out of the way. Adoption alone isn’t progress. Progress happens when people feel empowered to use new tools openly, ethically, and together.

Try it with me! Send me a message and let me know you’d like to try the AI Roundup challenge.

Start the conversation

Case study collage

continue reading

I delegate outcomes instead of tasks

When we manage by outcomes, we give our teams the autonomy, responsibility, and ownership to chart their own path.

- Teresa Torres

I set a direction, shine a light ahead, and then put trust in talented people to find the best path forward. It’s not an easy attitude to figure out, and loosening my grip on the reins was a challenge for me while growing in my career. When I began leading teams, I made a common leadership mistake: before assigning tasks, I would envision the steps I would take to complete them. When it came time to evaluate, I was just looking for ways the work differed from my expectations and I’d miss the merit of the way my teams would solve the problems their own way.

​

It took self-reflection, growth, and mentorship to learn an important lesson: Good leaders don’t assign tasks, they assign problems. If the navigation of a site isn’t working, I don’t tell a designer to “move a link” or “change a label.” I ask them to find out why people are getting lost. When you delegate the problem instead of the steps, you build ownership; and ownership builds momentum, creativity, and accountability.

​

Leadership, at its core, is trust paired with clarity. When people understand the goal and feel empowered to solve it, they don’t just follow, they lead. And there is no greater success as a leader than developing leadership in others.

continue reading

what-if?

I ask “what if...” to sell ideas

My dad often told me he could see me going into sales and I’d often reply with a scoff. I wanted to build things, solve real problems, turn chaos into something that actually worked. Sales was for people who didn’t want to create something. I had a plan, and it did not involve a quota.

​

Years later, deep into a career centered around craft, I had to reckon with something. The part of my job I had grown the most in and the part I looked forward to the most, was the part where I walk into a room, shine a spotlight on the work, and convince people. Convince them this idea is Worth pursuing. Worth fighting for. Worth making real. My work never saw the light of day if I couldn't get people excited enough to build it with me.

​

My dad was right. Turns out I went into sales after all.

​

I was terrible at selling ideas for longer than I'd like to admit. I remember a client meeting that went sideways from the first slide. I had everything: research, polish, a narrative that felt airtight. They questioned every single choice. I walked out deflated and went straight to my mentor. He heard me out, and told me: "You're approaching it like a lawyer. Trying to win. But your clients don't need to submit to you. They need to be on your side.”

​

That advice landed. I'd been designing with empathy for users and then walking into client rooms like I was there to prosecute them. The empathy just switched off.

​

So I changed my intent. Instead of trying to deliver a conclusion, I started trying to guide the room to one together. The simplest tool I found for doing that was to stop saying how things ought to be and start asking “what if we did it differently?”

​

What if it looked like this?

What would that mean for your users?

What would it take to get there?

​

Not "the data says we must do this."

Not "this is the right answer."

Just: what if...

​

If I ask you to picture a castle, yours won't look anything like mine. Different towers, different stones, different sky. And I don't need you to want my castle. I need you to want yours. When I open with mine, I've narrowed your imagination to fit around my vision, and something gets lost. ‘What if’ keeps the image open long enough for you to fill it in yourself.

​

It’s worked for me when leading teams towards change, too. But I want to be honest about how it actually works in practice, because organizational change doesn't happen because someone asked a good question in a meeting or an e-mail.

​

At one agency I worked at, the design team rarely shared work in progress. Unforgiving processes favored polished files, scheduled reviews, and work that had already calcified into something that felt difficult to challenge. Feedback became cautious. Revisions felt like admissions of failure. The work that made it to clients was fine, but it was rarely surprising, because we had optimized away the freedom to reach.

​

I didn't call a meeting and announce that we were doing things differently. That's not how people change.

​

Instead I started having individual conversations:With designers, I asked what it felt like to get feedback on finished work. Most of them, when given the space to be honest, admitted it felt like a verdict. With project managers, I asked what they thought they were actually seeing in those reviews, and whether they felt like they had any real influence on the outcome. With creative directors, I asked what it would mean for the quality of the work if they were seeing it three weeks earlier.

​

Nobody disagreed with the diagnosis. They just hadn't been asked to look at it directly.

​

From there it was incremental: A casual share here, an informal gut-check there. I framed early sharing not as a new process but as a favor: I'd love a quick gut-check before this goes too far in one direction. When it worked, people noticed. When a project came out stronger because a creative director had caught something early, I made sure that story got told.

​

Eventually it wasn't my idea anymore. That's how you know it worked.

​

The team trusted each other more because people had been invited into the work before it was finished, and that changed how we felt about it. Reviewers stopped feeling like judges. Designers stopped performing. The work got better, but the more lasting shift was that the team started thinking out loud together instead of presenting conclusions at each other.

​

Collaboration that happens in the open is how work moves forward.

​

The most useful thing I can bring into a room usually isn't an answer. It's a question that makes the answer belong to everyone.

When I worked with Panasonic Connect, asking “what if...” helped move the needle for their business strategy.

See my work with Panasonic

Case study collage

continue reading

More stuff I wrote...this time on LinkedIn

Core Principles

Empathy

Culture

Growth

Clarity

Energy

Curiosity