<aside> <img src="/icons/map-pin-alternate_green.svg" alt="/icons/map-pin-alternate_green.svg" width="40px" /> When I moved to Switzerland, I started as a senior UX Researcher in a central Product & UX (PUX) team.
At first, the team existed of three researchers, four designers, and three project managers.
Over time, I was promoted to a Research lead. In close to two years, I grew the research chapter from then two to six experts (including me).
</aside>
Go directly to:
Leadership | Customer Centric Transformation | Personas (& Quantification) | Customer Journey Mapping | ResearchOps | Guilds | Coaching | Target Operating Models |
UX Research Guild setup and facilitation
Quick prototype iteration and validation
The Product & UX team was part of the central teams of TX Markets (next to the Technology team, Marketing team, and Strategy team). These central teams are following different models in supporting the portfolio companies that belong to TX Group (with priority to TX Markets companies).
A SPOTIFY MODEL
We followed the Spotify-model (see the visual on the right - source): our team existed of a Design Chapter (incl. design lead), a Research Chapter (incl. me as research lead), and a team-lead.
The main difference between a team-lead and a chapter lead is the focus on people (team-lead) versus content (chapter-lead).
CONTENT & EXPERTISE
This meant that I, as a chapter lead, was more responsible for optimising the impact and value of the research that we offered to the companies.
GROW IMPACT & VALUE OF RESEARCH
As a research lead, I focussed on improving the team setup, project processes, and in general the impact and value of research for the company - focussing mainly on how to grow our influence and improve the actionability of research results.
BUILDING STRUCTURE & TRUST
I grew the team from two to six experts. There was no real structure in place (yet). And with every new member the team dynamics changed. Therefore I focussed a lot on building stability, structure, and trust.
We followed an adjusted design thinking approach, as visualised below
