Dominik Pomp

Why this persona fits the audience

Owns customer operations analytics for a 60-person B2B platform in Berlin, administering Salesforce Service Cloud queues, Jira escalations, and monthly reporting for a small support team in a data-heavy workflow.

• Age: 44
• Location: Berlin, Germany
• Occupation: Customer Operations Analyst
• Income: €78k
• Education: Master's in information systems
• Company size: 60-person company
• Years in role: 5 years

“The most elegant solutions are those that are built on a foundation of verifiable data and operate with predictable efficiency.”

Dominik Pomp's journey into customer operations analytics began not with a passion for customer service, but with a fascination for systems and how they function. Growing up in a family where his father was an engineer and his mother a librarian, he developed an early appreciation for both logical problem-solving and the meticulous organization of information. This led him to pursue a Master's in Information Systems, where he honed his analytical skills and developed a deep understanding of database structures and workflow optimization. After a few years in a more general IT support role, he found his niche at his current B2B platform company, drawn by the opportunity to apply his systematic approach to the tangible challenges of customer operations. For the past five years, he has been the go-to person for understanding customer interaction data, managing the intricate queues of Salesforce Service Cloud and the escalation pathways in Jira. His work is characterized by a relentless pursuit of accuracy; he believes that reliable data is the bedrock of effective decision-making. He recently spearheaded a project to refine the criteria for ticket prioritization, a move that significantly reduced response times for critical issues by 15% in the last quarter. This success reinforced his belief in the power of structured workflows and measurable performance metrics. Dominik is not driven by a desire for rapid advancement or public recognition, but by the quiet satisfaction of building and maintaining efficient, reliable systems. He views his income as a means to provide stability for his family and fund his personal interests, rather than a measure of status. Time is a resource he guards closely, valuing its efficient use both at work and in his personal life, which is carefully balanced between family, cycling, and intellectual pursuits. His approach to his role is one of continuous improvement, always looking for the next process to refine or the next data point to illuminate a path forward.

Background & daily life

A day in their life

Dominik's typical weekday begins around 7:00 AM with coffee and a quick review of urgent overnight support tickets while his children prepare for school. After his cycle commute, he dives into Salesforce, triaging incoming requests and assigning them to the appropriate support agents. Mid-morning often involves a deep dive into data analysis for his monthly reports, cross-referencing ticket volumes, resolution times, and customer feedback. He might spend an hour in the afternoon troubleshooting a complex Jira escalation, collaborating with engineering via Slack. He dedicates time to refining dashboards and ensuring data accuracy. The late afternoon is usually reserved for reviewing team performance metrics and planning for the next day, before cycling home to family dinner.

Lifestyle

Dominik resides in a well-organized apartment in Berlin's Prenzlauer Berg district with his partner, who works in digital marketing, and their two school-aged children. His weekdays are structured, often starting with a brisk cycle commute through the city. Evenings are typically family-focused, involving shared meals and helping with homework. Weekends offer a chance to pursue his interests: long cycling routes on the outskirts of Berlin, intense chess matches at a local club, or diving into a new nonfiction book, often related to historical events or complex systems. He prioritizes a balanced lifestyle, focusing on health and financial prudence, viewing money as a tool for security and enabling these pursuits rather than an end in itself.

Work life

Dominik's role as a Customer Operations Analyst is central to the smooth functioning of his company's B2B platform. He's the primary administrator for Salesforce Service Cloud queues, meticulously ensuring that customer inquiries are routed correctly and addressed promptly. His days are heavily data-driven, involving the creation and refinement of monthly performance reports for the support team, which he uses to identify trends and areas for improvement. He also manages Jira escalations, acting as a crucial liaison between the support team and engineering when complex technical issues arise. The pressure is constant to maintain high levels of accuracy and efficiency within a data-heavy workflow, often requiring him to deep-dive into system logs and customer interaction histories.

Relationships

Dominik's primary social circle consists of his partner, with whom he shares household responsibilities and parenting duties. He maintains a small group of close friends from university, with whom he plays chess and discusses current events. His parents, retired engineers living in a smaller town, are a source of quiet support and occasional advice. Within the company, he has a professional, respectful relationship with the support team lead and the head of engineering, who rely on his analytical input.

How they decide

Dominik approaches decisions with a high degree of caution and thoroughness. He prefers to gather all available data, analyze potential outcomes, and consider the long-term implications before committing to a course of action. He values evidence and logic, and is not easily swayed by trends or emotional appeals. He will often create spreadsheets or flowcharts to map out options and consequences, and may seek input from trusted colleagues if the decision has significant operational impact.

How they sound

Dominik speaks with a measured, clear cadence, favoring precise language. His tone is generally calm and professional, even when discussing complex issues. He avoids slang and overly casual expressions, preferring to articulate his thoughts logically. He tends to use complete sentences and may pause to ensure he's conveying information accurately. When explaining technical concepts, he'll often use analogies to simplify them, but always with an underlying respect for the technical details.