Rethink Your Understanding

This episode explores a needed shift in how software teams define when work is actually complete. Traditionally, “the definition of done” has meant that a feature was coded, tested, and released to production.The AI hosts discuss my perspective that this definition is incomplete because it focuses on delivery activity rather than customer or business impact.A more mature approach starts with anticipated outcomes and closes the loop after delivery to understand whether the work achieved its intended result. By connecting workflow with realization, organizations can move beyond output and turn delivery into learning, evidence, and strategic value.Link to the article: The Real Definition of Done, originally published April 14, 2026.Connect with me on LinkedIn

Today’s conversation explores why enterprise AI adoption should be treated as a system-wide transformation rather than simply a tool for faster coding.The AI host discusses how AI acts as a multiplier, strengthening organizations with mature delivery systems while exposing risk, defects, and fragility in weaker ones. The episode highlights the importance of AI literacy, strong DevOps practices, human accountability, and a full value stream mindset.At its core, this conversation challenges leaders to look beyond coding productivity and ask a bigger question: Is their operating model strong enough to amplify AI? AI will not fix a broken delivery system. It will reveal the truth of how an organization actually delivers value.Link to the article: AI Is a Multiplier, originally published April 09, 2026.Connect with me on LinkedIn

In this episode, the AI hosts explore why the agentic era is shaping up to be more than another AI feature wave.As software begins to act on behalf of users, engineering and product leaders may need to rethink the systems beneath the interface, from data quality and secure APIs to durable state, long-running workflows, and human approval checkpoints.They discuss why trust will likely build gradually, starting with lower-risk tasks before expanding into higher-stakes transactions. The bigger idea is simple: this looks more like a major systems shift, similar to cloud or continuous delivery, than a surface-level product enhancement.Link to the article: Software for Humans, Systems for Agents, originally published April 06, 2026.Connect with me on LinkedIn

In this episode, the AI hosts unpack my recent career reflection article, Staying Was the Hard Move, and the counterintuitive truth that long tenure doesn’t have to mean stagnation.They explore what it actually takes to lead through the “hard middle” of digital transformation: modernizing legacy architecture without breaking customer trust, scaling engineering practices through years of growth, and evolving from tactical management into executive leadership focused on team outcomes.It’s a story about compounding impact, how resilience, culture, and sustained reinvention can become the real advantage.Link to the article: Staying Was the Hard Move, originally published February 28, 2026.Connect with me on LinkedIn

I keep seeing “Agile is dead” headlines, now repackaged for the AI era. My take: AI isn’t killing Agile. AI is illuminating constraints that were already in the value stream.AI can do market research, write documentation, write code fast - it can’t take accountability. As AI compresses execution time, rebundles responsibilities, and enables smaller teams with faster release cycles, the real work shifts to human judgment: decision-making, validation, security, governance, and operating safely in production.This episode reframes Agile and agility as an enduring capability, and explores what must evolve when software delivery accelerates dramatically with AI.Link to the article: Agile Isn’t Dead and AI Isn’t Killing It Either, originally published January 24, 2026.Connect with me on LinkedIn

AI is now table stakes in software engineering hiring, but it is also warping the signals we used to trust.In this episode, the AI hosts cover my article about a growing pattern I call “AI-fluent, fundamentally lost”: candidates who can produce impressive output with prompts, yet struggle to explain the logic, constraints, and architectural trade-offs behind what they ship. The result is a new kind of risk: “glass cannons” that look productive fast, but can drive long-term maintenance cost and technical debt when fundamentals and judgment are missing.They cover the arguments for a more durable hiring approach that evaluates both system-level reasoning and AI-assisted execution, treating AI as a productivity accelerator, not a replacement for critical thinking.Link to the article: AI Fluent, Fundamentally Lost, originally published December 07, 2025.Connect with me on LinkedIn

In this episode, we unpack a new challenge in software hiring: AI is boosting productivity while also creating an illusion of mastery. Candidates can generate impressive AI-assisted code, yet struggle when the conversation moves to fundamentals like composition vs. inheritance, tradeoffs, and architectural decision-making. The result is a distortion of traditional hiring signals, where output can mask gaps in understanding.The AI hosts dig into why fundamentals still matter most in enterprise systems, where reliability, durability, and accountability matter more than raw speed. Great engineers don’t just produce code, they can debug it, validate it, and challenge AI-generated work with sound judgment. We close with what hiring practices must evolve to measure next: architectural reasoning and system-level decision-making, the areas where AI can assist, but not substitute.Link to the article: When AI Isn’t Enough, originally published November 29, 2025.Connect with me on LinkedIn

This episode breaks down the Product Operating Model and what it really takes to succeed in a modern software organization.The AI hosts explore why POM is not a plug-and-play framework, but a system that only works when architecture, funding, and team design actually support long-lived product ownership. We clarify the most common misconceptions, from the belief that POM replaces DevOps to the myth that it calls for larger teams, reframing the model around small, empowered groups owning a complete slice of value.They also discuss why shifting from project funding to product funding is essential, and how Value Stream Management provides the visibility needed to understand how work truly flows across the organization. If you’re trying to implement POM or make sense of the friction around it, this episode gives you a clear, practical view of what the model demands and how to make it work in your unique context.Link to the article: When the System Fits, the Product Operating Model Works, originally published November 27, 2025.Connect with me on LinkedIn

This episode explores why modern engineering organizations should move beyond activity metrics and project thinking and adopt a system built on measurable business outcomes. The AI hosts break down how Value Stream Management and the Product Operating Model work together to give teams long-lived ownership, product margin accountability, and the visibility needed to surface friction, align priorities, and understand where value is actually created.They also examine the leadership shift required to make it all work. Flow metrics show how efficiently teams deliver, Realization metrics show whether that delivery matters, and AI is rapidly amplifying both by revealing bottlenecks and opportunities in real time. For leaders navigating transformation, this conversation shows how to rethink your operating model and unlock the performance your organization is capable of.Link to the article: Why Value Stream Management and the Product Operating Model Matter (and What Comes Next), originally published November 05, 2025.Connect with me on LinkedIn

In this episode, The Price of Alignment, we explore what happens when innovation meets bureaucracy. When a large, centralized organization acquires a smaller, agile one, the push for alignment and consistency can come at a steep cost.Drawing from the story of two companies, “LegacyTech” and “AgileWorks,” we examine how forcing uniform management models onto autonomous, microservice-based teams can unravel the very agility and speed that made them valuable in the first place.The conversation dives into Conway’s Law, bounded contexts, and the critical leadership lesson every executive should learn before integrating two very different worlds of software delivery.Link to the article: The Price of Alignment, originally published October 21, 2025.Connect with me on LinkedIn

Today's conversation is a short follow-up to season 2, episode 48. In this episode, Beyond the Beyond: AI Across the Value Stream, we explore how artificial intelligence is reshaping software delivery, not as a magic fix, but as a mirror reflecting the strength of your existing systems.Drawing insights from the 2025 DORA Report and emerging Software Engineering Intelligence trends, this episode unpacks why AI’s real potential lies in amplifying disciplined engineering practices and end-to-end visibility.We’ll examine how leaders can move beyond creation and release metrics to apply AI across the full value stream, from idea to operation, turning insight into flow, and flow into measurable business impact.Link to the article: Beyond the Beyond Delivery: AI Across the Value Stream, originally published October 11, 2025.Connect with me on LinkedIn

When companies remove Agile Leaders, roles like Scrum Masters or Agile Delivery Managers, they often assume the system will self-regulate. But what really happens when no one is accountable for team health, continuous improvement, or flow?In this episode, the AI hosts unpack Phil's article about the quiet erosion of agility inside modern organizations, where well-intentioned efficiency moves end up dismantling the very disciplines that make agile work. Drawing from real-world transformations, he argues that while frameworks fade, the mindset of agile leadership must endure.Link to the article: What Happens When We Eliminate the Agile Leader?, originally published October 09, 2025.Connect with me on LinkedIn

In this episode, the AI hosts explore how artificial intelligence might reshape the very design of software teams. The “two-pizza rule” once defined how agile, cross-functional teams operated, but AI is changing what small and effective really means.As AI and automation expand what individuals and small teams can achieve, leaders must rethink the scale, structure, and collaboration required. We unpack what this shift means for engineering management, decision-making speed, and value delivery, and how organizations can use AI not just to optimize code, but to redefine how high-performing teams operate in the era of intelligent systems.Link to the article: From Two Pizzas to One: How AI Reshapes Dev Teams, originally published October 02, 2025.Connect with me on LinkedIn

AI’s full potential in software delivery isn’t in writing code faster, it’s in transforming the entire value stream. In this episode, the AI hosts explore why most delays happen in ideation and release, not coding, and how AI applied narrowly to delivery can actually amplify dysfunction. Drawing on insights from Mik Kersten, Laura Tacho, John Cutler, Atlassian’s 2025 AI Collaboration Report, and the DORA 2025 findings, we discuss how leaders can use Value Stream Management and flow metrics to measure AI’s true impact, reduce systemic waste, and accelerate idea-to-value across the enterprise.Link to the article: Beyond Delivery: Realizing AI’s Potential Across the Value Stream, originally published September 30, 2025.Connect with me on LinkedIn

In this episode, our AI hosts dive into Smarter Pull Requests: Balancing AI, Automation, and Human Review, a handbook redefining how teams approach code reviews in the age of AI. The framework shows how to integrate AI and automation responsibly, ensuring speed without sacrificing human judgment on quality, security, and design.We cover rules files, evidence-based PR templates, and AI gate checks with tools like GitHub Copilot and CodeRabbit, all reinforced by CI pipelines. These practices raise the baseline of consistency while letting reviewers focus on architecture and business alignment.We’ll hear how AI reinforces, rather than replaces, human accountability in code review.Link to the article: Smarter Pull Requests: Balancing AI, Automation, and Human Review, originally published September 28, 2025.Connect with me on LinkedIn

This episode takes you inside the evolving role of a VP of Engineering — far beyond a standard job description.The AI hosts discuss why the role is highly contextual, shaped by company size, leadership culture, and organizational maturity. I share the core accountabilities I’ve been held to: ensuring software quality and resilience, fostering people engagement, retaining and developing talent, and building the skills teams need to stay competitive.The conversation also explores the VP’s strategic importance in business alignment, global talent management, and transformation initiatives, while contrasting the role with that of a CTO. Finally, we touch on the personal evolution required to succeed — developing V-shaped skills, mentoring leaders, and balancing the rewards of culture-building with the challenges of tough decisions.Link to the article: So, What Does a VP of Engineering Do?, originally published August 21, 2025.Connect with me on LinkedIn

This episode advocates for a system-wide perspective when adopting AI in software development, extending beyond mere code generation to encompass the entire value stream.Recent studies show initial productivity dips and extra effort with AI tools, but this is just a transitional phase, not a failure of the technology. Robust delivery metrics, like those from SEI tools or Value Stream Management platforms, are key to pinpointing bottlenecks where AI can drive the greatest impact, avoiding indiscriminate application.Ultimately, the conversation advocates for intentional AI adoption grounded in measurable outcomes across all roles within the delivery system, including product, QA, architecture, and even business functions, to achieve sustained competitive advantage.Link to the article: AI in Software Delivery: Targeting the System, Not Just the Code, originally published August 09, 2025.Connect with me on LinkedIn

AI is transforming software engineering, but it addresses only one part of a much larger system. Speeding up code creation doesn’t solve deeper issues like unclear requirements, poor architecture, or slow feedback loops, and in some cases, it can amplify dysfunction when the system itself is flawed. Engineers remain fully responsible for what they ship, regardless of how the code is written. The real opportunity is to increase team capacity and deliver value faster, not to reduce cost or inflate output metrics.The bigger risk lies in how senior leaders respond to the hype. When expectations are driven by buzzwords instead of measurable outcomes, focus shifts to the wrong problems. AI is a powerful tool, but progress requires leadership that stays grounded, focuses on system-wide improvement, and prioritizes accountability over appearances.

In this episode, the AI hosts unpack the growing tension between AI hype and real-world adoption in software delivery.While AI is advancing rapidly, many leaders focus on bold claims, like replacing entire teams, without grounding them in metrics that matter. Leaders find it challenging to determine the right metrics to measure the impact of AI, as well as the success of AI adoption and investments. I challenge this narrative and explore how frameworks like Flow Metrics and developer sentiment can help teams measure AI’s actual impact on speed, quality, and effectiveness.Instead of chasing vanity metrics or using AI as a shortcut to cut headcount, we explore how it can expand capacity and elevate team performance when applied with intention.Link to the article: Leading Through the AI Hype in R&D, originally published July 27, 2025.Connect with me on LinkedIn

In this episode, our AI hosts dive into an article advocating for a radical reevaluation of software delivery commitments, shifting away from rigid, project-based models and “precise” estimates toward a probabilistic, continuous-discovery mindset. Drawing on Vasco Duarte’s insights and the Three Ways outlined in The DevOps Handbook, they explore treating development as a series of adaptive bets, budgeting for change, using experiments as real-time status reports, and empowering end-to-end team ownership to achieve true agility and align work with value streams.Link to the article: Bets, Budgets, and Reframing Software Delivery as Continuous Discovery, originally published June 07, 2025.Connect with me on LinkedIn

This episode explores the complexities of merging two distinct engineering organizational models after an acquisition. It highlights the friction that arises when one part of the organization uses small, self-managed, cross-functional teams with distributed leadership, while the other adheres to a traditional Engineering Manager (EM) model where a single manager oversees people, delivery, and agile practices. The core challenge lies in unifying job titles and responsibilities without disrupting high-performing teams or ignoring the cultural and architectural context that shaped their original effectiveness.True alignment requires prioritizing fit over rigid familiarity and considering a hybrid approach that respects existing strengths and avoids sacrificing autonomy and psychological safety for superficial consistency.Link to the article: When Team Structure Collides with Role Alignment, originally published May 26, 2025.Connect with me on LinkedIn

This episode addresses a common pitfall in software delivery management: using system-level metrics, such as Flow Metrics, to evaluate individual performance. The AI hosts cover how this practice, while logical to some leaders, can damage trust, produce misleading data, and hinder real improvement. The conversation covers using metrics as a tool to help teams improve, focusing on context, collaboration, and actionable steps. The main takeaway is clear: metrics should promote overall improvement, not serve as personal performance scores.Link to the article: We Have Metrics. Now What?, originally published May 11, 2025.Connect with me on LinkedIn

In this episode, The AI hosts explore why teams—unlike individuals—rarely get a performance review, and why that needs to change.Based on my latest article, you'll hear a practical framework designed for Agile and DevOps teams to reflect on how they work, not just what they deliver. We’ll walk through 10 team health dimensions—from collaboration to delivery integrity—and how your team can use them as conversation starters, not scorecards.If you're ready to look beyond metrics like DORA, Flow, and Developer Experience to ask deeper questions about team behavior, this one's for you.Link to the article: A Self-Guided Performance Assessment for Agile Delivery Teams, originally published May 03, 2025.Connect with me on LinkedIn

In this episode, the AI hosts explore my latest article on evolving our approach to Value Stream Management (VSM) — which we originally adopted to bring greater visibility to our Agile, Lean, and DevOps efforts. But while preparing for a conversation with an industry leader about the Product Operating Model (POM), I had a realization: we weren’t just managing flow — we were also structuring teams around outcomes.This episode dives into how VSM and POM, often seen as separate frameworks, are actually complementary disciplines. VSM optimizes how work flows; POM ensures that work is aligned to customer and business outcomes. When combined, they create a powerful operating model focused on both efficiency and purpose. Backed by industry research, we explore why high-performing organizations are embracing this convergence — and what it means for the future of software delivery.Link to the article: How Value Stream Management and Product Operating Models Complement Each Other, originally published April 27, 2025.Connect with me on LinkedIn

This episode covers a recent shift from the title of Scrum Master to Agile Delivery Manager (ADM). The AI hosts discuss how a change for the role of Scrum Master to Agile Delivery Manager represents a natural progression driven by an expanded need for delivery leadership, the adoption of Flow Metrics and Value Stream Management, and a move towards alternative practices from Scrum to Kanban or other custom Agile practices.The ADM role goes beyond a traditional Scrum Master, covering delivery metrics, team collaboration, and workflow optimization without being limited to specific tasks. This reflects the growing complexity of modern delivery and the need for a role dedicated to boosting team performance and delivery efficiency beyond standard Agile frameworks.Link to the article: From Scrum Master to Agile Delivery Manager: Evolution in the Age of Flow, originally published April 14, 2025.Connect with me on LinkedIn

This episode, "Beyond Frameworks," reflects on the challenges of leading large-scale Agile and DevOps transformations, even within successful organizations. It argues that despite adopting new structures and frameworks, persistent friction arises from diverging leadership philosophies and a superficial sense of alignment, leading to transformation fatigue.The AI hosts share my personal experiences and insights from over a decade, highlighting that real transformation takes ongoing effort, fresh thinking, and a commitment to maintaining a shared mindset—especially during leadership changes.The conversation connects with another article that underscores the necessity of genuine leadership trust for team autonomy to succeed, suggesting that erosion of this trust contributes to ongoing friction.Link to the article: Beyond Frameworks: The Real Weight of Leading Transformation at Scale, originally published April 14, 2025.Connect with me on LinkedIn

In today’s episode, we explore the idea of documenting anticipated outcomes and introduce Purpose-Driven Development (PDD), which focuses on defining expected outcomes for every software project. This approach helps ensure alignment with business goals and moves away from a "feature factory" mindset that prioritizes output over value.The AI hosts discuss my recent story about resistance to this idea, pointing out that it often comes from a lack of understanding or alignment. To track progress, they also discuss my introduction of the Feature Factory Ratio (FFR), which measures the percentage of initiatives or epics without clear outcomes.The conversation highlights that having a clear purpose and strong strategic alignment is essential for modern software leadership. This requires teams and leaders to adjust both their mindset and practices.Link to the article: From Feature Factory to Purpose-Driven Development: Why Anticipated Outcomes Are Non-Negotiable, originally published April 12, 2025.Connect with me on LinkedIn

In today’s episode, we explore the idea of documenting anticipated outcomes and introduce Purpose-Driven Development (PDD), which focuses on defining expected outcomes for every software project. This approach helps ensure alignment with business goals and moves away from a "feature factory" mindset that prioritizes output over value.The AI hosts discuss my recent story about resistance to this idea, pointing out that it often comes from a lack of understanding or alignment. To track progress, they also discuss my introduction of the Feature Factory Ratio (FFR), which measures the percentage of initiatives or epics without clear outcomes.The conversation highlights that having a clear purpose and strong strategic alignment is essential for modern software leadership. This requires teams and leaders to adjust both their mindset and practices.Link to the article: From Feature Factory to Purpose-Driven Development: Why Anticipated Outcomes Are Non-Negotiable, originally published April 12, 2025.Connect with me on LinkedIn

This episode dives into various team models within technology organizations, focusing on a comparison between the traditional Engineering Manager (EM) model—where a single manager handles both technical direction and people management—and autonomous cross-functional teams, inspired by frameworks like Team Topologies. I make the case for the latter, highlighting the intentional separation of people management from delivery responsibilities. This approach promotes greater autonomy, distributed leadership, and psychological safety, enabling teams to thrive in a more empowered and collaborative environment.The AI hosts dive into my perspectives, exploring the strengths and weaknesses of each model, including the challenges posed by "unicorn" EM roles and the critical role of trust in autonomous teams. The discussion ultimately underscores the importance of being intentional about the mindset an organization adopts to scale, regardless of the structural framework chosen.Link to the article: Mindsets That Shape Software Delivery Team Structures, originally published March 29, 2025.Connect with me on LinkedIn

In this episode, we examine the growing trend of cutting Agile leadership roles like Scrum Masters. While often viewed as a cost-saving move, I argue this approach harms team effectiveness and productivity.The AI host shares my experience evolving the role into an Agile Delivery Manager focused on flow metrics and value stream management, contrasting it with a parent company's decision to distribute these tasks. We discuss the hidden costs of removing such roles, including added burden on managers, reduced flow efficiency, and weakened team culture.The takeaway? Agile leadership is essential for balanced delivery, continuous improvement, and long-term team health.Link to the article: Why Cutting Agile Leadership Hurts Teams More Than It Saves, originally published March 21, 2025.Connect with me on LinkedIn

In this episode, we shift focus from software delivery to engineering and explore the topic of responsible engineering. The AI hosts discuss a conversation that broadened the definition of responsible engineering, emphasizing the importance of considering the consequences beyond just functionality.Leadership is key to creating a culture of responsibility by setting clear expectations and encouraging accountability. The discussion highlights the need for engineers to approach their work with care and a commitment to reducing harm. Ultimately, responsible engineering is framed as a matter of professional integrity and a fundamental aspect of the software engineering field.Link to the article: Responsible Engineering: Beyond the Code, Owning the Impact, originally published March 08, 2025.Connect with me on LinkedIn

This episode addresses confusion surrounding Flow Metrics in Agile environments by emphasizing the importance of understanding Value Stream Management, Flow Items, and the Agile Work Hierarchy. It clarifies how to align Agile work items, such as initiatives or themes, epics, features, user stories, and tasks, with Flow Items, which represent units of value like features, defects, risks, and debts. The AI hosts discuss the common misunderstandings, such as incorrectly mapping Jira issue types or confusing releases with work items. Ultimately, the conversation advocates for a standardized understanding of the work hierarchy and Flow Items to effectively measure and improve value delivery.Link to the article: Avoiding Flow Metric Confusion: Aligning Agile Work Hierarchy to Flow Items, originally published February 17, 2025.Connect with me on LinkedIn

The episode is a follow-up to my August 2024 article and Podcast Episode 18 from Season 1: Navigating the Digital Product Workflow Metrics Landscape: From DORA to Comprehensive Value Stream Management Platform SolutionsIn this episode, the AI hosts share my perspective on the increasing confusion between Software Engineering Intelligence (SEI) and Value Stream Management (VSM) platforms caused by overlapping features and marketing messages.The discussion highlights the importance of choosing platforms based on an organization’s specific needs: SEI for addressing engineering bottlenecks and VSM for broader, cross-functional improvements. It addresses common misconceptions, introduces a new framework called The DX Core 4, and highlights the need to choose tools that fit an organization’s budget, current situation, challenges, goals, and visibility needs.Link to the article: Decoding the Metrics Maze: How Platform Marketing Fuels Confusion Between SEI, VSM, and Metrics, originally published February 15, 2025.Connect with me on LinkedIn

In this episode, we delve into the article "Beyond Outcome-Focused Metrics: Connecting Work to Outcomes," which emphasizes the importance of aligning software development efforts with tangible business value. We discuss how adopting value stream thinking can transform software teams from perceived cost centers into strategic enablers. By focusing on customer value streams, organizations can enhance strategic alignment, foster continuous improvement, and ensure that every initiative contributes meaningfully to business goals. This approach not only clarifies the connection between work and value but also promotes a culture of collaboration and responsiveness to customer needs.Link to the article: Beyond outcome-focused metrics: Connecting Work to Outcomes, originally published February 04, 2025.Connect with me on LinkedIn

This episode picks up from the last episode, episode 27, Advocating for Refactoring: Prioritization in the Context of Business GoalsWe continue the conversion advocating for a proactive approach to managing technical debt, suggesting that teams treat it like a financial loan. I support making continuous "minimum payments" by regularly refactoring code, similar to making minimum payments on a loan, rather than waiting for large-scale cleanups. We also discuss prioritizing technical debt based on its "interest rate," or the cost of inaction, and its impact on business outcomes. The conversation based on my article emphasizes the importance of communicating the business value of addressing technical debt to stakeholders and integrating refactoring into the daily development process. Ultimately, the goal is to balance short-term business goals with long-term code maintainability.Link to the article: Managing Technical Debt: Interest Rates, Impact, and Continuous Payments, originally published February 02, 2025.Connect with me on LinkedIn

In this episode, the AI hosts dive into my article, which makes the case for viewing refactoring in software development not as a routine technical chore, but as a strategic business investment. The discussion examines the common drivers behind the need for refactoring—tight deadlines, shifting requirements—and outlines practical strategies for embedding it into established frameworks like Value Stream Management (VSM) and the Product Operating Model (POM). A key focus is on quantifying the business value of refactoring, using metrics to demonstrate its importance alongside features, defect resolution, and risk mitigation. Ultimately, the article advocates for a cultural shift toward continuous, incremental refactoring as a cornerstone of sustainable software delivery.Link to the article: Advocating for Refactoring: Prioritization in the Context of Business Goals, originally published January 19, 2025.Connect with me on LinkedIn

In today's episode, the AI hosts discuss my article, which expands on a recent piece by John Cutler about managing cross-team dependencies. It explores three common approaches to handling dependencies: minimizing them, institutionalizing them, and actively addressing them.I build upon Culter's concepts by introducing a prioritization framework that emphasizes prioritizing work based on anticipated outcomes and available capacity. I advocate for a dynamic approach to reprioritization as circumstances change and highlight the benefits of a proactive, outcome-focused strategy. The framework presented aims to reduce team burnout and improve alignment with organizational goals by encouraging transparency and collaboration. The episode suggests that, while inevitable, dependencies can be transformed from obstacles into opportunities for growth and innovation.Link to the article: Dependencies Are Here to Stay: From Challenges to Opportunities, originally published January 11, 2025.Connect with me on LinkedIn

In this episode, I share my journey of implementing Value Stream Management (VSM) and a Product Operating Model (POM) within my organization, highlighting the challenges, insights, and results along the way.It highlights the importance of not just implementing these frameworks, but also clearly articulating their value to foster alignment across teams and enhance operational efficiency.The AI hosts delve into the striking performance gap between organizations that effectively leverage these models and those that fall short, referencing key insights from the 2024 Project to Product State of the Industry Report.The episode emphasizes the importance of prioritizing outcomes over mere outputs and highlights the value of empowering cross-functional teams to take full ownership of the product lifecycle. It concludes by presenting my 2025 plan to deepen the integration of VSM and POM principles within the company, with a focus on enhancing communication and aligning team efforts with measurable business results.Link to the article: Why Value Stream Management and the Product Operating Model Matter, originally published January 05, 2025.Connect with me on LinkedIn

In today’s episode, the AI hosts discuss my vision for our team in 2025 as we move into the next phase of our 10-year transformation. Our aim is to address capacity pressures by shifting from an output-focused approach to an outcome-driven mindset. We’re also reinforcing our commitment to a product operating model and value stream management. The episode emphasizes how feedback and collaboration can improve team alignment, increase engagement, and amplify impact.Link to the article: From Good to Great: Shifting to Outcomes in 2025, originally published January 02, 2025.Connect with me on LinkedIn

In this episode, the AI hosts discuss that engineering teams should prioritize meaningful outcomes over simply delivering outputs—a concept known as the "build trap." It advocates for a product operating model using Value Stream Management (VSM) and Objectives and Key Results (OKRs) to ensure every effort delivers measurable business value.The discussion emphasizes the importance of defining anticipated outcomes for epics, fostering accountability through clear ownership of key results, and "closing the loop" by measuring and sharing actual results. Ultimately, the conversation advocates for shifting away from a feature factory mindset toward a focus on value creation and organizational alignment.Link to the article: Breaking Free from the Build Trap: Delivering Meaningful Outcomes, originally published December 25, 2024.Connect with me on LinkedIn

This is the second episode in a three-part series exploring Profitable Engineering and how Phil as a technology leader is transforming the engineering department from a cost center into a strategic business partner. The AI hosts dive into Phil's response to peer feedback recommending him to prioritize focusing on business results, highlighting how it prompted a transformation in his leadership approach.Link to the article: Transforming Engineering: From Cost Center to Strategic Partner, originally published December 24, 2024.Connect with me on LinkedIn

This episode is the first in a three-part series exploring the often-misunderstood role of software engineering, frequently dismissed as just a cost center. The AI hosts dive into my argument for adopting a product operating model and Value Stream Management to redefine engineering's value. By leveraging OKRs, teams can align their efforts with measurable business outcomes and customer impact. This shift requires intentional team design, emphasizing the movement of work to teams rather than individuals, enabling accurate cost tracking and demonstrating ROI. The ultimate aim is to transform the perception of engineering from a "black box" expense to a key driver of innovation and growth. In the next episodes, we’ll explore leadership strategies to make this vision a reality.Link to the article: Engineering’s Business Value: From Black Box to Clarity, originally published December 23, 2024.Connect with me on LinkedIn

Happy New Year! We're excited to kick off season two of the podcast. In this opening episode, the AI hosts introduce a three-part series on Profitable Engineering, exploring how to connect technology investments to meaningful business results.This three-part series dives into reimagining software engineering as a strategic business partner rather than merely a cost center. Tailored for technology leaders, product managers, and anyone seeking to align engineering efforts with customer value and measurable business outcomes, it provides valuable insights to bridge the gap between technical investments and organizational success.Link to the article: Profitable Engineering: Linking Software Engineering to Business Results, originally published December 22, 2024.Connect with me on LinkedIn.

This episode marks the end of Season 1 of the AI-generated podcast experiment and the culmination of my initial efforts to share insights from my three-year article-writing journey. At the same time, I reached a key point in my career where there's no turning back time, and I take a moment to reflect on my experience in software engineering and leadership. It's been a journey through two distinct eras of software delivery, which have shaped my growth and perspective.The AI hosts interpret my end-of-year article and reflection, "Crossroads 2024: Reflections on Leadership, Legacy, and Modern Practices."Although they diverge slightly from the main focus of my article, my mission, they highlight my emphasis on the transformative impact of modern practices like Agile, DevOps, and cloud computing and how these innovations have changed team dynamics and organizational culture.A key focus is on the importance of leadership in fostering a culture of continuous learning, experimentation, and psychological safety to achieve fast flow and deliver value.This year in technology has brought challenges and successes in Software Product Development and Delivery. We've seen the release of thought-provoking books, listened to insightful podcasts and interviews from industry leaders, and returned to in-person conferences. Along the way, we've dealt with layoffs and cost-cutting, witnessed significant advancements in AI, and seen shifting opinions—and even criticism—of Agile practices. At the same time, we've celebrated inspiring success stories from standout organizations.Here's to more progress and innovation—wishing you a great 2025!Link to the article: Crossroads 2024: Reflections on Leadership, Legacy, and Modern Practices, originally published December 02, 2024.Connect with me on LinkedIn

In this episode, the discussion by the AI hosts is based on my article, "Navigating the Digital Product Workflow Metrics Landscape: From DORA to Comprehensive Value Stream Management Platform Solutions." It acts as a guide for senior leaders in choosing the best software delivery metrics platform for their needs. It evaluates four types of platforms: DORA metrics, which focus on deployment; DX Core 4, which emphasizes speed, effectiveness, quality, and business impact; Software Engineering Intelligence (SEI) platforms, which offer broader insights into the delivery pipeline; and Value Stream Management (VSM) platforms, which provide a comprehensive view of the entire product lifecycle. The discussion emphasizes the importance of identifying bottlenecks before making a choice and highlights the need to consider factors such as budget, leadership readiness, and team sentiment. Additionally, the article provides several examples for each platform type.Link to the article: Navigating the Digital Product Workflow Metrics Landscape: From DORA to Comprehensive Value Stream Management Platform Solutions, originally published August 31, 2024.Connect with me on LinkedIn

In this episode, the AI hosts dive into my article, "Evolving the Agile Leadership Role: Integrating Value Stream Management into Agile Leadership." The conversation cites concerning statistics on Scrum Master maturity, indicating a significant lack of VSM expertise. He proposes integrating VSM into the Agile Leader role to enhance team performance, improve process efficiency, and better align with organizational goals. This integration, Phil contends, addresses the criticisms levied against the current definition of the Scrum Master role and provides a path to increase the value and impact of Agile leaders. Finally the conversation offers several benefits of this approach, including improved metrics, enhanced collaboration, and strategic alignment.Link to the article: Evolving the Agile Leadership Role: Integrating Value Stream Management into Agile Leadership, originally published May 19, 2024.Connect with me on LinkedIn

In this episode, the AI hosts discuss my article, "A Balanced Approach to Agile Metrics: Empowering Teams and Mitigating Risks." The article advocates for using Agile metrics wisely in software development. It argues that metrics like DORA and flow velocity are great for spotting bottlenecks and boosting team performance, but they can be misused. This misuse can lead to focusing on manipulating numbers rather than genuine improvement. The conversation highlights the need for team ownership of metrics, clear communication, and understanding each team's unique context. A big concern is to keep metrics from becoming tools for blame-shifting or pressure from business stakeholders. The ultimate goal is to use metrics to empower teams and encourage a culture of continuous improvement.Link to the article: A Balanced Approach to Agile Metrics: Empowering Teams and Mitigating Risks, originally published March 02, 2024.Connect with me on LinkedIn

This episode examines the vital, yet sometimes debated, role of Scrum Masters or Agile leaders in cross-functional software development teams. Nearly two years ago, Capitol One laid off most of its Agile Coaches and Scrum Masters, questioning their value. Recently, I've worked with an organization that eliminated the Scrum Master role, assigning its responsibilities to the Engineering Manager on each team. Whether you transfer these duties to the Product or Engineering Manager, I believe this creates significant "role overload."In this episode, our AI hosts discuss my article which argues that Agile leaders, distinct from product managers, are crucial for balancing work types (features, defects, technical debt, and risk), fostering team alignment, and ensuring sustainable high-quality software delivery. The author draws insights from "Team Topologies" and "Project to Product," emphasizing the importance of intentional team design and a product-centric approach. Ultimately, the article advocates for recognizing the unique value of Agile leadership in achieving high-performing, collaborative teams, concluding that while team structures may vary, the Agile leader's role is essential for success.Link to the article: Beyond Facilitation: The Agile Leader’s Place in Cross-Functional Team Dynamics, originally published February 25, 2024.Connect with me on LinkedIn

This episode examines the challenges of balancing cost savings with maintaining agile team effectiveness when geographically distributing software development teams. The author uses a US based example and argues against replacing individual team members in the US with cheaper alternatives in different time zones, emphasizing the negative impact on collaboration and efficiency due to significant time differences. Instead, the author advocates for relocating entire cross-functional teams to cost-effective locations to preserve team cohesion and agile principles.The article uses a real-world example to illustrate the potential pitfalls of a dispersed team structure and offers strategic recommendations for a more effective approach to global talent rebalancing. Ultimately, the article stresses prioritizing team unity and geographical proximity to optimize both cost and productivity.Link to the article: Pressures of Strategic Talent Cost Rebalancing in Agile Teams: Optimizing Global Geographical Costs for Cohesion and Efficiency, originally published February 13, 2024.Connect with me on LinkedIn

In this episode, our AI hosts take a deep dive into the challenges of transitioning to Agile, Lean, and DevOps methodologies in organizations, focusing on the resistance from senior leaders entrenched in outdated practices and metrics. The conversation highlights the negative impact of legacy leadership on modern digital transformation efforts, citing several real-world examples of friction and failed transformations.The fundamental challenge lies in the disconnect between traditional leadership styles and the collaborative, outcome-focused essence of agile methodologies.The referenced article emphasizes the need for senior leaders to adapt, learn new skills, and embrace a shift in mindset to successfully implement these modern practices. Ultimately, the author argues that strong, informed leadership is crucial for successful digital transformation.Link to the article: Agile Era Leadership: Overcoming Legacy Leadership Friction and Four Industry Conversations, originally published December 12, 2023.Connect with me on LinkedIn