Owen White

Why this persona fits the audience

He is the operations lead at a 15-person SaaS company in Manchester and owns the internal workflow for app listing updates, release checklists, and the occasional mobile UI mockup used by sales. He has not paid for a specialized screenshot tool before and mostly coordinates work across Figma, spreadsheets, and the product team.

• Age: 34
• Location: Manchester, UK
• Occupation: Operations Lead
• Income: £59k
• Education: BSc Information Systems
• Company size: 15-person
• Years in role: 4

“It's all about making sure the gears mesh smoothly; if one part grinds, the whole machine suffers.”

Owen White, 34, has carved out a niche as the Operations Lead at a burgeoning 15-person SaaS company based in Manchester, UK. His journey into operations wasn't a direct path; after completing his BSc in Information Systems, he spent a few years in a junior support role before transitioning into process management. This background gives him a grounded understanding of user issues and system workflows. He's deeply invested in his role, seeing it as the crucial connective tissue that allows the product and sales teams to function effectively. His primary responsibility revolves around the meticulous management of the company's mobile companion app's presence on various app stores. This involves owning the end-to-end workflow for app listing updates, ensuring all metadata, descriptions, and version information are accurate and timely. He also maintains the comprehensive release checklists that guide the engineering and product teams through each deployment, a task he approaches with almost religious diligence. A significant part of his role, often underestimated, is the creation of occasional mobile UI mockups. These aren't high-fidelity designs but rather functional representations used by the sales team to illustrate potential app features or demonstrate user flows during client pitches. He orchestrates this work using a combination of Figma for visual elements and detailed spreadsheets for tracking and coordination, liaising closely with the product managers to translate requirements. Owen has never felt the need to invest in specialized screenshot or UI mockup tools, viewing his current toolkit as sufficient, albeit time-consuming. His income of £59k reflects his experience and the responsibilities he holds within a small but growing tech firm. He values process discipline above all, believing that well-defined workflows are the bedrock of reliable operations. Pragmatism guides his approach; he seeks the most efficient and effective solutions, not necessarily the flashiest. Cross-team reliability is paramount, as he understands that delays or errors in his domain can have cascading effects. He's conscious of his time and money, preferring to invest in tools and processes that offer tangible, long-term benefits rather than quick fixes. His recent focus has been on refining the app update process, aiming to reduce the manual hours spent each month on compliance checks and asset uploads, a task that often eats into his evenings before major releases.

Background & daily life

A day in their life

Owen's typical weekday starts around 7:30 AM with a quick scan of industry news and emails before his commute. He arrives at the office by 9 AM, immediately diving into checking the status of any overnight app builds or pending updates. The morning is often spent coordinating with the product team on upcoming release features and updating the master release checklist. Lunch is usually a quick sandwich at his desk while reviewing sales feedback on app store listings. The afternoon involves creating or refining UI mockups in Figma for the sales team, troubleshooting any issues with current app store listings, and planning the next day's operational tasks. He aims to leave by 5:30 PM.

Lifestyle

Owen lives in a rented two-bedroom flat in Chorlton, Manchester, with his partner, Sarah, a primary school teacher. Their weekends are a mix of socialising with friends, visiting family in the Peak District, and catching up on household chores. He's a keen but casual runner, aiming for a 10k a couple of times a week. Money habits are sensible; they budget carefully, with a focus on saving for a house deposit, but don't shy away from occasional nice meals out or weekend trips. He’s a dedicated Manchester United fan, rarely missing a match, whether at Old Trafford or on TV.

Work life

As Operations Lead at a growing SaaS firm, Owen is the linchpin for internal processes, particularly those surrounding their mobile app. His days are consumed by ensuring smooth app listing updates for various app stores, meticulously managing release checklists, and occasionally generating basic UI mockups for the sales team using Figma. He juggles requests from product, engineering, and sales, often translating technical requirements into actionable steps. The pressure is on to maintain efficiency and accuracy, especially during critical product launch phases, all while operating within the constraints of a lean, 15-person team.

Relationships

Owen is in a stable, long-term relationship with Sarah, who provides a grounding influence. His close circle of friends, mostly met through university and work, are a source of support and shared interests, particularly football. He maintains a professional but friendly rapport with his colleagues, respecting the product team's technical expertise and the sales team's market insights.

How they decide

Owen is a methodical and research-oriented decision-maker. He weighs options carefully, prioritising practicality and proven reliability. He'll often create a simple pros and cons list, consult with relevant team members, and look for evidence of effectiveness before committing to a new process or tool. He’s not impulsive and prefers to understand the 'why' behind a decision.

How they sound

Owen speaks with a clear, measured tone, typical of a Manchester accent but without strong slang. He tends to be direct and factual, avoiding hyperbole. His language is professional but accessible, focusing on clarity and process. He might use phrases like 'right, so the plan is...', 'we need to make sure that...', or 'from an operational perspective...'. He avoids overly technical jargon unless speaking with engineers.