global website leadership
UX Team Identity, Task Navigation, and Agency guide
UX Team Identity, Task Navigation, and Agency guide
My team was having a difficult time navigating uncomfortable situations with stakeholders, so I needed to clearly establish their identity and authority.
My team was having a difficult time navigating uncomfortable situations with stakeholders, so I needed to clearly establish their identity and authority.
Stages
Problem
The UX team was struggling to navigate potential conflict with stakeholders. Many requests arrived with pre‑determined design solutions, dragged on for weeks, or were reopened after completion with new rounds of edits. The designers wanted to push back, say no, or draw a line in the sand but they hesitated despite their user experience expertise.
This dynamic led to:
Suboptimal turnaround times,
long editing cycles, and
Poorer user experiences than they knew we could deliver.
The team needed support, language, and structure to handle these situations without damaging relationships.
Problem
The UX team was struggling to navigate potential conflict with stakeholders. Many requests arrived with pre‑determined design solutions, dragged on for weeks, or were reopened after completion with new rounds of edits. The designers wanted to push back, say no, or draw a line in the sand but they hesitated despite their user experience expertise.
This dynamic led to:
Suboptimal turnaround times,
long editing cycles, and
Poorer user experiences than they knew we could deliver.
The team needed support, language, and structure to handle these situations without damaging relationships.
Strategy
Recalibrate the UX team’s identity
My strategy was to recalibrate the team’s identity and empower them to take the driver’s seat when collaborating with stakeholders. Instead of seeing themselves as service providers who simply execute requests, I wanted them to see themselves as experience owners with a duty to advocate for users.
To do that, we needed:
A shared identity and charter that clearly stated who we are and what we own
Practical guidance for navigating common, uncomfortable scenarios
Communication tools that made it easier to start tough conversations constructively
Strategy
Recalibrate the UX team’s identity
My strategy was to recalibrate the team’s identity and empower them to take the driver’s seat when collaborating with stakeholders. Instead of seeing themselves as service providers who simply execute requests, I wanted them to see themselves as experience owners with a duty to advocate for users.
To do that, we needed:
A shared identity and charter that clearly stated who we are and what we own
Practical guidance for navigating common, uncomfortable scenarios
Communication tools that made it easier to start tough conversations constructively
Approach & solution
To put this into practice, I designed a workshop and a supporting guide that combined mindset work with concrete, ready‑to‑use language.
Workshop and team identity
Held a 2‑hour workshop where we explored how the UX team saw themselves and how they wanted to be perceived
Identified common scenarios that were particularly tough to navigate with stakeholders (Figure 1)
Facilitated discussion on responsibilities, boundaries, and what “owning the experience” actually looks like day to day
From this, I created a UX team identity charter that:
Established the team as the user experience experts for our division
Defined their expertise, duties, and responsibility to advocate for customers
Clarified how we collaborate with stakeholders as partners, not order takers
Emphasized humility and empathy as core principles in all communication
Key scenarios and navigation protocols
We identified four recurring, challenging scenarios:
Bad UX / pre‑determined solutions
Tasks with no end in sight
The resurrected task (reopened after completion)
“Final” content that is not actually final
For each scenario, we developed:
A protocol outlining how to approach the situation step by step
Templated responses and conversation starters to make it easier to push back, reset expectations, or ask for what the team needed
The official guide
I then compiled all of the workshop content, the charter, the scenarios, and the protocols into a 15‑page LPS UX Identity, Task Navigation & Agency Guide and shared it with the team as a living reference (Figure 2).
Figure 1. Screenshot of our Miro board during the workshop. This board outlines four different scenarios with team notes.
Figure 2. Sample page from the LPS UX Identity, Task Navigation & Agency Guide. This begins the section dedicated to the 11 principles of LPS Digital UX identity.
Approach & solution
To put this into practice, I designed a workshop and a supporting guide that combined mindset work with concrete, ready‑to‑use language.
Workshop and team identity
Held a 2‑hour workshop where we explored how the UX team saw themselves and how they wanted to be perceived
Identified common scenarios that were particularly tough to navigate with stakeholders (Figure 1)
Facilitated discussion on responsibilities, boundaries, and what “owning the experience” actually looks like day to day
From this, I created a UX team identity charter that:
Established the team as the user experience experts for our division
Defined their expertise, duties, and responsibility to advocate for customers
Clarified how we collaborate with stakeholders as partners, not order takers
Emphasized humility and empathy as core principles in all communication
Key scenarios and navigation protocols
We identified four recurring, challenging scenarios:
Bad UX / pre‑determined solutions
Tasks with no end in sight
The resurrected task (reopened after completion)
“Final” content that is not actually final
For each scenario, we developed:
A protocol outlining how to approach the situation step by step
Templated responses and conversation starters to make it easier to push back, reset expectations, or ask for what the team needed
The official guide
I then compiled all of the workshop content, the charter, the scenarios, and the protocols into a 15‑page LPS UX Identity, Task Navigation & Agency Guide and shared it with the team as a living reference (Figure 2).
Figure 1. Screenshot of our Miro board during the workshop. This board outlines four different scenarios with team notes.
Figure 2. Sample page from the LPS UX Identity, Task Navigation & Agency Guide. This begins the section dedicated to the 11 principles of LPS Digital UX identity.
Outcome
The UX team found it very helpful to walk through the problematic scenarios so they could provide feedback. The identity guidelines also seemed to provide the team with a new view of themselves.
A core tool for the UX team
The guide is now a core part of our team’s makeup. It clearly defines who we are, how we see ourselves (Figure 3), and how we communicate with stakeholders when things get difficult. Designers have a shared language and a set of practical tools they can lean on instead of handling tough situations alone.
Within the first two months of its release, the guide helped the team navigate several tricky scenarios and move tasks along more smoothly. Designers reported feeling more confident pushing back when needed, and conversations with stakeholders became more balanced and constructive.
Going forward, this guide will be required onboarding material for new hires so they understand their value, authority, and communication playbook from day one.
Results
While the UX Identity, Task Navigation & Agency Guide needs some time to see major team changes, we expect to see:
A reduction in average edit cycles per task
Fewer tasks reopened after completion, and
A decrease in UX team members requiring my intervention to move tasks forward.
For now, I am very product of what we accomplished:
15
Pages empowering the UX team to take charge of tasks
4
Common scenarios with protocols and response templates
100%
UX team trained on the new guide
Outcome
The UX team found it very helpful to walk through the problematic scenarios so they could provide feedback. The identity guidelines also seemed to provide the team with a new view of themselves.
A core tool for the UX team
The guide is now a core part of our team’s makeup. It clearly defines who we are, how we see ourselves, and how we communicate with stakeholders when things get difficult. Designers have a shared language and a set of practical tools they can lean on instead of handling tough situations alone.
Within the first two months of its release, the guide helped the team navigate several tricky scenarios and move tasks along more smoothly. Designers reported feeling more confident pushing back when needed, and conversations with stakeholders became more balanced and constructive.
Going forward, this guide will be required onboarding material for new hires so they understand their value, authority, and communication playbook from day one.
Results
While the UX Identity, Task Navigation & Agency Guide needs some time to see major team changes, we expect to see:
A reduction in average edit cycles per task
Fewer tasks reopened after completion, and
A decrease in UX team members requiring my intervention to move tasks forward.
For now, I am very proud of my team and what we accomplished together:
15
Pages empowering the UX team to take charge of tasks
4
Common scenarios with protocols and response templates
100%
UX team trained on the new guide
Nicholas Fargher
© 2026 Nicholas Fargher
Nicholas Fargher
© 2026 Nicholas Fargher