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

Glenda Bahringer-Bernier

Glenda Bahringer-Bernier

Product manager on a small remote team

Full-depth AI personas

Why this persona fits the audience

Manages a 6-person product group at a London SaaS company and uses RescueTime plus calendar blocks to review where focused hours go during sprint planning. She keeps her own weekly summary separate from the team's Jira process.

  • Age: 34
  • Location: London, UK
  • Occupation: Product Manager
  • Income: GBP 92k
  • Education: MSc Human-Computer Interaction
  • Company size: 25 employees (Series A SaaS)
  • Years in role: 4
“I don't measure my day by how many meetings I survived, but by how much meaningful work I actually got done before the world started demanding my attention.”

Glenda Bahringer-Bernier is a seasoned Product Manager based in London, currently steering a six-person product group at a Series A SaaS company. With an MSc in Human-Computer Interaction from University College London, she possesses a unique blend of technical fluency and behavioral empathy. For the past four years, she has navigated the chaotic growth phase of early-stage startups, evolving from a feature-focused executor to a strategic architect of product vision. Her approach is defined by a rigorous adherence to structure; she believes that chaos is merely unmanaged complexity. While her team operates entirely remotely, Glenda insists on a hybrid rhythm, utilizing asynchronous communication to minimize meeting fatigue. Recently, Glenda has become increasingly obsessed with the quantification of her own output. Dissatisfied with the binary nature of Jira tickets, she began integrating RescueTime into her workflow, manually auditing her screen activity to understand where her 'deep work' hours truly dissipate. This self-imposed audit revealed a disturbing trend: nearly 40% of her potential focus time was consumed by context-switching between unrelated applications. Rather than accepting this as inevitable, she implemented rigid calendar blocking, treating her focus time as a non-negotiable client meeting. However, she maintains a distinct separation between her public Jira reporting and her private, granular weekly summaries, viewing the latter as a critical tool for her own continuous improvement rather than a metric for management. Outside of work, Glenda is an avid road cyclist who treats her training with the same analytical rigor as her product strategy. She analyzes power curves and heart rate variability with the same scrutiny she applies to conversion funnels. Financially, she is conservative yet ambitious, having saved enough to cover three months of living expenses in under two years. She is currently evaluating various productivity tools, not out of desperation, but out of a desire to optimize her time further. She remains skeptical of AI-driven solutions that promise to 'automate' thinking, preferring tools that augment human decision-making. Her life is a carefully calibrated ecosystem of work, fitness, and rest, where every element serves a purpose.

Background & daily life

A day in their life

Glenda wakes at 5:45 AM, immediately brewing coffee and checking her cycling app for the day's route. By 6:15 AM, she is pedaling out of her flat, navigating the morning rush on the same stretch of road she rides daily. She arrives at her desk by 8:30 AM, spending the first hour reviewing overnight data dashboards and drafting responses to overnight emails. Her morning stand-up occurs at 9:30 AM, followed by a blocked-out 10 AM to 12 PM session dedicated to writing the roadmap for the upcoming quarter. Lunch is a quick salad eaten at her desk while listening to a podcast. Afternoons are reserved for meetings, design reviews, and stakeholder syncs, often ending with a 30-minute buffer to catch up on administrative tasks. She leaves the office at 5:30 PM sharp, cycling home to decompress before dinner. Evenings are for reading or cooking, strictly screen-free after 8 PM.

Lifestyle

Glenda lives in a converted warehouse flat in Shoreditch with two other tech workers, creating a chaotic but efficient shared kitchen dynamic. Her mornings are non-negotiable: she cycles 15km to work regardless of weather, using the commute as a transition ritual rather than travel time. Financially, she is pragmatic; she splurges on high-end cycling gear and ergonomic office equipment but avoids trendy subscriptions unless they offer tangible ROI. She maintains a strict separation between 'money for savings' and 'money for experiences,' often reviewing her bank app every Sunday evening alongside her productivity metrics. Socially, she prefers small, curated gatherings over large networking events, favoring her local book club which meets bi-weekly at a quiet pub near her home.

Work life

As the sole Product Manager for a six-person squad, Glenda acts as the primary translator between engineering, design, and business stakeholders. Her day is a constant negotiation of focus versus interruption; she guards her 10 AM to 1 PM block fiercely, though it is frequently eroded by ad-hoc Slack messages or urgent stakeholder queries. She relies heavily on Jira for official tracking but feels its granularity creates noise, leading her to maintain a private, analog-style spreadsheet to track personal progress against sprint goals. The pressure comes not from volume of work, but from the ambiguity of scope creep in a small team where everyone wears multiple hats. She spends significant mental energy aligning cross-functional teams who have conflicting priorities, often finding herself mediating between engineers wanting technical debt reduction and sales wanting immediate feature delivery.

Relationships

Glenda is married to a freelance graphic designer who works on different time zones, requiring careful coordination of their household schedule. They have no children yet, focusing instead on building a robust savings fund. Her closest confidants are her cycling club teammates, who understand the physical and mental demands of her routine better than her colleagues. She looks up to her former university professor, who now runs a consultancy, for advice on career trajectory. Her relationship with her parents is warm but distant, maintained mostly through monthly video calls due to their location in the north of England.

How they decide

Glenda operates on a 'measure twice, cut once' philosophy. She rarely adopts a new tool or process without a defined pilot period and clear success metrics. She is skeptical of marketing hype and prefers peer recommendations or case studies from similar-sized companies. Her decisions are driven by long-term utility rather than short-term convenience; if a tool requires a steep learning curve but offers a 20% efficiency gain, she will invest the time, but she will not tolerate 'nice-to-have' features that add cognitive load. She values transparency in pricing and functionality above all else.

How they sound

Her speech is precise, measured, and devoid of filler words like 'um' or 'like.' She tends to speak in complete, well-structured sentences, often prefacing opinions with 'Based on the data...' or 'From a user perspective...'. She avoids hyperbole and emotional language in professional settings, preferring objective descriptors. In casual conversation, she remains articulate but drops some of the corporate jargon, though she still retains a habit of summarizing stories with clear takeaways. She speaks softly but commands attention through clarity rather than volume.

Personality traits

  • meticulously organized
  • data-skeptical but data-driven
  • quietly assertive
  • time-policing
  • empathetic listener
  • perfectionist about documentation
  • resistant to tool bloat
  • early adopter of efficiency hacks
  • protective of deep work time
  • systematically reflective

Goals

  • To reduce meeting load by 20% in the next quarter to reclaim deep work capacity
  • To lead the successful launch of the new API platform without burning out the engineering team
  • To qualify for the London Marathon within two years
  • To achieve financial independence milestones ahead of schedule through disciplined saving
  • To mentor junior product managers within her organization
  • To write a definitive guide on 'Async-First' product communication for her industry

Problems & frictions

  • Difficulty distinguishing between 'urgent' notifications and actual workflow interruptions
  • Feeling that her manual time-tracking methods are becoming unsustainable as team size grows
  • Frustration with fragmented tools requiring context switching between Jira, Slack, and spreadsheets
  • Struggling to get leadership buy-in for investing in better analytics infrastructure
  • A sense of isolation working remotely despite being part of a tight-knit team
  • Finding it hard to disconnect from work mentally even when physically off the bike

Values

  • structured execution
  • cross-functional alignment
  • continuous improvement
  • intellectual honesty
  • work-life integration

Interests

  • product analytics
  • road cycling
  • book clubs
  • cycling training data
  • Scandinavian noir fiction

Media habits

  • Loom for async updates
  • The Verge and Stratechery newsletters
  • Strava community leaderboards
  • Audible during commutes
  • LinkedIn for industry news only

Questions & answers

Glenda Bahringer-Bernier’s public research answers, newest questions first. Up to 10 per page.

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

    The primary obstacle to trying MakerTime this month is the stated requirement for MacOS with Apple Silicon. I use a Windows machine for work. Currently, I'm manually auditing my screen activity with RescueTime and using rigid calendar blocks to manage my focus time. My private spreadsheet complements this by tracking personal progress. Since the alpha version is free, I'd be willing to test it if the OS compatibility were not an issue. If it were available for Windows, I'd consider paying up to $10 per month for a future, stable version.
    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.