Why this persona fits the audience
Manages a 5-person support operations team at a healthtech company, where routine case updates, ticket lookups, and customer-status calls are still handled through a mix of spreadsheets, shared docs, and manual API calls. Maintains the internal API reference and checks each automated step before it goes live.
- Age: 41
- Location: Chicago, IL, US
- Occupation: Support operations manager
- Income: $112,000
- Education: Bachelor's degree in business administration
- Company size: 150 employees
- Years in role: 4
“If you can't explain exactly how the data flows from A to B, you don't have a process; you just have a hope that nothing breaks.”
Jeanette Herman, 41, is a Support Operations Manager at a Chicago-based healthtech firm, a role she has held for four years after climbing the ladder from a senior coordinator position. With a Bachelor's in Business Administration, she brings a unique blend of administrative rigor and technical curiosity to her leadership style. Her career is defined by a relentless pursuit of accuracy in an industry where margin for error is virtually non-existent. Currently, she manages a lean team of five, overseeing the intricate machinery of customer support that handles sensitive patient data. Despite the modernization efforts of her company, Jeanette finds herself entrenched in a hybrid workflow where critical tasks—case updates, ticket lookups, and status verification—are still executed via a patchwork of Google Sheets, shared documents, and manual API calls. This reliance on legacy methods creates a persistent tension in her daily life; she knows the system is fragile, yet the cost and complexity of replacing it remain daunting. As the custodian of their internal API reference, she personally inspects every automated step before it goes live, a responsibility that consumes hours of her day. Her value system is anchored in accountability and process; she believes that robust systems are built on meticulous documentation, not magic. While she is open to new technologies, her threshold for adoption is high, driven by a fear of disrupting the delicate balance of patient support. Jeanette navigates her world with a calm demeanor, masking the stress of potential failures with a facade of total control. She is a mother of two and a wife, balancing the demands of a high-responsibility job with a structured home life. Her recent decisions have focused on tightening documentation protocols and training her team to spot anomalies in spreadsheet data, buying time until a more sustainable solution can be implemented.
Background & daily life
A day in their life
Jeanette wakes up at 5:45 AM to a quiet house, starting her day with a 30-minute run along the lakefront path before the city gets loud. By 7:15 AM, she's brewing coffee and reviewing overnight Slack notifications, scanning for critical alerts while her children get ready for school. At 8:30 AM, she arrives at the office, immediately diving into a daily stand-up where she clarifies priorities for her five direct reports. Her morning is consumed by a frantic review of a new API integration script submitted by a developer, tracing every parameter to ensure it aligns with their internal OpenAPI spec. Lunch is often eaten at her desk while she compiles a status report for leadership, highlighting discrepancies found in yesterday's manual ticket audits. Afternoon hours involve one-on-one coaching sessions and troubleshooting a stalled customer escalation that requires a manual database lookup. She leaves the office by 6:00 PM sharp, driving home to help with homework, cook dinner, and spend quality time with her family before bed, ensuring her mind is off work by 9:30 PM.
Lifestyle
Jeanette lives in a quiet, well-maintained bungalow in Chicago's Lincoln Park, a neighborhood that balances urban convenience with family-friendly stability. Her weekends are structured around her husband's coaching schedule and her children's extracurriculars, leaving little room for spontaneity. She prioritizes financial security, maintaining a strict budget that allocates funds for college savings and emergency reserves rather than luxury experiences. Health is a constant priority; she runs three times a week and meal-preps on Sundays to ensure nutritious dinners during chaotic workweeks. Socially, she prefers small gatherings with close friends over large parties, valuing deep conversation about career challenges and family life over casual networking events.
Work life
As the sole manager of a five-person support operations team at a mid-sized healthtech firm, Jeanette's day is a high-stakes balancing act between people management and technical oversight. Her primary reality involves wrestling with legacy workflows: manually cross-referencing patient status updates across disparate spreadsheets and executing API calls by hand to verify ticket resolution. She acts as the final gatekeeper for any automation, meticulously reviewing code snippets and API endpoints before they reach production. The pressure is immense, not because of aggressive sales targets, but because a single data error could impact patient care delivery. She spends her mornings in stand-ups and her afternoons debugging process bottlenecks, constantly seeking ways to reduce human error without introducing new points of failure.
Relationships
Jeanette relies heavily on her husband, who works in civil engineering, for emotional grounding and logistical support. Her closest confidants are two colleagues from previous jobs whom she meets for coffee once a month to vent about industry frustrations. She has a strong relationship with her parents, who live nearby, often calling them weekly to discuss family matters. In her professional circle, she is respected for her reliability but sometimes viewed as overly cautious by more aggressive peers. Her influence stems from her ability to consistently deliver error-free results, making her a trusted voice in departmental strategy meetings.
How they decide
Jeanette operates with a 'verify twice, deploy once' philosophy. She is not impulsive and rarely adopts a new tool based on marketing hype or peer recommendation alone. Her decision-making is deeply research-heavy, requiring her to understand the underlying mechanics, security protocols, and integration capabilities of any proposed solution. She seeks validation through pilot programs and detailed documentation reviews before committing resources. If a tool lacks transparent guardrails or requires significant infrastructure changes, she will likely reject it regardless of its feature set. Peer consensus matters, but only if the consensus is backed by hard data and proven reliability.
How they sound
Jeanette speaks with a measured, Midwestern cadence that is direct but never rude. She avoids slang and hyperbole, preferring precise terminology like 'latency,' 'edge cases,' and 'audit trails.' Her sentences are complete and grammatically sound, reflecting her background in business administration. She rarely uses filler words like 'um' or 'like,' instead pausing briefly to gather her thoughts. She tends to ask clarifying questions repeatedly to ensure mutual understanding before moving forward. When discussing work, she uses phrases like 'let's validate this' or 'we need to document the logic.' She avoids emotional language unless necessary to highlight a risk, and she is careful not to make absolute promises without data to back them up.
Personality traits
- meticulous
- methodical
- reliable
- pragmatic
- calm under pressure
- detail-oriented
- systematic
- protective of data integrity
- collaborative but firm
- risk-averse regarding unverified tools
Goals
- Eliminate all manual data entry from the support workflow by Q4
- Achieve a 100% audit-ready status for all customer interaction logs
- Mentor two junior team members into senior operational roles within 18 months
- Reduce average ticket resolution time by 15% through better tooling
- Maintain a personal work-life boundary to prevent burnout
Problems & frictions
- The fragility of relying on multiple static spreadsheets for real-time data
- Time lost verifying API responses manually before deployment
- Difficulty tracking version control changes across shared documentation
- High cognitive load required to maintain context across disjointed tools
- Risk of human error when aggregating data from multiple sources
- Lack of clear visibility into why specific automated steps fail intermittently
Values
- accuracy
- accountability
- process
- stability
- transparency
Interests
- customer operations
- spreadsheets
- process documentation
- project management methodologies
- data visualization
Media habits
- Morning industry newsletters on healthcare compliance
- LinkedIn groups for operations leaders
- Podcasts on efficiency and workflow automation
- Evening reading of non-fiction business books
- Weekend browsing of niche tech forums