01
The client thought it was a webpage problem
The ask was framed as interface fixes and a help centre.
↓How I overcame it
Reframed it with their own data
I led with ticket and survey evidence and chose which findings to elevate for executives. They aligned on the real problem: knowledge and community, not a webpage.
02
Support felt like a grievance
Customers came in frustrated, and support staff felt the strain from the other side.
↓How I overcame it
Facilitated for partnership
I deliberately brought customers and support staff into the conversation. The tone shifted from complaint to partnership, and both sides shared ideas to reduce CTP tickets, a rare moment of alignment.
03
A highly specialised domain
Neurorobotics, custom task programming and unclear terminology made problems hard to describe, even for experts.
↓How I overcame it
Immersed myself in the lab
I watched researchers use the robots in their own environment, then turned the terminology gap into a recommendation: a shared plain-language glossary.
04
No baseline for “normal”
The support team had no way to plan for or measure demand.
↓How I overcame it
Built one from 2.5 years of tickets
4.6 tickets per new customer became the benchmark the team now plans with, and the 43% projection made the cost of inaction concrete.