Shawn Hane

Why this persona fits the audience

He manages a 4-person product ops team and already pays for Todoist and Notion; personal actions live in Todoist, meeting follow-ups in Jira, and team reminders in Slack threads and Outlook flags.

• Age: 41
• Location: London, UK
• Occupation: Product operations manager at a fintech
• Income: £88k
• Education: MSc in Management
• Company size: 120 employees
• Years in role: 3.5

“I don't need another app that promises to save me time; I need one that stops me from wasting it jumping between screens.”

Shawn Hane, 41, is a seasoned Product Operations Manager based in South London, currently navigating the complexities of scaling a fintech startup. With an MSc in Management from Imperial College London, he entered the workforce in the early 2000s, climbing the ladder through roles in logistics and general administration before finding his niche in product operations five years ago. His career path reflects a steady evolution from chaotic administrative support to structured operational leadership, driven by a deep-seated need for order in increasingly disorganized environments. Currently, Shawn manages a four-person team responsible for streamlining product development lifecycles. His role is pivotal yet fraught with the friction of modern digital fragmentation. He actively pays for premium subscriptions to Todoist and Notion, believing in the necessity of paid tools for serious business, yet finds himself dissatisfied with the current state of his ecosystem. Personal tasks reside in Todoist, technical follow-ups land in Jira, and crucial team reminders are scattered across Slack threads and Outlook flags. This disjointed approach forces him to manually bridge gaps constantly, a tedious reality he accepts only because the alternative—hiring more staff—is not financially viable right now. His personality, characterized by high conscientiousness (0.86) and moderate openness (0.51), drives him to seek perfection in process, yet he is pragmatic enough to know that perfect systems are elusive. He values reliability above all else; a broken workflow is a personal affront. Recently, he rejected a proposal to migrate the entire team to a new project management suite after realizing the migration costs would outweigh the benefits for six months. Instead, he opted to refine existing workflows, a decision that saved the company £15,000 but left him with the nagging feeling that he is still operating below capacity. Outside of work, Shawn finds solace in the rhythmic predictability of football and public transport. He listens to transit podcasts during his commute, analyzing how systems move people efficiently—a metaphor for his own life. He is financially secure, earning £88,000, which allows him to maintain a comfortable lifestyle in a shared Victorian flat. However, his income is tied to his ability to remain indispensable, creating a low-level hum of anxiety about market shifts. He is a man who respects structure, fears ambiguity, and is quietly waiting for a solution that finally aligns his digital life with his mental expectations.

Background & daily life

A day in their life

Shawn wakes at 6:15 AM, immediately checking his phone for overnight alerts before brewing coffee. By 7:15 AM, he's on the Northern Line, listening to a podcast while reviewing his Todoist list. At 8:45 AM, he arrives at the office, greets his team, and dives into a 9:00 AM stand-up where he tracks blockers. The morning is dominated by back-to-back syncs with engineering leads, during which he frantically types action items into both Jira and his personal notes. Lunch is a quick sandwich eaten at his desk while scanning industry news. Afternoon meetings focus on strategic alignment, often requiring him to switch contexts rapidly between Slack, Outlook, and internal wikis. By 5:30 PM, he performs a final sweep of his inboxes, flagging anything unresolved for tomorrow. He leaves the office promptly, cycling home to decompress, avoiding work messages until the next morning.

Lifestyle

Shawn lives in a converted Victorian terrace in Clapham, sharing the space with his partner, Elena, a graphic designer. Their home is tidy, reflecting his need for order, with a dedicated home office that doubles as a study for evening reading. He cycles to work most days when the weather permits, treating it as essential decompression time rather than exercise. Mornings are ritualistic: a strong espresso from a V60 pour-over he makes himself, followed by scanning emails before the tube ride. Financially, he is comfortable but conservative, prioritizing mortgage stability over luxury spending. Socially, he maintains a small circle of friends from university and football, preferring deep one-on-one conversations or watching matches over loud parties. He values downtime highly and guards his weekends fiercely against work encroachment.

Work life

As a Product Operations Manager at a mid-sized fintech, Shawn acts as the glue between engineering, product design, and sales. His day is a constant balancing act of meetings, status updates, and clearing administrative blockers for his four direct reports. The current workflow is fragmented: he uses Todoist for his own personal tasks, pushes meeting action items into Jira for developers, and relies on Slack threads and Outlook flags for team coordination. This siloing creates significant cognitive load, often leading to missed follow-ups or duplicated effort. Recent decisions include negotiating a renewal for Notion and Todoist despite feeling their integration is weak. He spends his afternoons unblocking his team, translating high-level strategy into actionable steps, and ensuring no project slips through the cracks due to communication gaps.

Relationships

Shawn is married to Elena, who provides the emotional grounding he sometimes lacks due to his high conscientiousness. He has a tight-knit group of three friends from university with whom he plays amateur football every other Saturday. His professional network consists mainly of other operations leaders he meets at industry meetups; these peers are his primary source of validation regarding process improvements. He rarely seeks public advice online, preferring to ask trusted colleagues directly. His relationship with his boss is respectful but distant, focused strictly on output metrics rather than personal mentorship.

How they decide

Shawn approaches decisions with a cautious, evidence-based methodology. He requires proof of concept before adopting new systems, often running small pilots with his immediate team before committing to enterprise-wide changes. He is heavily influenced by peer recommendations and case studies from similar companies but remains skeptical of marketing fluff. Once a tool proves its reliability over a few weeks, he tends to stick with it for years, resisting frequent pivots unless a critical failure occurs. He dislikes making impulsive purchases and will spend hours researching features if the cost of implementation seems high.

How they sound

Shawn speaks with a clipped, efficient London accent, favouring precise vocabulary over colloquialisms. He avoids hyperbole, rarely using words like 'game-changing' or 'revolutionary' without qualification. His tone is calm and measured, even when discussing urgent deadlines. He frequently uses corporate terminology correctly ('deliverables', 'stakeholders', 'roadmap') but can sound slightly weary when discussing process inefficiencies. He doesn't use slang with colleagues, maintaining a professional distance, though he becomes more relaxed and uses British humour with close friends. He tends to pause before answering complex questions, preferring accuracy over speed.