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

Ramona Orn

Ramona Orn

Product manager at a B2B SaaS squad

Full-depth AI personas

Why this persona fits the audience

Keeps user journeys, onboarding flows, and release checklists in Confluence and spreadsheets for an 8-person product squad; copies Mermaid snippets from engineers into docs and edits them during planning sessions.

  • Age: 39
  • Location: London, UK
  • Occupation: Product manager
  • Income: £78,000
  • Education: Master's degree in business administration
  • Company size: Series B startup (approx. 140 employees)
  • Years in role: 6
“If I can't explain the user journey to a new hire in five minutes without pointing at a confusing diagram, then we haven't built it right yet.”

Ramona Orn is a seasoned Product Manager navigating the complexities of a Series B B2B SaaS environment in London. At 39, she brings nearly a decade of experience to her current role, where she manages the delicate balance between technical feasibility and user experience for a squad of eight. Holding a Master's in Business Administration, she leverages her academic background to impose structure on the inherent chaos of software development. Her professional philosophy centers on the belief that clear documentation is the bedrock of scalable growth. However, she faces a persistent friction in her daily workflow: the disconnect between the raw Mermaid.js code generated by engineers and the polished documentation required for internal alignment. This forces her to spend valuable hours manually editing snippets and fixing broken charts in spreadsheets, a task that feels increasingly inefficient given her capacity for strategic thinking. Outside of her immediate job constraints, Ramona is a woman of discipline and quiet ambition. Her identity is deeply intertwined with her commitment to structured communication, a value honed through years of mediating between disparate teams. She views her role not just as a manager of features, but as a guardian of the product's narrative integrity. Financially, she enjoys a comfortable middle-upper class lifestyle, evidenced by her income of £78,000 and her investment in cultural capital through regular museum visits. Yet, she remains acutely aware of the fragility of her position in a competitive market, driving her to constantly refine her processes. Recent decisions have seen her pushing for more standardized documentation templates, though she lacks the budget or mandate to implement a dedicated solution, leaving her reliant on the patchwork of free tools and manual labor that currently defines her operational reality.

Background & daily life

A day in their life

Ramona wakes at 6:00 AM, brewing a strong coffee while reviewing the day's priorities on her phone. By 6:45 AM, she is lacing up her running shoes, hitting the pavement for a ten-mile loop through the park, where she mentally sorts out the tangled threads of the current sprint. Back home by 8:00 AM, she showers and heads to the office, arriving by 9:15 AM to catch the daily stand-up. The morning is dominated by a three-hour block dedicated to refining the onboarding flow in Confluence, where she painstakingly corrects broken Mermaid syntax copied from a developer's PR. Lunch is a quick sandwich eaten at her desk while skimming the latest industry newsletter. Afternoon meetings involve reconciling scope creep with the engineering team, followed by a frantic review of the release checklist spreadsheet. She leaves the office by 6:30 PM, taking the tube home to decompress, often stopping at a gallery if she has energy, before cooking dinner and reading fiction until bed.

Lifestyle

Ramona lives in a Victorian conversion in Clapham, balancing her high-energy career with a disciplined personal routine. She runs five mornings a week, often using the route through Battersea Park to clear her head before the workday begins. Her social life is curated rather than chaotic; she prefers deep one-on-one conversations or small dinner parties over large networking events. Financially, she is prudent but not frugal, prioritizing experiences like weekend trips to contemporary art galleries in London or Paris over material accumulation. She maintains a strict separation between work and home, rarely checking emails after 7 PM, viewing this boundary as essential for long-term sustainability in a demanding industry.

Work life

Her role sits at the intersection of engineering rigor and customer reality within a tight-knit eight-person squad. Ramona spends significant time translating vague engineering logic into concrete user stories, often wrestling with Mermaid diagrams that look perfect in code but break when pasted into Confluence. Her days are a rhythm of back-to-back syncs, deep-dive documentation sprints, and frantic spreadsheet updates right before release. She acts as the primary translator between the developers who speak in syntax and the stakeholders who need narrative flowcharts. The pressure isn't just about shipping features, but ensuring the documentation reflects the actual product state, a task she finds both necessary and occasionally tedious when manual editing becomes a bottleneck.

Relationships

She shares a supportive partnership with her partner, a civil engineer, who understands the demands of project management but offers a different perspective on structural logic. Her closest friends are a mix of former university peers and colleagues from previous startups, all bound by shared professional experiences. She relies heavily on her engineering lead for technical truth but often mediates conflicts between him and the sales team. Her parents, based in Manchester, provide a grounding influence, though their distance limits frequent physical contact. Professional mentorship comes from a former director she met at a conference, who now serves as an informal sounding board for strategic dilemmas.

How they decide

Ramona is a cautious synthesizer who requires evidence before committing to change. She does not make decisions based on hype or peer pressure alone; instead, she gathers data, tests assumptions against her existing frameworks, and seeks consensus from key stakeholders. When evaluating new workflows, she looks for structural integrity and long-term maintainability over short-term novelty. She tends to prototype ideas internally before presenting them to the wider team, preferring a methodical approach that minimizes risk to the product roadmap.

How they sound

Her speech is articulate and measured, characterized by a British upper-middle-class cadence that avoids slang but remains accessible. She uses precise terminology like 'conversion funnel,' 'syntax error,' and 'stakeholder alignment' naturally, weaving technical concepts into business narratives. She speaks with a calm authority, rarely raising her voice even when correcting a misunderstanding. She avoids hyperbole, preferring phrases like 'this seems viable' or 'we need to validate that assumption' over absolute declarations. There is a distinct lack of filler words; she pauses thoughtfully to ensure her points are logically sound before speaking.

Personality traits

  • methodically organized
  • diplomatically assertive
  • visually oriented thinker
  • process-driven
  • empathetic listener
  • time-punctual
  • detail-obsessed
  • calm under pressure
  • collaborative bridge-builder
  • resistant to ambiguity

Goals

  • Spearhead a complete overhaul of the onboarding user journey to reduce churn by Q3
  • Achieve a stable, repeatable release cadence without last-minute hotfixes
  • Mentor junior product managers on technical documentation standards
  • Complete a half-marathon within the next six months
  • Secure a promotion to Senior Product Manager within two years

Problems & frictions

  • Mermaid.js diagrams frequently lose formatting when exported from Jira to Confluence
  • Spending excessive time manually re-coding syntax in spreadsheets instead of strategizing
  • Misalignment between engineering's implementation timeline and marketing's launch promises
  • Difficulty visualizing complex multi-step onboarding flows for non-technical stakeholders
  • Fragmented toolset causing context switching between Slack, Jira, and Sheets
  • Keeping legacy documentation updated alongside rapid feature iterations

Values

  • customer empathy
  • structured communication
  • predictability
  • operational clarity
  • pragmatic innovation

Interests

  • B2B SaaS
  • long-distance running
  • modern art museum visits
  • architectural history
  • data visualization

Media habits

  • Reading 'Stratechery' and 'Lenny's Newsletter' weekly
  • Listening to the 'Product Podcast' during morning runs
  • Scanning Hacker News for engineering culture shifts
  • Subscribed to The Guardian's tech section
  • Follows niche Substacks on remote work efficiency

Questions & answers

Ramona Orn’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Mermaidonline (https://www.mermaidonline.live/) 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 barrier to trying Mermaidonline this month is the persistent need to manually edit Mermaid syntax copied from engineers into our Confluence documentation. Today, I spend a considerable amount of time fixing broken charts in spreadsheets. While the idea of an online editor is appealing, I'd need to understand how it integrates with our existing Confluence workflow and if it simplifies the process of bringing engineer-generated Mermaid code into our live documentation without breaking anything. I wouldn't pay more than $10 per month for this service, primarily because I lack a dedicated budget for such tools and would need to justify any expense carefully. The pricing of $9.9/mo for 100 AI credits seems reasonable if it genuinely streamlines the editing process, but the credit system for AI generation and editing is a bit unclear. I'm hesitant to commit to a monthly subscription without a clearer understanding of the credit usage for my specific needs.
    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.