Why this persona fits the audience
Writes help-center articles for a UK SaaS startup with a two-person support team, uploading annotated screenshots and GIFs for internal review, then placing public links in the CMS and ticket macros. Keeps a separate folder of reference images for recurring fixes.
- Age: 38
- Location: Bristol, UK
- Occupation: Knowledge base writer
- Income: GBP 49k
- Education: Bachelor's degree in Technical Communication
- Company size: 15-person SaaS startup (B2B HR compliance tools)
- Years in role: 4
“I don’t just write documentation—I design user peace of mind. If someone has to contact support, that’s already a failure of the documentation.”
Jeff Schuster, 38, has spent the last four years crafting the knowledge base for CompliSure, a HR compliance SaaS startup based in Bristol. A former technical writer for a London consulting firm, he moved to Bristol for 'real city living without the rent' and has since become obsessed with the granular details of user documentation. His current workflow involves creating hundreds of annotated screenshots monthly, which he uploads to a free image hosting service before embedding into knowledge base articles. He keeps an elaborate folder system for reference materials, color-coding them by product module. Recently, he implemented a macro system for support tickets that standardizes documentation references, saving his tiny support team 4+ hours weekly. Jeff spends his weekends at Bristol’s independent bookstores, where he hunts for rare editions of old technical manuals he finds 'elegantly structured.' His personal Notion workspace contains over 200 documentation templates he shares with others in the field. He’s currently experimenting with AI tools to automate parts of his screenshot workflow, though he’s skeptical of anything that might compromise accuracy. His biggest professional frustration is the lack of a reliable, no-signup screenshot host that doesn’t watermark images or require branding. He sets aside £20 monthly for 'UX tools' but prefers open-source solutions. He’s saving for a renovations fund, having recently discovered his flat’s walls contain original 1970s blockwork that he’s spent months restoring in his spare time. Jeff takes pride in his documentation discipline, viewing it as 'the last line of defense against chaos.'
Background & daily life
A day in their life
Jeff's day starts at 6:45 AM with a black coffee and a 5-minute mobility routine. By 7:30, he's at his standing desk reviewing overnight tickets, flagging any that might need documentation updates. His first major task is batch-processing 20 support GIFs for a new feature update. At 10, he has a standing 15-minute sync with the support team to align on documentation priorities. Post-lunch (always a pre-ordered low-allergen meal from a local deli), he spends two hours writing a user guide, constantly tweaking the visuals to match the brand's palette. Before he leaves, he preps the next day's work by setting up a ‘screenshot roundup’ folder with placeholder files. He commutes home by bike, intentionally taking the longer route to clear his head. He spends evenings organizing his reference materials, a habit he finds 'oddly meditative' but his friends call 'a bit too much.'
Lifestyle
Jeff rents a 70s-era flat in Bristol's Easton neighborhood, where he shares a narrow garden with his landlord's potted herbs. His morning routine involves cold brew coffee, a 7-minute pelvic floor stretch (post-running injury), and an audiobook on urban design. He bikes to work in all weather, maintaining a strict 'no car' policy since moving back from London. He spends weekends at Bristol's independent bookstores or curating Notion templates for personal projects. His only indulgence is a standing appointment at a local espresso bar where they know his order before he arrives. His social circle is small but close-knit, mostly fellow SaaS professionals who meet for post-work 'doc sprints' at a co-working space.
Work life
Jeff works for a two-person support team handling documentation for CompliSure, a UK-based HR compliance SaaS startup. His workday revolves around maintaining a 12,000-article knowledge base where he writes process guides, troubleshoots edge cases, and creates visual aids. He spends 30% of his time producing annotated screenshots and GIFs to illustrate fixes, which he uploads to a private folder before incorporating into CMS articles. He recently implemented a macro system to standardize ticket resolutions. His biggest challenge is translating developer jargon into user-friendly language without oversimplifying. He advocates for 'screenshot discipline'—disallowing images of live user data—after a case where an API key was accidentally captured in a support GIF.
Relationships
Jeff maintains close ties to his older sister in Manchester, who runs a small marketing agency. He's the go-to tech support for her team, which he enjoys but sometimes resents when it interrupts his weekend productivity. His professional network consists of mostly female colleagues in tech comms, which he finds refreshing. He has a soft spot for the two support agents at his company, both of whom are newer to tech roles, and often coaches them on how to spot documentation gaps. He avoids Twitter politics but follows a handful of UX writers on Bluesky.
How they decide
He researches thoroughly but trusts his instinct when documentation patterns emerge. Prefers platforms that don't require learning curves—once burned by a complicated ticketing system, he now only recommends tools that let him 'get to work in 30 seconds.' Dislikes cold calls and ignores most vendor emails, but will open a LinkedIn message if it's clearly from someone who's read his Notion templates.
How they sound
Jeff speaks in measured, precise sentences with occasional self-deprecating humor. He uses Britishisms like 'a bit rubbish' and 'that’s not how it works, mate' but avoids slang. He has a habit of pausing before answering technical questions. He dislikes jargon but uses 'knit-picking' to describe his own attention to detail. He always says 'thank you for your time' in meetings, even if it's just a team of two. His writing voice is warm but direct, with a signature phrase: 'Here’s what actually happens...'
Personality traits
- detail-obsessed
- prefers quiet consistency
- passionate about self-documentation
- notices environmental textures (keeps a folder of 'good screenshot examples')
- obsession with keyboard shortcuts
- hates vague instructions
- keeps a 'noise' tracker of workplace inefficiencies
- dislikes spontaneous meetings
- over-prepares for QA reviews
- uses 'technical empathy' as a mantra
Goals
- Complete his 'SaaS Documentation Patterns' side project and publish it as a Notion template
- Improve his own writing workflow by automating more of the screenshot-URL process
- Cycle the Camino de Santiago after retiring
- Reduce his 'cognitive load' by eliminating unnecessary documentation steps
Problems & frictions
- Frustrated by the lack of a reliable, brand-agnostic tool for hosting temporary support screenshots
- Annoyed when colleagues send unredacted screenshots with personal data visible
- Constantly reorganizing his reference image folders as the product evolves
- Struggles to make GIFs short enough to be helpful but small enough to load quickly
- Feels documentation isn't given enough weight in product development discussions
Values
- accuracy
- helpfulness
- documentation discipline
- empathy
- systematic thinking
Interests
- SaaS
- UX writing
- screen recording
- Notion
- minimalist design
- city cycling
Media habits
- Reddit (r/techworkers, r/SaaS)
- YouTube (UX tutorials, coding walkthroughs)
- Indie hacker newsletters
- BBC News app