I transform complex and technical product challenges into clear user-centred solutions. My work spans the entire product lifecycle. I can lead and structure the work for my teammates and me

• Leading problem discovery and ideation workshops (Design Sprints, Design Days)
• Conducting end-to-end product design (defining goals and key metrics, UX/UI, user research, testing)
• Maintaining design systems
• Supporting product strategy through OKR development, as well as opportunity identification and in-tool maintenance
• Product ownership (User Story Mapping, Jira initiatives/epics/stories creation and description, technical feasibility reviews with scope trimming, monitoring implementation with troubleshooting, monitoring customer feedback and driving issue resolution, creating and maintaining functional documentation)
• Product leadership (tool org, defining design direction, prioritizing product bets, introducing feedback frameworks and handover processess)
• Product analytics with a sprinkle of SEO/SEM: interpreting analytical data to inform product decisions, defining product metrics for specific OKRs, negotiating analytic event tracking with devs, understanding organic and paid searches against current OKRs
• Using IDE in AI prototyping and improving everyday work efficiency

It's my ability to adapt and dive deep. I'm not just designing screens — I'm understanding entire product ecosystems and their users, facilitating team alignment, and bringing a mix of product insight and user empathy to even the most technical challenge. Just someone fun to be around 😉, vastly empathetic, and respectful. After having worn many hats, I'm adaptive to specific team setups and expectations/goals set out for me. My broad experience helps me out empathise better with my teammates and become a more integrated sparring partner

I defined key metrics for the project that are both addressing current OKRs and are feasible in a current data/dev stack. In teams without robust analytics, I've gotten creative 🧠.
I tracked success through user-submitted issues, positive feedback, and direct user interviews + Likert scale. Currently, metrics based on the transactional data will inform my redesign. My goal is always to establish quantifiable metrics with a clear baseline — whether that's through quantitative data or qualitative insights gathered directly from users. I just check how my product hypotheses turn out using available means.
Needless to say, some methods can only vaguely suggest the trend due to their natural limitation – to me, no single method has a 10/10 power of proof and has to be interpreted with the product context in mind!

I'm tool-agnostic but have already worked with:

• 🎨 Interface Design: Figma, Sketch
• 🤝 Collaboration and documentation: Miro, FigJam, Confluence
• 🔍 User Research: User Interviews, Lookback, UserTesting, Lyssna
• 🌐 Prototyping: Webflow, ProtoPie, Visual Studio Code
• 📋 Project boards: Jira, Jira Product Discovery, Asana, Trello, ClickUp
• 📊 Data repositories: Google Looker Studio, Sentry (and Visual Studio Code again :)
• 👣 User Analytics: Site Improve, Adobe Analytics, Amplitude (trained)