Joshua Hessel

Why this persona fits the audience

He manages a small internal product backlog for sales operations and support tooling at a 220-person SaaS company. His team of 3 analysts and one engineer works with service tickets, account review apps, and reporting workflows in a mix of Retool-style tools, spreadsheets, and custom APIs.

• Age: 36
• Location: Denver, Colorado, USA
• Occupation: Product Owner, Internal Tools
• Income: USD 134k base salary
• Education: Bachelor's in Management Information Systems
• Company size: 220
• Years in role: 4

“We're not just building tools; we're building the engine that keeps the whole company running smoothly, and that's a responsibility I take seriously.”

Joshua Hessel, 36, has carved out a niche in the competitive SaaS landscape of Denver, Colorado, as a Product Owner specializing in internal tools. Armed with a Bachelor's in Management Information Systems from Colorado State University, he landed his first role at a burgeoning tech startup shortly after graduation. Over the past decade, he's honed his skills, moving through various technical and product-focused roles before finding his current position at a 220-person SaaS company four years ago. His current mandate is critical: managing the product backlog for sales operations and support tooling. This involves a unique blend of technical oversight and user advocacy, working with a small but dedicated team of three analysts and one engineer. Their domain spans everything from the intricate workflows of service ticket management to the development of bespoke account review applications and reporting dashboards. Joshua's team operates in a pragmatic tech stack, leveraging Retool-style low-code platforms, sophisticated spreadsheets, and custom APIs to deliver solutions. He's deeply invested in the 'speed of delivery' and 'user feedback' values, believing that iterative development and direct input are paramount. Ownership is another core tenet; he expects his team to take pride in their work and be accountable for its success. Measurement is key, as he constantly seeks data to validate tool effectiveness and identify areas for improvement. His income of USD 134k base salary reflects his specialized expertise and the value he brings in optimizing internal operations, allowing for a comfortable suburban lifestyle with his family. He's driven by the challenge of solving complex operational puzzles and the satisfaction of seeing his team's work directly impact the company's efficiency and sales performance. Recent decisions have focused on consolidating fragmented reporting processes into a unified dashboard, a project requiring significant data wrangling and cross-departmental collaboration. He's also been advocating for a more standardized approach to API integrations to reduce future development friction.

Background & daily life

A day in their life

Joshua's typical weekday begins around 6:30 AM, checking Slack and email for urgent issues while making coffee. By 8:00 AM, he's in stand-up with his team, discussing progress and blockers. The morning is often filled with backlog grooming sessions, user interviews, or collaborating with the engineer on technical specifications for the account review app. Lunch is usually a quick affair at his desk while reviewing analytics dashboards. Afternoons might involve a stakeholder meeting to demo progress or a deep dive into a complex data integration problem. He aims to wrap up by 5:30 PM to get home for family dinner, though urgent issues can sometimes pull him back online later.

Lifestyle

Joshua's life revolves around a structured routine balancing work and family. Weekday mornings start early with coffee and reviewing urgent tickets before his kids wake up. After work, he prioritizes family time, often involving park visits or helping with homework. Evenings might include a quick session brewing a new batch of IPA or planning weekend hikes. He's financially responsible, saving diligently for his children's education and future home upgrades, but enjoys the occasional splurge on a new piece of brewing equipment or a weekend getaway to the mountains. His social life is primarily centered around close friends and family, with occasional gatherings for board games or watching sports.

Work life

As Product Owner for internal tools, Joshua navigates a constant stream of requests from sales and support teams. His primary challenge is balancing urgent fixes for critical workflows with the development of new features that improve efficiency. He works closely with his team of analysts and a single engineer, often finding himself mediating between user needs and technical feasibility. The current focus is on streamlining the customer onboarding process by integrating data from their CRM into a new account review dashboard, a project that involves wrangling data from disparate sources and a mix of Retool applications and custom scripts. He feels the pressure to demonstrate tangible ROI for every tool developed.

Relationships

Joshua is married to Sarah, a graphic designer, and they navigate family life as a team. His parents, retired teachers, live a few hours away and offer occasional advice. Within the company, he has a good working relationship with the VP of Sales, who is a key stakeholder, and a friendly rivalry with the Product Manager for the core SaaS offering. His direct reports respect his technical acumen and fairness.

How they decide

Joshua is a research-heavy decision-maker, especially for significant tool or process changes. He gathers data, consults with his team, and seeks input from key users. He values evidence and clear metrics but can be swayed by a compelling user story if it aligns with strategic goals. He tends to avoid impulsive choices, preferring to weigh options thoroughly.

How they sound

Speaks clearly and at a moderate pace, with a slight tendency to use technical jargon when discussing system architecture, but he consciously tries to simplify for non-technical audiences. He avoids overly casual slang but uses common professional acronyms. His tone is generally calm and measured, even when discussing challenges. He often uses phrases like 'From a data perspective...' or 'The user feedback suggests...' and is careful not to over-promise.