nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Customer journey map

Terrence Young_wfxx3k

I am currently working with a very technical team that is very solution focused. While Vision has been clearly defined, the team often struggle to connect with the user they are solving for.

It is for this reason I will run a Customer Journey Mapping play, which will be conducted in person so that we collaborate with intention, the reason for choosing this is for the team to connect and identify what the customer feels when they are using our platform. This will help the team to deliver better solutions as they will identify with the users better.

Comments

G subramanyam

Okay!! This is a nice plan of action. Please do post the outcomes

Mark Cruth

Amazing! Can't wait to hear how it goes @Terrence Young !

alison.eyring

hi Terrence. I love that you are doing that. good luck! my engineering teams also have this issue. some of the things we do/have done to address this are: 1) record conversations with Users or user personas so they hear real people, 2) share written comments from Users with them in a slack channel, 3) review User Journeys from recording w/LogRocket. If a team lack empathy, they need great insight. this requires data in the form of audio, written inputs from real people.

Ingrid Blake

100% Alison! I've also seen success with this model- achieving the outcome of having a group of deeply technical security-focused engineers really deeply understanding the emotions of the customers they were serving and even referencing them proactively throughout the project as decisions came up!

Prabhu Palanisamy {Onward}

Often, there are multiple stakeholders/customers. Curious to learn how you map multiple customer journeys.

Ingrid Blake

What we recommend at https://www.atlassian.com/team-playbook/plays/customer-journey-mapping is to be crystal clear about just one E2E journey for just one customer persona.

You can layer these journeys on top of each other after the fact to mine for insights, or assess impact of a particular pain-point or opportunity. To keep laser focused on what the customer experiences, and not accidentally get caught up too much in backstage ops, you want to map each journey independently.

Tim Kopperud

Hi @Terrence Young, welcome to the Atlassian Community and to this group.

I think you idenfied one of the main barrier when delivering ITSM. It's the customer who defines the value. This is related to the users feeling, and the value of the service delivered is then defined by in their personal preferences and perceptions. IT often forget that the percived value diminish over time even if the service delivered has not changed. I find the Kano modell to be helpfull when I explain this to clients.