Why this persona fits the audience
He already keeps pay stubs, mortgage statements, passport scans, and warranty PDFs in OneDrive and Apple Files, with a simple naming convention and an Excel tracker for expiry dates on his laptop.
- Age: 52
- Location: Seattle, WA, USA
- Occupation: IT support lead
- Income: $131,000
- Education: B.S. Information Systems
- Company size: 45-70 employees
- Years in role: 8
“If I can't verify the integrity of the data myself, it doesn't belong in my life.”
Bryan Moore, 52, is a seasoned IT professional based in Seattle who views information management not just as a job function but as a personal philosophy. With a B.S. in Information Systems earned in the late 1990s, he has witnessed the transition from floppy disks to cloud-native architectures, a shift that has only reinforced his belief in local control. Currently serving as an IT Support Lead for a regional logistics company, he commands a small team and acts as the primary architect for their internal documentation standards. His income of $131,000 affords him a comfortable lifestyle, yet he remains fiscally conservative, channeling surplus funds into durable goods and technology that ensures self-sufficiency. His home life mirrors his professional rigor. He maintains a sophisticated home lab in the basement, running multiple virtual machines and a local NAS that serves as the backbone of his digital existence. Unlike many peers who rely exclusively on consumer cloud services, Bryan employs a hybrid strategy: critical documents like mortgage statements, passport scans, and pay stubs are stored locally with versioned backups, while less sensitive items reside in OneDrive. He has built a custom Excel-based tracking system on his laptop to monitor document expiry dates, a habit born from past experiences where missed renewals caused unnecessary stress. Despite his technical prowess, Bryan struggles with the friction of modern software ecosystems that demand constant connectivity. He finds himself spending more time maintaining his existing filing structure than actually accessing the files within it. His recent decision to audit his digital footprint revealed a chaotic sprawl of screenshots, downloaded invoices, and scanned receipts scattered across different apps. While he values the convenience of these tools, the lack of a unified, offline-first interface creates a persistent low-level anxiety about data loss and privacy. He is currently exploring ways to consolidate this chaos without sacrificing the autonomy he has fought hard to maintain.
Background & daily life
A day in their life
Bryan wakes at 5:30 AM for a 45-minute run along the waterfront, listening to a podcast on system architecture. By 7:00 AM, he is at his desk, reviewing overnight alerts and clearing the top five priority tickets before the rest of the office arrives. He spends his morning leading a stand-up meeting, focusing on blocker removal and script updates. Lunch is a packed bento box eaten while reading technical documentation or configuring a new node in his home lab. Afternoons are dedicated to complex troubleshooting, often involving deep dives into logs that require intense concentration. He leaves work promptly at 5:30 PM to avoid overtime culture. Evenings are reserved for woodworking in the garage or hiking trails, disconnecting completely from screens until bedtime, where he checks his automated backup status one last time.
Lifestyle
Bryan lives in a quiet, well-maintained craftsman-style home in the Ballard neighborhood of Seattle. His weekends are split between long hikes in the Cascades to clear his head and hours spent tinkering with his home server rack in the basement. He is financially secure but avoids luxury spending; money goes toward high-quality gear that lasts. He and his wife maintain a low-key social circle of fellow professionals and neighbors, preferring board game nights over loud bars. Health is a priority, managed through consistent morning runs and a diet he plans himself, viewing his body as another system requiring maintenance and optimization.
Work life
As an IT Support Lead for a mid-sized logistics firm, Bryan manages a team of three junior technicians. His day is a mix of ticket triage, managing active directory permissions, and acting as the human firewall against ransomware attempts. He spends significant time documenting procedures because his team turnover is high, ensuring continuity. He uses a custom PowerShell script library for routine tasks rather than buying new SaaS tools unless absolutely necessary. The pressure comes from the expectation of zero downtime during business hours, forcing him to prioritize stability over novelty. Coworkers respect his ability to fix things without escalating to vendors, though they sometimes find his insistence on strict protocols tedious.
Relationships
Bryan is married to Sarah, a high school biology teacher who handles the bulk of their social planning and emotional labor. Their son, 19, is a college freshman studying graphic design and often asks for help with cloud sync issues, which Bryan solves with patience but little enthusiasm. He has two close friends from his university days who share his interest in mechanical keyboards; they meet monthly for dinner and tech talk. He feels most connected when collaborating on shared projects, like building a PC or organizing a community garden plot, rather than casual socializing.
How they decide
Bryan is a deliberate researcher who prefers deep dives over quick summaries. He relies heavily on documentation, technical specifications, and peer reviews from trusted communities before committing to any software. He is highly skeptical of 'free' models that monetize data, preferring transparent pricing structures. He rarely makes impulse purchases and will often test a tool's free tier or open-source alternative for weeks before considering a paid license. His decisions are driven by long-term utility and the assurance of data sovereignty rather than feature lists or UI polish.
How they sound
His speech is measured, precise, and devoid of filler words. He uses industry terminology naturally but avoids marketing jargon. When explaining concepts, he breaks them down into logical steps, often using analogies related to machinery or infrastructure. He speaks with a calm, flat cadence, rarely raising his voice even when frustrated. He avoids hyperbole and emotional exaggeration, preferring factual descriptions. He tends to pause before answering questions, processing the logic internally first. In conversation, he listens more than he speaks, asking clarifying questions to ensure he understands the premise before offering a solution.
Personality traits
- Methodical
- Meticulous
- Introverted
- Pragmatic
- System-oriented
- Self-reliant
- Detail-obsessed
- Cautious
- Steady
- Low-drama
Goals
- Achieve full financial independence by age 60
- Complete a self-built off-grid cabin project
- Reduce digital clutter across all personal devices
- Master the Rust programming language for system scripting
- Maintain physical fitness standards equivalent to his 30-year-old self
- Create a comprehensive disaster recovery plan for his household data
Problems & frictions
- Managing the fragmentation between cloud storage and local backups creates anxiety about data consistency
- The sheer volume of digital receipts and warranties is becoming unmanageable with current manual methods
- Difficulty finding intuitive tools that don't force a subscription model or cloud dependency
- Keeping family members compliant with his strict file organization standards
- The cognitive load of remembering which expiration dates are approaching without constant checking
- Balancing the desire for offline security with the convenience of mobile access for documents
Values
- control
- consistency
- self-sufficiency
- privacy
- efficiency
- reliability
Interests
- home labs
- mechanical keyboards
- hiking
- retro computing
- woodworking
Media habits
- r/sysadmin
- MacRumors forums
- Local tech subreddits
- Podcasts about productivity systems
- Hobbyist hardware review sites
- Digital nomad tech blogs