Greg Hackett

Why this persona fits the audience

Manages a 120-person regional distributor's Azure tenant, six Linux and Windows servers, and VPN access. Patching, backup verification, and license tracking are kept in spreadsheets, while a part-time MSP handles after-hours alerts and a helpdesk analyst logs routine tickets.

• Age: 44
• Location: Columbus, Ohio, USA
• Occupation: IT Operations Manager
• Income: $118k
• Education: B.S. in Information Systems
• Company size: Approx. 120 employees
• Years in role: 7

“You can't build a stable house on shaky foundations, and that applies to everything – from servers to spreadsheets.”

Greg Hackett, 44, has been the IT Operations Manager for a regional distributor in Columbus, Ohio, for the past seven years. His career path was fairly linear, starting with an internship during his B.S. in Information Systems at Ohio State and moving through various IT support and systems administration roles before landing his current management position. He’s responsible for a complex, albeit somewhat dated, IT environment: a significant Azure tenant supporting core business applications, six on-premises servers (a mix of Linux and Windows), and the company's VPN infrastructure. Greg is deeply committed to reliability and steady operations; his personal ethos is that IT should be invisible, working perfectly in the background. This commitment drives his meticulous, albeit manual, approach to critical tasks. Patching schedules, backup verification logs, and software license tracking are all meticulously maintained in a series of interconnected spreadsheets. He views these spreadsheets not as a failing, but as a clear, auditable record of his diligent oversight. He has a working relationship with a part-time Managed Service Provider (MSP) who handles urgent after-hours alerts, a necessary measure to ensure business continuity without the overhead of a 24/7 internal team. He also supervises a lone helpdesk analyst who logs routine tickets. Greg earns $118k annually, a salary that feels adequate but not extravagant, especially with college tuition looming for his two teenagers. He's focused on maintaining their current lifestyle while carefully managing household expenses. Financial decisions are typically conservative, prioritizing needs over wants and always with an eye towards long-term security. His recent focus has been on optimizing Azure costs and ensuring the company's compliance posture is up-to-date, a task that often requires late nights poring over documentation and reports, trying to make sense of usage patterns and licensing agreements. He recently pushed back on an informal request to 'just spin up some new servers' for a departmental project without a formal change request, prioritizing stability and his established documentation process over expediency.

Background & daily life

A day in their life

Greg's alarm goes off at 6:00 AM. After a quick coffee and checking personal emails, he might do a short ride on his stationary bike if time permits. By 7:30 AM, he's reviewing his calendar and the previous night's MSP report. The workday officially starts with a brief huddle with his helpdesk analyst to go over urgent tickets. The rest of the morning is a mix of server monitoring, responding to user requests, and meticulously updating his spreadsheets for patching, backups, and software licenses. Lunch is usually a quick sandwich at his desk while reading tech news. Afternoons involve planning for upcoming updates, vendor communications, and dealing with unexpected issues. He tries to log off by 5:30 PM to make it home for dinner with his family, but often finds himself checking emails again before bed.

Lifestyle

Greg lives in a comfortable suburban home in Westerville with his wife, Sarah, and their two kids, Emily (16) and Ben (14). Weekends often involve home improvement projects, from fixing a leaky faucet to more ambitious landscaping. He's a creature of habit during the week, preferring early mornings for a quick workout before work. Budgeting is key; he's saving for college tuition and a potential home addition. Social life is mostly centered around family and a few close friends, with occasional nights out for dinner or catching a local brewery. He finds satisfaction in tangible progress, whether it's a completed DIY project or a smoothly running IT system.

Work life

Greg's days are a constant juggle of maintaining the company's digital backbone. He spends a good chunk of time updating spreadsheets with patching schedules, license counts, and backup logs – a process he finds tedious but necessary. He interacts daily with his small internal IT team (a helpdesk analyst) and relies heavily on external support for anything outside core business hours, which he views as a necessary cost for peace of mind. The pressure to keep everything running smoothly, without major incidents, is ever-present, especially knowing how disruptive even minor outages can be. He's constantly evaluating if the current setup is sufficient or if more robust solutions are needed.

Relationships

Greg is married to Sarah, a nurse, and they function as a solid team managing household logistics and finances. His influence is primarily within his direct IT team and with department heads who rely on his services. He has a friendly but professional relationship with the owners of the part-time MSP. His children are at an age where his decisions impact their activities and future opportunities.

How they decide

Greg is a cautious and research-oriented decision-maker. He values data and evidence, preferring to gather information from multiple sources before committing to a course of action. He's not prone to impulse buys and will weigh pros and cons carefully, often sketching out flowcharts or comparison tables to visualize options. He trusts his own analysis but will sometimes solicit opinions from trusted peers in similar roles if the opportunity arises.

How they sound

Greg speaks in a clear, measured tone. He's not overly formal but avoids slang or overly casual language in professional settings. He tends to be direct and factual, preferring to stick to the technical details rather than speculating. He rarely uses hyperbole and speaks with a slight, almost imperceptible Midwestern accent. You won't hear him complain excessively, but he'll likely frame issues in terms of operational impact and risk.