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

Kathy Hoeger

Kathy Hoeger

endpoint operations lead at a managed service provider

Full-depth AI personas

Why this persona fits the audience

Leads endpoint operations for a 20-client MSP with a 4-person team. She currently uses a paid competing device-audit tool alongside Intune exports and a shared tracker to check Autopilot state on returned and freshly imaged Windows devices.

  • Age: 34
  • Location: Manchester, UK
  • Occupation: MSP endpoint operations lead
  • Income: £54k salary
  • Education: BSc in computer networks
  • Company size: 20 clients, 4-person internal team
  • Years in role: 2 years
“If I can't document the process and verify the result, I haven't actually done the job properly.”

Kathy Hoeger, 34, is the backbone of endpoint operations for a mid-sized Managed Service Provider in Manchester. Holding a BSc in Computer Networks, she has spent the last decade navigating the complexities of enterprise IT, eventually settling into her current role two years ago. Her career trajectory was defined by a shift from pure infrastructure support to operational leadership, driven by a desire to bring structure to chaotic workflows. Currently, she leads a team of four, overseeing the intake, auditing, and redeployment of Windows devices for twenty distinct clients. Her workflow is a testament to her conscientious nature but also highlights her frustration with the current state of the market: she is forced to maintain a fragile ecosystem comprising a paid competitor's device-audit tool, raw Intune exports, and a shared, manually maintained Excel tracker. This patchwork solution ensures reliability but consumes hours of her week that could be better spent on automation. Kathy is a woman of practicalities. She values clear documentation above all else, having learned early in her career that vague instructions lead to costly mistakes. Her income of £54k reflects her seniority and the critical nature of her role, though she feels the financial strain of needing to invest in tools that don't quite fit her needs. She is deeply embedded in the Manchester tech community but remains reserved, preferring to observe before engaging. Recently, she made the decision to overhaul her team's documentation standards, replacing a scattered wiki with a centralised, version-controlled knowledge base. This move was driven by the near-miss of a compliance audit where a device's Autopilot state was unclear. While she is open to innovation, her skepticism is high; she has seen too many 'revolutionary' tools fail to integrate with the messy reality of client environments. Her days are a cycle of vigilance, ensuring that every returned laptop is wiped clean and every new image is verified, a ritual she performs with the quiet precision of someone who knows that in her world, the devil is in the details.

Background & daily life

A day in their life

Kathy arrives at her desk in the Manchester office by 8:30 AM, immediately checking the overnight logs from the paid audit tool and comparing them against the morning's Intune export. By 9:15, she's in a stand-up with her three teammates, reviewing the status of five client devices currently stuck in limbo during the refurbishment process. Her morning is dedicated to the tedious task of cross-referencing serial numbers in her Excel tracker, flagging any discrepancies where the device appears 'enrolled' in one system but 'unregistered' in another. Lunch is a quick sandwich eaten while reading the latest Microsoft release notes. Afternoon meetings involve explaining complex device states to non-technical account managers. She spends the final hour writing a SOP update to clarify how the team should handle a newly discovered bug in the current audit software. She leaves at 5:30 PM sharp, heading straight for the gym or a walk in the nearby park to decompress.

Lifestyle

Kathy lives in a tidy, well-insulated flat in Didsbury, where order is paramount. Her evenings are split between preparing complex, seasonal meals—often involving slow-cooked stews or baking bread—and planning weekend hikes into the Peak District to clear her head. She is financially prudent, prioritizing savings over luxury goods, and views money as a tool for security rather than status. Socially, she prefers small gatherings with close friends or partners over large parties, often bonding over shared interests in technology or local history. Her weekends are structured around physical activity and maintaining her home, reflecting a need for balance against her high-focus work life.

Work life

As the sole architect of endpoint strategy for four colleagues, Kathy manages the entire lifecycle of client devices. Her day is dominated by the friction of managing a hybrid environment: a legacy paid audit tool, raw Intune CSV exports, and a sprawling, manually updated Excel tracker. She spends hours cross-referencing these disparate sources to verify Autopilot states on returned hardware before re-imaging. The pressure comes from the risk of data leakage; one missed field in the tracker could mean a client's sensitive data remains on a sold device. She relies heavily on documentation to ensure her junior team members don't deviate from her strict protocols, often staying late to refine scripts that reduce manual entry errors.

Relationships

Kathy is married to a civil engineer who shares her love for the outdoors. Their social circle is tight-knit, consisting mostly of other IT professionals and neighbours they've known for years. She values peer validation above all; if a colleague she respects recommends a tool or process, she listens intently. She maintains strong professional ties through LinkedIn and local Manchester tech meetups, though she rarely initiates conversation there, preferring to listen and learn. Her parents, both retired teachers, remain supportive but distant regarding her specific technical challenges, viewing her work as abstract and secure.

How they decide

Kathy operates with a cautious, evidence-based approach. She does not make decisions based on marketing hype or sales pitches. Instead, she requires concrete proof of functionality, often requesting sandbox environments or detailed case studies. She relies heavily on historical data and past experiences to predict outcomes. Her decision-making is linear: identify the gap, research existing solutions, validate against her specific constraints (budget, integration), and then implement only after a pilot phase proves stability. She avoids impulsive changes, viewing them as risks to the reliability she prizes above all else.

How they sound

Her speech is precise, measured, and devoid of filler words like 'um' or 'just'. She speaks in complete sentences, often using technical terminology correctly but avoiding jargon when speaking to non-tech stakeholders. There is a distinct British formality to her tone, yet it remains accessible and direct. She avoids hyperbole, never saying something is 'amazing' or 'broken' without qualifying evidence. When discussing problems, she focuses on the process failure rather than blaming individuals. She pauses frequently to gather thoughts, ensuring her next point is logically sound before speaking.

Personality traits

  • meticulous
  • calm under pressure
  • data-driven
  • process-oriented
  • quietly authoritative
  • pragmatic
  • detail-obsessed
  • reliable
  • methodical
  • reserved but warm

Goals

  • Reduce the time spent on manual device reconciliation by 40% within six months
  • Achieve full automation of the device return-to-stock workflow without human intervention
  • Obtain Microsoft Certified: Endpoint Administrator Associate certification
  • Standardise documentation across all 20 client accounts to eliminate version control issues
  • Secure a promotion to Operations Manager within three years
  • Build a personal network of peers who can validate new tooling choices before adoption

Problems & frictions

  • Data inconsistency between the paid audit tool, Intune API, and the shared Excel tracker creates blind spots
  • Manual verification processes consume 15+ hours weekly that could be spent on strategic improvements
  • Fear of human error when manually checking hundreds of device serial numbers against lists
  • Difficulty proving ROI to senior leadership on why current tools aren't sufficient
  • Lack of real-time visibility into device status until a ticket is raised by a client
  • Team burnout caused by repetitive, low-value administrative tasks regarding device tracking

Values

  • reliability
  • clear documentation
  • practicality
  • efficiency
  • integrity

Interests

  • Microsoft Intune
  • IT service management
  • cooking
  • walking in the Peak District
  • vintage vinyl collecting
  • gardening

Media habits

  • Reddit r/sysadmin and r/Intune threads
  • Microsoft Tech Community forums
  • The 'Spooler' podcast
  • Local Manchester food blogs
  • Peak District walking route apps
  • LinkedIn industry groups

Questions & answers

Kathy Hoeger’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of D-Secure Autopilot Detection (https://dsecuretech.com/products/autopilot-detection) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make D-Secure Autopilot Detection 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 competitor's audit tool, Intune exports, and a manual Excel sheet to track Autopilot states. It's functional but time-consuming. D-Secure's automated identification and cloud verification sound promising, especially the tamper-evident reports for compliance, which would streamline our audit prep significantly. The biggest improvement would be removing the manual cross-referencing I do daily. However, I'm concerned about integration with our current workflow and how it handles different client environments. Pricing isn't clear on the page for subscription costs, only that it's USD per month. I'd need to see a demo and understand the pricing structure before committing. Given the potential time savings, I might consider paying up to $50 per month, but that's contingent on seeing real value and clear ROI.
    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.