Why this persona fits the audience
He coordinates delivery for a 14-person Denver web agency. Engineering notes live in GitHub wiki pages and markdown files inside repos, while non-technical handoffs are captured in shared Docs so designers, account staff, and developers can all reference the same steps.
- Age: 36
- Location: Denver, Colorado, USA
- Occupation: Technical project manager
- Income: USD 108k base salary
- Education: Bachelor's degree in computer science
- Company size: 14 people
- Years in role: 7
“If we don't document it clearly, it's like it never happened. We're building knowledge, not just websites.”
Bernard Blanda's journey into project management was a natural evolution from his computer science degree. He spent his early career as a full-stack developer, where he repeatedly encountered the friction caused by poorly documented processes and requirements. This firsthand experience fueled his passion for creating order and clarity within development workflows. He joined his current web agency seven years ago, initially as a senior developer, but quickly gravitated towards the project management side due to his knack for organization and communication. He found that by proactively managing information flow, he could significantly reduce bottlenecks and improve team morale. His approach is rooted in the belief that well-maintained documentation is not a bureaucratic burden but a critical asset for team efficiency and knowledge retention. He recently championed a minor internal policy shift, reinforcing the expectation that all design mockups and critical client feedback, even those shared verbally in meetings, must be summarized and linked within their respective project's Google Doc, ensuring a single source of truth accessible to everyone, regardless of their technical background. This commitment to structured delivery extends to his personal life, where he meticulously plans household projects and financial goals with his wife. He sees his role as facilitating seamless execution, ensuring that the collective intelligence of the team is captured, accessible, and leveraged effectively, rather than being lost in email threads or whispered hallway conversations. His focus is always on predictable outcomes and fostering a sense of shared understanding across all stakeholders.
Background & daily life
A day in their life
Bernard's typical weekday begins around 6:30 AM. After a quick shower and coffee, he scans Hacker News on his phone while his wife makes breakfast. By 7:30 AM, he's usually on his commute, listening to a tech podcast. He arrives at the office by 8:15 AM, checks his email and Slack, and attends a daily stand-up with the development team at 9:00 AM. The rest of his morning is spent in project planning meetings, reviewing GitHub pull requests for documentation updates, and answering client emails. Lunch is usually a quick affair at his desk, often a packed meal. The afternoon involves more meetings, troubleshooting with developers, and updating project status reports, aiming to wrap up by 5:30 PM.
Lifestyle
Bernard lives with his wife in a modest but well-maintained townhouse in Denver's Platt Park neighborhood. They prioritize experiences over possessions, saving for travel and home improvements. His routine involves an early start, a quick breakfast, and a commute that allows him to catch up on tech news via podcasts. Weekends are split between DIY projects around the house, hiking in the nearby foothills, and trying out new breweries with friends. He maintains a disciplined approach to personal finances, preferring to plan and save for larger purchases.
Work life
As a Technical Project Manager at a 14-person web agency, Bernard is the linchpin for project delivery. His days are a constant juggle of client communications, developer task management, and ensuring technical documentation stays current. He champions the use of GitHub for engineering artifacts, believing strongly in keeping code-related knowledge close to the source. For less technical aspects, like design handoffs or client requirements, he relies on Google Docs, meticulously organizing them for easy access by designers, account managers, and developers. The pressure is constant, driven by tight deadlines and the need to maintain client satisfaction while keeping the engineering team focused and unblocked.
Relationships
Bernard is married to Sarah, a graphic designer, who offers a valuable non-technical perspective on his work. His close circle includes a few former college classmates who are also in tech, providing a sounding board for professional challenges. He's respected by his team for his organized approach, though some find his insistence on documentation a bit much at times.
How they decide
Bernard is a deliberate decision-maker. He gathers information from multiple sources, weighs pros and cons systematically, and often seeks input from trusted colleagues or his wife for major personal decisions. He's not prone to impulsive choices and prefers to have a clear understanding of potential outcomes before committing.
How they sound
Bernard speaks with a clear, measured cadence. He tends to be articulate and avoids excessive jargon with non-technical people. In technical discussions, he's precise and uses industry terms naturally. He avoids overly casual slang but is friendly and approachable. He often uses phrases like 'From a process perspective...' or 'To ensure we have a shared understanding...' He rarely raises his voice, even under stress.
Personality traits
- meticulous
- organized
- detail-oriented
- analytical
- calm under pressure
- proactive
- collaborative
- methodical
Goals
- Achieve greater predictability in project timelines
- Mentor junior members of the development team
- Streamline internal knowledge sharing processes
- Contribute to open-source projects in his spare time
- Eventually move into a more senior technical leadership role
Problems & frictions
- Information silos forming between technical and non-technical teams
- Difficulty in quickly onboarding new team members to project histories
- Ensuring consistency in documentation across disparate tools
- Managing scope creep without alienating clients
- Balancing urgent client requests with long-term technical debt reduction
Values
- structured delivery
- shared understanding
- predictable execution
- efficiency
- clear communication
Interests
- web development
- team coordination
- documentation habits
- agile methodologies
- cloud infrastructure
Media habits
- Reads tech blogs (e.g., Hacker News, Smashing Magazine)
- Listens to tech podcasts during commute
- Uses LinkedIn for industry news and connections
- Follows key figures in web development on Twitter
- Occasional participation in online forums