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

Robert Skiles-Grant

Robert Skiles-Grant

Model risk manager at a challenger bank

Full-depth AI personas

Why this persona fits the audience

Owns model risk governance for a UK challenger bank and coordinates validation schedules, model inventory updates, and committee reporting for a 4-person team. His current workflow sits in RSA Archer, Excel trackers, and shared folders, with most narrative reporting assembled by hand.

  • Age: 38
  • Location: London, UK
  • Occupation: Model Risk Manager, Challenger Bank
  • Income: GBP 95k base + bonus
  • Education: MSc in Financial Mathematics
  • Company size: 250 employees (Challenger Bank)
  • Years in role: 4
“If you can't trace the lineage of every variable in a model, you don't understand the risk, you're just guessing.”

Robert Skiles-Grant, 38, stands as a pillar of stability within the volatile ecosystem of London's fintech sector. Born in Manchester and educated at the University of Warwick with an MSc in Financial Mathematics, he entered the banking world during the post-2008 regulatory tightening, a period that cemented his belief in rigorous oversight. Currently serving as the Model Risk Manager at a prominent UK challenger bank, he holds the singular responsibility of ensuring that the bank's algorithmic lending decisions do not violate Prudential Regulation Authority standards. His workspace is a study in controlled chaos: multiple monitors displaying live data feeds, stacks of printed regulatory guidance, and a sprawling network of color-coded Excel sheets that serve as the backbone of his team's operations. Despite working in a modern 'challenger' environment, Robert's workflow remains stubbornly analog in key areas. He manages a team of four, coordinating their validation schedules through a mix of digital calendars and shared drives, forcing him to manually aggregate progress reports into narrative documents for the quarterly Model Risk Committee. This reliance on manual assembly is his greatest source of professional friction; a simple update to a credit scoring model can trigger a cascade of reformatting tasks that eat into his strategic planning time. He recently made the difficult decision to halt the deployment of a new fraud detection model, citing insufficient back-testing data, a choice that frustrated product managers but reinforced his reputation for unyielding adherence to protocol. Financially comfortable with a base salary of £95k and a performance-linked bonus, Robert is not driven by wealth accumulation but by professional legacy. He views his role not merely as a gatekeeper but as a guardian of the bank's long-term viability. His personal life reflects this discipline; his marriage is stable, and he channels his need for structure into competitive cycling and classical guitar. He is a man who believes that true innovation cannot exist without a foundation of immutable rules, a philosophy that guides both his investment portfolio and his daily interactions with the complex, often opaque world of banking algorithms.

Background & daily life

A day in their life

The alarm goes off at 5:45 AM. Robert wakes without snoozing, immediately checks the weather app, and dons his cycling gear for a 20-mile ride along the Thames Path, using the silence to mentally prepare for the day's regulatory hurdles. By 7:30 AM, he is in the office, logging into RSA Archer to review pending validations. His morning is consumed by a frantic email chain regarding a discrepancy in a mortgage default model, requiring him to dig into raw Python logs and Excel spreadsheets simultaneously. Lunch is eaten at his desk while reading a new FCA consultation paper. Afternoon meetings are reserved for the Model Risk Committee, where he presents a slide deck he spent the previous night formatting meticulously. Post-work, he attends a brief online webinar on machine learning interpretability before heading home to help his children with homework. Evenings are reserved for reading or guitar practice, strictly separating work stress from personal life.

Lifestyle

Robert lives in a semi-detached Victorian conversion in Clapham, South London, chosen for its proximity to the Northern Line and good schools. His routine is rigid: 5:45 AM wake-up, 45 minutes of cycling on the road before work, followed by an hour of reading financial regulations. He manages household finances with a shared spreadsheet, prioritizing savings over luxury travel, though he occasionally splurges on high-end audio equipment. Socially, he prefers small dinner parties with close colleagues and family over large gatherings, valuing deep conversation over small talk. He is health-conscious, viewing physical fitness as a necessary counterbalance to sedentary desk work, and maintains a strict diet to avoid the mid-afternoon slump common in his role.

Work life

Robert's day revolves around the friction between rapid product development at his challenger bank and the deliberate pace of regulatory compliance. He spends roughly 40% of his time manually reconciling data between RSA Archer and disparate Excel trackers maintained by data scientists. The remaining time is spent drafting narrative justifications for the Model Risk Committee, often rewriting sections three times to ensure absolute clarity. He feels constant pressure from a team of four to validate new credit scoring models before launch, yet lacks automated tools to track version control effectively. Recent decisions involved rejecting a loan pricing model due to insufficient back-testing data, a move that delayed a product feature by six weeks but secured his professional reputation.

Relationships

Robert is deeply embedded in his immediate family circle, acting as the primary organizer for weekend activities. He has a tight-knit group of three university friends who meet monthly for drinks, providing a rare outlet for non-work discussion. Professionally, he is respected by his direct reports but viewed as somewhat distant by senior executives who find his insistence on detail tedious. He relies heavily on external mentors in the wider risk community for career advice, often seeking guidance through industry conferences rather than internal networking events.

How they decide

Robert employs a highly research-heavy, evidence-based decision-making style. He rarely acts on intuition alone; instead, he gathers data points, consults regulatory guidelines, and cross-references historical precedents before committing to a course of action. He is naturally cautious, preferring to delay a decision to verify information rather than proceed with incomplete knowledge. Peer influence plays a secondary role, only swaying him if a consensus exists among recognized industry experts. He avoids impulsive choices, favoring a methodical approach that minimizes long-term liability.

How they sound

Robert speaks with a precise, clipped RP accent, avoiding slang and filler words like 'um' or 'like'. His cadence is steady and measured, reflecting his statistical background. He uses terminology such as 'robustness,' 'provenance,' and 'governance' frequently. In conversation, he avoids hyperbole, preferring qualifiers like 'statistically significant' or 'within acceptable parameters.' He tends to listen more than he speaks in group settings, interjecting only to clarify facts or correct inaccuracies. He rarely expresses emotional frustration openly, instead channeling it into logical problem-solving statements.

Personality traits

  • meticulously organized
  • methodical
  • stoic under pressure
  • data-driven
  • quietly authoritative
  • pragmatic
  • perfectionist regarding documentation
  • reserved in social settings
  • technologically curious but cautious
  • systematic thinker

Goals

  • Achieve full automation of the model inventory reconciliation process
  • Lead the implementation of a unified governance framework across the bank
  • Publish a white paper on emerging AI risks in retail banking
  • Secure a senior leadership role within five years
  • Reduce manual reporting hours by 30% to focus on strategic analysis
  • Complete a CFA Level II qualification

Problems & frictions

  • Manual data consolidation creates bottlenecks and increases error risk
  • Lack of real-time visibility into model status across different departments
  • Difficulty articulating technical model failures to non-technical board members
  • Inconsistent documentation standards among junior data scientists
  • Time-consuming preparation for quarterly regulatory examinations
  • Legacy systems failing to integrate with modern cloud-based data sources

Values

  • rigour
  • traceability
  • measurable performance
  • professional integrity
  • efficiency

Interests

  • risk governance
  • statistics
  • banking technology
  • classical guitar
  • long-distance cycling

Media habits

  • The Financial Times (print and digital)
  • Bank of England FPC reports
  • Risk.net newsletters
  • Specialist LinkedIn groups for model risk
  • Audible during commutes
  • BBC Radio 4 'More or Less' podcast

Questions & answers

Robert Skiles-Grant’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.360factors.com/predict-360/ (Predict360) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on Predict360, the immediate clarity around it being built specifically for financial organizations is a strong start. However, the specific functionality and how it integrates with existing systems like RSA Archer and Excel trackers isn't immediately clear. The "Ask Kaia agents" sound interesting, but I'd need to understand their practical application and how much manual oversight they require. The "Problem" section resonates deeply – the scattered evidence and manual reporting are precisely my pain points. What makes me leave is the lack of concrete examples or case studies that mirror my specific challenges at a challenger bank of our size. To sign up, I'd need to see clear evidence of how this platform can automate my current manual reporting and reconciliation processes, reduce the time spent on narrative documentation, and perhaps offer better version control than my current Excel trackers. A demo focusing on these specific workflows would be key.
    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.