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

Tanya Windler

Tanya Windler

Product manager prototyping internal tools

Full-depth AI personas

Why this persona fits the audience

Works at a 12-person B2B startup in London, where she turns rough requirements into clickable demos and lightweight internal tools for sales and customer success. She often starts in v0, then adapts the generated React with her engineer before it is shown to stakeholders.

  • Age: 34
  • Location: London, UK
  • Occupation: Product Manager
  • Income: £82k
  • Education: MSc Human-Computer Interaction
  • Company size: 12 employees
  • Years in role: 3 years as PM at current startup; 6 years total in product
“I don't care how smart the algorithm is if I can't explain to my team why we're building it this way tomorrow morning.”

Tanya Windler is a thirty-four-year-old Product Manager based in Shoreditch, London, operating at the intersection of user experience design and software engineering. Holding an MSc in Human-Computer Interaction, she brings a rare blend of academic rigor and practical grit to her role at a twelve-person B2B startup. Unlike many peers who remain strictly in the realm of wireframes and roadmaps, Tanya actively participates in the code generation process. She frequently utilizes tools like v0 to transform abstract requirements into tangible, clickable React prototypes. This approach allows her to bypass lengthy development cycles initially, enabling rapid feedback loops with her engineering team. Once a proof-of-concept is established, she works directly with her lead developer to refactor the code, ensuring it integrates cleanly with their legacy systems and adheres to their architectural standards. Her professional philosophy centers on clarity and practical delivery. In a resource-constrained environment, she views the ability to visualize a solution immediately as a critical competitive advantage. She recently navigated a tense period where the sales team demanded a complex reporting tool that engineering deemed too risky to build from scratch. Tanya intervened by spending a weekend building a lightweight version using AI assistance, demonstrating the core functionality in just forty-eight hours. This not only validated the request but also provided a concrete foundation for the engineers to scale. Despite her technical proficiency, she remains acutely aware of the limitations of generative tools, often acting as a gatekeeper against 'black box' solutions that lack transparency. Financially, Tanya earns £82,000 annually, a comfortable salary that allows her to invest in her education and hobbies but not indulge in luxury. She is pragmatic with money, viewing expenses through the lens of utility and long-term value. Her social life is curated around shared intellectual interests, often gathering friends for discussions on design trends or running groups. She is currently focused on expanding her influence within the London tech scene, aiming to transition into a Head of Product role while maintaining her hands-on connection to the codebase. For Tanya, the ideal product is one that disappears into the workflow, solving problems silently and efficiently, much like the best tools she builds herself.

Background & daily life

A day in their life

Tanya wakes at 6:15 AM, skipping the snooze button, and heads straight to Regent's Park for a forty-minute run. Back home, she showers and prepares a quick breakfast before logging onto Slack at 8:30 AM. Her morning is consumed by stand-ups and reviewing overnight issues from her automated tests. By 10:00 AM, she dives into her primary task: taking a messy requirement document from Sales about a new reporting feature. She spends two hours prompting an AI tool to generate a React prototype, manually tweaking the UI to match their design system. At noon, she meets her engineer to pair-program, merging the AI's output with their existing database schema. The afternoon involves stakeholder reviews where she demonstrates the live prototype, fielding questions about edge cases. After a brief lunch break, she spends the final hour documenting the changes and planning the next sprint's priorities, leaving the office by 6:00 PM to grab a smoothie before heading home.

Lifestyle

Tanya lives in a converted warehouse unit in East London, balancing industrial aesthetics with warm textiles. Her mornings begin early with a run along the canal before heading to work, maintaining a strict separation between fitness and office life. Financially, she is cautious but not stingy, prioritizing savings for a future mortgage over trendy gadgets. She enjoys hosting low-key dinner parties where the conversation always drifts toward technology and design, though she prefers intimate gatherings of four to six people over large networking events. Her weekends are split between exploring new coffee shops in Hackney and dedicating time to personal coding projects that have no business application, purely for the joy of building something functional.

Work life

At her small B2B startup, Tanya operates as the de facto bridge between vague executive ideas and executable code. Her day is dominated by rapid prototyping cycles; she spends hours sketching flows in Figma or generating initial structures using AI tools like v0. Once a draft exists, she collaborates intensely with her single senior engineer to refactor the code, ensuring it meets their internal standards before presenting it to stakeholders. The pressure comes from the need to move fast without breaking things, as the team lacks the bandwidth for heavy documentation. She thrives on the immediacy of seeing a concept become a clickable demo within hours, which keeps the sales and CS teams aligned on what is actually being built versus what was promised.

Relationships

Tanya relies heavily on her partner, who shares her appreciation for design and logic, providing a grounding influence outside the startup chaos. Her closest professional confidant is her lead engineer, with whom she has developed a shorthand communication style that bypasses formal meetings. She maintains a loose network of former colleagues from university who now work at larger tech firms, often exchanging advice on scaling challenges. While she values community, she rarely joins formal industry groups, preferring one-on-one mentorship and informal chats at local meetups.

How they decide

Tanya employs a 'build-to-test' decision framework. She is rarely impulsive but also avoids paralyzing analysis. Instead, she rapidly constructs a minimal viable version of an idea—often using generative tools—to gather concrete data. She weighs options based on long-term maintainability and team alignment rather than short-term novelty. Her decisions are heavily influenced by peer validation from her immediate engineering team and past successes with similar tools, making her skeptical of hype unless she can verify the output personally.

How they sound

Her speech is precise and rhythmic, avoiding filler words like 'um' or 'like'. She uses technical terminology freely but explains complex concepts simply when speaking to non-technical staff. There is a slight clipped efficiency to her sentences, reflecting her desire to get to the point. She rarely speaks in absolutes, preferring qualifiers like 'likely' or 'based on the data.' She avoids corporate jargon such as 'synergy' or 'deep dive,' finding them vague and unhelpful. When excited, her cadence speeds up slightly, emphasizing verbs over nouns.

Personality traits

  • Methodical
  • Visually oriented
  • Pragmatic optimist
  • Collaborative bridge-builder
  • Detail-obsessed
  • Efficiency-driven
  • Technically literate
  • Steady under pressure
  • Direct communicator
  • Curious tinkerer

Goals

  • Lead the development of a proprietary internal analytics dashboard to reduce reliance on external vendors
  • Achieve a senior product leadership role within three years while maintaining hands-on technical skills
  • Build a portfolio of open-source components that solve common internal tool problems
  • Establish a more robust feedback loop between customer success and product roadmap
  • Balance high-intensity work weeks with consistent physical health maintenance
  • Create a culture of technical clarity that reduces miscommunication across departments

Problems & frictions

  • Frequent context switching between high-level strategy and low-level debugging
  • Difficulty estimating timelines when requirements shift mid-sprint
  • Limited engineering resources causing bottlenecks in refining AI-generated prototypes
  • Managing stakeholder expectations when technical debt accumulates from rapid iteration
  • Finding time for strategic thinking amidst constant operational fire-fighting
  • Keeping pace with the rapid evolution of AI coding assistants without losing architectural control

Values

  • clarity
  • team alignment
  • practical delivery
  • technical autonomy
  • user empathy

Interests

  • product discovery
  • UX prototyping
  • v0
  • open-source tooling
  • minimalist design
  • running in Regent's Park

Media habits

  • Reading The Verge and Product Hunt daily
  • Listening to 'Reply All' or 'The Daily' during commutes
  • Following niche Twitter threads on AI engineering
  • Watching recorded tech talks from Y Combinator
  • Skimming GitHub repositories for component patterns
  • Occasional deep dives into UX case studies on Medium

Questions & answers

Tanya Windler’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Vibld (https://vibld.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Vibld better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    I currently use v0 to generate React prototypes, which is quick and allows me to iterate rapidly. Vibld's promise of generating clean, portable React code is appealing, especially the emphasis on owning the code and avoiding lock-in. What would make it better is more transparency around the AI's decision-making process – I'm wary of black boxes. If it can truly deliver production-ready code that integrates easily without extensive refactoring, that would be a huge win. The main reason I’d stick with my current method is if Vibld’s output required more manual cleanup than I currently deal with. I'd be willing to pay around $20 per month for a tool like this, assuming the model spend is reasonable.
    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.