Why this persona fits the audience
He oversees 14 mixed Android devices at a London design agency. The team currently relies on free Android privacy settings, a shared spreadsheet, and occasional MDM reports to note when apps access the camera or microphone during working hours.
- Age: 39
- Location: London, UK
- Occupation: IT operations manager
- Income: £68,000
- Education: Bachelor's degree in information systems
- Company size: Small creative agency (approx. 45 employees)
- Years in role: 4
“I don't mind the work, I just hate the guesswork. You can't manage what you can't see, and right now, half my day is spent guessing what's happening on these phones.”
Ryan Keeling has spent the last fifteen years navigating the shifting tides of IT infrastructure, moving from general helpdesk roles to specialized operations management. At 39, he stands at the intersection of rigid corporate security requirements and the chaotic, fluid nature of a creative design agency. His Bachelor's degree in Information Systems provided a solid foundation, but his true expertise lies in the gritty reality of maintaining hardware and software ecosystems that were never designed to play nicely together. Currently, he serves as the IT operations manager for a mid-sized London design firm, where he is tasked with securing 14 disparate Android devices used by a team of artists who value freedom over protocol. His current operational model is a patchwork of goodwill and outdated methods. Without a dedicated budget for premium enterprise management, Ryan relies on the built-in privacy indicators of Android, a Google Sheet that tracks sensor usage via manual entry, and sporadic exports from a basic Mobile Device Management (MDM) tool. This approach works in theory but fails in practice; the manual tracking is prone to error, the free settings offer no historical context, and the MDM reports are too coarse-grained to detect subtle, background activity. Consequently, Ryan spends a disproportionate amount of his week chasing ghosts—trying to reconstruct timelines of camera or microphone access after the fact to satisfy client confidentiality agreements. Despite the friction, Ryan remains steadfast. He is a man who believes in simple, robust processes and takes genuine pride in keeping the lights on. He is not resistant to technology but is deeply skeptical of solutions that add complexity without solving core problems. His recent decision to audit every single device manually suggests a growing awareness that the current gap between 'available data' and 'actual visibility' is becoming a liability. He is looking for a way to automate the verification of sensor usage, not to spy on his team, but to provide them with undeniable proof of their own digital hygiene. For Ryan, the goal isn't just security; it's clarity.
Background & daily life
A day in their life
Ryan wakes at 6:30 AM, checks the weather and his commute updates before waking his family. After dropping the kids at school, he heads to the office in Shoreditch, grabbing a flat white along the way. His morning begins with a review of overnight server logs and a quick check of the agency's shared status spreadsheet. By 10:00 AM, he is deep in a meeting with the creative director, defending why a new app installation request needs a security audit. Lunch is a solitary affair while he reads tech threads on his phone. The afternoon is consumed by manual log reconciliation; he spends an hour cross-referencing timestamps from different devices against the team's activity logs, frustrated by gaps in the data. He leaves around 6:00 PM, stopping for groceries, and spends the evening helping his children with homework before finally unwinding with some coding projects at home.
Lifestyle
Ryan lives in a renovated Victorian terrace in Dalston, balancing a busy career with family life. His evenings are often dedicated to his two young children and household chores, though he finds solace in tinkering with home automation scripts on his Raspberry Pi server. He is financially prudent, avoiding unnecessary subscriptions but willing to invest in tools that save time or secure assets. Socially, he maintains a tight circle of colleagues and university friends, preferring low-key dinners over loud clubs. He prioritizes health through cycling on weekends and tries to maintain a strict separation between work emails and personal time, though this boundary is frequently tested by the nature of his role.
Work life
As the sole IT operations manager at a bustling design agency, Ryan manages a fragmented landscape of 14 mixed Android devices used by creatives who refuse standard corporate restrictions. His day is a constant juggling act: troubleshooting connection issues before meetings, manually updating spreadsheets to track which designer accessed their camera during a client call, and generating ad-hoc MDM reports to prove compliance. He faces pressure from non-technical designers who view security protocols as obstacles to creativity, yet he must ensure uptime and accountability. The lack of a unified logging system means he spends significant hours cross-referencing logs and asking staff to self-report device usage, creating a workflow that feels archaic and prone to human error.
Relationships
Ryan is married to Sarah, a graphic designer who understands the unique pressures of his job. They have two children, aged five and three, who keep him grounded outside of work. His primary professional influence comes from a mentorship group of senior sysadmins in London, where they exchange war stories about legacy systems and mobile chaos. He trusts peer recommendations over marketing materials and values the opinions of his direct reports, who rely on him to be the steady hand that keeps their digital workspace functional.
How they decide
Ryan approaches decisions with cautious pragmatism. He rarely acts impulsively and prefers to gather evidence, test solutions in a sandbox, and consult with trusted peers before committing resources. He evaluates options based on long-term reliability and ease of maintenance rather than flashy features. If a solution requires complex setup or ongoing subscription fees without clear ROI, he will likely reject it regardless of its popularity. He needs to see concrete proof of efficacy before changing established workflows.
How they sound
Ryan speaks in a calm, measured British tone, using precise terminology but avoiding unnecessary jargon when explaining things to non-technical staff. He tends to use phrases like 'let's verify,' 'that's not scalable,' or 'we need to close the loop.' He avoids emotional outbursts, even when frustrated, preferring to state facts objectively. In casual conversation, he might drop into dry humor about the absurdity of modern software, but generally maintains a professional demeanor. He dislikes hyperbole and vague promises, often pausing to ask clarifying questions before responding.
Personality traits
- Methodical
- Pragmatic
- Quietly authoritative
- Detail-oriented
- Frustrated by inefficiency
- Protective of data
- Systematic
- Low-drama
- Resourceful
- Process-driven
Goals
- Implement a fully automated audit trail for all device sensors within the next fiscal quarter
- Reduce daily administrative overhead by at least 30% through better tooling
- Achieve zero downtime during critical client pitch weeks
- Mentor junior staff members to take ownership of basic device troubleshooting
- Secure a formal certification in mobile enterprise security
- Transition the agency to a more unified OS environment without disrupting creative workflows
Problems & frictions
- Reliance on manual spreadsheet tracking leads to inconsistent data and missed entries
- Designers frequently bypass privacy settings, making it impossible to know if background apps are active
- Lack of real-time alerts means security incidents are only discovered after the fact
- Fragmented device models create compatibility issues with current free monitoring tools
- Difficulty proving exactly when a camera or mic was accessed to satisfy client NDAs
- Time-consuming reconciliation of MDM reports against actual user behavior logs
Values
- uptime
- simple processes
- team support
- accountability
- data integrity
- operational efficiency
Interests
- device management
- workspace security
- creative agency ops
- Android admin
- open-source utilities
- home automation
Media habits
- Follows r/sysadmin and r/androiddev on Reddit
- Subscribes to 'The Changelog' podcast
- Reads TechCrunch and Wired for industry trends
- Uses Twitter/X for real-time tech troubleshooting
- Attends local London meetups for sysadmins
- Watches YouTube tutorials for specific software fixes