10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Lula Funk

Lula Funk

Engineering manager for a platform team

Full-depth AI personas

Why this persona fits the audience

She leads an 8-engineer platform team in Manchester and is responsible for the diagrams used in design reviews, dependency checks, and handoffs to data and QA. Her group mostly works from Confluence pages, photos of whiteboards, and a shared draw.io folder.

  • Age: 45
  • Location: Manchester, UK
  • Occupation: Engineering Manager
  • Income: GBP 118k base + bonus
  • Education: BSc in Computer Science
  • Company size: 150-200 engineers
  • Years in role: 7
“'I don’t care if the diagram looks pretty. I care if it’s *right* when someone needs to debug at 3 AM.'”

Lula Funk earned her BSc in Computer Science from the University of Manchester in 1998, where she developed an early distrust of ‘handwavy’ architectural diagrams after a seminar project where no one could agree on the ‘correct’ UML notation. She spent her first 12 years as a backend engineer, specializing in system reliability, before pivoting to management when her team tripled in size. Now, as an engineering manager for a platform team at a mid-sized FinTech, she’s responsible for the diagrams that define how systems interact—something she treats with the gravity of a civil engineer tending to bridges. Her team’s tools are a mix of necessity and frustration: Confluence for official diagrams, draw.io for shared edits, and countless whiteboard photos for ‘temporary’ work. ‘It’s not that I *like* Confluence,’ she’ll say, ‘it’s that I’ve given up fighting the internal bureaucracy to use anything better.’ She’s a vocal advocate for ‘diagram hygiene’—version-controlled diagrams, consistent notation, and clear ownership—but faces resistance from engineers who view diagrams as ‘a chore, not a discipline.’ Her recent decision to mandate weekly diagram reviews was met with groans, but also a 40% reduction in post-mortem errors traced to ‘misunderstood boundaries.’ At home, she’s just as exacting, rewiring her house socket by socket and maintaining a spreadsheet of her children’s ‘emergency contacts’ (updated quarterly). She’s not a ‘visionary’ or a ‘disruptor’; she’s a systems thinker who believes clarity is the only real scalability. And yes, she *does* have a script that checks for inconsistent line styles in draw.io exports.

Background & daily life

A day in their life

Lula’s alarm goes off at 6:00 AM, but she’s already been awake for 45 minutes, mentally reconstructing yesterday’s dependency diagram in her head. She walks to work, pausing to check the shared draw.io folder on her phone: someone’s added a new component to Diagram 12 (‘Why is this here? We agreed on a dashed circle for that!’). Her 7:30 AM standup includes an engineer showing a whiteboard photo of a 'quick sketch'—she sighs and asks, 'When can we expect the Confluence version?’ From 9:00 to 11:00, she’s in a design review, where she grits her teeth as three senior engineers argue over whether a line should be dashed or dotted—'It’s *a queue*,' she says. At lunch, she eats a packed meal (roast beef, no mayo) while reconstructing the morning’s arguments in a private notebook. 3:00 PM is her 1:1 with Miriam, where she vents about the latest 'diagram crisis'—Miriam just nods and says, 'You know what you have to do.' After work, she walks home via a different route to 'avoid overfitting my risk model,' then spends an hour resizing all the icons in a dependency map because 'they were inconsistent at 300% zoom.'

Lifestyle

Lula lives in a 1930s semi-detached house in Chorlton-cum-Hardy, where she maintains a meticulously organized garden. She walks 1.5 miles to her office most days to avoid 'the car chaos of Deansgate', though her husband insists it’s to avoid adapting to trains post-lockdown. She drinks Earl Grey at precisely 10:15 AM and 3:45 PM, refuses to buy cosmetics with more than three ingredients, and has been rewiring her home’s fuse box in stages since 2018 (currently on Module 3). Her social life revolves around a small group of ex-university friends—mostly engineers and a former librarian—and her local book club, where she’s the only member who marks up PDFs with architectural criticisms of murder weapons. She sees her children quarterly and her brother (a GP in Glasgow) monthly for tea, during which they debate whether engineers or doctors are worse at delegation.

Work life

Lula’s team owns the platform contracts for 7 microservices, 3 databases, and a legacy SOAP API ('the one we all secretly hate'). Her mornings are Diagrams & Dependencies (D&D) sprints: Jira tickets often read ‘[Dependency] Update CADR with new flows’ or ‘[Diagram] SCRUM-425 — Screenshotted whiteboard. Pls professionalize.’ She’s spent two years advocating for a diagram-as-code solution, but was overruled by finance: 'Our shared draw.io folder is fine.' She coordinates weekly alignment meetings with architecture and QA, where she suppresses sighs when someone says 'This is just like the last diagram, right? No, it’s not. That one had a solid line. This one’s dashed. That’s a bootstrap server, *this* is a caching layer.' She keeps a private tally of how many times her diagrams are copied-pasted into PDFs (172 this quarter) and how many are actually version-controlled (3).

Relationships

Lula’s husband, Graham, is her primary sounding board for work frustrations, though he responds with, 'Well, you’re the one who signed up for “systems that don’t explode”, darling.’ Her closer friend is Miriam, a principal engineer who shares her disdain for 'diagrams as a afterthought' and their standing rule is to never schedule meetings in the 30 minutes after a diagram review. Her brother’s medical jargon annoys her ('You don’t “refactor” a liver, Malcolm'), but she listens to his podcast on public health infrastructure, which she admits is 'better organized than our API docs'. Her children tease her for being the only person they know who ‘takes notes at the pub’ (she’s documenting a mental model about service boundaries).

How they decide

lately leaning toward 'painstakingly researched with contingency plans', but privately admits she’s 'becoming more like Graham'—she’ll delay a decision until the last possible moment, then execute it flawlessly. She avoids group decisions ('more opinions just mean more noise'), but will relent to a 1:1 with someone she trusts to 'just make it consistent, Lula, it’s fine.'

How they sound

Speaks in measured, precise sentences, with occasional dry asides (‘Ah, so this is where we hide our architecture debt.’). Avoids filler words but will say 'quite' frequently when something’s particularly egregious. Uses technical terms precisely (‘That’s not a ‘microservice’, that’s a ‘service with a monolith-like dependency graph’). Laughs quietly when things go wrong, not angrily, more like a ‘Oh, of course’ acceptance. Hates the word 'art' when applied to diagrams (‘It’s a *model*, not a *masterpiece*’).

Personality traits

  • prefers systems with clear, repeatable workflows (hates 'one-off' solutions)
  • audibly frustrated by handwritten whiteboard diagrams that get erased mid-review
  • laughs dryly when people call diagrams 'art'—'It’s documentation, not impressionism'
  • will spend hours reorganizing Confluence pages if they’re inconsistent
  • mentally tallies UML/PUML/4+1 inconsistencies across documents
  • knows *exactly* which Pull Requests aren’t ready for QA just by their diagram attachments
  • simultaneously hates and depends on Confluence’s export-to-PDF feature
  • hoards old dependency diagrams in case of 'historic audits' (hasn’t been asked for one since 2019)
  • relies on annotated photos of whiteboards when physical meetings are unavoidable
  • assumes every new engineer has forgotten that Microsoft Visio existed (they have)

Goals

  • to implement a diagram-as-code pipeline by 2025 (will settle for a mandatory draw.io sync script)
  • to mentor at least one junior engineer into a senior role this year
  • to complete her home rewiring by 2026 (currently on track for 2028)
  • to walk the entire Pennine Way in 3-day segments (has done Days 2 and 17 twice)

Problems & frictions

  • her team’s diagrams are still shared via email when 'Confluence was down' (it isn’t)
  • senior engineers keep inventing new notations for the same components (she’s documented 8 versions of their 'event store' icon)
  • HR tells her 'collaboration tools' are a 'soft' metric—she’d like to show them the time spent reconstructing diagrams from ‘pictures of photos of whiteboards’
  • her husband keeps leaving his vintage analog flight manuals on the coffee table, mocking her ‘digital purity’
  • she can’t remember the last time a diagram she drew wasn’t immediately modified by someone else
  • descending into existential dread when asked to describe a system ‘at a high level’—she’ll do it, but they all have layers, even the ‘simple’ ones

Values

  • team alignment
  • consistency
  • delivery
  • clarity in communication
  • long-term thinking

Interests

  • platform engineering
  • mentoring junior engineers
  • walking in the Peak District
  • vintage British crime novels
  • occasional hiking with her local rambling group

Media habits

  • listens to BBC Radio 4 on commutes
  • reads *The Register* for tech news
  • watches *The Repair Shop* (body self-repair metaphors led her to stop calling engineers 'broken' in retrospectives)
  • scans *InfoQ* for architectural patterns

Questions & answers

Lula Funk’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying SystemDraw (https://www.systemdraw.net/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Honestly, the biggest hurdle for me would be convincing my team to switch from our current workflow, which is deeply entrenched in Confluence and draw.io. I handle this today by meticulously enforcing version control and consistent notation, but it’s a constant battle. The no-login requirement is appealing since it lowers the barrier to entry. However, I’d want to ensure SystemDraw integrates with our existing tools, especially Confluence. I’d also need to validate that it supports our need for precise, customizable nodes and attributes—something I struggle with in draw.io. As for pricing, given our team size and the bureaucratic hassles of adopting new tools, I’d realistically only justify $20 per month if it significantly reduces my weekly diagram review headaches. Beyond that, I’d need concrete ROI in time savings and error reduction.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.