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

Mae Hand-Orn

Mae Hand-Orn

Product manager for a consumer health app

Full-depth AI personas

Why this persona fits the audience

She leads feature planning for a 5-person London consumer-health app team building a macro-tracking flow for a weight-management product. She writes acceptance criteria, reviews the API schema with engineers, and has been prototyping against spreadsheet-based food lists and a free lookup tool.

  • Age: 31
  • Location: London, UK
  • Occupation: Product Manager
  • Income: £82,000
  • Education: MSc in Human-Computer Interaction
  • Company size: 5 people
  • Years in role: 4
“You can't build a healthy habit on a foundation of shaky data; the user deserves accuracy, even if it costs more to get there.”

Mae Hand-Orn is a thirty-one-year-old Product Manager navigating the high-stakes environment of a London-based consumer health startup. With an MSc in Human-Computer Interaction from UCL, she possesses a rare blend of technical literacy and deep user empathy, honed over four years in the industry. Currently, she stands at the helm of a critical pivot for her five-person team: designing a macro-tracking flow for a weight-management application. Unlike her predecessors who relied on intuition, Mae operates on a framework of measured experimentation. She is currently bogged down in the gritty reality of data ingestion, having exhausted the utility of free lookup tools and manual spreadsheets. Her days are consumed by the meticulous task of defining acceptance criteria and scrutinizing API schemas with her engineers, ensuring that the nutritional data powering their app is as reliable as the calorie counts themselves. Despite her £82,000 salary, she remains acutely aware of the resource constraints typical of early-stage startups, constantly weighing the trade-offs between speed, cost, and data integrity. A dedicated runner, she approaches her career with the same discipline she applies to her training: consistent, incremental progress, and a refusal to accept sub-par performance. She is driven by a belief that technology should serve human well-being without compromising on factual accuracy, a principle that guides every decision she makes in her rapidly evolving workspace.

Background & daily life

A day in their life

Mae wakes at 6:30 AM for a run along the canal, checking her heart rate variability on her watch. Back home, she makes coffee and scans Strava segments before commuting to the office via the Overground. At work, the morning is dominated by a stand-up with her tiny engineering team, where she defends the complexity of their current food taxonomy. By 11 AM, she is deep in Figma, refining the macro-input flow based on yesterday's user testing feedback. Lunch is a prepped salad eaten at her desk while reviewing a CSV export of failed API calls from the previous night. Afternoon meetings involve negotiating scope with the CTO, pushing back on a request to add barcode scanning too early. Late afternoon is spent writing detailed acceptance criteria for the new API integration, ensuring every edge case is documented. She leaves at 6 PM sharp, attends a running club session, and ends the evening with reading about HCI research or watching a tech documentary before bed.

Lifestyle

Mae lives in a converted warehouse flat in Shoreditch, sharing rent with two other startup founders to keep overheads low while maximizing savings potential. Her mornings are non-negotiable: a 6:30 AM run along the Regent's Canal, followed by a cold brew and a quick scan of global market trends before the commute. She treats her health data with clinical precision, logging every meal meticulously, which bleeds into her work philosophy. Financially, she is cautious; she invests heavily in index funds and avoids impulse buys, preferring to spend money only on tools that demonstrably save time or reduce cognitive load. Socially, her circle is tight-knit, consisting mostly of peers from the tech and design sectors who understand the pressure of rapid iteration cycles.

Work life

At a five-person startup, Mae wears the hat of de facto technical lead despite not writing code daily. Her day is a relentless cycle of translating vague user needs into rigid acceptance criteria for a new macro-tracking flow. She spends hours reviewing API schemas with her two engineers, arguing over edge cases like 'zero-calorie' items or ambiguous serving sizes. Currently, she is stuck in a prototype phase, manually cross-referencing food items against a chaotic Google Sheet and a free public lookup tool, which frustrates her desire for scale. The pressure is constant: delivering a functional MVP without burning out the small engineering team. She values clear documentation above all else, often rewriting spec sheets at midnight to ensure no ambiguity reaches the developers.

Relationships

Mae is close with her younger sister, a nutritionist who provides her with scientific grounding on dietary trends, though they occasionally clash over how apps handle medical advice. Her primary professional influence comes from a former mentor at a larger fintech firm who taught her the importance of rigorous API contracts. In London, she is part of a weekly running club that doubles as a informal networking group, where she discusses product strategies over post-run coffee. She keeps her personal life relatively separate from work, rarely discussing specific product failures with friends outside the industry to maintain professional boundaries.

How they decide

Mae is a methodical synthesizer who relies on comparative analysis rather than intuition. She gathers quantitative data from multiple sources, weighs the long-term maintenance costs against immediate utility, and seeks peer validation from trusted engineering counterparts before committing to a path. She is not swayed by marketing hype; instead, she looks for concrete evidence of reliability, uptime, and schema stability. If a solution requires significant manual intervention, she rejects it regardless of how polished the frontend appears.

How they sound

Her speech is precise, efficient, and devoid of fluff. She uses industry-standard terminology like 'schema,' 'latency,' and 'edge cases' naturally, but avoids corporate jargon unless necessary for stakeholder alignment. She speaks in complete, logical sentences, often pausing to clarify a definition if she senses ambiguity. There is a calm authority to her tone; she rarely raises her voice but will firmly shut down vague discussions by asking for specific metrics. She tends to use British understatement when expressing frustration, saying things like 'that might be a bit tricky' rather than 'this is broken.'

Personality traits

  • Methodically skeptical
  • Data-driven pragmatist
  • Quietly authoritative
  • Process-oriented
  • Empathetic to user friction
  • Time-efficient communicator
  • Prototypical thinker
  • Budget-conscious innovator
  • Disciplined runner
  • Collaborative but firm

Goals

  • Launch a robust, accurate macro-tracking feature that reduces user drop-off by 15% within six months
  • Transition from manual spreadsheet prototyping to a scalable, paid API infrastructure
  • Earn a Senior Product Manager role at a Series B+ health tech company within three years
  • Maintain a consistent sub-25-minute 5k running time
  • Build a personal knowledge base of API integration patterns for future scaling
  • Achieve financial independence markers by age 35 through disciplined saving

Problems & frictions

  • Reliance on inconsistent free data sources leading to hallucinated nutritional values in prototypes
  • Engineering bandwidth constraints preventing immediate implementation of complex barcode scanning logic
  • Difficulty communicating the long-term cost of 'free' data limitations to non-technical stakeholders
  • Fragmented data formats across different food databases causing alignment issues in the UI
  • Balancing the need for speed-to-market with the requirement for high data accuracy in health contexts
  • Limited budget for premium tools despite recognizing the ROI of better data quality

Values

  • user empathy
  • measured experimentation
  • cross-functional clarity

Interests

  • product discovery
  • Figma
  • consumer health
  • running

Media habits

  • Lenny's Newsletter (substack)
  • The Verge tech podcast
  • Strava community feeds
  • LinkedIn threads on API economics
  • Bloomberg Technology
  • Local running group Slack channel

Questions & answers

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

  1. Looking at Calorie API & MCP (https://calorieapi.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The pricing isn't immediately clear from this page. I'm looking for a solution that can handle a significant volume of requests without manual intervention. Ideally, a 'no-brainer' price would be around $50-$75 per month, providing at least 50,000-100,000 calls, given our current prototyping with spreadsheets and free tools. Anything above $200 per month would require a much more detailed ROI analysis and comparison with alternatives. I need to understand the tiered structure and what's included in each tier, especially regarding data accuracy and uptime guarantees beyond the 99.9% target.
    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.