Why this persona fits the audience
He owns the corporate CMS for a mid-sized software vendor and works with a 3-person web team plus outside agency support. The site mixes a modern front end with older page templates and a backlog of content fixes, and he already coordinates releases, redirects and search settings with the platform vendor.
- Age: 45
- Location: Austin, TX, US
- Occupation: CMS product owner
- Income: $130k
- Education: BA in business administration
- Company size: Mid-sized (approx. 500 employees)
- Years in role: 5
“You can't build a solid future on a shaky foundation; you've got to shore up what you have before you start adding new floors.”
Alvin Boehm, 45, found his niche in product ownership after a few years in a business analyst role following his BA in Business Administration. The transition felt natural, bridging the gap between business needs and technical execution. He landed at his current mid-sized software company over five years ago, initially focused on improving internal tools before taking ownership of the corporate CMS. Austin’s tech-friendly environment offered opportunities, but also presented challenges with a competitive job market. His income of $130k allows for a comfortable life, but he remains mindful of saving and investing, influenced by a desire for long-term financial security rather than overt displays of wealth. His personal philosophy centers on building robust systems and processes, a trait evident in both his professional work and his approach to home life – he’s the type to research and plan a home renovation meticulously before picking up a hammer. He recently approved a plan to incrementally update several key page templates that have been notorious performance bottlenecks, a decision that required significant negotiation with marketing over scope and timeline. This project aims to improve load times by 15% and reduce the complexity of content updates for common components. He’s also invested significant personal time in documenting the intricacies of their current CMS setup, recognizing that poor documentation has been a recurring source of friction and inefficiency for the team and external agencies.
Background & daily life
A day in their life
Alvin’s typical weekday starts around 6:00 AM with coffee and a quick scan of industry news and his company's internal dashboards. By 7:30 AM, he’s commuting to the office, listening to a tech podcast. His workday is a mix of meetings – stand-ups with his web team, syncs with the marketing department, and calls with the CMS platform vendor – and focused work. He spends significant time in Jira, reviewing tickets, prioritizing the backlog, and documenting release notes. He’ll often block off an hour in the afternoon for deep work on performance metrics or SEO audit analysis, interspersed with fielding urgent requests and troubleshooting minor site issues. He aims to leave by 5:30 PM to make it home for dinner.
Lifestyle
Alvin lives in a comfortable, but not ostentatious, suburban home in Austin with his wife and two teenage children. His routine is fairly structured: early mornings are for coffee and scanning tech news before his commute. Evenings are family-focused, often involving helping with homework or catching up on a show. Weekends might involve yard work, a bike ride along the greenbelt, or tackling a DIY home project. He's financially responsible, saving diligently for college and retirement, and prefers practical purchases over impulsive ones. He values quiet time and efficient solutions to household tasks.
Work life
Alvin's role is a constant balancing act. He juggles strategic planning for the CMS with the daily grind of managing content, coordinating with his small web team and an external agency, and troubleshooting issues. The existing technical debt of older page templates, coupled with a backlog of content fixes, means he's often prioritizing bug fixes and minor enhancements over larger features. He lives by his release calendar, ensuring uptime is always paramount. He spends a good chunk of his day in Jira, Slack, and communicating with the platform vendor, trying to get the most out of a system that's showing its age.
Relationships
Alvin is married to Sarah, a teacher, and they have a son, Ethan (17), and a daughter, Chloe (15). His primary social circle consists of a few close friends from college and some fellow parents from his kids' school. He trusts the opinions of experienced developers and product managers he's worked with over the years.
How they decide
Alvin is a research-heavy, data-informed decision-maker. He prefers to gather all available information, weigh pros and cons systematically, and consult with relevant stakeholders before committing to a course of action. He’s not easily swayed by trends and prioritizes proven reliability and long-term value over quick fixes or flashy features.
How they sound
Speaks clearly and deliberately, with a moderate pace. Avoids excessive jargon unless discussing technical specifics with peers. Tends to be measured and factual, occasionally uses mild humor when discussing frustrations. Doesn't use much slang. His tone is generally calm and professional, but can convey a sense of weariness when discussing persistent technical challenges.
Personality traits
- Methodical
- Detail-oriented
- Pragmatic
- Patient
- Reliable
- Resourceful
- Slightly reserved
- Analytical
- Proactive
Goals
- Achieve a fully modernized and stable CMS platform within two years.
- Develop a more robust content governance strategy.
- Streamline the release process to reduce manual effort and risk.
- Mentor his junior web team members to improve their technical skills.
- Maintain a healthy work-life balance to be present for his family.
Problems & frictions
- Persistent technical debt in legacy page templates slowing down development.
- Inconsistent content quality and formatting across the website.
- Limited budget for major platform upgrades or new tooling.
- Difficulty in accurately forecasting the time required for content migration/fixes.
- Managing conflicting priorities between marketing requests and technical stability.
- Understaffed internal web team requiring heavy reliance on agency resources.
Values
- measurable uptime
- documentation
- speed
- autonomy
- efficiency
- clarity
Interests
- web performance
- SEO
- developer tools
- analytics
- content strategy
- automation
Media habits
- Reads industry blogs (Smashing Magazine, Search Engine Journal)
- Listens to tech podcasts during commute
- Scans LinkedIn for industry news and professional connections
- Uses Reddit for developer-focused discussions (r/webdev, r/seo)
- Watches YouTube tutorials for new tools and techniques