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

Dewey Ernser

Dewey Ernser

Product operations manager at a small SaaS team

Full-depth AI personas

Why this persona fits the audience

Coordinates a 6-person product team that shares meeting transcripts, customer feedback, and release notes across Google Docs, Slack, and spreadsheets; he personally tests ChatGPT, Notion AI, and Perplexity for summarizing docs and tracking decisions.

  • Age: 41
  • Location: Manchester, UK
  • Occupation: Product operations manager
  • Income: £78k
  • Education: MSc
  • Company size: Small SaaS startup (35 employees)
  • Years in role: 4
“If you can't measure it, document it, and trace it back to a specific user pain point, it doesn't exist in our product roadmap.”

Dewey Ernser is a 41-year-old Product Operations Manager based in Manchester, UK, earning a salary of £78,000. Holding an MSc in Information Systems from the University of Manchester, Dewey has spent the last fifteen years navigating the transition from traditional waterfall methodologies to agile SaaS environments. Currently, he serves as the operational backbone for a thirty-five-person B2B software startup, where he coordinates a lean six-person product team. His role is less about coding or designing features and more about creating the infrastructure that allows creativity to happen efficiently. He personally manages the flow of information between engineering, sales, and customer success, acting as a filter for noise and a translator for complexity. Dewey is a known enthusiast for the intersection of human workflow and artificial intelligence. Unlike many peers who adopt AI tools blindly, he treats them as experimental variables. He actively tests ChatGPT, Notion AI, and Perplexity daily, not for novelty, but to solve specific friction points: summarizing hours of unstructured customer feedback, extracting decision logs from chaotic Slack threads, and cross-referencing release notes with bug reports. Despite his enthusiasm for technology, he remains deeply skeptical of 'magic buttons' that promise to replace human judgment. He has recently rejected several expensive enterprise platforms in favor of custom-built spreadsheet macros because they offered better transparency and control. His professional philosophy is rooted in the belief that clarity is the most valuable currency in a startup. He believes that a team of brilliant engineers working in isolation is less effective than a slightly less brilliant team operating with perfect alignment. This drives his rigorous approach to documentation; he insists that every decision made in a meeting must be captured, tagged, and searchable. However, this pursuit of order sometimes clashes with the rapid pace of a small team, leading to occasional friction when developers feel bogged down by administrative overhead. Outside of work, Dewey balances his analytical mind with physical exertion, running regularly to maintain mental sharpness. He is married with two school-aged children, and his life outside the office is characterized by a desire for stability and predictable routines, mirroring his professional need for structured systems.

Background & daily life

A day in their life

Dewey starts his day with a solitary run through Sale Water Park, listening to a podcast on B2B strategy. By 8:00 AM, he is at his desk, reviewing the overnight logs from their US customers and scanning the latest GitHub activity. His morning is dominated by a 45-minute stand-up where he translates vague engineering updates into clear action items for the rest of the week. Mid-morning is reserved for deep work: building a complex dashboard in Looker to visualize churn drivers, a task requiring intense concentration. Lunch is often eaten at his desk while skimming industry reports or testing a new Notion AI prompt. Afternoons are fragmented by ad-hoc requests from Sales and Support, requiring him to jump between Slack and email to clarify requirements. He ends his day by updating the central project tracker, ensuring every open ticket has a clear owner and deadline before logging off to spend quality time with his family.

Lifestyle

Dewey lives in a semi-detached Victorian terrace in Didsbury, Manchester, sharing the home with his wife Sarah and their two sons. He is an early riser, typically up by 5:30 AM to run 5km before the family wakes, using this time to clear his head and check global market trends. His weekends are split between active duty as a father—coaching his son's football team and managing school logistics—and quiet evenings spent tinkering with home automation or testing new productivity software. Financially, he is prudent; they have a solid mortgage but avoid luxury splurges, preferring to invest in high-quality gear that lasts. Socially, he maintains a tight-knit circle of colleagues and old university friends, valuing depth over breadth in relationships.

Work life

As the operational glue for a six-person product team, Dewey spends his days bridging the gap between engineering, design, and sales. His reality involves constant context-switching: synthesizing hours of customer interview recordings into actionable insights, maintaining the 'single source of truth' in shared Google Docs, and ensuring release notes are accurate across platforms. He relies heavily on a chaotic mix of Slack channels, Trello boards, and complex Excel trackers. The pressure comes from the need to prevent information silos; if a feature request gets lost in a thread, it costs the company money. Recently, he has been aggressively prototyping how to use LLMs to automate the manual transcription and tagging of customer calls, though he remains wary of hallucinations in critical data.

Relationships

Dewey is deeply embedded in the Manchester tech scene, frequently attending meetups at the CoWorks space. His primary influence comes from a peer group of other Product Ops managers he chats with weekly, where they swap war stories about scaling issues. At home, his relationship with his wife is a partnership of equals; she manages the household's emotional and logistical rhythm, allowing him to focus on his career goals. He is close to his parents in Leeds, visiting monthly, and values their grounded advice on long-term stability over short-term gains.

How they decide

Cautious and evidence-driven. Dewey rarely commits to a new tool or process without a defined pilot period. He prefers to test solutions against specific, measurable metrics (time saved, error rate reduction) rather than relying on marketing claims or peer recommendations alone. He is comfortable spending weeks researching a solution if the potential ROI justifies the implementation time, but once a standard is set, he is slow to deviate unless proven necessary.

How they sound

Dewey speaks with a calm, measured Mancunian accent, avoiding slang but using precise, industry-specific terminology. His cadence is deliberate; he pauses to structure his thoughts before speaking, often prefacing statements with 'From an operational perspective...' or 'The data suggests...'. He avoids hyperbole, emotional outbursts, or absolute terms like 'always' or 'never'. In meetings, he is the one who gently steers conversations back to the agenda, asking clarifying questions like 'Can we define success metrics for that?' rather than offering immediate solutions. He values brevity but will elaborate if the lack of clarity threatens the project's integrity.

Personality traits

  • methodical
  • process-oriented
  • calm under pressure
  • pragmatic
  • detail-obsessed
  • collaborative
  • tech-curious but skeptical
  • structured
  • efficient
  • grounded

Goals

  • Reduce the time spent on administrative documentation by 40% within the next fiscal year
  • Establish a standardized, AI-augmented knowledge base that requires zero manual entry from engineers
  • Secure a senior leadership role within a larger enterprise organization while retaining hands-on product influence
  • Maintain a consistent running pace improvement without compromising work-life balance
  • Build a personal library of automated workflows that can be reused across different teams
  • Achieve financial independence to support children's university education without debt

Problems & frictions

  • Fragmented data sources make it impossible to get a holistic view of product health without manual aggregation
  • Meeting fatigue where key decisions are made verbally and never formally documented for future reference
  • The cognitive load of constantly switching between five different tools (Slack, Docs, Sheets, Jira, CRM) causes focus fragmentation
  • Difficulty distinguishing between AI-generated noise and genuine user insights in customer feedback summaries
  • Team members resisting standardized processes due to perceived bureaucracy
  • Lack of long-term memory retention in current chat tools leads to repeated questions being asked by the same stakeholders

Values

  • clarity
  • reliability
  • cross-functional alignment
  • operational efficiency
  • evidence-based decision making

Interests

  • product analytics
  • AI tools
  • spreadsheets
  • B2B software
  • data visualization
  • running

Media habits

  • Morning tech newsletters (TLDR, Stratechery)
  • LinkedIn technical threads
  • YouTube deep-dives on workflow automation
  • Local running club podcasts
  • Slack communities for Product Ops
  • Hacker News

Questions & answers

Dewey Ernser’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying MetriQ (https://www.metriqai.space) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My main hesitation with trying MetriQ this month is understanding how it integrates with my current workflow. I already use a mix of tools like ChatGPT, Notion AI, and Perplexity daily to summarize documents and track decisions. I need to see concrete examples of how MetriQ would actually *improve* this process, not just add another layer. For instance, how does it handle extracting decisions from Slack threads better than my current prompts? I'm also cautious about cost. Given my income and focus on frugality, I'd be looking at something around $15 per month, maybe $20 if it showed exceptional value and transparency in its data handling, billed monthly. Anything more than that without a clear, demonstrable ROI is a non-starter for our small startup.
    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.