Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches Episode: Business Analyst to Product Owner—More Than a Title Change | Joel Tekven
Release Date: July 18, 2025
Host: Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner
Guest: Joel Tekven

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Joel Tekven to discuss a critical transition within Agile teams: moving from a Business Analyst (BA) role to a Product Owner (PO) role. Joel shares his experiences, highlights common pitfalls, and offers practical strategies to ensure a successful transformation beyond just a title change.

Identifying the Anti-Pattern: BA to PO Transition

[01:21 - 02:34]

The conversation kicks off with Vasco introducing the topic of the day: the often problematic transition from Business Analyst to Product Owner. Joel identifies a prevalent anti-pattern in Agile teams:

“I think the worst product owner anti pattern I see is a BA who got a role change, a title change, and now they're a product owner. Except they don't know how to be a product owner.” ([01:50])

Joel emphasizes that merely changing titles without equipping individuals with the necessary skills and mindset leads to ineffective product ownership. Organizations sometimes mistakenly assume that a BA’s analytical skills seamlessly translate to the broader responsibilities of a PO, which isn't always the case.

Common Behavioral Shifts and Challenges

[02:34 - 05:41]

Vasco prompts Joel to delve deeper into the specific behaviors that hinder BAs transitioning into POs. Joel elaborates on the differences between the two roles:

“One of the biggest ones is that they really see themselves as a scribe and not a visionary.” ([03:29])

Joel points out that former BAs often focus heavily on managing tools like Jira, writing user stories, and handling administrative tasks. However, they may lack the visionary aspect of a PO, such as setting a product vision, understanding customer needs, and prioritizing features based on strategic metrics rather than gut feelings.

Vasco adds that this replication of the BA role within the PO context leads to overlooking critical PO responsibilities like defining the product vision and understanding the target customers. Joel agrees, highlighting the ease with which individuals revert to familiar BA habits when unsure about their new PO duties.

Strategies to Facilitate the Transition

[05:41 - 08:21]

Addressing the challenges, Vasco asks Joel about effective methods to help former BAs embrace their new roles as POs. Joel shares practical tools and techniques:

“One of the things...is to give them a format when they think about their epics and features that, starting with a hypothesis statement...” ([05:59])

By introducing structured frameworks, such as hypothesis statements, Joel helps new POs focus on defining the problems they aim to solve, formulating hypotheses for solutions, and establishing metrics to measure success. This approach encourages strategic thinking and aligns the team’s efforts with the overall product vision.

Joel also mentions the importance of elevating the conversation beyond story-level tasks to encompass higher-level strategic planning. This shift in perspective is crucial for POs to effectively guide their teams towards long-term goals.

Exemplary Product Ownership: A Case Study

[08:21 - 11:49]

To illustrate the qualities of an effective PO, Joel recounts his experience working with an outstanding Product Owner in a healthcare company:

“He really understood that vision piece of it. He understood the need to experiment and how to let that the team needed to figure out how to solve the problem.” ([08:21])

This PO excelled in setting a clear vision, fostering a culture of experimentation, and empowering the team to innovate. Joel praises his ability to remain patient and collaborative, especially when the team struggled to adapt to new methodologies:

“He had patience in letting them get to the next level... We collaborated together on it instead of him expressing that to the team.” ([09:10])

By continuously communicating the product’s North Star and focusing on customer value during sprint reviews, this PO ensured that the team remained aligned and motivated. Joel underscores the importance of such leadership in driving successful Agile transformations.

Balancing Vision and Patience

[11:12 - 12:46]

Vasco and Joel discuss the delicate balance a PO must maintain between being a visionary and exercising patience. While a clear and compelling vision is essential, it can be frustrating when the team doesn't immediately grasp or align with it. Joel explains that effective POs must persistently communicate and reinforce the vision while allowing the team the time and space to adapt:

“It's not an easy transition for them, just like it's not an easy transition for a product owner who's, you know, a retitled B.A.” ([11:49])

This balance ensures that both the PO and the team can navigate the challenges of their new dynamics without losing sight of their collective goals.

Conclusion and Further Engagement

[12:46 - End]

As the episode wraps up, Vasco encourages listeners to connect with Joel on LinkedIn for further insights. He also emphasizes the value of community learning and sharing experiences to enhance Agile practices.

Key Takeaways

1. Role Clarity is Crucial: Transitioning from BA to PO involves more than a title change. It requires a shift from task-oriented activities to strategic vision setting.

2. Avoid Common Pitfalls: Former BAs may overly focus on administrative tasks and tool management, neglecting essential PO responsibilities like defining product vision and prioritizing based on customer value.

3. Implement Structured Frameworks: Using tools like hypothesis statements can help new POs develop a strategic mindset and align their teams with broader product goals.

4. Exemplary Leadership Inspires Teams: Effective POs demonstrate vision, patience, and collaboration, fostering an environment where teams can thrive and innovate.

5. Continuous Communication Reinforces Vision: Persistently conveying the product’s North Star and customer value ensures that the team remains aligned and motivated, even during challenging transitions.

Notable Quotes

• “I think the worst product owner anti pattern I see is a BA who got a role change, a title change, and now they're a product owner. Except they don't know how to be a product owner.” — Joel Tekven ([01:50])

• “One of the biggest ones is that they really see themselves as a scribe and not a visionary.” — Joel Tekven ([03:29])

• “One of the things...is to give them a format when they think about their epics and features that, starting with a hypothesis statement...” — Joel Tekven ([05:59])

• “He really understood that vision piece of it. He understood the need to experiment and how to let that the team needed to figure out how to solve the problem.” — Joel Tekven ([08:21])

• “It's not an easy transition for them, just like it's not an easy transition for a product owner who's, you know, a retitled B.A.” — Joel Tekven ([11:49])

Further Resources

For more insights and to connect with Joel Tekven, listeners are encouraged to visit his LinkedIn profile. Additionally, explore the Scrum Master Toolbox membership for access to over 700 hours of Agile content, live workshops, and a community of like-minded practitioners.

This episode offers valuable lessons for organizations and individuals navigating the transition from Business Analyst to Product Owner. By recognizing common challenges and implementing strategic frameworks, teams can ensure that their Product Owners are not only well-titled but also well-equipped to drive product success.