Rethink Your Understanding

Too often, organizations design roles and reporting structures before understanding the work that actually needs to get done.

In this episode, the AI host explores my article on why effective organizational design starts with clearly defined responsibilities, balancing capability with capacity, and establishing accountability. From small teams wearing multiple hats to larger organizations introducing specialists and AI agents, the challenge remains the same: ensuring essential work has clear ownership.

Adding people or technology doesn't eliminate responsibilities. It changes how they're distributed, and leaders need to understand those shifts.

Link to the article: Start With Responsibilities. Then Design the Roles, originally published October 26, 2026.

Connect with me on LinkedIn

Organizations have become increasingly effective at measuring software delivery, but how often do they measure whether that work delivers the expected business value?

In this episode, the AI host explores my article on Outcome Engineering, a practical approach to connecting delivery performance with measurable business outcomes. From documenting anticipated value and tracking the Feature Factory Ratio to evaluating actual results after release, the discussion explores how organizations can close the loop without adding unnecessary bureaucracy.

Shipping software is only part of the equation. Understanding whether it delivered the intended value is what drives learning, accountability, and better investment decisions.

Link to the article: Outcome Engineering: Closing the Loop on Business Value, originally published October 17, 2026.

Connect with me on LinkedIn

What good is predictable software delivery if the features we ship fail to deliver meaningful business value? In this episode, the AI hosts explore why organizations have become increasingly effective at forecasting delivery while paying far less attention to predicting and validating business outcomes.

They examine how product discovery, evidence-based assumptions, and confidence levels can improve investment decisions before development begins. Just as engineering is accountable for delivery confidence, product and business leaders must establish anticipated outcomes, measure actual results, and learn from the differences. Ultimately, predictability must be a two-way street, connecting what teams deliver with the value their work creates.

Link to the article: Predictability vs. Outcomes: What Are We Actually Predicting?, originally published October 14, 2026.

Connect with me on LinkedIn

How has software engineering evolved, and why do so many familiar challenges remain? In this episode, the AI hosts explore my reflections on a technology career spanning decades of change, from traditional software development to Agile, cloud computing, and AI.

They examine the growing importance of business outcomes, delivery confidence, and the leadership behaviors that shape organizational success. Along the way, they explore how shared experiences, continuous learning, and the willingness to unlearn outdated practices reveal new possibilities for technology teams and the businesses they serve.

Link to the article: The Art of the Possible, originally published October 05, 2026.

Connect with me on LinkedIn

Why do software delivery commitments so often miss the mark? In this episode, The AI hosts explore why uncertainty is unavoidable in software development and how organizations can build greater delivery confidence through evidence-based forecasting, realistic capacity planning, and transparent communication.

They examine the hidden impact of competing priorities, unplanned work, and shifting requirements, and why missed deadlines should prompt learning rather than blame. Ultimately, delivery confidence comes from communicating changes early enough for business leaders to make informed decisions and adjust course.

Link to the article: Software Delivery Confidence: How to Build Trust in Commitments, originally published September 12, 2026.

Connect with me on LinkedIn

In this episode, the AI hosts explore my article on the leadership gap that appears when strong individual contributors are promoted into management without meaningful preparation.

So much has already been written and shared on leadership over the years. Yet, I found myself unexpectedly back in the conversation after a meetup dinner raised many of the same questions again. They examine why effective leadership is shaped by the experience of the people being led, and how psychological safety, autonomy, coaching, and deliberate development create the conditions for teams to thrive.

The discussion also explores why soft skills and environmental enablement often matter more than technical expertise alone, and how strong leaders leave a lasting positive imprint by developing others who carry those lessons forward.

Link to the article: Yet Another Leadership Article, originally published August 30, 2026.

Connect with me on LinkedIn

In this episode, the AI hosts explore my article on the Team Flow Improvement Loop and how teams can improve software delivery by finding and removing systemic friction. They examine how Flow Metrics can help expose bottlenecks without becoming performance quotas, why continuous experimentation and psychological safety matter, and how leaders can support team autonomy by clearing obstacles outside the team’s control. The discussion closes on an important point: fast flow creates the most value when it is connected to Realization and meaningful business outcomes.

Link to the article: Fast Flow Happens When Friction Fades, originally published August 23, 2026.

Connect with me on LinkedIn

In this episode, the AI hosts explore my short three-part series on the shift from delivery speed to meaningful business outcomes. They examine why producing more software does not automatically create more value, how leaders can work backward from the intended outcome to align technology with business strategy, and why artificial intelligence should be applied to specific problems rather than treated as the objective itself. The conversation brings these ideas together into a unified system of Flow and Realization, where teams understand both how efficiently work moves and whether that work ultimately creates real value for customers and the organization.

Link to the articles:

1. Eight Widgets Instead of Five. Did We Actually Get Better?, originally published August 13, 2026.
2. Why We Keep Trying: The Art of the Possible in Digital Delivery, originally published August 16, 2026.
3. Start With the Outcome, Then Work Backward, originally published August 18, 2026.

Connect with me on LinkedIn

In this episode, the AI hosts explore my article on why AI graph engineering may feel more familiar than new. They connect it to value stream mapping and established software delivery systems, where work, dependencies, and shared state have long been managed across a flow.

The discussion looks at how AI agents can participate as workers, how shared memory can preserve context and reduce friction, and why human accountability still matters. The participants may be changing, but leadership still owns the responsibility for ensuring the work flows toward outcomes that create real value.

Link to the article: AI Graph Engineering Looks Familiar for a Reason, originally published August 04, 2026.

Connect with me on LinkedIn

In this episode, the AI hosts explore my article on how artificial intelligence is changing the role of management without eliminating the need for strong leadership.

They examine the difference between task coordination and human development, why AI agents and people require different forms of orchestration, and why human accountability remains essential.

As teams become smaller and more efficient, the leadership challenge becomes distributing work intelligently while continuing to coach, mentor, and develop people.

Link to the article: AI Is Changing Management, Not Reinventing It, originally published July 27, 2026.

Connect with me on LinkedIn