Boyd Swaniawski

Why this persona fits the audience

He is a growth analyst at a London subscription app, part of a five-person growth squad that monitors acquisition, trial-to-paid conversion, and cohort retention. He works in Mixpanel day to day and shares dashboards with the PM and CRM manager for weekly experiment reviews.

• Age: 29
• Location: London, UK
• Occupation: Growth Analyst
• Income: £72k base + bonus
• Education: Master's in Economics
• Company size: Series B startup, approx. 140 employees
• Years in role: 3 years

“Data doesn't lie, but the story you tell with it can easily mislead if you don't respect the underlying mechanics.”

Boyd Swaniawski is a 29-year-old Growth Analyst rooted in the vibrant tech ecosystem of London's Shoreditch. Holding a Master's in Economics from LSE, he transitioned from academic research to the fast-paced world of SaaS three years ago, drawn by the tangible impact of data on product direction. Currently embedded in a lean five-person growth squad at a Series B subscription app, Boyd serves as the critical bridge between raw data and strategic decision-making. His daily reality involves wrestling with the messiness of real-world user behavior, ensuring that the events tracked in Mixpanel accurately reflect the user journey from acquisition to paid conversion. His professional identity is built on a foundation of precision and experiment discipline. Unlike peers who might chase vanity metrics, Boyd obsesses over cohort retention and the causal link between specific UI changes and long-term engagement. He recently led a contentious initiative to standardize event tracking across three different engineering teams, a move that initially slowed deployments but ultimately reduced reporting errors by 40%. This experience cemented his belief that infrastructure hygiene is a prerequisite for growth, even in a 'move fast' environment. Outside of work, Boyd's life is a counterbalance to his analytical career. He finds solace in the deterministic nature of tabletop wargaming, where rules are absolute and outcomes depend on strategy and probability. He is also a devoted follower of Premier League football, applying his analytical skills to fantasy leagues and match predictions. Financially prudent, he navigates London's high cost of living with a rigid budget, viewing his £72k salary as a means to secure a stable future rather than fund a lavish lifestyle. Boyd is currently navigating the complexities of scaling his influence within the company, balancing the demands of a growing team against the need to maintain the rigorous standards that define his approach to growth.

Background & daily life

A day in their life

Boyd wakes at 6:45 AM, making a single-origin pour-over coffee while scanning overnight US market trends and competitor news. By 8:30 AM, he's on the tube, listening to a podcast on Bayesian inference. Work starts at 9:15 AM with a quick stand-up where he flags a drop in Day-7 retention for a specific user cohort. The bulk of his morning is spent writing complex SQL queries in the data warehouse to investigate the anomaly, followed by building a new dashboard view in Mixpanel for the Product Manager. Lunch is a quick sandwich eaten at his desk while reviewing a technical spec for a new API integration. Afternoon meetings include a rigorous critique of a proposed A/B test design with the CRM manager, where he challenges the sample size calculation. The day ends around 6:30 PM with a wrap-up email summarizing findings, leaving time for an evening run or hobby projects before bed.

Lifestyle

Boyd lives in a converted warehouse unit in Shoreditch, sharing rent with two friends from university to keep costs manageable while saving aggressively for a deposit. His evenings are a mix of low-key socializing and structured hobbies; he plays in a local Saturday morning fantasy football league and spends Sunday afternoons assembling intricate tabletop miniatures. He is health-conscious but not obsessive, relying on meal-prepped lunches and a strict coffee ritual before work rather than gym memberships. Financially, he is disciplined, contributing heavily to his pension and maintaining a high-yield savings account, viewing money as a tool for future optionality rather than immediate status signaling.

Work life

As the de facto data guardian in a lean five-person growth squad, Boyd's days are split between SQL querying, dashboard maintenance, and cross-functional syncs. He operates primarily in Mixpanel but constantly evaluates if their event tracking schema is robust enough for deeper causal inference. His main friction point is the speed of engineering deployment versus the rigor required for valid A/B tests. He frequently finds himself cleaning dirty data before it reaches the Product Manager, often having to manually reconcile discrepancies between frontend events and backend logs. The pressure is high; every percentage point in trial-to-paid conversion directly impacts the team's quarterly bonus, forcing him to balance rapid iteration with statistical significance.

Relationships

Boyd maintains a tight-knit circle of four close friends, mostly from his Master's program, who meet monthly for board games. He has a supportive relationship with his parents in Manchester, though they struggle to understand the nuances of his job. At work, he acts as a mentor to two junior analysts, guiding them on statistical validity. He is influenced by senior data scientists he follows online and respects pragmatic leaders who can translate complex models into actionable business strategy.

How they decide

Analytical and evidence-based. Boyd rarely makes decisions based on intuition alone; he requires a clear hypothesis, a defined success metric, and a review of historical precedents. He tends to research thoroughly, often creating small-scale prototypes or spreadsheets to validate a concept before committing resources. Peer validation is important, but only if backed by data. He avoids impulsive choices, preferring a calculated risk that aligns with long-term objectives.

How they sound

Boyd speaks with a clipped, precise cadence, avoiding filler words like 'um' or 'like'. He uses industry terminology naturally (e.g., 'statistical power,' 'attribution window') but explains concepts simply when necessary. He is direct and polite, often prioritizing clarity over diplomatic softening. He rarely admits uncertainty publicly, instead framing unknowns as 'areas requiring further investigation.' He avoids emotional language in professional settings, focusing strictly on the data narrative.