Why this persona fits the audience
He is the only in-house IT person at a 60-person manufacturer and handles routine website admin tasks when requested, including updating browser icons for the corporate site and regional microsites.
- Age: 45
- Location: Cologne, Germany
- Occupation: IT administrator
- Income: €58,000/year
- Education: Diplom in Business Informatics
- Company size: 60 employees
- Years in role: 8
“A system that requires constant attention is just a broken system waiting to happen.”
Henry Burger, 45, has spent the better part of two decades navigating the intersection of traditional manufacturing and modern digital infrastructure in Cologne. Holding a Diplom in Business Informatics, he entered the workforce just as the Y2K panic was subsiding, a formative experience that instilled in him a lifelong reverence for stability and redundancy. For the last eight years, he has been the solitary guardian of IT operations for a 60-person steel component manufacturer. His world is defined by the tension between rigid, aging industrial machinery and the relentless pace of web evolution. While the marketing department occasionally demands flashy updates, such as custom favicons for microsites targeting specific regions, Henry approaches these tasks with the same meticulous caution he applies to server migrations. He views the internet not as a playground, but as a fragile extension of the factory floor that must be kept clean, documented, and secure. Living in Rodenkirchen with his wife and two teenagers, Henry's life outside work is a counterbalance to his professional rigidity; he finds solace in mechanical repairs and organizing his home network, hobbies that mirror his professional need for order. Despite a comfortable income of €58,000, he remains financially cautious, investing heavily in emergency savings rather than luxury goods. His recent decisions have focused on reducing reliance on external vendors, opting instead to build internal scripts for routine tasks. He is a man who believes that if something can be automated or standardized, it should be, because human error is the only variable he cannot afford to tolerate.
Background & daily life
A day in their life
Henry wakes up at 6:00 AM, immediately checking the overnight server logs on his phone to ensure no critical failures occurred during the night. After a quick breakfast with his family, he cycles to the office in Cologne, listening to a podcast on industrial automation. Upon arrival, he spends the first hour reviewing emails and responding to ticket queues, prioritizing any hardware alerts. By mid-morning, he is deep in code or configuration files, working on a migration script for the internal database. Around noon, he meets briefly with the HR manager to resolve a printer issue for a new hire. The afternoon is often consumed by ad-hoc requests, such as the marketing team needing a favicon updated for a new regional campaign. He spends the last hour documenting the day's changes and ensuring all backups are verified before leaving at 5:30 PM, making sure the office lights and HVAC are set for the night.
Lifestyle
Henry lives a structured life in the affluent suburb of Rodenkirchen, balancing his role as the primary breadwinner with family responsibilities. His weekends are dedicated to home maintenance projects, often involving the repair of old furniture or optimizing his home network. He avoids chaotic social scenes, preferring quiet evenings with his wife, where they discuss budget planning or watch documentaries about German engineering. Health-wise, he prioritizes regular cycling to work when the weather permits, viewing it as essential stress relief rather than exercise for vanity. Financially, he is conservative; every expense is tracked in a spreadsheet, and he resists impulse buys unless there is a clear long-term utility. His social circle consists largely of colleagues from his university days and neighbors who share similar interests in practical hobbies.
Work life
As the sole IT administrator for a mid-sized manufacturing firm in Cologne, Henry wears many hats, ranging from server maintenance to user support. The company relies heavily on legacy ERP systems that require constant vigilance. When marketing requests arise, such as updating browser icons for the corporate site or regional microsites, Henry treats them as minor but necessary deviations from his core infrastructure duties. He prefers using internal scripts over third-party web tools to maintain control. His workspace is organized with multiple monitors displaying monitoring dashboards, and he keeps a physical notebook for password resets and change logs. The pressure comes not from deadlines, but from the fear of a single point of failure disrupting production lines.
Relationships
Henry is deeply connected to his immediate family, relying on his wife's organizational skills to manage household logistics. He maintains a tight-knit group of three close friends from university, mostly meeting monthly for dinner to discuss career stability and local politics. Professionally, he has a respectful but distant relationship with the CEO, who views him as a 'fixer' rather than a strategic partner. He rarely seeks external advice, preferring to solve problems independently before escalating issues. His influence within the company is high among technical peers but limited in executive decision-making circles.
How they decide
Henry employs a highly analytical and risk-averse decision-making process. He rarely makes impulsive choices, preferring to gather extensive data, read documentation, and simulate outcomes before acting. If a new tool is proposed, he will test it in a sandbox environment first, checking for compatibility with existing workflows and security implications. He values peer reviews and official certifications over marketing claims. His decisions are driven by long-term stability and the minimization of future maintenance burdens rather than short-term gains or novelty.
How they sound
Henry speaks in a measured, low-volume tone typical of the Rhineland, avoiding slang and overly enthusiastic language. He uses precise terminology and often pauses to consider the exact wording of a sentence. He tends to avoid absolutes like 'always' or 'never,' preferring qualifiers like 'typically' or 'under normal conditions.' In conversation, he focuses on facts and procedures rather than emotions or speculation. He rarely interrupts others and often nods slowly while processing information before responding.
Personality traits
- meticulous
- reserved
- pragmatic
- methodical
- reliable
- cautious
- detail-oriented
- independent
- calm under pressure
- process-driven
Goals
- Automate 80% of routine helpdesk tickets within the next fiscal year
- Migrate the company's file storage to a more secure, local private cloud solution
- Complete a certification in industrial cybersecurity protocols
- Reduce server downtime to less than 0.01% annually
- Create a comprehensive documentation library for all legacy systems
- Secure a promotion to Senior IT Manager by age 50
Problems & frictions
- Legacy hardware failing faster than replacement budgets allow
- Marketing department requesting frequent, non-standard website changes that break standardization
- Lack of time to document complex internal tools due to urgent troubleshooting
- Difficulty finding reliable vendors for specialized industrial IT components
- Balancing security compliance requirements with user convenience
- Managing expectations of non-technical staff regarding IT capabilities
Values
- stability
- documented processes
- low-maintenance systems
- predictability
- efficiency
Interests
- internal tools
- site administration
- IT support
- mechanical keyboards
- home automation
- regional history
Media habits
- German tech blogs (e.g., Heise Online) for updates
- Reddit r/sysadmin and r/ITSupport for troubleshooting
- Local news apps for Cologne traffic and weather
- YouTube tutorials on legacy system maintenance
- LinkedIn for professional networking
- Printed manuals for software installation