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

Sherry Kuhlman

Sherry Kuhlman

Support operations manager

Full-depth AI personas

Why this persona fits the audience

Manages the public help center for a 40-person B2B SaaS company in Austin. Coordinates article updates with 4 support reps and 2 PMs, pulling from Jira tickets, release notes, and a shared Google Doc of pending edits after each product launch.

  • Age: 34
  • Location: Austin, Texas, US
  • Occupation: Support Operations Manager
  • Income: $118k/year
  • Education: Bachelor's degree in communication
  • Company size: 40
  • Years in role: 4
“The best support experience is one where the customer finds the answer themselves before they even have to ask.”

Sherry Kuhlman has carved out a niche for herself in the B2B SaaS support landscape, driven by a deep-seated belief in the power of clear, accessible information. A communication graduate from a state university, she initially gravitated towards content creation roles but found herself increasingly drawn to the operational side of managing knowledge. Her career trajectory has been marked by a steady progression, moving from technical writer to support lead, and finally into her current role as Support Operations Manager at a growing Austin-based SaaS firm. She thrives on bringing order to the chaos of product updates, seeing it as a puzzle to be solved. Her tenure of four years in this role has allowed her to deeply understand the company's product lifecycle and the intricate dependencies between engineering, product management, and customer support. She's a pragmatist, always seeking the most efficient path to a reliable outcome, which has led her to explore AI tools that promise to streamline documentation workflows. Sherry is financially responsible, prioritizing long-term stability, but she isn't afraid to invest in tools or experiences that demonstrably improve her efficiency or well-being, like her quality running shoes or subscriptions to productivity software. Her recent focus has been on automating the tedious aspects of content management, driven by the constant influx of new features and the need for her team to respond quickly to customer inquiries. She recently initiated a project to catalog all existing help articles, identifying gaps and redundancies, a task that requires meticulous attention to detail and a strategic vision for the help center's future.

Background & daily life

A day in their life

Sherry's typical weekday begins around 5:30 AM with a refreshing trail run. After showering and a quick breakfast, she’s at her desk by 8:00 AM, fueled by coffee. The first hour is dedicated to reviewing urgent tickets and team communication. The bulk of her morning is spent in cross-functional meetings with PMs discussing upcoming features and potential documentation needs, or reviewing the shared Google Doc for pending article edits. Lunch is usually a quick affair at her desk while catching up on industry newsletters. The afternoon involves coordinating with her support reps on article drafts, analyzing Jira tickets for content gaps, and working on process improvements for the help center workflow. She usually wraps up by 5:30 PM, aiming to disconnect fully for her evening routine.

Lifestyle

Sherry lives a structured but active life in Austin. She rents a comfortable one-bedroom apartment in a walkable neighborhood. Her mornings start early with a trail run at Barton Creek Greenbelt, followed by a strong cup of coffee and reviewing her meticulously planned day. Evenings are often spent trying out a new recipe, catching up on a podcast, or occasionally meeting friends at a local brewery. She's conscious about her finances, contributing regularly to savings and retirement accounts, but enjoys treating herself to good quality running gear and books. She values routine but also seeks out new experiences within her comfort zone.

Work life

Sherry's days are a constant juggle of ensuring the company's public help center is accurate and accessible. She spends significant time coordinating with Product Managers (PMs) and the support team to translate complex technical updates into user-friendly articles. Her primary tools include Jira for tracking ticket trends and feature requests, Confluence for internal documentation, and a shared Google Doc that acts as a staging ground for all pending edits. The pressure mounts after each product launch, requiring her to rapidly synthesize information from release notes and stakeholder feedback to update existing articles and create new ones. She champions streamlined processes to reduce the workload for her team.

Relationships

Sherry maintains close ties with her family, who live in a different state, communicating weekly via video calls. Her core social circle consists of a few long-time college friends in Austin, with whom she shares weekend brunches and occasional trail runs. Professionally, she relies on her PM colleagues for product insights and her support reps for direct customer feedback, valuing their input and collaborative spirit.

How they decide

Sherry is a methodical researcher. She tends to gather information from multiple sources, weigh pros and cons carefully, and often seeks input from trusted colleagues or reviews before making a significant decision, whether personal or professional. She prefers tangible evidence and clear rationale over gut feelings.

How they sound

Sherry speaks clearly and at a moderate pace. Her tone is generally calm and professional, but she can become more animated when discussing process improvements or positive customer feedback. She avoids overly casual slang but uses standard professional jargon when appropriate. She tends to be concise but will elaborate if asked for more detail, focusing on facts and logical progression. She doesn't typically use hyperbole.

Personality traits

  • Methodical
  • Diligent
  • Organized
  • Collaborative
  • Detail-oriented
  • Proactive
  • Patient
  • Reliable
  • Analytical

Goals

  • Implement a more automated system for help center content updates
  • Mentor junior support team members in documentation best practices
  • Achieve a better work-life balance without sacrificing team performance
  • Complete a half-marathon next spring
  • Develop a comprehensive knowledge base strategy for future product expansion

Problems & frictions

  • The current process for updating help center articles is highly manual and time-consuming, especially post-launch.
  • Ensuring consistent tone and accuracy across all articles written by different contributors is a challenge.
  • Managing competing priorities from Product and Support teams regarding content updates.
  • Keeping up with the rapid pace of product development means documentation often lags slightly behind.
  • Finding and vetting new tools that can genuinely improve efficiency without adding complexity.

Values

  • operational clarity
  • customer responsiveness
  • steady team routines
  • knowledge sharing
  • efficiency

Interests

  • process design
  • trail running
  • AI workflow tools
  • local craft breweries
  • podcasts on productivity

Media habits

  • Listens to NPR and productivity podcasts during commute
  • Reads industry blogs and newsletters (e.g., SupportOps Weekly)
  • Uses LinkedIn for professional networking and news
  • Occasionally browses Reddit for tech tips and community discussions
  • Follows AI and SaaS news outlets

Questions & answers

Sherry Kuhlman’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of DocCharm (https://doccharm.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make DocCharm 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).

    Right now, we manually update our help center articles. We use Jira tickets and a shared Google Doc to track changes, which is very time-consuming, especially after product launches. DocCharm sounds promising because it seems to automate the initial draft creation, which would save us a lot of manual effort. The biggest concern would be ensuring the AI-generated content is accurate and aligns with our brand voice without significant editing. Also, understanding how well it integrates with our existing Jira workflow would be key. If it truly streamlines the process and maintains quality, I could see paying around $150 per month for it.
    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.