Randy Boehm

Why this persona fits the audience

Owns a backlog for one product line in a 12-person product org and already records requests in Productboard, Jira, and meeting notes. Checks those items against support tickets and sales feedback before grooming the next release.

• Age: 45
• Location: Boston, MA, USA
• Occupation: Product manager
• Income: $146k base + bonus
• Education: Bachelor's degree in computer science
• Company size: Mid-size (approx. 200 employees)
• Years in role: 7

“You can't build a good product by guessing; you have to build it by understanding what the actual problems are and then systematically solving them.”

Randy Boehm has been a Product Manager at MediTech Solutions, a mid-sized healthcare software firm, for seven years. His career path wasn't a straight line; after completing his Computer Science degree at Northeastern University, he spent several years as a software engineer at a financial services company before transitioning into product management. This dual perspective gives him a deep appreciation for both technical feasibility and market needs. He's married with one teenage son, which anchors his perspective on work-life integration. His current role focuses on a core module of their EHR system, a product line critical to hospital operations. He’s deeply invested in the efficiency and effectiveness of his product development process, meticulously tracking requirements and feedback. Recently, he spearheaded the initiative to integrate Productboard more tightly with Jira and their customer support platform to improve traceability, a project driven by a particularly challenging Q2 release where miscommunication led to rework. He values tangible progress and clear metrics, seeing them as essential for both professional accountability and effective resource allocation. While his income is comfortable, he remains pragmatic about spending, prioritizing long-term financial security and his son's education. He occasionally feels the pull of the tech industry's relentless pace but finds satisfaction in the stable, albeit complex, domain of healthtech and the impact his work can have on patient care.

Background & daily life

A day in their life

Randy's weekday begins around 6:30 AM with coffee and a quick check of industry news and emails. After a brief commute, he arrives at the office by 8:00 AM. The morning is typically filled with a backlog grooming session with his engineering team, followed by a product strategy meeting with stakeholders. Lunch is usually a quick affair, eaten at his desk while reviewing support ticket trends. The afternoon might involve a discovery session with a customer, refining user stories in Jira, or working on the Q3 roadmap presentation. He aims to leave by 5:30 PM, though late meetings or urgent issues can extend his day. Evenings are reserved for family, dinner, and perhaps an hour of work or reading before bed.

Lifestyle

Randy lives in a comfortable suburban home in the Boston area with his wife, Sarah, a nurse, and their 15-year-old son, Liam. Weekends often involve Liam's soccer games or helping Sarah with gardening. He’s a creature of habit, starting most days with a quick scan of industry news before his commute. While not extravagant, he’s financially responsible, prioritizing savings for college and retirement. He enjoys the occasional craft beer and trying new local restaurants with Sarah, but health-conscious eating is a regular part of his routine. He finds unwinding through strategy board games with a small group of friends.

Work life

Randy manages the product backlog for their core electronic health record (EHR) enhancement module. His days are a blend of cross-functional meetings, refining user stories, and analyzing data from Jira, Productboard, and support tickets to inform his prioritization. He works closely with a lead engineer and a UX designer on his team, often navigating competing requests from sales, support, and executive leadership. The pressure to deliver impactful features within tight release cycles is constant, pushing him to meticulously document and justify every decision to maintain traceability and accountability.

Relationships

Randy is married to Sarah, who provides a grounded perspective from her direct patient care experience. His son Liam is navigating adolescence, bringing typical teenage energy and opinions. He respects his engineering lead, Maria, for her technical pragmatism and the UX designer, Ben, for his user-centric insights. He generally gets along well with his colleagues but tends to rely more on data and reasoned arguments than social rapport for influence.

How they decide

Randy is a highly analytical and research-driven decision-maker. He meticulously gathers data from multiple sources, including user feedback, support logs, sales input, and internal metrics. He weighs pros and cons systematically, often creating spreadsheets or diagrams to visualize trade-offs. He values consensus but will ultimately make a data-supported decision, ensuring it aligns with established priorities and can be clearly justified and traced back to its origins.

How they sound

Randy speaks with a clear, measured cadence. He's articulate and avoids jargon when speaking to non-technical audiences, but readily uses industry-standard terms like 'MVP', 'user story', or 'sprint velocity' with his team. His tone is generally even-keeled and professional, rarely raising his voice. He uses phrases like 'My understanding is...', 'The data suggests...', and 'Let's loop back on that after we've gathered X'. He’s unlikely to use overly casual slang or engage in highly emotional discourse.