Why this persona fits the audience
Manages support tooling for a 12-agent team in Manchester and regularly reviews webhook logs, ticket metadata, and customer account exports that arrive as JSON. He prepares table views for escalations, quarterly reviews, and internal training examples.
- Age: 41
- Location: Manchester, UK
- Occupation: Support operations lead
- Income: £49k
- Education: Diploma in Business Information Systems
- Company size: Mid-sized SaaS provider (approx. 150 employees)
- Years in role: 4
“If you can't show me the numbers in a way I can read in five seconds, then the data isn't helping anyone.”
Ricardo Lowe is a forty-one-year-old Support Operations Lead based in Manchester, UK, who has spent the last decade bridging the gap between technical data streams and human customer service needs. Holding a Diploma in Business Information Systems, he rose through the ranks from a frontline agent to managing a team of twelve, driven by a belief that operational consistency is the backbone of service quality. His daily reality is defined by the messy, unstructured nature of raw data; he frequently receives customer account exports and webhook logs in JSON format, which often contain nested objects and inconsistent schemas that standard spreadsheets struggle to handle cleanly. This forces him to spend considerable time manually curating these datasets into table views for escalations and quarterly business reviews. Ricardo is pragmatic by nature, valuing tools that solve immediate friction points over those that offer flashy, unused features. His income of £49k reflects a solid mid-level management position in a growing SaaS company, allowing him to maintain a comfortable but budget-conscious lifestyle in Didsbury. He is married with two young children, and his personal life is anchored in routine and community involvement, particularly through local football coaching. While he possesses a moderate level of technical confidence, he is not a developer; he navigates the world of APIs and data structures out of necessity rather than passion. Recent decisions have seen him investing time in scripting basic automations to reduce manual effort, yet he remains frustrated by the lack of user-friendly tools that can instantly transform complex JSON into formatted Excel sheets without requiring coding knowledge. He is currently evaluating ways to streamline his reporting pipeline, looking for solutions that respect his time and the integrity of his team's workflow, though he remains skeptical of any tool that claims to be a 'magic bullet' without proof of reliability.
Background & daily life
A day in their life
Ricardo starts his day at 5:30 AM with a run along the canal, using the time to mentally decompress. By 7:00 AM, he is preparing breakfast for his family before dropping the kids off at school. He arrives at the office by 8:45 AM, immediately checking the dashboard for any overnight webhook errors. At 9:30 AM, he joins a stand-up with his twelve agents, discussing ticket volume trends and assigning specific cases to specialists. Mid-morning is dedicated to his core task: parsing JSON exports from the customer portal, converting them into readable tables for the upcoming executive review. He spends an hour troubleshooting a recurring issue where a third-party API returns malformed data, writing a small script to normalize it. Lunch is a quick sandwich eaten at his desk while reading a technical article. Afternoon meetings focus on training materials and refining the escalation protocol. He leaves at 5:30 PM sharp, heading home to coach football and spend quality time with his family, refusing to check emails after dinner.
Lifestyle
Ricardo lives in a semi-detached house in Didsbury with his wife, Sarah, and their two young boys. His routine is rigidly structured; he wakes at 5:30 AM to exercise before the family stirs, ensuring he has quiet time for himself. Weekends are split between coaching his son's football team and tackling household projects, often involving him tinkering with old hi-fi gear or fixing garden furniture. Financially, he is prudent, budgeting strictly for school fees and savings while avoiding unnecessary debt. Socially, his circle consists mostly of work colleagues and long-standing neighbours from his primary school days, preferring deep, practical conversations over large, chaotic gatherings. He prioritizes health, walking to the gym three times a week, though stress occasionally creeps in during peak support seasons.
Work life
As the Operations Lead, Ricardo spends his mornings reviewing overnight webhook logs and ticket metadata, identifying patterns in customer account exports delivered as JSON files. His day involves transforming these raw data dumps into clean, tabular formats for escalation meetings and quarterly reviews. He manages a team of twelve agents, focusing heavily on consistency and process improvement rather than just fire-fighting. The pressure comes from the need to ensure data accuracy for internal audits and the constant demand to reduce resolution times. He relies on a mix of legacy spreadsheet software and custom scripts, often spending hours manually reformatting data because existing tools lack specific filtering capabilities. His workspace is organized but cluttered with sticky notes tracking complex workflow bottlenecks.
Relationships
Ricardo is deeply embedded in his local community, viewing his role as a father and husband as equally important to his career. His wife, Sarah, acts as his primary sounding board for work frustrations, offering a grounding perspective. He maintains close ties with his parents, who live nearby, often helping them with technology issues. Professionally, he is respected by his direct reports for his fairness and by senior management for his reliability. He influences his team through example, encouraging them to ask questions about data logic rather than just following procedures blindly.
How they decide
Ricardo approaches decisions with a methodical, risk-averse caution. He rarely adopts new tools without a thorough trial period and a clear understanding of how they integrate with existing workflows. He values peer recommendations and case studies over marketing hype, preferring to see concrete evidence of efficiency gains before committing resources. If a solution requires significant setup time or training for his team, he will likely delay adoption until the long-term ROI is undeniable.
How they sound
Ricardo speaks with a distinct Mancunian cadence, neither overly formal nor slang-heavy, striking a balance of professional clarity and local warmth. He avoids jargon unless necessary, preferring plain English to explain complex concepts to his team. His tone is steady and measured, rarely raising his voice even when addressing urgent issues. He tends to pause thoughtfully before answering, ensuring precision in his words. He dislikes hyperbole and vague promises, often asking 'how exactly does that work?' when presented with abstract solutions.
Personality traits
- Meticulous about data formatting
- Calm under pressure
- Pragmatic problem solver
- Team-oriented mentor
- Skeptical of 'flashy' features without utility
- Structured communicator
- Values clear documentation
- Efficient with time
- Loyal to reliable tools
- Protective of team workload
Goals
- Reduce manual data formatting time by 20% within the next fiscal year
- Achieve a 95% customer satisfaction score across all support channels
- Implement a fully automated alert system for critical webhook failures
- Mentor two junior analysts to take over specific reporting duties
- Secure a promotion to Head of Customer Experience within three years
- Complete a part-time certification in Data Analytics
Problems & frictions
- Inconsistent data structures in incoming JSON exports require manual cleaning
- Legacy reporting tools cannot visualize nested JSON objects effectively
- Team members struggle to interpret raw ticket metadata without guidance
- Time spent on repetitive data entry reduces capacity for strategic analysis
- Difficulty in creating dynamic, shareable dashboards for non-technical stakeholders
- Fragmented communication between engineering and support teams regarding data changes
Values
- service quality
- team consistency
- practical reporting
- operational efficiency
- data integrity
Interests
- support systems
- ticket analytics
- process improvement
- local football (Manchester City)
- DIY home maintenance
- vintage audio equipment
Media habits
- Skims industry newsletters like 'The Supportive' on Sundays
- Listens to tech podcasts during commute
- Active in niche Slack communities for Ops leads
- Reads financial news on the BBC app
- Follows local Manchester community groups on Facebook
- Avoids clickbait lifestyle content