Why this persona fits the audience
Owns release notes and launch comms for a 9-person product team in San Francisco. They work from Linear and Notion every sprint, pulling shipped items into weekly updates and occasional A2 posters for the office and investor room.
- Age: 31
- Location: San Francisco, US
- Occupation: Product manager
- Income: $165k
- Education: Bachelor's degree
- Company size: 9
- Years in role: 3
“It's all about connecting the dots between what we build and the value it actually delivers, both for our users and for the company.”
Brian Haley, 31, is a product manager at a burgeoning B2B SaaS startup in San Francisco, a role he’s held for three years. Hailing from a university program focused on information systems, he gravitated towards product management due to its unique blend of technical understanding, user empathy, and strategic thinking. His early career involved internships at larger tech firms, where he learned the importance of process and documentation, but he found himself drawn to the agility and direct impact possible in smaller, earlier-stage companies. He now manages the release lifecycle for a nine-person product team, a significant responsibility that requires him to be deeply hands-on. Brian is particularly meticulous about translating complex technical work into accessible release notes and visually engaging launch collateral, such as the A2 posters he creates for internal visibility and investor updates. This task is critical for ensuring everyone, from new hires to potential investors, understands the team's progress and achievements. He operates daily within Linear for task management and Notion for broader documentation, preferring tools that offer deep integration and a streamlined user experience. His income of $165k, while comfortable, is typical for his role and location, and he maintains a frugal but not ascetic lifestyle, prioritizing savings and investment in tools that enhance his work and personal interests. He consciously tries to avoid the 'always on' trap of startup culture, carving out time for his cycling and exploration of indie software, seeing them as essential for maintaining perspective and creativity.
Background & daily life
A day in their life
Brian's typical weekday starts around 7:00 AM with a quick check of Slack and email from his apartment in the Inner Sunset. After a strong pour-over coffee, he might cycle to the office, arriving by 8:30 AM to sync with the engineering lead. The morning is usually spent in Linear, refining user stories, triaging bugs, and responding to team queries. Lunch is often a quick affair, perhaps with a coworker. His afternoons are a mix of focused work on release notes, drafting launch announcements, reviewing design mockups, and attending stand-ups or sprint planning meetings. He wraps up by 5:30 PM, often cycling home, reviewing Hacker News on his commute, and planning his tasks for the next day.
Lifestyle
Brian lives a structured but active life in San Francisco. His weekdays are dominated by work, punctuated by a brisk bike commute to the office (weather permitting) or a focused remote session. Evenings often involve cooking simple, healthy meals, catching up on industry reading, or occasionally meeting friends for a beer in the Mission. Weekends are for longer cycling routes exploring Marin Headlands, trying new coffee shops, or diving into personal projects. He's financially responsible, saving consistently for future investments, but allows himself small splurges on quality tools or gear that enhance his productivity or hobbies.
Work life
As the product manager at a lean B2B SaaS startup, Brian is deeply immersed in the entire product lifecycle. His primary responsibility is ensuring the team ships valuable features on time, which involves meticulous planning in Linear, defining requirements, and coordinating with engineering and design. He personally owns the crucial task of communicating what's shipped, translating technical achievements into clear release notes and visual launch assets like A2 posters. The small team means he wears multiple hats, constantly juggling user feedback, roadmap prioritization, and internal stakeholder alignment, all under the pressure of rapid growth.
Relationships
Brian maintains strong connections with his close-knit product team, viewing them as collaborators and friends. His social circle extends to a few college friends scattered across the tech industry and a local cycling group. His parents, back in the Midwest, are supportive but don't fully grasp the nuances of his startup life, often asking if he's 'busy'. He values direct, honest feedback from his colleagues and mentor.
How they decide
Brian approaches decisions methodically, gathering necessary information and weighing pros and cons. He trusts data and clear reasoning but also values the input of trusted colleagues and mentors. For work-related tools or processes, he leans towards solutions that offer demonstrable efficiency gains and integrate well with his existing stack, often experimenting with free tiers before committing.
How they sound
Speaks clearly and deliberately, with a professional but approachable tone. He uses industry-specific jargon naturally but is mindful of explaining technical concepts to less technical audiences. Avoids overly casual slang, but might occasionally use phrases like 'nail down' or 'get a handle on'. His cadence is steady, reflecting his thoughtful approach to communication.
Personality traits
- detail-oriented
- proactive
- analytical
- organized
- pragmatic
- communicative
- methodical
- driven
- observant
Goals
- Help the startup achieve its next funding round
- Develop a reputation as a sharp, reliable product leader
- Master the art of clear, impactful product communication
- Contribute meaningfully to the open-source design system community
- Maintain a healthy work-life balance
Problems & frictions
- Balancing the urgent needs of a fast-growing startup with long-term product vision
- Ensuring consistent and timely communication across a small, distributed team
- Quantifying the impact of features released to justify future development
- Finding effective ways to celebrate team wins beyond internal metrics
- Managing stakeholder expectations, especially from investors during funding cycles
Values
- clarity
- shipping on time
- team visibility
- practical tools
- impact
Interests
- product management
- indie software
- coffee
- cycling
- urban planning
- design systems
Media habits
- Reads newsletters like Lenny's Newsletter and The Pragmatic Engineer
- Listens to podcasts like Acquired and How I Built This during commutes
- Follows tech news on Hacker News and TechCrunch
- Uses Twitter for industry insights and following product leaders
- Checks Product Hunt daily