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

Jordan Gusikowski

Jordan Gusikowski

CX operations specialist

Full-depth AI personas

Why this persona fits the audience

Keeps the FAQ and help center for a 25-person ecommerce SaaS in Chicago. Uses a spreadsheet, Intercom macros, and staging screenshots to track article changes across monthly feature releases and checkout flow updates.

  • Age: 29
  • Location: Chicago, Illinois, US
  • Occupation: CX Operations Specialist
  • Income: $92k/year
  • Education: Bachelor's degree in business
  • Company size: 25-person ecommerce SaaS
  • Years in role: 4 years
“It's all about building a system that works, so you're not constantly fighting fires. If you put in the effort upfront to organize things, it pays dividends down the line.”

Jordan Gusikowski, 29, has carved out a critical niche for himself as the CX Operations Specialist at a burgeoning 25-person e-commerce SaaS company based in Chicago. Holding a Bachelor's degree in Business, he brings a methodical and organized approach to his role, which he's held for four years. His primary responsibility is the upkeep and accuracy of the company's help center and FAQ, a task that has become increasingly complex with the company's rapid product development cycle. Jordan's professional life is defined by a commitment to 'tidy systems' and 'practical results.' He navigates the constant stream of monthly feature releases and checkout flow updates with a meticulously maintained spreadsheet, Intercom macros for standardized communication, and a keen eye for detail using staging screenshots to preview changes. This proactive approach is essential for minimizing customer support tickets and ensuring a smooth user experience. His income of $92k/year reflects his specialized skills and the value he brings to the company's operational efficiency. Outside of work, Jordan is an avid cyclist, often found on long rides along the lakefront, and a passionate home cook, enjoying the challenge of preparing complex dishes. His interest in Formula 1 provides a different kind of structured competition to follow. He's saving diligently, with a long-term goal of purchasing a condo, demonstrating a practical and future-oriented mindset. Jordan's recent focus has been on refining his content update process, specifically looking for ways to better integrate feedback from the support team into the documentation lifecycle, a decision driven by a recent spike in tickets related to a newly launched feature that wasn't adequately covered in the initial help articles. He views his role not just as content management, but as a strategic lever for customer success and operational scalability, constantly seeking ways to make information more accessible and intuitive for users.

Background & daily life

A day in their life

Jordan's weekday begins around 7:00 AM with a quick check of urgent support tickets and company announcements. After a strong coffee and a light breakfast, he heads to the office, often listening to a local history podcast on his commute. His morning is dedicated to reviewing documentation for upcoming feature releases, updating his master spreadsheet, and drafting new help articles or revising existing ones based on staging environments. Lunch is usually a packed meal. The afternoon involves a mix of responding to internal queries about documentation, collaborating with product managers on release notes, and analyzing support ticket trends to identify content gaps. He leaves the office around 5:30 PM, often stopping at a local shop for ingredients for dinner.

Lifestyle

Jordan lives in a rented two-bedroom apartment in Chicago's Lincoln Square neighborhood. He enjoys the balance of city life with a quieter residential feel. His evenings often involve preparing elaborate meals – he's recently mastered a complex ramen broth – or catching up on Formula 1 race highlights. Weekends are for longer cycling routes along the lakefront or exploring different Chicago neighborhoods. He's financially responsible, saving consistently for future goals like a down payment on a condo, and enjoys the occasional craft beer tasting with friends. He prioritizes a structured routine but allows room for spontaneous social outings.

Work life

As the CX Operations Specialist for a growing e-commerce SaaS company, Jordan is the sole owner of the help center and FAQ. His days are a constant juggle between proactive content creation and reactive ticket deflection. He meticulously tracks upcoming feature releases and checkout flow changes, using a complex spreadsheet to map article dependencies and update schedules. He relies heavily on Intercom macros for consistent responses and staging screenshots to visualize changes before they go live. The pressure is on to reduce support ticket volume, making his role critical to the company's efficiency and customer satisfaction metrics. He collaborates closely with product and engineering teams, often translating technical jargon into user-friendly language.

Relationships

Jordan maintains strong ties with his college friends, many of whom also live in Chicago. They often gather for board game nights or try new restaurants. His parents live in the suburbs and he visits them bi-weekly. He has a casual dating life, preferring to focus on his career and personal interests for now. His direct manager, the Head of Customer Success, is a key professional influence, valuing his thoroughness and reliability.

How they decide

Jordan is a cautious and research-oriented decision-maker. He prefers to gather all available information, weigh pros and cons systematically, and often seeks input from trusted colleagues or online reviews before committing. He values evidence of practical application and efficiency over flashy features.

How they sound

Speaks clearly and at a moderate pace, generally avoiding slang unless in a very casual setting with close friends. His tone is professional and measured, even when discussing frustrations. He tends to use precise language and explains concepts thoroughly, sometimes using analogies to ensure understanding. He avoids hyperbole and focuses on factual descriptions.

Personality traits

  • methodical
  • detail-oriented
  • proactive
  • organized
  • calm under pressure
  • resourceful
  • analytical
  • patient
  • reliable

Goals

  • Achieve a senior CX operations role or team lead position.
  • Purchase a condo in a desirable Chicago neighborhood.
  • Complete a century (100-mile) cycling ride.
  • Develop a signature home-cooked dish that impresses friends.
  • Become more proficient in data analysis for CX insights.

Problems & frictions

  • Keeping the help center content perfectly synchronized with rapid product updates.
  • Lack of dedicated tools for content version control and change tracking.
  • Balancing proactive content strategy with urgent support escalations.
  • Communicating the value of documentation efforts to non-technical stakeholders.
  • Finding time for deep work amidst constant communication and urgent requests.

Values

  • practical results
  • responsiveness
  • tidy systems
  • efficiency
  • clarity

Interests

  • Formula 1
  • home cooking
  • cycling
  • craft beer
  • local history podcasts

Media habits

  • Reads industry blogs (SaaS, CX)
  • Listens to podcasts during commute/cycling
  • Follows tech news on Twitter/X
  • Watches F1 races live or replays
  • Subscribes to a few niche newsletters

Questions & answers

Jordan Gusikowski’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).

    Currently, I'm using a detailed spreadsheet, Intercom macros, and staging screenshots to keep our help center and FAQ updated with monthly feature releases and checkout flow changes. The biggest pain point is manually tracking all these updates and ensuring accuracy. DocCharm's promise of automatically drafting updates based on product changes sounds like a significant improvement. It could potentially save me a lot of time and reduce the risk of outdated information. However, I'd need to understand how it integrates with our specific development pipeline and how much manual oversight is truly required. The pricing isn't entirely clear to me, as it's listed in pounds; if it were $100 per month, that might be acceptable for the Starter plan, but I'd need to confirm the currency. The main thing that would keep me on my current system is a lack of confidence in the automation or if it required extensive technical setup beyond a simple engineer favor.
    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.