Why this persona fits the audience
She works in product operations at a Dutch ecommerce startup, where she normalizes CSV files, rewrites support macros, compresses screenshots, and checks small code snippets passed between ops and engineering. Her current process mixes spreadsheets, internal scripts, and free online tools.
- Age: 36
- Location: Utrecht, Netherlands
- Occupation: Product operations analyst
- Income: €68,000
- Education: Master's degree
- Company size: Startup, ~75 employees
- Years in role: 4 years
“The real magic happens not in the final output, but in the meticulous, invisible work of making the data coherent.”
Liselotte van Doorn's journey into product operations began not with a grand design, but with an inherent knack for untangling complexity. Growing up in a family that valued practicality and hard work, she pursued a Master's degree in Information Science, where her fascination with how systems function and interact took root. She found herself drawn to the messy, vital intersection of data and user experience. After a brief stint in a more traditional data entry role, she landed at her current Dutch ecommerce startup four years ago, initially in a support-adjacent capacity. Her aptitude for identifying inefficiencies and her meticulous approach quickly propelled her into the product operations analyst role. She thrives on the challenge of optimizing workflows, viewing each CSV file as a puzzle and each support macro as an opportunity for improvement. Recently, she pushed back against a proposal to adopt a costly, all-in-one platform, advocating instead for a phased approach to integrate more robust, specialized free tools and internal scripts, a decision that reflects her pragmatic, cost-conscious mindset. She sees her current tools – a mix of Google Sheets, Python scripts she’s gradually built, and various online utilities for tasks like image compression and text formatting – as functional but increasingly strained. Liselotte views time as a valuable, finite resource; efficiency isn't just about speed, but about minimizing wasted effort and preventing future rework. Status is less about title and more about the demonstrable impact of well-functioning systems, a testament to her deep-seated belief in accuracy and systematic improvement.
Background & daily life
A day in their life
Her typical weekday begins around 7:00 AM with a quick breakfast and scanning headlines. By 8:30 AM, she's logged into her company's systems, usually starting with checking overnight data feeds and any urgent operational alerts. The morning is often consumed by data normalization tasks, running scripts to process incoming CSV files from suppliers or customer interactions, and then meticulously verifying the output. She might spend an hour responding to support tickets that require operational input or reviewing code changes submitted by engineering. Lunch is a brief, healthy meal at her desk while perusing industry news. The afternoon often involves more complex data analysis, collaborating with a colleague on refining a support workflow, or documenting a newly implemented process. She aims to wrap up by 5:30 PM, often spending the last 30 minutes planning tasks for the next day.
Lifestyle
Liselotte enjoys a balanced life, prioritizing her work during the week but cherishing her downtime. She lives alone in a comfortable but modestly furnished apartment in Utrecht, which she keeps impeccably tidy. Her evenings often involve preparing healthy meals, catching up on industry news, or working on a personal coding project. Weekends are for recharging – cycling through the Dutch countryside, visiting museums in nearby cities, or meeting friends for coffee and 'borrel'. She’s mindful of her spending, focusing on experiences and practical investments rather than fleeting trends, and maintains a small but dedicated savings account for future security.
Work life
Her role as a Product Operations Analyst is a constant juggling act of maintaining operational smoothness for a rapidly growing ecommerce platform. A typical day involves sifting through mountains of CSV data from various sources, cleaning and normalizing it for import into internal systems. She's also responsible for streamlining customer support by refining macro responses and ensuring all visual assets, like screenshots used in documentation, are appropriately compressed. A significant portion of her week is dedicated to bridging the gap between the operations team and engineering, reviewing small code snippets for clarity and adherence to operational standards before they are implemented. This requires a keen eye for detail and a deep understanding of both the business logic and the technical underpinnings.
Relationships
Liselotte maintains strong professional relationships with her immediate team and the engineering leads she collaborates with, valuing direct communication and clear documentation. Her close friends, primarily met during her university years, share similar professional backgrounds and often discuss work challenges over drinks. She has a good, though slightly distant, relationship with her parents and siblings, who live in another province and don't fully grasp the nuances of her tech role.
How they decide
Liselotte is a highly research-oriented and cautious decision-maker, especially when it comes to adopting new tools or processes for her work. She meticulously evaluates options, weighs pros and cons, and often creates comparative matrices. She'll seek out peer reviews, technical documentation, and even free trial versions if available, ensuring any chosen solution aligns precisely with her need for accuracy and efficiency before committing any resources.
How they sound
Speaks clearly and precisely, with a slight Dutch accent. Her tone is generally calm and measured, avoiding overly casual slang or jargon unless discussing technical specifics with peers. She uses complete sentences and prefers direct, factual communication. When excited about a potential improvement, her pace might quicken slightly, but she remains articulate and professional. She tends to avoid hyperbole and emotional language in professional contexts.
Personality traits
- Meticulous
- Analytical
- Methodical
- Patient
- Detail-oriented
- Pragmatic
- Independent
- Reliable
- Resourceful
Goals
- Develop a more robust, scalable data pipeline for operational reporting
- Automate at least 70% of her current repetitive data processing tasks
- Gain deeper proficiency in Python for scripting and data analysis
- Contribute to a more seamless user experience for both internal teams and end-customers
- Achieve a senior analyst position or move into a dedicated data engineering role within the next five years
Problems & frictions
- The current patchwork of tools and scripts is becoming increasingly fragile and time-consuming to maintain
- Manual data normalization is prone to human error, leading to downstream issues in reporting and system integrity
- Lack of integrated solutions means context switching between spreadsheets, scripts, and online tools significantly slows down her workflow
- Difficulty in tracking changes and versions across different data sources and operational procedures
- Limited budget for new software tools within the startup environment
- Balancing urgent operational fixes with long-term process improvement projects
Values
- systems thinking
- accuracy
- process improvement
- efficiency
- data integrity
Interests
- ecommerce operations
- CSV cleanup
- support workflows
- light scripting
- automating repetitive tasks
- user experience optimization
Media habits
- Reads industry blogs (e.g., Product Hunt, TechCrunch Europe, local startup news)
- Listens to podcasts during commute (e.g., 'This Week in Startups', 'Acquired')
- Active on LinkedIn for professional networking and industry news
- Occasional Reddit browsing for tech tips and niche communities
- Follows specific open-source projects on GitHub