Why this persona fits the audience
He manages security risk and third-party reviews for a 120-person healthcare software company in Chicago, and he keeps a hand-built tracker of incidents, data-breach stories, and regulator commentary for leadership updates. His research stack is mostly free tools, saved articles, and a recurring spreadsheet review each Friday.
- Age: 49
- Location: Chicago, Illinois, US
- Occupation: Security Risk Manager
- Income: $138k
- Education: MBA and BS Information Systems
- Company size: 120 employees
- Years in role: 7
“I don’t trust tools that make security look easy. And I *definitely* don’t trust people who don’t have a 'what if' folder.”
Moses Roberts learned patience the hard way: he spent the first decade of his career watching companies treat security as an afterthought, then another five years proving it was cheaper to invest than to recover. Now 49, he’s the security risk manager at a 120-person Chicago healthtech firm, where his day-to-day is a mix of firefighting and strategic nudging. His hands-on, spreadsheet-driven approach to risk means he’s built a reputation as the person who *actually* reads the fine print—but also as the one who knows which regulations *really* matter. His office is a shrine to preparedness: a whiteboard covered in deadlines, a binder of vendor assessments (color-coded by risk level), and a wall of sticky notes reminding him to follow up. He’s pushed for standardized vendor risk forms, patched his own reporting tools, and once spent a weekend re-archiving breach reports because his older system crashed. His biggest win was getting leadership to acknowledge a recurring problem with medical device firmware updates; his biggest frustration is that they still wait until the last minute to fix it. Outside of work, he’s a volunteer mentor for high schoolers interested in cybersecurity, a reluctant but dutiful father to two college-bound kids, and a cyclist who mentally invents disaster scenarios mid-commute (though his wife insists he’s *not* ready for that survivalist reality show). His life runs on watchlists, recall dates, and the quiet satisfaction of a well-organized emergency kit—because in his line of work, the only thing worse than a crisis is a preventable one.
Background & daily life
A day in their life
Moses’s alarm goes off at 5:30 AM, and he checks his phone for weather and regulatory news before rolling out of bed. If the temperature’s above freezing, he’ll bike; otherwise, he takes the Metra to Ogilvie Station. At the office, he starts with his 'red folder' of urgent items (today, a missed vendor questionnaire deadline). His 10 AM meeting with engineering is spent translating a new CMS security requirement into actionable tasks. Lunch is at his desk, where he scans headlines for breach stories that might become case studies. Post-lunch, he fields a frantic call from a sales rep whose new vendor can’t produce a SOC 2 report. By 3 PM, he’s digging into a spreadsheet full of incident dates, patch cycles, and regulatory citations—his Friday ritual. He leaves by 5:30 PM, stops at the library to return books (he’s 17 days early), and cycles home in the twilight. That evening, his kids quiz him on the ethics of AI in healthcare (he’s skeptical) while he tries to explain why he’s auditioning his old VHS tapes for the 4K upgrade.
Lifestyle
Moses lives in a three-bedroom house in Lincolnwood, where he and his wife have lived since 2005. His mornings start at 5:30 AM with a black coffee and a weather check before deciding whether to bike or train. He packs his lunch (usually a turkey wrap and baby carrots) and ties his bike helmet to his briefcase. Weekends rotate between errands, volunteering at a local tech mentorship program, and restoring his 1990s-era home theater system—he’s currently debating whether to upgrade to 4K. His teenage kids have inherited his skepticism; family debates often involve fact-checking memes. He pays bills immediately to avoid late fees and has never carried credit card debt. His social life is small but intentional: quarterly dinners with a college friend who’s now a nurse, and a monthly poker night with colleagues (he always brings printouts of cybersecurity trivia to share).
Work life
As the sole security risk manager at a mid-sized healthtech firm, Moses spends his days juggling third-party vendor assessments, internal audit responses, and leadership briefings. His office is a controlled chaos of sticky-note-covered monitors, a whiteboard with regulatory deadlines (colored by priority), and a rotating stack of 'action required' folders. He meets weekly with the engineering team to translate compliance requirements into practical fixes, then distills those into plain-language updates for executives. Fridays are sacred spreadsheet days—he reviews incident logs, patches a colleague’s spreadsheets (they always break PIVOT tables), and archives news about breaches that might become teaching moments. His biggest frustration is the fragmented nature of his tools: email for tracking, PDFs for regulations, and a homebuilt Excel dashboard that should be a database. He’s recently pushed to standardize vendor risk forms, which took six months of internal lobbying.
Relationships
Moses’ wife, a school librarian, manages the household finances and gently teases him about his 'apocalypse prep' tendencies (he still thinks she’s overconfident about their retirement savings). His kids, now 18 and 20, roll their eyes at his breach horror stories but know to ask for his advice on tech privacy. At work, he’s the go-to person for panicked 'just lost a laptop' calls, which means he’s also the one who gets coffee orders right. His poker group includes a former HIMSS colleague, two engineers, and a compliance lawyer—their group chat is 80% regulatory gossip and 20% bad puns. His biggest external influence is a former regulator he met at a HIPAA summit; they still exchange periodic 'did you see this?' emails.
How they decide
Systematic but pragmatic. He researches thoroughly (Google searches, peer networks, and back-issue regulatory digests), but if a tool’s learning curve exceeds its usefulness, he’ll abandon it. He prefers solutions that integrate with existing workflows and can be explained in a single sentence. His biggest decisions—like the vendor risk standard—are stress-tested against hypothetical audits and board questions. For personal purchases, he waits 3-6 months to see if he *actually* needs something before buying.
How they sound
Speaks in deliberate, measured cadences, with a habit of pausing before key points. Uses analogies to explain technical concepts (e.g., 'This is like locking the barn door after the horses have bolted'). Avoids jargon in meetings but drops acronyms freely with peers. Occasionally mutters phrases like 'That’s not how it works in the real world' when vendors overpromise. Prone to dry humor with a single raised eyebrow. When frustrated, he’ll say 'I have a spreadsheet for this' instead of swearing. His email signature includes his direct phone number—'just in case.'
Personality traits
- Methodically checks every data point twice before presenting it
- Writes sticky notes to himself in the margins of his morning coffee cup
- Briefly panics when a new regulation drops, then systematically organizes the response
- Develops workarounds for clunky compliance tools before complaining about them
- Uses non-technical analogies to explain security risks to non-experts (e.g., 'This is like leaving your house keys under the mat')
- Maintains a 'worst-case scenario' folder with every breach report since 2010
- Pauses before sending emails to edit them down to essentials
- Returns library books two days early
- Tries to bicycle commute 2-3 days a week, despite Chicago’s weather
- Stores his emergency kit in the trunk year-round
Goals
- Streamline the company’s security reporting into a single source of truth
- Convince leadership to budget for a dedicated GRC tool (he’s been making do with workarounds)
- Get his daughter through her first year of college without her raiding his emergency fund
- Cycle across Wisconsin’s Kettle Moraine Trail without stopping for snacks (his last attempt failed at mile 45)
- Pay off the house by 55, even if it means fewer home theater upgrades
Problems & frictions
- The company’s growing vendor list means more assessments with the same headcount
- Leadership nods at his reports but rarely acts until auditors arrive
- His homegrown tracking system is outgrowing its spreadsheets and saved links
- His daughter’s transfer to a private university is straining their college savings
- Chicago’s winter weather makes his bike commute a gamble (he’s already slipped once this year)
- He’s the only person at the company who *wants* to read HIPAA guidance documents
Values
- risk reduction
- plain language
- accountability
- precision
- preparedness
- skepticism
Interests
- healthtech
- breach reporting
- compliance frameworks
- emerging cyber threats
- urban cycling
Media habits
- listens to *Darknet Diaries* and *Risky Business* podcasts
- reads *HealthITSecurity* and *Bleeping Computer*
- follows HIPAA regulatory updates on Feedly
- writes weekly memos in simple, actionable language