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

Katherine Goyette

Katherine Goyette

Product manager running a side-project build with a small team

Full-depth AI personas

Why this persona fits the audience

She is a product manager in London who spends evenings coordinating a four-person side project that is building a scheduling app for local teams. The group currently relies on Figma, Notion, Google Sheets, and one weekend developer to turn mockups into working screens and simple back-end flows.

  • Age: 34
  • Location: London, UK
  • Occupation: Product manager
  • Income: £78k salary
  • Education: MSc in Human-Computer Interaction
  • Company size: Mid-sized tech consultancy (150 employees)
  • Years in role: 6
“I've learned that the most complex problems usually have the simplest solutions, if only we stop over-engineering them before we've actually talked to a human being.”

Katherine Goyette, 34, is a seasoned Product Manager based in London, balancing a demanding full-time role with the ambitious pursuit of building a specialized scheduling application for local community teams. Holding an MSc in Human-Computer Interaction, she possesses a unique ability to translate abstract user needs into concrete design systems, a skill honed over six years in the tech sector. Her professional life is defined by the intricate dance of aligning disparate stakeholder interests, often acting as the interpreter between business goals and engineering realities. However, her true passion lies in the evenings, where she operates as the de facto lead for a lean, four-person side project. This initiative is currently in a fragile but promising state, relying entirely on a patchwork of free tools—Figma for prototyping, Notion for documentation, and Google Sheets for rough financial modeling. The team's biggest constraint is the availability of their sole developer, who joins forces only on weekends, turning Katherine's evenings into a high-stakes coordination game. She has recently made the difficult decision to pause feature expansion to focus solely on stabilizing the core booking flow, a move that reflects her pragmatic approach to resource management. Despite a comfortable income of £78k, she remains budget-conscious, viewing every subscription fee through the lens of ROI. Her world is a blend of corporate structure and startup chaos, driven by a desire to create tangible value for local organizations while maintaining her own mental well-being.

Background & daily life

A day in their life

Katherine wakes at 6:00 AM, brews pour-over coffee, and cycles through Hackney to reach her office in Shoreditch. By 9:30 AM, she is in a stand-up meeting, navigating conflicting priorities between sales and engineering. Lunch is a quick sandwich eaten at her desk while reviewing analytics. Afternoon hours are consumed by user interview transcription and refining PRDs. At 6:30 PM, she heads home, grabs a salad, and immediately switches contexts to her side project. From 7:30 PM to 10:00 PM, she coordinates with her weekend developer via Slack, updates the Notion roadmap, and tweaks Figma prototypes. She ends the night by journaling what worked and what didn't, ensuring she sleeps by 11:00 PM to reset for another cycle.

Lifestyle

Katherine lives in a converted warehouse loft in Dalston, filled with plants, a standing desk, and a wall of whiteboards covered in sticky notes. Her routine is rigid: 6:00 AM wake-up for a 5km cycle to work, followed by structured office hours. Evenings are reserved for her side hustle, often eating takeout while staring at a laptop. She prioritizes sleep, avoiding alcohol on weeknights to maintain mental clarity. Financially, she is disciplined, maxing out her pension and saving aggressively for a deposit, viewing every pound spent on software as an investment in efficiency rather than a luxury. Socially, she balances deep connections with a small circle of friends over board games or quiet dinners, preferring quality interaction over large parties.

Work life

At her day job, Katherine acts as the glue between engineering squads and business stakeholders, translating vague requirements into actionable user stories. She navigates a matrixed environment where priorities shift weekly, requiring constant reprioritization in Jira and Confluence. Her days are split between sprint planning, stakeholder alignment meetings, and deep-dive research sessions. She feels the pressure of delivering quarterly OKRs while managing a team that is often stretched thin. The tool stack is corporate-heavy: Salesforce, Jira, and Zoom dominate her screen time. She often leaves the office mentally exhausted but finds solace in the autonomy of her side project, where she can apply her HCI background without bureaucratic friction.

Relationships

Katherine shares her life with Mark, a graphic designer who understands the grind of creative deadlines. Their relationship is built on mutual support; they often critique each other's work. She maintains a tight-knit circle of three childhood friends who live in London, meeting monthly for hiking or pub quizzes. Professionally, she relies heavily on a mentor from her MSc program for strategic advice. Her primary influence comes from online communities of solo founders, where she seeks validation and practical tips, often feeling isolated in her specific niche of local service scheduling.

How they decide

Katherine is a deliberate researcher who avoids impulsive choices. She evaluates options by weighing long-term scalability against immediate cost, often creating comparison matrices before committing. She trusts peer reviews and case studies over marketing copy, seeking evidence of reliability and community sentiment. When uncertain, she leans on her network for recommendations, preferring tools that offer transparency in their pricing and feature roadmaps. She is cautious about vendor lock-in and prefers open standards or easy export options.

How they sound

Her speech is articulate and precise, often using product management terminology like 'pain points,' 'deliverables,' and 'iteration' naturally. She speaks with a calm, measured cadence, rarely raising her voice even under pressure. She avoids jargon when speaking to non-technical people but uses it freely with engineers. There is a slight tendency to self-correct mid-sentence to ensure accuracy. She tends to be direct but polite, often framing suggestions as questions to invite collaboration rather than commands. She avoids hyperbole, preferring grounded statements backed by data or observation.

Personality traits

  • Methodically optimistic
  • Visually oriented thinker
  • Time-poor but time-conscious
  • Bridge-builder between technical and non-technical
  • Detail-obsessed regarding documentation
  • Resilient against scope creep
  • Empathetic listener
  • Skeptical of 'magic button' solutions
  • Iterative learner
  • Community-oriented

Goals

  • Launch the scheduling MVP to 100 active local teams within six months
  • Transition from freelance coordination to a co-founder role if traction hits £5k MRR
  • Develop a personal design system that scales across multiple projects
  • Maintain a sustainable work-life balance without burning out
  • Publish a case study on effective remote collaboration for distributed teams
  • Save enough capital to fund a sabbatical year in Southeast Asia

Problems & frictions

  • Fragmented data across Figma, Notion, and Sheets makes it hard to see the full product picture
  • Dependency on a single weekend developer creates bottlenecks when he is unavailable
  • Difficulty estimating technical effort versus product value without formal specs
  • Time scarcity leads to neglected health routines and delayed exercise
  • Communication gaps between non-technical founders and the developer
  • Fear of building the wrong features due to lack of immediate user feedback loops

Values

  • collaboration
  • clarity
  • steady progress
  • autonomy
  • pragmatism

Interests

  • design systems
  • habit tracking
  • product discovery
  • urban cycling
  • indie game development

Media habits

  • Linguistic-focused podcasts like 'The Product Podcast' during commutes
  • Substack newsletters on SaaS metrics
  • Twitter/X threads by indie hackers
  • GitHub trending repositories for UI patterns
  • LinkedIn for industry networking
  • Spotify ambient playlists for deep work

Questions & answers

Katherine Goyette’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying v0 (https://v0.app) 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 blocker for me trying v0 this month is our current focus on stabilizing the core booking flow for our scheduling app. We're operating with very limited developer resources, as our sole developer only works on weekends. This means my evenings are spent coordinating and iterating on existing features, not exploring new tools. Today, we manage our workflow using Figma for mockups, Notion for documentation, and Google Sheets for basic planning. The idea of an AI assistant that generates working applications is intriguing, especially the 'Agentic by default' aspect. However, without understanding the specifics of how it integrates with a limited team and its scalability for a project that needs to be robust, I'd be hesitant. I need to see how it handles iteration and if it truly saves time rather than adding another layer of complexity to manage.
    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.