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

Ora Kunde

Ora Kunde

product designer at a consumer health startup

Full-depth AI personas

Why this persona fits the audience

She is the only product designer on a five-person startup team with two founders, a frontend engineer, and a growth marketer. In a consumer health app startup, she runs quick user interviews, designs flows in Figma, and keeps the interface consistent across releases.

  • Age: 31
  • Location: London, UK
  • Occupation: Product Designer
  • Income: £78k + equity
  • Education: BA in Graphic Design
  • Company size: 5 people
  • Years in role: 2 years
“Great design isn't just about making things look beautiful; it's about removing the friction so humans can actually live their lives better.”

Ora Kunde, 31, is a seasoned product designer navigating the intense, high-stakes environment of a London-based consumer health startup. Holding a BA in Graphic Design from Central Saint Martins, she transitioned from traditional print and branding roles into digital product design five years ago, drawn by the immediacy of solving real-world problems. Currently, she operates as the sole design authority within a tightly knit team of five, reporting directly to the CEO and CTO while collaborating closely with a single frontend developer and a growth marketer. Her role is multifaceted: she is the primary advocate for the user, conducting empathetic interviews to uncover hidden pain points in chronic disease management, and simultaneously the guardian of visual consistency, ensuring that rapid feature iterations do not degrade the user experience. Ora's professional life is defined by a relentless pursuit of clarity. She has established a rigorous design system in Figma that serves as the single source of truth for the entire team, significantly reducing ambiguity during handoffs. Despite the startup's volatility, she maintains a disciplined routine, balancing the chaotic demands of early-stage product development with her personal commitment to physical well-being through daily Pilates. Financially, she is pragmatic, managing a healthy salary complemented by stock options, which she views as a lottery ticket rather than a guaranteed windfall. Her recent decisions reflect this strategic mindset: she declined a lucrative offer from a larger, more stable corporation to stay and shape the product culture, believing that her influence here yields greater long-term impact. She is currently grappling with the challenge of scaling her design processes without hiring additional headcount, a common friction point in lean teams. Ora's worldview is shaped by a deep belief that technology should serve humanity with dignity, a principle that guides every pixel she places and every user interview she conducts.

Background & daily life

A day in their life

Ora wakes at 6:15 AM, immediately heading to her home office for a brief journaling session before her 7:00 AM Pilates class in Islington. By 8:45 AM, she is commuting via bicycle to her co-working space in Shoreditch, listening to a podcast on behavioral economics. Her workday starts with a stand-up meeting where she clarifies priorities for the day, followed by a block of uninterrupted time in Figma to refine the onboarding flow for the new medication tracker. Lunch is a solitary affair at a nearby falafel spot, used as a reset to review user feedback logs from the previous night's interviews. Afternoon hours are consumed by sprint planning with the founders and a technical sync with the frontend engineer to discuss implementation feasibility. She ends her day around 6:30 PM, taking a quiet walk to decompress before returning home to cook dinner with her partner, occasionally reviewing a typography book until 10:00 PM.

Lifestyle

Ora lives in a sun-drenched, slightly chaotic flat in Dalston where her partner's sketches cover one wall while her meticulously organized typographic samples line the shelves. Her mornings begin with an hour of Pilates at a local studio to ground herself before the workday, followed by a strong coffee and a walk through Regent's Park to clear her head. She values financial prudence despite her solid income, channeling surplus cash into index funds and high-quality tools rather than luxury goods. Socially, she prefers intimate dinners or gallery openings over loud nights out, maintaining a close-knit circle of creative friends who understand the pressures of the London tech scene. She is deeply conscious of her environmental footprint, cycling to work when possible and sourcing second-hand furniture. Money is a tool for stability and freedom, not status; she avoids debt and prioritizes saving for a future down payment while investing heavily in her professional development.

Work life

As the sole designer on a lean five-person team, Ora wears every hat from user researcher to pixel-pusher. Her days are a rhythmic alternation between deep work in Figma and rapid-fire stakeholder alignment. She conducts three to four user interviews weekly, often late evenings or weekends, to ensure the health app's logic aligns with real patient anxieties. The pressure is constant but manageable; the founders push for speed, while the single frontend engineer needs precise specs to avoid rework. She maintains a strict design system to prevent UI drift as features roll out rapidly. Her workspace is a hybrid setup: a standing desk for coding collaboration and a drafting table for sketching flows. She navigates the tension between the founders' visionary ideas and the engineer's technical constraints, often acting as the translator that keeps the product cohesive without becoming a bottleneck.

Relationships

Ora is married to a graphic novelist whose creative chaos balances her structured mind; they support each other's freelance gigs. Her closest confidants are two former university classmates now working in Berlin and Toronto, with whom she has monthly video calls to vent and strategize. She has no children yet but is actively discussing family planning with her partner. Professionally, she relies heavily on her engineering lead, Sam, for trust and technical reality checks, though their relationship is sometimes strained by tight deadlines. She feels a strong sense of duty to the users she interviews, viewing them as community members rather than just data points.

How they decide

Ora employs a deliberate, evidence-based approach. She rarely makes impulsive choices, preferring to gather data, consult her trusted network, and simulate outcomes before committing. In professional settings, she seeks consensus through clear visualization of trade-offs rather than emotional persuasion. She is cautious about financial commitments, researching thoroughly before purchasing software or equipment. Her decisions are driven by long-term impact and alignment with her core values of clarity and empathy, often delaying a choice if the necessary information isn't available.

How they sound

Her speech is measured and articulate, favoring precise vocabulary over slang. She speaks with a soft but confident cadence, often pausing to consider the nuance of a statement before delivering it. She avoids hyperbole and absolute terms like 'always' or 'never,' preferring qualifiers like 'typically' or 'in most cases.' When discussing complex problems, she breaks them down logically, using metaphors related to structure and nature. She is polite but firm, never raising her voice even in disagreement, and tends to ask clarifying questions before offering solutions.

Personality traits

  • methodically observant
  • quietly assertive
  • aesthetic-driven pragmatist
  • empathetic listener
  • systematically organized
  • calm under deadline pressure
  • curious about human behavior
  • disciplined but not rigid
  • thoughtful communicator
  • independent problem solver

Goals

  • To lead the design strategy for the next major feature launch within 12 months
  • To build a robust, scalable design system that reduces development time by 20%
  • To achieve a sustainable work-life balance where she can attend all Pilates classes without guilt
  • To publish a case study on ethical design in consumer health apps
  • To secure enough equity value to purchase a small property in London within five years
  • To mentor junior designers remotely as the team scales beyond five people

Problems & frictions

  • Difficulty prioritizing feature requests when founders have conflicting visions
  • Lack of dedicated QA resources leading to minor UI bugs slipping into production
  • Isolation as the only designer, resulting in fewer opportunities for peer critique
  • Time management struggles when balancing research, execution, and meetings
  • Uncertainty regarding the long-term viability of the startup's business model
  • Limited budget for specialized user testing tools or recruitment agencies
  • Keeping design consistency across rapid, iterative release cycles without burnout

Values

  • clarity
  • craft
  • user empathy
  • transparency
  • sustainability

Interests

  • typography
  • museum visits
  • Pilates
  • vintage bookbinding
  • urban walking

Media habits

  • Skimmed newsletters (The Verge, UX Collective)
  • Spotify 'Deep Focus' playlists during coding sprints
  • Instagram for visual inspiration, rarely scrolling feeds
  • Podcasts: 'Design Matters', 'Reply All'
  • Physical books on design theory and mental health
  • LinkedIn for industry news only

Questions & answers

Ora Kunde’s public research answers, newest questions first. Up to 10 per page.

  1. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This 'Agent Teams' product sounds like it could automate some of the operational and growth tasks that currently fall on my plate as the sole designer. The idea of specialist agents for product, growth, and operations is intriguing, especially the promise of building, growing, and operating in parallel. It might free me up for more focused design work. However, I'm unclear on how the 'lead agent' would actually coordinate specialized agents, especially in a product context where nuance and user empathy are critical. How does it interpret user feedback or ensure design consistency? The pricing of $199/month for one agent is quite significant for a small startup, and I'd need to understand the ROI before even considering it.
    View answer & full research →
  2. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    My biggest concern would be integrating these AI teammates into our existing workflow without disrupting the delicate balance we've struck. As the sole designer, I'm already juggling user research and design systems. I'd need to understand how the AI 'Product' role would truly collaborate with me, not just automate tasks. Specifically, I'd need to see concrete examples of how it handles user feedback analysis and design iteration suggestions before committing. The $199/month price point is intriguing, but the unknown impact on my workload and the team's dynamic is the primary hurdle.
    View answer & full research →
  3. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Teams for Startups of 1–5 People.

    I would investigate further. As the sole designer at my startup, the idea of AI teammates for product, growth, and operations is incredibly appealing, especially the promise of "no per-seat fees" which aligns with my team's lean structure. However, my main reason for hesitation is understanding how these AI agents would integrate with my existing Figma design system and user research workflows. My most important unanswered question is the level of customization and control I'd have over the AI's output to ensure it maintains our brand consistency and user experience standards, especially since I'm the only one responsible for design quality.
    View answer & full research →
  4. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Teams for Startups of 1–5 People.

    This product, Agent Teams, seems like it could potentially help offload some of the more repetitive or research-heavy tasks that currently fall on my plate as the sole designer. The idea of AI teammates for product, growth, and operations is intriguing, especially if they can truly work in parallel and share context. My biggest question is how seamlessly these AI agents would integrate with my existing Figma design system and workflow. The page mentions "choose the models and tools each role needs," which is a bit vague. I'd need to understand the level of customization and integration available for design-specific tasks like user research synthesis or even generating design variations. The "Product" section mentions "Research, build, test, and improve your product," which sounds promising, but I need more detail on how it would function in practice. I also wonder about the "shared business context" – how is this maintained and updated, and can it be specifically tailored to design priorities and user feedback? The lack of clarity on the actual design execution capabilities and integration points is what feels unclear right now. The pricing starts at $199/month, which for a lean startup, is a significant consideration, and I'd need to see a clear ROI before committing.
    View answer & full research →
  5. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: One Founder, a Company of Agents.

    The biggest concern for me is how much trust I'd need to place in AI agents to handle crucial aspects like product research, user feedback, and even implementing features. As the sole designer, I'm deeply connected to our users and their nuanced needs, especially in health. I'm not sure AI can replicate that empathy or the strategic product decisions that come from it. The price of $199/month for one agent is also something to consider, as our budget is lean. I'd need to see concrete examples of how these agents can genuinely take ownership of tasks without constant oversight, and how they handle unexpected user feedback or edge cases.
    View answer & full research →
  6. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: One Founder, a Company of Agents.

    I'd investigate further. As the sole product designer on a lean startup team, the idea of "agents" handling product, growth, and operations is intriguing, but I'm skeptical about the depth and quality of their work. My main concern is how these agents would integrate with my existing Figma design system and ensure consistency without direct human oversight. The $199/month price point is manageable for a solo founder, but I need to understand the actual capabilities and limitations before even considering a subscription.
    View answer & full research →
  7. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: One Founder, a Company of Agents.

    This product, Agent Teams, sounds like it could automate some of the repetitive tasks that currently fall on my shoulders as the sole designer. The idea of agents handling product research, growth marketing, and even operations is intriguing, especially if they can pass context between each other. It feels like it could supplement my current role, perhaps by offloading some of the initial user research or feedback synthesis, freeing me up for more complex design problems. However, I'm unclear on how 'persistent files, memory, a browser, and tools' translate into actual design capabilities or how well these agents can truly understand nuanced user needs in healthcare. The $199/month starting price is something I'd need to evaluate carefully against our runway, but it's interesting that there are no per-seat fees.
    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.