Why this persona fits the audience
She shares a two-person content design function at a scaleup and tracks UI text, fallback copy, and review cycles in Figma comments, Notion, and a spreadsheet. Most work is embedded in product tickets, with copy decisions recorded manually for later reference.
- Age: 29
- Location: Amsterdam, Netherlands
- Occupation: UX content designer
- Income: €72k
- Education: MA interaction design
- Company size: Scaleup (approx. 150 employees)
- Years in role: 4
“It’s the small details, the exact word choice, that truly make a product feel intuitive and trustworthy. If it’s slightly off, the whole experience falters.”
Isabelle de Wit's journey into UX content design began during her MA in Interaction Design, where she became fascinated by the intersection of language, usability, and user psychology. Growing up in a household that valued order and precision, she naturally gravitated towards roles where meticulous attention to detail was paramount. After graduating, she spent two years at a small digital agency, honing her skills across various client projects, before joining her current scaleup company in Amsterdam three years ago. At the scaleup, she shares a two-person content design function, a setup that often leaves her feeling stretched thin across multiple product teams. Her days are a constant juggle of refining microcopy, crafting error messages, and ensuring tonal consistency, all while embedded within product development cycles. She meticulously tracks UI text, fallback copy, and review cycles using a combination of Figma comments, Notion databases, and a sprawling spreadsheet that acts as her personal log. Most of her work is documented directly within product tickets, with critical copy decisions painstakingly recorded manually for future reference, a process she finds essential but time-consuming. Isabelle is driven by a deep-seated value for consistency and usability; she believes well-crafted content is not just about aesthetics but is fundamental to a product’s success. Her income allows for a comfortable life, but she remains mindful of her spending, prioritizing experiences and long-term financial security over material possessions. She views her role as a crucial, albeit often understated, component of the product development lifecycle, constantly striving for clearer communication and a more seamless user experience.
Background & daily life
A day in their life
Isabelle's typical weekday begins around 7:30 AM with coffee and a quick scan of industry news. She cycles to the office by 9:00 AM, immediately diving into Slack and her prioritized Jira board. The morning is often spent refining UI copy for a new feature, meticulously documenting decisions in Figma comments and a shared Notion page. Lunch is usually a packed meal eaten at her desk while catching up on emails. The afternoon involves a product review meeting, followed by more content refinement, often requiring significant back-and-forth with developers. She tries to wrap up by 6:00 PM, cycling home to cook dinner with her partner. Evenings might include a short online course or reading, but rarely extend beyond 10:30 PM.
Lifestyle
Isabelle lives in a comfortable, but not large, apartment in Amsterdam's Oud-West district with her partner, a software engineer. Their routine is generally well-structured, with shared cooking duties and regular evenings spent reading or watching documentaries. She cycles everywhere, valuing the efficiency and environmental aspect. While she enjoys socialising with a close-knit group of friends, she prefers quieter evenings over loud parties. Financially, she’s responsible, saving diligently for future travel and potential property ownership, but enjoys investing in good quality, long-lasting possessions rather than fleeting trends.
Work life
Isabelle finds satisfaction in meticulously crafting clear and consistent user experiences, though the constant context-switching between multiple product streams at her scaleup can be demanding. She works closely with a single product manager and a handful of engineers per project, often feeling like the sole advocate for content quality. Her days are heavily structured around Jira tickets, Slack messages, and deep dives into Figma. The lack of a centralized system for tracking copy decisions across various features is a persistent point of friction, often leading to repetitive questions and manual cross-referencing.
Relationships
Isabelle maintains a strong relationship with her partner, who understands the demands of tech work. Her core social circle consists of a few university friends who work in related creative fields. Her parents, living in a smaller town in the Netherlands, are supportive but don't fully grasp the nuances of her profession. Her immediate manager, the Head of Product, is her primary professional influencer regarding process and priorities.
How they decide
Isabelle is a research-heavy and cautious decision-maker. She meticulously gathers information, weighs pros and cons, and often seeks consensus or validation from peers or trusted colleagues before committing to a course of action. She values evidence and logical reasoning over gut feelings.
How they sound
Her tone is measured and articulate, with a slight, almost imperceptible Dutch accent. She speaks with precision, favoring clear, descriptive language over slang or overly casual expressions. When discussing work, she tends to be precise and factual, avoiding hyperbole. She avoids making definitive pronouncements unless she has strong data to back them up. Her speech is generally unhurried.
Personality traits
- meticulous
- detail-oriented
- analytical
- methodical
- patient
- reserved
- organized
- pragmatic
Goals
- Develop a comprehensive, company-wide content style guide.
- Become a senior UX content designer, potentially leading a small team.
- Contribute to open-source design system projects.
- Achieve a better work-life balance by streamlining content workflows.
- Travel to Japan for an extended cultural immersion.
Problems & frictions
- Difficulty ensuring consistency of UI text across different product teams.
- Time spent manually tracking copy variations and review statuses.
- Lack of a single source of truth for all UI copy and its history.
- Managing feedback and approvals from multiple stakeholders with varying design literacy.
- Feeling siloed in her role, with limited visibility into broader content strategy discussions.
Values
- consistency
- usability
- careful iteration
- clarity
- efficiency
Interests
- content design
- Figma
- product UX
- design systems
- typography
- cognitive psychology
Media habits
- Reads industry blogs (NN/g, UX Collective)
- Listens to podcasts on design and tech during commute
- Follows design leaders on LinkedIn and Twitter
- Subscribes to newsletters on UX and content strategy
- Occasionally watches YouTube tutorials for specific tools