Episode #68: Making UX Stories Matter with Emilie Mazurek

Emilie Mazurek once expected to become a doctor. She studied biochemistry, applied to medical school three times, and reached a revealing moment during the third attempt: acceptance caused more anxiety than rejection. That reaction prompted her to step back and examine what she actually wanted from a career.

Career counseling helped Emilie identify achievement and work-life balance as important needs. Web design appeared among the suggested paths, and further research led her to UX. The field connected analytical research, creative problem solving, and work with people. Her decade in hospitality had already trained her to solve immediate human problems, from dietary restrictions and seating requests to strict departure times. UX offered a way to apply that instinct to work with a longer-lasting impact.

What you'll learn

• How career counseling helped Emilie separate achievement from the medical path

• Why hospitality and scientific research became relevant UX experience

• How storytelling gives stakeholders context for design decisions

• Why large critiques need clear goals instead of informal voting

• How designers can use analytics, interviews, collaboration, and success metrics together

Build a design career from transferable skills

When Emilie entered a UX bootcamp, classmates with graphic design backgrounds could produce polished visual work quickly. Comparing herself with them created doubt. Over time, she realized that UX benefits from varied backgrounds and that her own experience was not a detour. Scientific training made her analytical and comfortable with experiments. Hospitality developed communication, collaboration, and responsive problem solving.

Those skills became a hiring advantage. Emilie says her first employer chose her over a candidate with five years of experience because the role needed someone comfortable running experiments. The lesson for aspiring designers is practical: recruiters and hiring managers may not infer how an earlier career relates to UX. Candidates must make the connection explicit and explain how prior work equips them to understand users, evaluate evidence, or work with teams.

She also revised her view of the craft after entering the profession. Figma efficiency and other technical skills matter, but soft skills carry more of the daily work than she initially expected. A designer has to communicate, facilitate collaboration, ask useful questions, and solve problems with other people. Tool fluency cannot substitute for those abilities.

Emilie's design philosophy begins with research. She asks why the team is solving a problem, why one direction appears stronger than another, and what evidence supports the choice. User conversations provide explanation. Analytics may not reveal why behavior occurs, but they can identify patterns and tell the team where to investigate. The designer then works with colleagues to improve the initial idea. Emilie does not expect her first answer to be the best one. The solution becomes stronger through discussion and combined input.

Give stakeholders a reason, a goal, and evidence

Storytelling is central to Emilie's approach. When presenting work, she establishes the problem, the intended outcome, and the impact of the proposed design. That structure helps stakeholders understand why the work matters instead of reacting only to visual details. Regular check-ins also let people participate early enough to shape the direction rather than encountering it as a finished decision.

Metrics belong at the beginning, not only in a retrospective. Emilie recommends defining success standards before the design is complete so the team can later show whether the work produced the intended effect. This evidence makes a stronger case than enthusiasm alone.

She learned the importance of framing during a critique process that required three design variations and three rounds of review: first with an internal team, then with a product group, and finally with external stakeholders such as sales or marketing. Some meetings included 15 to 20 people. With three options on screen, participants could easily treat the discussion as a vote for whichever version they personally liked.

Clear goals protect the critique from that trap. The designer should explain which option best supports the user and the specific outcome, and why. Participants can still challenge the reasoning, but the conversation remains tied to the problem rather than becoming a tally of aesthetic preferences. This does not mean the designer works alone. It means collaboration has a decision frame.

Emilie expects UX to become common across more industries because user-centered problem solving also benefits the business. Companies waste less effort when they identify the right problem before building. She hopes UX will become a core capability rather than a specialty that organizations consider optional.

Her own professional visibility also grew through LinkedIn. A bootcamp career advisor suggested posting there, advice that initially frustrated her. Writing once or twice a week became a way to practice storytelling, meet people, exchange ideas, and participate in the design community. What began as a job-search tactic turned into part of how she learns and contributes.

Listen to the conversation

Hear Emilie Mazurek discuss her move from biochemistry to UX, research, storytelling, stakeholder critiques, career confidence, and community participation.

Listen to the full episode.