Alonzo Barton-Donnelly

Why this persona fits the audience

Manages engineering delivery for a 14-person product team in Manchester. Keeps onboarding notes, runbooks, and release context in Notion and GitHub, while Slack and Linear capture day-to-day decisions; they are the person newer engineers ask when they need a sourced answer.

• Age: 39
• Location: Manchester, England, UK
• Occupation: Engineering Manager
• Income: £98k base + equity
• Education: Master's degree
• Company size: 14-person product team
• Years in role: 4

“Documentation isn't just words on a page; it's the only way we can guarantee that tomorrow's version of us remembers why we did what we did today.”

Alonzo Barton-Donnelly is a seasoned Engineering Manager based in Manchester, currently leading a twelve-person product squad at a mid-sized fintech firm. At 39, he sits comfortably in the upper-middle class, earning £98k annually plus a meaningful equity package that reflects his tenure and impact. His background includes a Master's in Computer Science from the University of Manchester, where he developed a lifelong fascination with distributed systems and reliability engineering. Over the last decade, he transitioned from a hands-on developer to a leader who views himself as a force multiplier rather than a super-coder. His current role demands a delicate balance between fostering innovation and enforcing discipline. Alonzo is the de facto custodian of the team's institutional memory. While the company utilizes a standard stack including Slack, Linear, and GitHub, Alonzo has taken personal responsibility for synthesizing this chaos into a coherent knowledge base. He manually curates Notion pages that serve as the single source of truth for onboarding, runbooks, and release contexts. This is not a delegated task; he believes that if the documentation is not accurate, the entire system fails. Recently, he initiated a refactor of the onboarding process, reducing the time-to-productivity for new hires by two weeks by consolidating scattered GitHub issues and Slack threads into structured guides. Financially, Alonzo is conservative yet strategic. He maximizes his pension contributions and invests in index funds, avoiding speculative crypto ventures despite industry pressure. His spending reflects a preference for quality over quantity; his home espresso setup costs more than many people's cars, but he views it as a necessary tool for his morning routine. Socially, he is selective, valuing deep connections with a few close friends and colleagues over broad networking. He is a skeptic of rapid technological change that lacks a clear utility, often questioning whether new AI tools actually solve the root cause of information silos or merely add another layer of abstraction. His greatest fear is not failure, but stagnation—the slow erosion of clarity and purpose within his team. He measures success not by lines of code written, but by the resilience and autonomy of the engineers he leads.

Background & daily life

A day in their life

Alonzo wakes at 5:30 AM, brewing espresso with exacting precision before his morning ride. By 8:30 AM, he is in his office, reviewing overnight logs and clearing urgent Slack messages before the team joins. His first hour is dedicated to deep work, typically writing architectural docs or refining onboarding guides. Stand-up occurs at 10:00 AM, followed by a block of 1:1s and code reviews. Lunch is a strict 30-minute break away from the screen. Afternoons are reserved for stakeholder meetings and Linear triage, where he acts as the gatekeeper for feature scope. He leaves work by 5:30 PM to be home for dinner, dedicating evenings to family and occasional hobby projects like tinkering with his espresso setup or reading technical papers. Weekends are mostly offline, focused on cycling, family activities, or home maintenance.

Lifestyle

Alonzo resides in a Victorian terrace in Didsbury, where he has installed a dedicated home office separate from the living space to enforce work-life boundaries. His mornings begin before 6:00 AM with a precise espresso ritual using a manual lever machine, followed by a 40km ride along the River Irwell or through the Cheshire lanes. He is financially prudent but invests heavily in high-quality gear that lasts, viewing tools as long-term assets rather than consumables. Socially, he maintains a tight circle of friends from university and cycling clubs, preferring deep one-on-one conversations over large networking events. He prioritizes family dinners without screens and actively manages his health to maintain the energy required for his demanding role.

Work life

As an Engineering Manager, Alonzo spends roughly 40% of his time in code reviews and architectural discussions, 30% in people management, and 30% in cross-functional alignment. His primary battlefield is information flow; he personally curates the team's Notion wiki and GitHub repositories to ensure every decision is logged. He shields his 14 direct reports from external noise, often acting as a buffer against stakeholder urgency. The pressure comes from maintaining velocity without burning out the team, requiring him to constantly evaluate process overhead. He relies heavily on Slack for quick syncs but distrusts it as a record, insisting on Linear for ticketing and Notion for institutional memory.

Relationships

Alonzo is married to Sarah, whose career in architecture provides a counterbalance to his tech-heavy world; they rely on each other for stress relief and logistical support regarding their two children, aged four and six. His professional influence stems from his former university mentors who instilled a love for rigorous engineering practices. He is a regular at a local independent coffee shop where he meets peers from other Manchester startups, though these interactions remain low-key. His most trusted advice comes from a small, private group of five other engineering managers who meet monthly to discuss leadership challenges without corporate oversight.

How they decide

Alonzo employs a slow-decision, fast-execution framework. He rarely commits to a new tool or process change without a period of observation, testing, and peer validation. He prefers data-backed arguments over hype, often creating a small proof-of-concept before committing organizational resources. He values independence in his decision-making but will defer to subject matter experts when the topic falls outside his immediate domain. Once a decision is made after thorough vetting, he expects full adherence and minimal debate.

How they sound

Alonzo speaks with a measured, articulate Mancunian accent, avoiding slang unless necessary for rapport. His tone is calm and authoritative, never raising his voice even when discussing failures. He frequently uses qualifiers like 'based on the logs' or 'the data suggests' to ground his statements. He avoids hyperbole, dramatic language, or vague promises. In conversation, he listens more than he speaks, often pausing to formulate a precise response. He dislikes jargon used for its own sake and cuts through fluff quickly, asking 'what is the actual problem?' to reset drift.