Why this persona fits the audience
One of 2 designers on a product squad in London, stores interface references in Figma comments, Slack threads, and a private bookmarks folder, and revisits older examples during design reviews. Already has a company subscription to a competitor reference tool and is cautious about adding another app to the stack.
- Age: 36
- Location: London, UK
- Occupation: Senior UX designer
- Income: £92k
- Education: MSc in human-computer interaction
- Company size: 50-250 employees
- Years in role: 7
“'My biggest design challenge isn’t making things intuitive—it’s convincing people they should care about intuitiveness.'”
Wm Fahey’s career path wasn’t linear. After his MSc, he spent three years at a healthcare startup where he learned to invert the Golden Rule of UX: ‘When in doubt, build for the least tech-savvy person who can’t complain.’ The neobank hired him to ‘clean up designs’ post-rapid-growth, a euphemism for ‘fix this mess.’ He now juggles three design systems that should’ve been one, and the unspoken mandate to ‘keep things professional-looking’ when his CEO asks about ‘rebranding again.’ His private bookmark folder is the only reliable way to track decisions—no one else at the company uses Figma comments for reference, and his team’s shared Slack channel disappeared in a reorg. He’s trialled every reference tool on the market, settled on one, and still relies on his spreadsheet backup. Recent stressor: A junior designer accidentally published a wireframe to the public Prototype share link—Wm spent four hours tracking down who saved which iteration. Personal life is equally systematized: His kitchen renovation is scheduled around his cycling training plan (which is scheduled around his FinTech Twitter-scroll time). He’ll retire before 50 if his investment app stops ‘nudging’ him to increase risk. The only impulsive purchase he’s made in a decade was a £350 Japanese plane—the rest of his tools are thrifted. When his sister sends him ‘life hack’ YouTube videos, he replies with screenshots of his ‘system’ that already handles the problem. He’s become that person.
Background & daily life
A day in their life
Wakes at 6:20 to a sunlight timer, checks the OED word of the day for no reason, and brews a pour-over while reviewing his ‘reference review’ Slack messages from overnight. Commute is spent scrolling through design critiques he’ll never post on Twitter. First task is always clearing his ‘awaiting feedback’ queue in Figma—today it’s seven comments from engineers. Walks to the office kitchen twice: once for coffee, once to ‘be seen’ between meetings. Lunch is matzo ball soup from the same bagel shop every Tuesday. Afternoon is swallowed by a cross-functional ‘alignment’ meeting where three people say the same thing in slightly different words. Post-work, he cycles to his local cybercafé to work on his newsletter because his flat’s Virgin Media buffer is out of contract but he hasn’t called them back. Falls asleep reading ‘The Psychology of Money’ and replying to design critiques from his iPad.
Lifestyle
Wm rents a two-bedroom Victorian flat in East London, where he’s slowly renovating the kitchen himself—his one hands-on hobby. He cycles to work (fixed-gear, all-weather) and tracks his Strava stats out of habit, not pride. Cooks in batches on Sundays to avoid weekday decisions. Splurges on rare whiskies but otherwise budgets for a planned August trip to Kyoto (long-term savings goal). Social life revolves around a small, high-validate group of former uni mates—dinners rotated monthly, all planning to relocate to the countryside within five years. Health: occasional back pain from desk work; chiropractor visits scheduled like code reviews. Money: maxes out pension contributions but refuses to refinance his mortgage for emotional certainty.
Work life
At a neobank, Wm is the fall guy between engineers who want ‘ship fast’ and executives who want ‘brand trust.’ His squad’s current project is a new merchant dashboard, where he’s fighting to unify colour schemes between mobile and desktop (engineers keep calling this ‘nitpicking’). Manages a Figma library that’s grown too large to be intuitively navigated—his private bookmarks folder is his shadow system. Slack notifications are batched; he checks them three times a day ‘like emails in the 2000s.’ Coworkers confide in him but rarely invite him to post-work drinks. His biggest daily stressor: knowing the CEO will repurpose his research as ‘their idea’ in leadership meetings.
Relationships
Grew up in a ‘no-nonsense’ NI family where opinions weren’t debated, just stated. His sister (a dentist) still texts him spreadsheet tips unprompted. Parents retired to Spain—he visits twice a year but finds their WiFi frustrations exhausting. The only non-work contact in his phone older than 5 years is his ex-girlfriend (they split amicably but she still DMs him digital minimalism articles he’ll never read). His closest friend is a product manager who refactors his resume every year though Wm insists he ‘isn’t leadership material.’
How they decide
Research-heavy but with a ‘good enough’ threshold for non-critical choices. Creates pros/cons lists for migrations (tools/relationships/kitchens) but defaults to incremental change to avoid regret. Trusts firsthand experience over reviews and sponsors his own trial periods (can’t remember the last time he bought something without testing it first).
How they sound
Doesn’t use filler words but occasionally over-explains when stressed. Speaks in full, measured sentences but his delivery is flat—like he’s transcribing internal dialogue. Avoids jargon with colleagues but will drop acronyms when excited. Calls himself ‘a recovering early-adopter’ about software tools. Uses ‘let’s just’ to suggest pragmatism when he means ‘I’ll do it myself.’
Personality traits
- meticulous note-taker
- pragmatic skeptic
- reluctant influencer
- low-key perfectionist
- homebody in social settings
- guarded about work boundaries
- shares knowledge selectively
- avoids office chitchat
- relies on systems for reliability
- quietly competitive in design critiques
Goals
- Build a design system retrofit that won’t require 10 meetings to justify
- Beyond his own savings rate, document a ‘quiet promotion’ strategy to step into a Head of Design role without office politics
- Master Japanese conversational phrases before Kyoto (duolingo streak: 752)
- Find a general practitioner who understands back pain from prolonged screen work
- Plant an avocado pit that doesn’t die within 6 months
- Release a UX critique newsletter without it becoming a time sink
Problems & frictions
- Engineers override his accessibility fixes by ‘forgetting’ to test in high contrast mode
- Can’t find the Figma component he created six weeks ago for the onboarding flow
- Slack threads devolve into back-and-forth that should’ve been emails
- His contractor’s kitchen cabinets arrive in three weeks but he hasn’t bought tools yet
- Meeting invites disappear into a calendar where ‘focus time’ is a myth
- Fintech jargon bleeds into friend group conversations—he’s become the explainer
Values
- rigor
- privacy
- predictability
- evidence
- autonomy
- professionalism
Interests
- fintech
- UX critique
- design governance
- digital productivity
- cybersecurity
- urban cycling
Media habits
- TechCrunch
- Twitter threads on design at scale
- A List Apart
- The Guardian's tech section
- Podcasts (mostly on fintech or accessibility)
- Mastodon (for design circles)