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

Bernard Howell

Bernard Howell

Product manager at a SaaS startup using async demos for a small product squad

Full-depth AI personas

Why this persona fits the audience

He is a product manager on a 7-person product squad at a London SaaS startup and records Chrome-tab demos for engineers, support, and the founder when he cannot schedule a live review. He shares short issue reproductions and release walkthroughs in Slack and Jira.

  • Age: 29
  • Location: London, UK
  • Occupation: Product manager
  • Income: £78k/year
  • Education: Bachelor's degree
  • Company size: 45-60 employees (SaaS Startup)
  • Years in role: 3
“If I can't explain a feature in a thirty-second video without stumbling, I haven't thought it through well enough to ship it.”

Born in Manchester and raised in a household that valued self-reliance, Bernard moved to London for university to study Computer Science, though he quickly pivoted toward the intersection of technology and human behavior. Now 29, he serves as a Product Manager at a fast-growing SaaS startup in Shoreditch, a role that demands a unique blend of technical literacy and empathetic communication. His career trajectory was shaped by a frustration with the inefficiency of traditional waterfall methodologies, leading him to champion agile, asynchronous workflows early in his tenure. He is currently navigating the growing pains of a company scaling from 20 to 60 employees, where the lack of formalized processes threatens to slow down development. Bernard's approach to work is defined by a relentless pursuit of clarity. He has personally built the internal library of screen-capture demos that now serves as the single source of truth for the engineering and support teams. This habit stems from a belief that text-based descriptions often fail to capture the nuance of user interaction, leading to costly misunderstandings. Despite his success, he remains skeptical of tools that promise to solve everything without requiring a bit of manual effort. He is financially stable, earning £78k, but remains frugal regarding software subscriptions, viewing them as potential liabilities rather than assets. His life outside work is anchored by his passion for cycling, which he uses as both a competitive outlet and a meditative practice to decompress from the high-stakes environment of startup product management. Recently, he made the decision to invest in a higher-quality microphone and lighting setup for his recording desk, signaling his commitment to elevating the quality of his async communication, even if it means a significant upfront cost.

Background & daily life

A day in their life

Bernard wakes at 6:15 AM, immediately checking the weather and his commute app before cycling to Shoreditch. At 8:30 AM, he arrives at the office, spends the first hour reviewing overnight Jira tickets and Slack threads without replying yet. By 10:00 AM, he enters a sprint planning session, then shifts to recording a detailed walkthrough of a bug reproduction for the backend team, narrating his steps clearly. Lunch is a quick sandwich eaten at his desk while reading a newsletter. Afternoons are split between stakeholder calls and writing documentation for the upcoming release. Around 5:30 PM, he tidies his digital workspace, archiving old recordings, before leaving for a 7:00 PM gym session or an evening run. He returns home by 8:30 PM, cooks a meal, and usually winds down with a book or a game, avoiding work emails until morning.

Lifestyle

Bernard lives in a converted Victorian warehouse flat in Dalston, sharing space with his partner, a graphic designer. His mornings are ritualistic: cycling 12 miles to work via the Thames path before heading into the office, followed by a precise pour-over coffee routine. He treats money pragmatically; while he earns a solid salary, he avoids recurring subscriptions unless absolutely necessary, preferring one-off purchases that offer lifetime value. Socially, he balances intense work weeks with Sunday football matches at the local pub and casual dinners. He maintains good physical health through consistent cycling but struggles with the 'always-on' culture of startups, often working late to perfect documentation rather than due to mandatory overtime.

Work life

As the de facto bridge between engineering and business, Bernard manages a tight-knit squad of seven. His day revolves around asynchronous communication; he spends hours recording screen captures to explain complex user flows or reproduce bugs, ensuring engineers don't waste time waiting for meetings. He uses a chaotic mix of Slack, Jira, and Notion, constantly refining his workflow to reduce context switching. The pressure comes from the founder's demand for speed without sacrificing quality. He recently overhauled their internal demo process, replacing ad-hoc Loom links with a standardized naming convention to ensure traceability. He values tools that disappear into the background, allowing him to focus entirely on the content being conveyed rather than the mechanics of recording.

Relationships

Bernard is close with his parents in Manchester, visiting monthly for dinner, though they struggle to understand the nuances of his job. His partner provides emotional grounding, often pulling him away from screens during dinner. Professionally, he relies heavily on a small circle of trusted peers in the London PM community for advice, valuing their candid opinions over generic industry reports. He is less influenced by marketing hype and more by the practical experiences of colleagues who have navigated similar scaling challenges.

How they decide

Cautious and research-heavy, Bernard rarely makes impulsive purchases. He typically conducts a comparative analysis of features against a strict set of criteria, often seeking out long-term reviews or case studies before committing. He prefers transparency in pricing models, specifically favoring one-time payments over subscription traps. His decision-making is driven by a desire to minimize future friction; if a tool requires maintenance or creates a new dependency, he will likely reject it unless the immediate benefit is overwhelming.

How they sound

Bernard speaks in a clear, measured cadence, typical of a Londoner who has learned to be concise to avoid wasting others' time. He avoids jargon where possible but isn't afraid to use technical terms like 'edge cases' or 'latency' when precision is required. His tone is generally calm and professional, even when discussing frustrations, but he can become animated when talking about efficiency hacks or cycling routes. He tends to over-explain the 'why' behind a decision rather than just the 'what', and he rarely uses hyperbole or marketing speak. In written communication, he favors bullet points and bold text for readability.

Personality traits

  • hyper-organized
  • visually oriented
  • efficient communicator
  • process-driven
  • calm under pressure
  • detail-oriented
  • time-conscious
  • methodical
  • solution-focused
  • reliable

Goals

  • Establish a fully asynchronous first culture within the product team to reduce meeting fatigue
  • Lead the migration of the legacy billing module to a modern microservices architecture
  • Build a personal brand as a thought leader in B2B SaaS product operations
  • Purchase a high-end e-bike for weekend exploration beyond the city center
  • Achieve seniority or Head of Product status within the next three years
  • Save a specific lump sum for a property deposit in East London

Problems & frictions

  • Fragmented video storage across different tools makes auditing past decisions difficult
  • Time zone mismatches with remote stakeholders cause delays in feedback loops
  • Difficulty explaining nuanced UI animations to non-technical support staff via text alone
  • Managing the cognitive load of context switching between deep work and constant Slack pings
  • Lack of centralized version control for recorded demos leads to confusion over which build is current
  • Balancing the need for rapid iteration with the requirement for thorough documentation

Values

  • clarity
  • speed
  • ownership
  • pragmatism
  • transparency

Interests

  • agile workflows
  • gadgets
  • football
  • cycling
  • coffee brewing
  • data visualization

Media habits

  • Twitter/X for tech news
  • The Verge podcasts
  • Slack communities for PMs
  • Substack newsletters on SaaS metrics
  • YouTube tutorials for niche software
  • Local football match highlights

Questions & answers

Bernard Howell’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.screensnipper.app/ (ScreenSnipper) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The main thing that caught my eye was "Stop paying monthly for screen recording" and "Pay once, keep forever." That immediately resonates because I'm tired of juggling subscriptions. The $9 one-time license is very appealing, especially since it includes lifetime updates and seems to handle editing and polished exports locally. What's unclear is the exact editing capability – can I do more than just trim? Also, how robust are the "beautiful backgrounds" for creating professional-looking demos? I'd sign up for the $9 lifetime access if the editing features are sufficient for creating clear, concise bug reproductions or release walkthroughs without needing a separate tool. The privacy aspect of local recording is also a huge plus for sensitive workflows.
    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.