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

Leonard Stokes

Leonard Stokes

Technical writer at fintech company

Full-depth AI personas

Why this persona fits the audience

He is a technical writer for a 60-person fintech company in Boston, creating help docs, release notes, and internal how-to guides with tight terminology constraints. He routinely compares AI rewrite output with his own edits because product names, numbers, and compliance language must stay exact.

  • Age: 46
  • Location: Boston, MA, US
  • Occupation: Technical Writer
  • Income: $122k
  • Education: MS in Technical Communication
  • Company size: 60
  • Years in role: 12
“If it's not documented with absolute certainty, it might as well not exist.”

Leonard Stokes has always been drawn to systems that require order and precision. Growing up in a suburban Massachusetts town, his childhood was marked by a fascination with intricate LEGO constructions and a penchant for organizing his stamp collection by catalog number. This inclination naturally steered him towards technical communication, where he earned an MS from Northeastern University. For the past twelve years, he has applied this meticulous approach to his role as a Technical Writer at a Boston-based fintech firm. His daily reality involves navigating the highly regulated world of financial technology, where a misplaced comma or an incorrect product version number can have significant consequences. He’s currently deep in documentation for a new secure transaction API, a project demanding extreme accuracy regarding compliance language and numerical data. Leonard sees his work not just as writing, but as a critical component of risk control for the company. His professional life is characterized by a commitment to thoroughness; he spends hours comparing draft text against actual system outputs and even experiments with AI paraphrasing tools, scrutinizing their rewrites to ensure they don't inadvertently alter critical financial figures or regulatory terminology. This rigorous process, while time-consuming, ensures the integrity of the company's communications and safeguards against potential errors. He views his income as a means to achieve financial stability rather than a measure of status, preferring to invest conservatively and maintain a buffer against unforeseen events. His personal life is similarly ordered, with routine road biking rides and strategic chess matches providing structured outlets for his analytical mind.

Background & daily life

A day in their life

Leonard's day begins precisely at 6:00 AM with a quick review of overnight market news and industry blogs, followed by a cup of black coffee while reading a technical manual or industry white paper. He commutes by train to his Boston office, often listening to a podcast on personal finance or API development. His workday is a cycle of writing, editing, and verifying documentation – meticulously updating release notes for a new feature, drafting a how-to guide for an internal tool, and rigorously cross-referencing API endpoints against system logs. Lunch is usually a packed meal at his desk. He collaborates with engineers via Slack, attending brief stand-ups. Evenings involve dinner with his wife, reviewing financial statements, or a few rounds of chess online before bed around 10:30 PM.

Lifestyle

Leonard lives a structured, home-centric life with his wife, Sarah, a graphic designer, in a quiet neighborhood of Arlington. Their finances are managed meticulously, with a focus on long-term savings and avoiding unnecessary debt, reflecting his value of risk control. Weekday evenings are often spent preparing for the next day or engaging in quiet hobbies like reading or playing chess online. Weekends involve long road biking excursions through the Massachusetts countryside, weather permitting, or catching up on household projects. He prioritizes routine and predictability, finding comfort in established patterns and avoiding impulsive decisions, especially concerning finances or major life changes.

Work life

As a technical writer at a fast-growing fintech, Leonard is the go-to for all documentation. His days are consumed by distilling complex financial product features and API specifications into clear, accessible language for help guides and release notes. The pressure is immense due to strict regulatory compliance and the need for absolute accuracy with financial figures and product names. He works closely with product managers and engineers, often mediating minor disputes over terminology. His primary tools include MadCap Flare for authoring, a version control system for tracking changes, and a battery of testing environments where he meticulously verifies every detail against live system outputs.

Relationships

Leonard is married to Sarah, his wife of 18 years, who grounds him and encourages his more reserved nature. His close circle of friends is small, mostly consisting of former university colleagues who share his appreciation for intellectual pursuits like chess. He maintains professional relationships with his engineering and product teams, respected for his thoroughness, though he rarely socializes outside of work hours.

How they decide

Leonard is a highly cautious and research-heavy decision-maker. He meticulously gathers information, weighs pros and cons, and often consults established best practices or reliable sources before committing. He prefers to avoid hasty choices and will delay a decision if he feels insufficient data has been collected or understood. His process is analytical and risk-averse, aiming to minimize potential negative outcomes.

How they sound

Leonard speaks with measured cadence, his tone is generally calm and professional. He uses precise language, avoiding slang or overly casual expressions in professional contexts. He tends to pause to formulate his thoughts before speaking, ensuring accuracy. He might use terms like 'verifiably', 'adherence to protocol', or 'mitigate risk' in casual conversation, but generally sticks to standard English. He avoids hyperbole and focuses on factual reporting.

Personality traits

  • meticulous
  • diligent
  • systematic
  • reliable
  • detail-oriented
  • risk-averse
  • analytical
  • reserved
  • principled

Goals

  • Achieve a senior technical writer position with oversight of documentation strategy
  • Contribute to industry standards for fintech documentation
  • Maintain financial security and plan for a comfortable retirement
  • Develop a more robust personal knowledge base in cybersecurity for fintech
  • Complete a challenging century road bike ride by next summer

Problems & frictions

  • Balancing speed of development releases with thoroughness of documentation
  • Ensuring consistent terminology across disparate internal teams and external-facing materials
  • Dealing with legacy documentation systems that are difficult to update
  • The constant threat of compliance errors leading to significant financial penalties
  • Finding time for professional development amidst demanding project timelines

Values

  • precision
  • documentation
  • accountability
  • risk control
  • clarity
  • accuracy

Interests

  • APIs
  • personal finance
  • chess
  • road biking
  • technical documentation standards
  • data visualization

Media habits

  • Reads industry news sites (e.g., The Block, TechCrunch)
  • Follows documentation-focused subreddits and blogs
  • Listens to podcasts on finance and technology during commutes
  • Subscribes to newsletters on API best practices
  • Uses LinkedIn for professional networking and news

Questions & answers

Leonard Stokes’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Lattice (https://lattice.aryy.in): 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 tool's promise of preserving technical terms and numerical data is appealing, given my work. The description mentions a free tier with daily limits, which is a good starting point. For a no-brainer price, I'd need to see unlimited usage for my professional needs, perhaps around $15 per month. Anything significantly above $30 per month would make me reconsider, especially if I can't verify it preserves exact figures and compliance language without errors.
    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.