Find the button or swipe left to move to the next step.
Tap each skill to help me earn my credentials!
Tap the screens to help me gain valuable experience!
Open my first projects in UX Research & Design!
Tap my phone to get my contacts.
Send a paper plane to share my portfolio.
Grab the paper from my bag to download my CV.
Insurance agencies in Switzerland struggle with too few applications and high turnover in their sales teams. As part of developing an internal recruiting platform, I explored the end-to-end recruiting and onboarding experience to understand what high-performing agencies do differently.
My role involved planning and conducting interviews, mapping the employee journey, synthesizing patterns, and translating them into How Might We questions and early concept directions for improving recruitment and onboarding experiences.
Disclaimer:
This work forms part of an internal project for the company I am currently employed at, supporting the development of a digital recruiting platform. To maintain confidentiality and respect company ownership, specific findings and strategic insights are not disclosed here. The focus lies on my UX research process and individual contribution.
I combined interviews with a structured employee-journey to understand motivations, friction, and retention triggers across the first two years.
To understand the business and organizational context, I conducted stakeholder interviews with recruitment leads, regional managers, and HR professionals. These conversations helped frame the problem from multiple perspectives β balancing agency needs with candidate experience.
In parallel, I spoke with career changers currently in sales training and early career stages. The goal was to map what motivates them to join β and what makes them stay.
I mapped the journey from first contact to year two to spot expectation gaps and drop-off risks.
βThe best kind of design isn't necessarily an object, a space or a structure: it's a process - dynamic and adaptable.β - Don Norman
We set out to design a wedding vendor platform. But we discovered that what couples actually need is not better bookings, but better planning and collaboration.
My role focused on uncovering these insights through interviews, journey mapping, and user story definition. This research reframed the concept into a shared planning tool that reduces stress and helps couples stay aligned.
Disclaimer:
We developed and tested an interactive MVP with real users. Due to confidentiality, detailed designs and test results cannot be shared at this stage. Insights presented here are anonymized and generalized.
I followed a classic UX process, but let research guide every pivot and priority.
I examined the existing wedding tech landscape, identifying gaps in existing tools:
Through in-depth interviews with recently married and engaged individuals, I explored their planning journeys.
To manage large volumes of qualitative data, I created a custom GPT that allowed our team to query interview transcripts and reference synthesis notes in seconds, saving time and improving consistency during concept development.
I clustered insights to find repeating pain points.
Surprisingly, the vendor search was rarely the bottleneck:
βI never really had a clear picture of what was happening when or everything that had to happen.β β F.
At this point, we decided to shift our concept from a vendor directory to a smart, collaborative planning companion. Instead of helping couples find services, we would help them plan together, with less stress, more structure, and a clear overview.
βIt felt like project management. But when it worked, it gave us peace.β β O.
I mapped emotional highs and lows from engagement to wedding day. This helped me pinpoint key stress phases and uncover opportunity areas where a digital tool could reduce anxiety.
I wrote prioritized user stories to frame key features. These stories later shaped the usability test scenarios and informed our design priorities.
βAs a bride, I want a shared checklist with my partner, so I can feel supported and stay in sync.β
I analyzed user pains and gains to define the most relevant product values β from clarity and overview to task sharing and emotional reassurance. This became the foundation for the MVP requirements.
After translating research insights into product requirements, we built a clickable MVP and conducted usability testing with our target group. While detailed outcomes are confidential, the tests confirmed core assumptions and guided the next iteration.
This project stands out to me for how deeply research reshaped our direction. The process highlighted how early discovery can prevent teams from building the wrong product efficiently.
Kloop is a concept developed as part of the Google UX Design Certificate β. The brief was to design an app for buying and selling secondhand childrenβs clothes. But my research reframed the challenge into something broader: how to make passing on kidsβ things effortless, trustworthy, and emotionally rewarding for parents.
Throughout the project, I applied the Design Thinking process, from empathizing with real users through interviews and diary studies, to defining key insights and ideating possible solutions.
Before diving into design, I explored how parents in Switzerland already buy, sell, or recycle kidsβ items. I compared popular resale platforms, donation options, and recycling programs.
I conducted three interviews with parents living in Switzerland to understand why βkeeping things in the loopβ so often fails in practice. I asked parents questions such as:
To better understand the pain points, I turned the lens on myself. As a mother using the same platforms, I started documenting my own experiences in a diary for one month every time I bought or sold a secondhand childrenβs item.
To make sense of the interviews and diary notes, I clustered all the observations into themes using affinity mapping.
βIn Switzerland, reuse is neither practical nor social.β β J.
I defined user groups and problem statements based on behavior and motivations observed during research.
I mapped four user journeys with friction points and design opportunities based on my research.
To move from research to ideation, I translated the key pain points into βHow Might Weβ questions.