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

Myron Kuvalis

Myron Kuvalis

Engineering manager running retros for a small product team

Full-depth AI personas

Why this persona fits the audience

Manages an 8-person product engineering team in Manchester. Retro notes live in Notion, and he keeps a running log of blocker complaints and postmortem follow-ups after each sprint.

  • Age: 34
  • Location: Manchester, UK
  • Occupation: Engineering manager
  • Income: £92k
  • Education: Master's degree
  • Company size: 15-50 employees (Series B startup)
  • Years in role: 3
“If you can't measure the friction, you're just guessing why the machine is grinding.”

Myron Kuvalis, 34, has spent the last decade transitioning from a pure coder to a guardian of engineering culture. Born in Leeds and educated at the University of Manchester with a Master's in Computer Science, he initially thrived in the solitary depths of backend architecture. However, three years ago, he accepted a management role at a mid-sized fintech startup in Manchester, drawn by the challenge of scaling teams without sacrificing code quality. His income of £92k reflects his seniority, yet he remains frugal, viewing money as a tool for security and freedom rather than status. His professional identity is defined by a paradox: he is deeply collaborative but fiercely protective of his team's 'flow state.' He runs his engineering team with a military-grade precision that borders on obsessive. While the company encourages agility, Myron insists on rigid documentation for post-sprint reviews. He believes that without a 'running log' of every complaint and blocker, the team is doomed to repeat mistakes. This philosophy has led to a unique workspace setup where physical whiteboards track immediate issues, while a highly structured Notion database serves as the long-term archive. Recently, he made the controversial decision to halt a major feature launch to refactor legacy code, citing long-term maintainability over short-term speed. This decision, though unpopular with stakeholders, cemented his reputation as a leader who values craftsmanship above all. Outside of work, Myron channels his need for control into cycling and espresso brewing, hobbies that reward patience and technique. He is not a natural leader in the charismatic sense; he leads by example, by being the most prepared person in the room, and by ensuring that every meeting has a tangible outcome.

Background & daily life

A day in their life

Myron wakes at 6:15 AM to brew coffee and review his digital dashboard, checking overnight build statuses. By 7:30 AM, he is cycling through the rain toward the city center, listening to a podcast on system design. At 9:00 AM, he attends a brief stand-up, quickly identifying a deployment bottleneck. The bulk of his morning is spent reviewing the previous day's sprint data in his personal tracker, cross-referencing Notion entries with his blocker log. After lunch, he holds a one-on-one with a junior developer, focusing entirely on career growth rather than tasks. The afternoon involves clearing administrative roadblocks for the team, often canceling non-essential meetings. He leaves the office by 5:30 PM sharp to cycle home, then spends an hour on a hobby project or preparing for tomorrow's retro facilitation. His evenings are strictly screen-free until late, dedicated to family and relaxation.

Lifestyle

Myron lives in a renovated period property in Chorlton, where he maintains a precise routine. His mornings begin with manual espresso brewing using a V60, a ritual that grounds him before the day's noise. He cycles 30 miles to work twice a week, treating it as active meditation rather than transport. Evenings are reserved for low-stimulation activities: playing complex strategy board games with his partner or tinkering with mechanical watches. Financially, he is conservative, prioritizing a robust emergency fund and investing heavily in personal development tools rather than luxury goods. His social circle is small, consisting mostly of colleagues and childhood friends who respect his need for quiet weekends.

Work life

Managing eight engineers in a high-growth environment, Myron's primary friction point is the chaotic nature of retrospective data. While his team uses Notion for notes, the information is often buried in nested pages, making trend analysis impossible. He personally maintains a separate, rigid log of blockers and post-mortem action items, which he updates daily. His days are a balance of removing impediments and shielding his team from stakeholder chaos. He despises 'meeting bloat' and often cancels calls if they lack a clear agenda. The pressure comes from maintaining code quality amidst rapid feature delivery, forcing him to constantly audit his own management style to ensure predictability without stifling creativity.

Relationships

Myron is married to Sarah, a graphic designer who manages his need for order with her own creative chaos. They have a close-knit group of four other couples from their university days who meet bi-monthly. Professionally, he relies on a mentorship network of three senior directors he met at conferences five years ago. He avoids office politics, preferring relationships built on shared competence and mutual respect rather than social climbing.

How they decide

Highly analytical and risk-averse regarding workflow changes. Myron rarely adopts new tools immediately upon hearing about them. He requires evidence of efficacy, typically through case studies or pilot programs with a defined success metric. He values peer validation from trusted technical leads over marketing claims. Decisions are made slowly but executed with precision once a conclusion is reached.

How they sound

Speaks in a measured, clipped British accent, avoiding slang. Sentences are structured logically, often starting with context before the main point. He uses precise terminology like 'latency,' 'impediment,' and 'throughput' frequently. He rarely raises his voice, even when frustrated, preferring to speak quietly but firmly. He avoids hyperbole ('amazing,' 'terrible') in favor of quantitative descriptions ('a 15% drop,' 'two weeks delayed').

Personality traits

  • meticulously organized
  • reserved but approachable
  • data-driven decision maker
  • protective of team focus time
  • methodical problem solver
  • dislikes unstructured meetings
  • prone to over-preparing
  • values silence as a resource
  • patient under pressure
  • seeks root causes over symptoms

Goals

  • Achieve a state where team velocity is consistent and predictable for three consecutive quarters
  • Develop a fully automated feedback loop for engineering bottlenecks within the next year
  • Complete a century ride on a road bike by age 36
  • Mentor two junior engineers into senior roles within the current fiscal year
  • Reduce meeting time by 20% across the department while increasing output clarity
  • Build a custom home lab server for learning distributed systems architecture

Problems & frictions

  • Retrospective data is fragmented across multiple Notion pages and sticky notes, leading to forgotten action items
  • Difficulty tracking recurring blockers due to a lack of centralized logging against specific sprints
  • Team members struggle to articulate emotional frustrations constructively during group sessions
  • Post-mortem follow-ups often drift into administrative limbo without clear ownership tracking
  • Balancing the need for detailed documentation with the desire for rapid, fluid collaboration
  • Feeling isolated as the sole manager in a remote/hybrid setup without peer support for process refinement

Values

  • craftsmanship
  • predictability
  • quiet focus
  • intellectual honesty
  • systematic improvement

Interests

  • road cycling
  • home espresso
  • strategy board games
  • analog watch collecting
  • architectural photography

Media habits

  • Weekly deep-dive tech podcasts during commute
  • Curated Substack newsletters on software architecture
  • Silent reading of technical documentation late at night
  • Minimal social media usage (mostly LinkedIn for industry news)
  • Physical books on productivity and management theory
  • Local Manchester tech meetup attendance (monthly)

Questions & answers

Myron Kuvalis’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at pfff!!! (https://pfff.me/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This product seems to be aimed at personal catharsis rather than professional tooling, so its value proposition for me is unclear. The pricing is listed in Euros, starting at 1.99 euros/month, which converts to approximately $2.15 USD/month. For that price, I would expect a robust system for tracking and analyzing recurring complaints, perhaps with some AI-driven insights into root causes. However, the core functionality appears to be simply venting. It's difficult to assess a 'no-brainer' price point without understanding the depth of the analytics or community interaction. My maximum would be $5 per month, but only if it demonstrably improved team morale or productivity by surfacing systemic issues.
    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.