API customer experience

PEXA’s world-first digital settlements platform transformed property exchange in Australia. Working in a small team, we created user service blue print and archetypes.

We researched the API customer experience, developing a service blueprint to identify pain points. The impact being a 35% reduction in customer support requests the API.

Research, Transpire for PEXA


Role & Responsibilities

I was the lead UX Researcher, the project was conducted over a month with a small team including myself and another junior UX desinger. I took responsibility for interview and research guides for API integrators, I got support for synthesizing insights, and creating the customer journey map.

Research Plan

We developed a discussion guide of open ended questions that would help us to better understand the experience from the customer’s perspective and gain insights into their actual process. After that we worked with PEXA to find twelve participants to interview with. Another addition to the research plan is we developed our consent form to ensure our participants are aware of the information we’re looking to gather.

Planning & Discussion Guide

  • A research plan and an interview guide were developed to explore the real experiences of API integration teams.

  • Twelve participants were recruited from law firms, banks, and property developers to share their perspectives.

Discussion Guide

Qualitative Interviews & Synthesis

  • Remote interviews were conducted and documented on Miro, using the fish bone diagram method

  • Findings were synthesised into categories representing key themes, emotions, tasks, tools, and stakeholder roles.

Customer Journey Mapping

  • A detailed journey map was created outlining stages of the API integration process.

  • Each stage included:

    • Tasks and subtasks

    • Emotions experienced

    • Communication channels and tools used

    • Stakeholder archetypes

    • Opportunities for improvement in the PEXA experience

Draft blueprint

Service blueprint

The journey map is broken down into various aspects of the experience. The stages show us the main sections of the journey and these are then further divided into tasks and subtasks. Each task column will reflect the overall emotion that the stakeholder was experiencing as well as a description of the feeling they had around that particular task.  The channel tells us which methods of communication or tools they were using, the archetype for the stakeholders involved is listed and any opportunities for PEXA within that aspect of the experience is also noted.

Major pain points;

  • Documentation

    • Customers were confused by the developer documentation hub, and audit was reccomended

  • Build and Test

    • Customers were frustrated by the lack of support in building and testing of the API, we found again recommending better documentation and the ability to book a support call

Archetypes

We found that archetypes made more sense than personas, that were originally agreed upon. We started to look at the behaviours of each group of participants and from there we were able to ideate a view of archetypes.

Archetypes

Behavioral graphs

We also developed some behavioral graphs to help PEXA understand the the needs and actions of there customers more.

Impact

After the recommendations were taken on-baord and actioned, we heard back from our client PEXA that they saw a 35% reduction in the amount of customer support queries in relation to the API.

Final thoughts

We developed a really solid bunch of artifacts that helped our customer to better understand their own customers and identify some major pain points. I worked by myself on this project and I found it was quite hard to keep up the momentum so I found myself relying on my colleagues for little pep talks.