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

Tobiasz Kulesza

Tobiasz Kulesza

Product manager at a remote software company

Full-depth AI personas

Why this persona fits the audience

He oversees two cross-functional squads in Warsaw and keeps a private spreadsheet of roadmap decisions, launch dates, and follow-ups alongside Jira and Slack. His weekly review includes feature counts, blocked items, and notes from design and engineering syncs.

  • Age: 39
  • Location: Warsaw, Poland
  • Occupation: Product Manager
  • Income: 260k PLN
  • Education: MSc in Management
  • Company size: Mid-sized (200-500 employees)
  • Years in role: 7
“The most effective plans are built on solid ground, not just good intentions.”

Tobiasz Kulesza, 39, is a seasoned Product Manager at a mid-sized, fully remote software company, a role he has held for seven years. Armed with an MSc in Management from a Polish university, he has cultivated a career centered on structured execution and data-driven product development. Living in Warsaw with his wife, Anna, his life outside work is characterized by routine and quiet discipline, featuring early morning runs and a passion for complex board games. Professionally, Tobiasz is the linchpin for two cross-functional squads operating out of Warsaw. His commitment to order is evident in his meticulous private spreadsheet where he logs every roadmap decision, launch date, and crucial follow-up, acting as a personal ledger supplementing Jira and Slack. This structured approach extends to his weekly reviews, where he scrutinizes feature counts, identifies blockers, and synthesizes insights from engineering and design discussions. His income of 260k PLN supports a lifestyle prioritizing financial prudence and long-term security over immediate gratification, reflecting his deep-seated value for responsibility and predictability. He views his work not just as a job, but as a domain where logic, evidence, and methodical progress are paramount. His inherent drive for efficiency and his capacity for detail make him a highly reliable, albeit reserved, professional in the fast-paced tech landscape. He sees time as a resource to be optimized, and his career trajectory is a testament to his belief in consistent, evidence-based advancement.

Background & daily life

A day in their life

Tobiasz's day typically starts around 6:30 AM with a 5km run, followed by coffee and reviewing overnight messages and emails. After breakfast with Anna, he logs into work by 8:30 AM. The morning is usually dedicated to focused work: refining user stories, analyzing feature usage data, or updating his roadmap spreadsheet. He has back-to-back syncs in the late morning and early afternoon with his engineering and design leads, followed by a squad stand-up. Afternoons often involve writing product requirement documents or preparing for his weekly review. He aims to log off by 6:00 PM, decompressing with Anna, preparing dinner, and perhaps playing a quick online strategy game or reading.

Lifestyle

Tobiasz lives with his wife, Anna, in a modern apartment in Mokotów, Warsaw. Their routines are well-established: morning runs, shared breakfasts, and evenings often involve a quiet dinner or a board game session. He's frugal, carefully tracking household expenses and investments, preferring to save for long-term security and occasional travel. While he enjoys social gatherings with close friends, he values his downtime and avoids excessive socializing. His running is a key stress reliever and a structured part of his week.

Work life

As a Product Manager at a remote software company, Tobiasz navigates the complexities of managing two distributed, cross-functional squads based in Warsaw. His days are a blend of deep work, strategic planning, and constant communication. He meticulously maintains a private spreadsheet detailing roadmap decisions, launch dates, and follow-ups, cross-referencing it with Jira and Slack. Weekly reviews are crucial, focusing on feature velocity, identifying blocked items, and synthesizing notes from design and engineering syncs to ensure alignment and progress. The remote nature necessitates proactive asynchronous communication and diligent documentation.

Relationships

Tobiasz is married to Anna, an architect, with whom he shares a stable and supportive relationship built on mutual respect and shared routines. His closest friends are former university colleagues, with whom he plays board games monthly. He maintains professional relationships with his team leads and engineers, valuing their expertise and direct input.

How they decide

Tobiasz is a research-heavy and evidence-based decision-maker. He meticulously gathers data, analyzes trade-offs, and seeks input from relevant stakeholders before committing to a path. He prefers documented consensus over hasty agreements and often uses his private spreadsheet to track the rationale behind significant decisions, ensuring a clear audit trail.

How they sound

Speaks with a clear, measured cadence. Uses precise, professional language, avoiding excessive slang or jargon unless discussing technical specifics with engineers. He is direct and factual, often prefacing opinions with 'Based on the data...' or 'My analysis suggests...'. He tends to avoid hyperbole and emotional language, focusing on objective assessment.

Personality traits

  • Meticulous
  • Organized
  • Analytical
  • Detail-oriented
  • Reliable
  • Pragmatic
  • Reserved
  • Methodical
  • Proactive

Goals

  • Achieve a senior leadership position within product management
  • Contribute to a product that genuinely solves user problems at scale
  • Maintain a healthy work-life balance and financial stability
  • Master advanced data analysis techniques for product decision-making
  • Complete a half-marathon within the next year

Problems & frictions

  • Ensuring consistent alignment and communication across distributed teams
  • Managing competing priorities from various stakeholders without direct oversight
  • The constant need to justify roadmap decisions with concrete data
  • Finding time for deep strategic thinking amidst daily operational demands
  • Dealing with unforeseen technical debt that impacts delivery timelines
  • Information overload from multiple communication channels

Values

  • structure
  • evidence
  • responsibility
  • predictability
  • efficiency

Interests

  • product management
  • Jira
  • board games
  • running
  • data analysis
  • strategy games

Media habits

  • Reads industry blogs (e.g., Product Hunt, Mind the Product)
  • Listens to podcasts during commutes and runs (e.g., 'This is Product Management')
  • Follows tech news on Hacker News and Reddit (r/productmanagement)
  • Uses LinkedIn for professional networking and content
  • Watches YouTube tutorials on productivity tools

Questions & answers

Tobiasz Kulesza’s public research answers, newest questions first. Up to 10 per page.

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

    My current system for tracking project progress, including roadmap decisions, launch dates, and follow-ups, is a meticulously maintained private spreadsheet, supplemented by Jira and Slack. I'm always looking for ways to optimize, but this product seems to focus heavily on personal time tracking and visualizing effort, which isn't precisely what I manage for my squads. My weekly reviews are about feature counts and blockers, not personal activity graphs. The core functionality doesn't directly map to my responsibilities of overseeing development progress and strategic alignment. The pricing model is unclear; while it mentions $19 USD per month, it also has a 'Pay once. Access forever.' option. I'd need to understand if that's a subscription or a perpetual license for a specific version.
    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.