10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Bruce Dietrich

Bruce Dietrich

Operations coordinator at a small architecture studio

Full-depth AI personas

Why this persona fits the audience

He supports an 8-person architecture studio, collecting drawing sets, marked-up PDFs, and site photo folders from staff and sending them to consultants and contractors. The team keeps files in OneDrive and uses email threads for one-off handoffs.

  • Age: 31
  • Location: Manchester, UK
  • Occupation: Operations coordinator
  • Income: £34,000/year
  • Education: BSc in Architecture
  • Company size: 8 employees
  • Years in role: 4
“If you can't find the file in three clicks, it doesn't exist, and then nothing gets built.”

Bruce Dietrich is a 31-year-old operations coordinator based in Manchester, holding a BSc in Architecture from the University of Salford. Despite his academic background, he found his true calling not in drafting designs, but in orchestrating the complex logistics required to bring those designs to life. Currently employed by a boutique eight-person studio, Bruce serves as the operational linchpin, bridging the gap between creative architects and practical contractors. His daily reality is defined by the sheer volume of data movement: he collects marked-up PDFs, organizes terabytes of site photography, and ensures that every consultant receives the exact iteration of a drawing set they need. Bruce's approach to work is rooted in a deep-seated need for order. He finds chaos in unstructured file sharing deeply distressing, often spending his evenings refining Excel macros to automate repetitive tasks. Although he earns £34,000 annually—a solid middle-class income in the region—he is budget-conscious, viewing money as a resource to buy efficiency rather than luxury. His living situation in Didsbury reflects this pragmatism; he shares a spacious flat to keep costs manageable while saving for a mortgage. Recently, Bruce faced a significant friction point when a contractor began building from an outdated structural plan due to a misfiled email attachment. This incident highlighted the fragility of the studio's reliance on email threads for critical handoffs. Since then, he has been quietly researching solutions to centralize file distribution, driven by a desire to eliminate human error. He is not looking for a magic wand, but a robust, logical system that respects the hierarchy of his current tools. Bruce views himself as the guardian of the studio's workflow, believing that good architecture is impossible without impeccable administration.

Background & daily life

A day in their life

Bruce wakes at 6:30 AM to a quiet house, making coffee while checking the weather for his cycle commute to Deansgate. By 8:15 AM, he is at the studio, immediately logging into OneDrive to download overnight updates from structural engineers in London and Berlin. His morning is spent triaging emails, extracting attachments, and re-naming files before the 9:30 AM stand-up. After lunch, he spends two hours cleaning up messy photo folders from a recent site visit, organizing them by date and location for the project archive. The afternoon involves chasing missing signatures from contractors via email and preparing the final PDF packs for Friday's client review. He leaves at 5:30 PM sharp, taking the tram home to cook a simple meal, edit his weekend photography, and relax with a match replay.

Lifestyle

Bruce lives in a converted Victorian terrace in Didsbury with two colleagues, sharing rent and bills. His evenings are a mix of solitary maintenance—organising his digital photos or tweaking Excel macros—and social time spent at local pubs discussing football tactics or walking the canal paths near Ancoats. He is financially prudent, avoiding debt but willing to spend on high-quality tools that save time. Health is managed through regular cycling to work and Sunday hikes in the Peak District. He values stability over excitement, preferring a predictable routine where he knows exactly where every file and document is located.

Work life

At the studio, Bruce is the invisible backbone, managing the flow of information between eight architects and external stakeholders. His day is a constant juggling act of downloading massive CAD files from consultants, renaming them according to strict naming conventions, and ensuring the latest revisions are uploaded to OneDrive before the afternoon meeting. He relies heavily on email chains to track 'one-off' requests, which often leads to version confusion. While the architects focus on design, Bruce focuses on logistics, spending hours verifying that a contractor has received the correct structural drawings. The pressure isn't physical but cognitive; a single misplaced attachment can halt construction, so his attention to detail is absolute.

Relationships

Bruce maintains a tight-knit circle of three close friends from university, mostly fellow creatives and engineers. He is the designated 'fixer' among his group, often helping others troubleshoot tech issues. At work, he has a respectful but distant relationship with the lead partners, who rely on him implicitly but rarely engage with his workflow details. He attends weekly pub quizzes with colleagues, using these informal moments to gauge team morale. Family visits are rare, limited to monthly calls with parents in Cheshire, whom he keeps updated on his steady career progression.

How they decide

Cautious and research-heavy. Bruce does not make impulsive purchases. When evaluating a new tool, he creates a comparison matrix of features against his current manual process, seeking peer validation on professional forums before committing. He prioritizes reliability and long-term cost-effectiveness over flashy interfaces, requiring proof that a solution will integrate seamlessly with existing Microsoft workflows without disrupting the team's delicate balance.

How they sound

His speech is measured, precise, and free of hyperbole. He avoids slang unless discussing football, speaking in clear, complete sentences. In professional settings, he uses technical terminology correctly but simply, never showing off. He tends to pause before answering complex questions to ensure accuracy. He avoids emotional outbursts or complaining about workload, preferring to frame issues as logistical puzzles to be solved. His tone is calm and reassuring, often used to de-escalate tension when deadlines are missed.

Personality traits

  • meticulous
  • quietly observant
  • systematically minded
  • dependable
  • diplomatic
  • tech-savvy but cautious
  • methodical
  • low-drama
  • efficiency-obsessed
  • pragmatic

Goals

  • To implement a foolproof version control system that eliminates email confusion
  • To transition into a project management role within five years
  • To master advanced automation in Microsoft Office
  • To purchase a home in Greater Manchester by age 35
  • To reduce personal administrative stress to allow more time for hobby photography
  • To build a reputation as the most reliable operator in the local architectural community

Problems & frictions

  • Frequent misplacement of critical PDF versions across different email threads
  • The lack of real-time visibility when consultants update large drawing sets
  • Time wasted manually renaming and sorting hundreds of daily files
  • Difficulty tracking who has seen the latest revision without sending reminders
  • OneDrive's folder structure becoming cluttered and hard to navigate
  • Delays caused by waiting for contractors to acknowledge receipt of heavy file transfers

Values

  • order
  • reliability
  • practicality
  • teamwork
  • transparency

Interests

  • building design history
  • football (Manchester United)
  • spreadsheet shortcuts
  • city walks
  • analog photography
  • local brewing

Media habits

  • ArchDaily and Dezeen newsletters
  • BBC Radio Manchester during commutes
  • Reddit r/UKArchitecture and r/excel
  • LinkedIn for industry news
  • Spotify playlists for deep work

Questions & answers

Bruce Dietrich’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of FileFlan (https://fileflan.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make FileFlan better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, we manage file handoffs using OneDrive and email threads, which is quite inefficient. The recent incident with the outdated structural plan highlights the risks of this approach. FileFlan's promise of 'instant universal file sharing' and end-to-end encryption sounds appealing for improving our workflow and security. However, I need more clarity on how it integrates with our existing systems like OneDrive, and if it supports the large file sizes typical for architectural drawings. The fact that it's P2P and has no logins is intriguing, but I'm unsure how that translates to managing files for an 8-person studio with external consultants. Without understanding the integration and bulk file handling capabilities, it's hard to say if it's better or worse than our current method. I wouldn't pay anything until I understand its practical application for our specific needs.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.