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

Litzy Jacobi

Litzy Jacobi

Product Operations Manager

Full-depth AI personas

Why this persona fits the audience

Manages product operations for a 28-person analytics company in London. The company already licenses Confluence and Jira, and they use them alongside Slack to document release notes, feature decisions, and support handover context.

  • Age: 35
  • Location: London, England, UK
  • Occupation: Product Operations Manager
  • Income: £102k base + bonus
  • Education: Master's degree
  • Company size: 28
  • Years in role: 5
“The real magic happens when everyone knows where to find the 'why' behind what we're building, not just the 'what'.”

Litzy Jacobi, 35, has carved out a niche as a Product Operations Manager at a burgeoning 28-person analytics company in London. Their journey into this role wasn't a straight line; after completing a Master's in Information Science, they initially gravitated towards data analysis, fascinated by how information could drive decisions. However, they quickly realized their true passion lay in optimizing the *systems* that generated and managed that information. They found that while data was crucial, its utility was severely hampered by poor documentation and fragmented communication. This led them to product operations, where they could apply their analytical rigor to the processes themselves. Litzy thrives on establishing order and clarity, viewing well-maintained documentation not as a chore, but as the bedrock of efficient product development. They champion Confluence and Jira as essential tools, but are constantly seeking ways to make their usage more effective, particularly in bridging the gap between engineering, product, and support. Their current focus is on standardizing the handover process for new features, a task that requires meticulous attention to detail and strong collaborative skills to navigate the different team needs. Litzy’s approach is deeply rooted in their values of rigor and collaboration; they believe that well-documented decisions foster trust and enable faster, more informed iteration. They see time as a valuable, finite resource, both for themselves and their colleagues, and are driven to eliminate inefficiencies. While not overtly status-seeking, Litzy derives satisfaction from building robust systems that demonstrably improve the company's output and internal communication, viewing this as a tangible measure of success.

Background & daily life

A day in their life

Litzy's typical weekday begins around 7:00 AM with a walk and coffee. By 9:00 AM, they're at their desk, reviewing overnight Slack messages and prioritizing tasks. The morning is often filled with cross-functional meetings: a quick sync with engineering on bug priorities, a deeper dive with product on upcoming feature specs, and a session with marketing to align on release messaging. Lunch is usually a quick affair, often eaten at their desk while catching up on industry news. The afternoon involves deep work: refining Jira workflows, updating Confluence documentation for a recent feature release, and responding to ad-hoc requests for information. They aim to wrap up by 6:00 PM, often spending the last hour planning for the next day.

Lifestyle

Litzy lives in a vibrant, slightly-too-small flat in Hackney with their partner and two rescue cats, Pip and Squeak. Weekends often involve exploring a new exhibition at the V&A or Tate Modern, followed by a competitive board game night with friends. They're a creature of habit during the week, starting with a brisk walk to a local coffee shop before heading to the office. While they appreciate good food and occasional travel, they're generally pragmatic with finances, prioritizing long-term security over extravagant spending.

Work life

Litzy's role is the connective tissue for product development at their 28-person analytics firm. They spend their days ensuring that the flow of information between engineering, product, and customer-facing teams is seamless. This involves a constant cycle of refining Jira workflows, updating Confluence pages for new feature releases, and ensuring Slack channels are used effectively for quick decision logging. They're currently wrestling with standardizing the handover process for new features from product to support, aiming to reduce ambiguity and speed up resolution times.

Relationships

Litzy's primary support system is their partner, a graphic designer, with whom they share household responsibilities and life decisions. They have a close-knit group of friends from university, many of whom work in tech or creative fields, providing a sounding board for professional challenges. Their manager, the Head of Product, is a key influencer at work, valuing Litzy's structured approach.

How they decide

Litzy is a research-heavy decision-maker, preferring to gather all available data, consult relevant stakeholders, and weigh pros and cons methodically before committing. They are not impulsive and will often create comparison matrices or flowcharts to visualize options. Peer consensus is important, but the final decision rests on logical analysis and alignment with established principles.

How they sound

Litzy speaks with a clear, measured cadence, avoiding overly casual slang but not being stiffly formal. They tend to use precise language, especially when discussing technical or process-related matters. They might say things like, 'To ensure clarity,' 'My primary concern is,' or 'Let's establish a consistent framework for this.' They avoid hyperbole and focus on factual reporting.

Personality traits

  • methodical
  • structured
  • inquisitive
  • patient
  • observant
  • diplomatic
  • proactive
  • analytical
  • detail-oriented

Goals

  • Establish a robust, searchable knowledge base for all product decisions
  • Streamline the release documentation process to be more efficient
  • Mentor junior team members in product operations best practices
  • Achieve a better work-life balance by automating repetitive tasks
  • Contribute to the company's strategic planning through data-driven insights

Problems & frictions

  • Information silos forming between different teams
  • Difficulty in quickly finding historical feature rationale
  • Inconsistent quality and depth of documentation across projects
  • Time spent manually collating information for reports
  • Onboarding new team members takes longer than desired due to scattered resources

Values

  • rigor
  • collaboration
  • documentation discipline
  • efficiency
  • clarity

Interests

  • product analytics
  • museums
  • board games
  • linguistics
  • urban planning

Media habits

  • The Economist
  • WIRED
  • The Daily podcast
  • BBC Radio 4
  • Substack newsletters on product management

Questions & answers

Litzy Jacobi’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 TinyLaunch: The single source of truth for your company.. the product is an AI-powered knowledge base built for teams tired of stale docs and scattered information.… 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.

    Our biggest challenge is definitely information silos, especially when it comes to historical feature rationale. We currently rely heavily on Confluence and Jira, but finding that specific 'why' behind a decision can be a real time sink for both myself and newer team members trying to get up to speed. It leads to duplicated effort and sometimes a lack of clarity on the original intent. We've tried to standardize our Confluence structure, but it's manual and doesn't always catch everything. It costs us valuable hours each week that could be spent on proactive improvements, and I worry it slows down our iteration speed.
    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.