Why this persona fits the audience
She oversees a patient-facing CMS and a 4-person content operations team at a regional healthcare network. The stack includes a legacy CMS with custom integrations, weekly release windows, and a separate search layer used for location, physician and service pages; the team already licenses Coveo for site search and tracks content changes in Jira.
- Age: 38
- Location: Boston, MA, US
- Occupation: Web content operations lead
- Income: $112k
- Education: BA in Communications
- Company size: 500-1,000 employees
- Years in role: 6
“In healthcare, a typo isn't just an annoyance; it's a barrier to someone getting the help they need right now.”
Alice Conn has spent the better part of her career bridging the gap between the rigid world of healthcare administration and the fluid nature of digital user experience. Born in Connecticut and raised in a family that valued education and service, she earned her BA in Communications from Boston University before diving into the digital landscape of the early 2010s. Her journey took her from freelance web design to corporate marketing, eventually landing her at the New England Regional Healthcare Network six years ago. There, she found herself thrust into the role of Web Content Operations Lead, a position that demanded she master both the technical intricacies of a decades-old Content Management System and the nuanced compliance requirements of the medical field. Her current reality is defined by a paradox: she must modernize the patient experience while keeping a legacy system running smoothly enough to handle millions of annual visits. Alice leads a small but mighty team of four, tasked with ensuring that every piece of information—from a surgeon's bio to the hours of a rural satellite clinic—is accurate, accessible, and compliant. She operates within a strict weekly release cycle, a rhythm that dictates the pace of her entire department. Every Friday afternoon is a high-stakes audit session where she personally verifies that no broken links or outdated insurance codes have slipped through. Despite the pressures, Alice is deeply committed to the mission of improving patient access. She views her role not just as a manager of text and images, but as a guardian of trust. When a new doctor joins the network, Alice ensures their profile reflects their actual specialties and availability, knowing that a mismatch could delay a patient's diagnosis. She navigates the tension between the desire for instant updates from clinical staff and the necessity of rigorous quality assurance, often acting as the buffer that protects the integrity of the public-facing site. With a steady hand and a strategic mind, she continues to push for gradual improvements, believing that stability is the foundation upon which true innovation is built.
Background & daily life
A day in their life
Alice wakes up at 5:30 AM for a quiet run before the house stirs, using this time to mentally prepare for the day's complexities. By 7:00 AM, she's navigating the breakfast rush, packing lunches, and ensuring her kids are ready for school. At 8:15 AM, she arrives at the regional healthcare network, immediately checking the overnight server logs and reviewing the daily Jira queue for urgent content fixes. Her morning is dominated by stand-up meetings with her four direct reports, where she reviews the status of upcoming release candidates and addresses any blockers. Lunch is often eaten at her desk while scanning industry news or drafting governance policies. Afternoon hours are spent in cross-departmental meetings with clinical leadership, translating their needs into technical requirements. She spends the last hour of her day finalizing the weekly release checklist, double-checking every link and phone number. By 5:30 PM, she heads home, mentally transitioning from the high-stakes environment of healthcare IT to the warmth of family life, often stopping for groceries on the way.
Lifestyle
Alice lives in a bustling household where order is the antidote to chaos. Her evenings are split between managing homework for her two energetic children and maintaining her marathon training schedule, which serves as her primary stress reliever. Financially, she is prudent but not stingy; she prioritizes paying off student loans early while saving aggressively for her children's college funds. She enjoys hosting small dinner parties where conversation flows easily, often focusing on local community issues or travel plans. Her weekends involve visiting historic Boston neighborhoods, hiking in the Blue Hills, and occasionally volunteering with a local literacy nonprofit. Money is managed through automated savings and spreadsheets, reflecting her need for control over her financial future.
Work life
Alice's day is a delicate balancing act of technical maintenance and human coordination. She manages a legacy CMS that requires constant patching to avoid breaking critical patient information links, all while coordinating a four-person team responsible for updating physician profiles and service locations. Her workdays revolve around rigid weekly release windows, demanding absolute precision in testing before any content goes live. She spends significant time in Jira tracking tickets and mediating between clinical staff who want immediate updates and IT security protocols that slow them down. The pressure is constant: a wrong phone number or outdated clinic hours can directly impact patient care, making her role one of high stakes and meticulous oversight.
Relationships
Alice relies heavily on her husband, Mark, for emotional grounding and domestic logistics, creating a strong partnership based on mutual respect for each other's professional demands. Her circle includes a tight-knit group of fellow healthcare tech leaders in Boston, with whom she shares frustrations and strategies over coffee. She maintains close ties with her parents in Worcester, who provide childcare support when needed. Her influence stems less from charisma and more from her reputation as a reliable problem-solver; people trust her judgment because she consistently delivers accurate, compliant results. She values deep, long-term friendships over broad social networks.
How they decide
Alice is a deliberate, evidence-based decision-maker who rarely acts on impulse. She approaches choices by gathering data, consulting stakeholders, and mapping out potential risks against benefits. Peer recommendations carry weight, but only if backed by case studies or proven success metrics. She prefers incremental changes that can be rolled back if things go wrong, avoiding 'big bang' implementations unless absolutely necessary. Her process involves extensive documentation and clear communication to ensure alignment across her team and leadership.
How they sound
Alice speaks with a measured, articulate cadence typical of someone accustomed to explaining complex systems to non-technical audiences. She avoids jargon when possible, preferring plain English to ensure clarity, though she naturally slips into specific technical terms like 'API endpoint' or 'taxonomy structure' when speaking with peers. Her tone is generally calm and professional, even when discussing urgent issues, but she can become firm and directive when compliance or accuracy is at stake. She rarely uses slang or hyperbole, favoring precise verbs and clear constraints. In conversation, she asks clarifying questions to ensure she fully understands the context before offering an opinion.
Personality traits
- Meticulous
- Diplomatic
- Process-oriented
- Patient advocacy-focused
- Calm under pressure
- Detail-obsessed
- Collaborative leader
- Pragmatic problem-solver
- Time-conscious
- Ethically grounded
Goals
- Achieve full HIPAA compliance across all digital touchpoints without operational friction
- Implement a unified search experience that reduces patient call volume by 15%
- Mentor junior team members into senior roles within the next three years
- Complete a half-marathon in under 2 hours and 15 minutes
- Secure funding for a comprehensive CMS migration pilot project
- Establish a robust content governance framework that scales with network growth
Problems & frictions
- Legacy system dependencies causing unpredictable downtime during peak traffic
- Discrepancies between internal provider data and public website listings
- Difficulty integrating real-time availability data from disparate EMR systems
- Limited budget approval cycles delaying necessary infrastructure upgrades
- High turnover rate among entry-level content coordinators
- Balancing rapid content requests from clinicians with strict QA requirements
Values
- patient access
- accuracy
- compliance
- teamwork
- operational stability
- clarity
Interests
- CMS architecture
- analytics
- content governance
- UX writing
- historical preservation
- marathon training
Media habits
- Healthcare IT newsletters (HIMSS, eHealth Times)
- NPR's 'Up First' during morning commute
- Slack communities for CMS administrators
- LinkedIn articles on digital transformation in healthcare
- Podcasts on organizational psychology
- Local Boston food and culture blogs