10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Emma Lakomy

Emma Lakomy

Technical product manager

Full-depth AI personas

Why this persona fits the audience

Works in Berlin at a 15-person logistics SaaS, where she coordinates a 3-person internal tools group that builds onboarding forms, admin screens, and customer data syncs. Their stack is a mix of PostgreSQL, Zapier, and a low-code competitor used on a paid team plan.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Technical product manager
  • Income: €78k-€95k per year
  • Education: MSc Information Systems
  • Company size: 15-person company
  • Years in role: 3
“The most elegant solutions are often the ones that make the complex feel simple, both for the user and for the team building it.”

Emma Lakomy's journey into technical product management began with a fascination for how systems could be optimized for human interaction. Growing up in a family that valued order and diligence, she naturally gravitated towards subjects that involved logic and structure. Her MSc in Information Systems provided a strong theoretical foundation, but it was her early roles in software support and QA that honed her practical understanding of user pain points and the importance of robust internal processes. She found her niche in Berlin's vibrant startup scene, drawn to the dynamic environment and the opportunity to build impactful tools. For the past three years, she's been instrumental at a growing logistics SaaS company, leading a small but vital team focused on internal tools. This involves a constant balancing act: ensuring the onboarding forms are intuitive for new clients, that administrative screens provide clear oversight for the operations team, and that customer data syncs are reliable. Her current tech stack, a pragmatic mix of PostgreSQL for core data, Zapier for automation, and a specific low-code competitor for rapid prototyping of forms and interfaces, presents both opportunities and constraints. Emma is deeply invested in the usability and efficiency of these tools, seeing them as critical enablers for the company's growth. She views her role not just as managing a product, but as orchestrating the flow of information and improving the daily working lives of her colleagues and the experience of their customers. She is driven by a desire for order and accountability, always seeking to refine processes and ensure her team's work is well-defined and impactful, reflecting her inherent conscientiousness and a quiet ambition to leave things better than she found them.

Background & daily life

A day in their life

Emma's typical weekday begins around 7:00 AM with a cup of coffee and a quick scan of industry news. She cycles to the office by 8:30 AM, using the commute to mentally prepare for the day. Her morning is usually dedicated to team stand-ups, reviewing Jira tickets, and deep work on feature planning for the onboarding forms. After a quick lunch, often a packed meal, she spends the afternoon in meetings with other department heads to gather requirements for admin screen enhancements or troubleshooting data sync issues. She aims to wrap up by 6:00 PM, cycling home to prepare dinner and unwind, perhaps with a chapter of her current book or a brief call with her partner.

Lifestyle

Emma leads a structured yet balanced life in Berlin. Her weekdays are focused on work, but she carves out time for her passions. Evenings often involve cooking a healthy meal, reading, or a quiet evening with her partner. Weekends are for longer bike rides through the Brandenburg countryside or exploring Berlin's cultural offerings. She's financially responsible, saving diligently for future travel and home improvements, but enjoys occasional splurges on good quality coffee or books. She values her close-knit circle of friends and makes an effort to maintain those relationships.

Work life

Emma's role is deeply embedded in the operational efficiency of her company. She manages a small but crucial team responsible for internal tooling. This involves constant communication with various departments – sales, customer success, and engineering – to understand their needs for better data management and customer interaction. Her days are a blend of planning sprints, reviewing user feedback, troubleshooting integration issues, and collaborating with her team on developing and refining their internal tools, which currently rely on a mix of PostgreSQL, Zapier, and a low-code platform.

Relationships

Emma is in a stable, long-term relationship with her partner, who provides a supportive and creative counterbalance to her structured professional life. She maintains a small but strong group of friends from university and previous jobs, with whom she shares intellectual discussions and weekend activities. Her parents, who live in a smaller town in Bavaria, are a source of quiet encouragement, though they don't fully grasp the nuances of her tech career.

How they decide

Emma approaches decisions methodically. She gathers information, consults relevant stakeholders, and weighs pros and cons carefully. She prefers solutions that offer long-term stability and efficiency over quick fixes. While she trusts her team's input, the final decision rests on her analysis of data and potential impact on usability and team alignment.

How they sound

Speaks clearly and precisely, with a measured pace. Her tone is generally calm and professional, but can become more animated when discussing technical challenges or process improvements. She avoids overly casual slang or jargon, preferring clear, descriptive language. She tends to use phrases like 'from a process perspective,' 'the key challenge here is,' and 'we need to ensure alignment on.'

Personality traits

  • methodical
  • detail-oriented
  • proactive
  • communicative
  • analytical
  • patient
  • reliable
  • observant

Goals

  • To streamline internal processes and reduce manual data entry across the company
  • To mentor and develop her internal tools team
  • To achieve a better work-life balance, allowing for more dedicated time for personal projects
  • To contribute to the strategic growth of the company by improving data accessibility and usability
  • To complete a personal project involving a custom-built cycling route planner

Problems & frictions

  • The current low-code tool has limitations that require workarounds, slowing down development
  • Balancing the urgent requests from other departments with the planned roadmap for internal tools
  • Ensuring data consistency and integrity across disparate systems
  • Limited resources and time for her small team to tackle all desired improvements
  • The constant need to adapt to evolving logistics software requirements

Values

  • organization
  • accountability
  • usability
  • team alignment
  • efficiency

Interests

  • process design
  • city cycling
  • product ops
  • German literature
  • urban gardening

Media habits

  • Reads the digital edition of Die Zeit daily
  • Listens to podcasts on tech trends and historical documentaries during commutes
  • Follows industry blogs on product management and SaaS development
  • Occasional browsing of design and architecture magazines

Questions & answers

Emma Lakomy’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on startupbase: Ship your product, not your backend. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem for us right now, and it's a significant drain on resources, is the constant need to build workarounds for our current low-code tool. We're using it for internal forms, like onboarding and admin screens, and while it's faster than building from scratch, hitting its limitations means my team of three spends too much time on these workarounds. This diverts them from more strategic improvements and leads to data inconsistencies because we're patching things together. It probably costs us a good half-day per week in development time across the team, plus the mental overhead for my engineers. We've tried optimizing the existing workflows, but the platform itself is the bottleneck.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.