product leadership Archives - Scrum Master Toolbox Podcast

Somya Mehra: When Technical Expertise Becomes Product Owner Micro-Management

The Great Product Owner: The Clear Communicator and Dependency Master

Somya worked with an exceptional Product Owner on a project with multiple team dependencies. This PO excelled at clear, direct communication with both stakeholders and the team. They were proactive in stakeholder communication and maintained strong focus on what was needed and why. Their backlog management was exemplary, creating proper epics with comprehensive information including dependencies, enabling the team to easily know who to contact. This approach led to a much more motivated team.

The Bad Product Owner: The Technical Micro-Manager

Somya encountered a technically strong Product Owner whose knowledge became a liability. While technical strength can be beneficial, this PO used their expertise to control the team, telling developers exactly what solutions to implement. Initially, developers accepted this direction, but it escalated to every feature and task. The developers became uncomfortable voicing their perspectives, creating an unhealthy dynamic where the PO’s technical knowledge stifled team autonomy and creativity.

Self-reflection Question: How do you help Product Owners leverage their technical knowledge without falling into micro-management patterns?

The Ultimate Guide to Supporting Product Owners as a Scrum Master

Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Somya Mehra

Somya is a Scrum Master at u-blox with nearly 7 years of IT experience across India and Finland. With experience in Waterfall and Agile models, she leads with empathy and a people-first approach. Somya is deeply interested in human behavior and understanding the motivations behind people’s actions.

You can link with Somya Mehra on LinkedIn.

Marina Lazovic: Leadership Skills Make the Difference for Product Owners

The Great Product Owner: The PO as a Leader

Marina identifies that while product skills are important, it’s leadership abilities that truly distinguish exceptional Product Owners. Great POs demonstrate strong empathy and lead by example, creating an environment where the team feels supported. Marina emphasizes the importance of availability – outstanding Product Owners make themselves accessible to their teams when needed, establishing a presence that goes beyond just attending ceremonies. This leadership through presence and support fosters trust, enabling teams to approach challenges with confidence knowing their PO has their back.

The Bad Product Owner: The PO Who Did Not Understand Their Team

Marina describes a problematic pattern where Product Owners fail to understand their team’s strengths and weaknesses. These POs lack awareness of team composition – not recognizing the balance between senior and junior members or understanding their specific challenges. This blindness leads to unrealistic expectations about what the team can accomplish in a sprint. Marina suggests addressing this by establishing regular sync meetings with the PO to discuss team dynamics and challenges. By helping Product Owners understand team composition, Scrum Masters can bridge this knowledge gap and foster more realistic planning and expectations.

Self-reflection Question: How might you help a Product Owner better understand the unique composition and capabilities of your team without creating an adversarial dynamic?

🚀 Global Agile Summit 2025

Join us in Tallinn, Estonia, from May 18th – 20th, 2025, for an event that will inspire, challenge, and equip you with real-world Agile success stories.

🌍 Connect with global Agile leaders.
💡 Learn practical strategies for impact.
🔥 Break free from Agile fatigue and become a Pragmatic Innovator.

Check Full Program

About Marina Lazovic

Marina is a Scrum Master and Kanban Trainer from Belgrade, Serbia, with nearly a decade in the IT industry. Though not from a technical background, she is passionate about helping development teams and organizations optimize processes and build great products using Agile. She thrives on driving efficiency and fostering collaboration.

You can link with Marina Lazovic on LinkedIn.

Global Agile Summit Preview: Unifying Strategy, Discovery, and Delivery in Product Development With Roman Pichler

In this BONUS Global Agile Summit preview episode, we explore a crucial topic that’s shaping how we approach product development—sometimes in ways that serve us well and sometimes in ways that hold us back.

There’s a growing trend in our industry to explicitly separate strategy, discovery, and delivery into distinct activities or even different teams. On the surface, this seems logical: strategy decides the right thing to do, discovery figures out how to do it, and delivery gets it done. But is this division actually helping us? Or is it creating barriers that make great product development harder?

The Origins of Product Discovery

“I think it’s partly based, at least on Marty Cagan’s work, and his insight that many teams are very much focused traditionally on delivering outputs, on writing code. And I think his original intention was to say, ‘Let’s not worry about creating outputs. Let’s also make sure that what we creating makes sense.'”

Roman Pichler shares insights on how the concept of product discovery emerged as a reaction to teams being overly focused on outputs rather than outcomes. He explains that conceptually distinguishing between product strategy, discovery, and delivery can be helpful—much like organizing clothes into different sections of a wardrobe. However, in reality, these activities must be connected, informing and guiding each other rather than existing as sequential steps.

The Risks of Separating Product Strategy, from Discovery, and from Delivery

“If we have a group of people who takes care of strategic decisions, a different group focusing on product discovery, and another group—the tech team—who focuses on product delivery, and those groups don’t talk as much as they could and should do, then suddenly we have a sequential process and handoffs.”

One of the primary challenges with separating strategy, discovery, and delivery is the risk of creating handoffs between different teams. Roman highlights how this sequential approach can slow down value creation, lead to knowledge loss, and increase the likelihood of introducing mistakes. This separation can create barriers that ultimately make product development more difficult and less effective.

In this segment, we refer to the podcast interview with Tim Herbig on the concept of Lateral Leadership, and how that is critical for product people.

Integrating the Work Streams

“What I usually use as a visualization tool is three work streams: a strategy work stream, a discovery work stream, and a delivery work stream. The strategy stream guides the discovery stream. The discovery stream guides the delivery stream, and then the delivery stream informs the discovery stream, and the discovery stream informs the strategy stream.” Continue reading Global Agile Summit Preview: Unifying Strategy, Discovery, and Delivery in Product Development With Roman Pichler

CTO Series: Mastering the CTPO Role, Katrina Clokie’s Guide to Tech and Product Leadership

In this BONUS episode, we sit down with Katrina Clokie, a seasoned leader in strategy, change management, and building inclusive teams. Katrina shares pivotal moments in her career, offers practical leadership insights, and discusses her role as Chief Technology and Product Officer (CTPO), where she’s balancing innovation with business objectives. Whether you’re an aspiring tech leader or looking to sharpen your leadership toolkit, Katrina’s wisdom will inspire you to embrace growth, resilience, and collaboration.

Defining Moments in Leadership

“Look for roles you can’t fully do yet—it’s the best way to grow.”

Katrina reflects on a transformative moment early in her career when a mentor from the shipping industry encouraged her to seek out challenging roles that would push her growth. This advice set her on the path to engineering management and C-level leadership. She shares how fostering curiosity and pursuing conversations about topics she didn’t yet fully understand has kept her continually learning.

“Ask yourself: where do I feel stretched? That’s often where the best growth opportunities lie.”

The Role of CTPO: Combining Technology and Product Strategy

“We needed both a unified vision and an efficient structure to remain competitive.” Continue reading CTO Series: Mastering the CTPO Role, Katrina Clokie’s Guide to Tech and Product Leadership

BONUS: Mastering Product Management in a Remote World, Insights from Tuple’s Head of Product, Eli Goodman

NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!

In this episode, Eli Goodman, Head of Product at Tuple, shares insights from his extensive experience in software development and product management. Having transitioned from engineering management to product leadership, Eli reveals the key strategies Tuple uses to develop its remote pair programming service, which is trusted by companies like Figma and Shopify. Tune in to discover how Tuple handles remote team dynamics, customer-driven development, and balances tech debt with client needs, all while maintaining a customer-centric focus.

Introduction to Tuple and Why It’s Unique

Tuple, a remote pair programming service designed by engineers, solves a pain point that its founders, all pairing enthusiasts, experienced firsthand. They were unsatisfied with generic screen-sharing tools that disrupted the flow of coding collaboration. Tuple’s product philosophy is about staying “one inch wide, one mile deep” to ensure the tool stays focused on enhancing the pairing experience without getting in the way.

“The details matter. Generic screen-sharing tools just don’t cut it for productive pairing.”

Managing a Remote Team at Tuple

Managing a distributed team across the U.S. and Europe comes with its challenges. Eli highlights the importance of alignment and ensuring everyone is on the same page, despite working remotely. He emphasizes the role of Product Owners as “connective tissue” and the power of connecting team members with key initiatives. Through personal conversations, Eli uncovers what motivates his team, allowing him to support them without micromanaging.

“What makes you proud? What brings you shame? Understanding these emotions helps uncover what drives our team.”

Ensuring Effective Communication in a Remote Environment

Effective communication is the backbone of remote work, and Eli shares some of the practices that have helped Tuple’s team stay aligned and collaborative. From using spontaneous pairing sessions to fostering a culture of checking in, Tuple has created a remote work environment where conversations are naturally sparked, and collaboration is effortless.

“We have more space in our schedules for spontaneous pairing, which keeps collaboration flowing.”

Lessons Learned from Pairing Remotely

One of the key insights Eli shares is how Tuple has evolved its remote pairing process. In the past, pairing might have felt like a formal meeting, but now it happens more spontaneously. Tuple’s app facilitates this by offering the metaphor of a phone call—engineers can call each other at any time, making collaboration easy, especially when someone is deep into a task and needs quick support.

“At Tuple, engineers only have three meetings a week, leaving the rest of the time open for pairing and creative work.”

Pairing Beyond Programming Tasks

While pairing is typically associated with programming, Eli explains how Tuple uses pairing for other activities, like design or planning sessions. This practice has extended beyond coding, fostering a culture where team members collaborate on various tasks that benefit from shared perspectives and live problem-solving.

“We’ve expanded pairing beyond coding, using it for activities like design reviews and project planning.”

Balancing Customer Feedback with Product Vision

Responding to customer feedback is vital, but it can also lead to losing focus. Eli explains how Tuple balances this by capturing as much feedback as possible, using tools like Product Board to keep track of customer requests. However, instead of building every requested feature, Eli focuses on synthesizing broader patterns and emotional triggers that align with Tuple’s long-term vision.

“Focus on discovery as a product person. Understand the emotional context behind customer feedback—that’s what drives great products.”

Tuple’s Ideal Customer and Core Value

Tuple’s ideal customers are teams that value deep collaboration through pair programming. The platform’s most important offering is the ability to make remote pairing seamless and intuitive, something traditional tools fail to deliver.

“Tuple is built for teams that believe in the power of collaboration and want a tool that enhances their pairing experience, not disrupts it.”

Roadmapping: How to Prioritize the Right Work in Product Development

Looking ahead, Eli shares Tuple’s plans to continue investing in quality and lowering the barriers to remote pairing. One exciting potential direction includes creating a “social layer” within the app to help users feel more connected with their teammates. Another idea is incorporating non-human pairing agents that could assist with specific tasks.

“We want to see if we can make it feel like you’re right there with your teammates, lowering the barriers to start pairing.”

Recommended Resources

Eli recommends The Mom Test by Rob Fitzpatrick, a must-read for anyone working in product management. The book teaches how to talk to customers in a way that gets honest, useful feedback rather than polite responses that don’t help improve the product.

“I thought caring about people was enough to talk to customers, but The Mom Test taught me what not to do during customer interviews.”

About Eli Goodman

Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.

You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.