What Comes After Why (And So Does How)

Troubleshooting Agile

If you’re using Sinek’s “why, what and how” framework for team collaboration, what do you do when it turns out you’re lacking two out of the three?! In this episode, Squirrel and Jeffrey talk about their own experience of this, the concept of leaky abstractions, and the importance of shared problem ownership. Links: - Simon Sinek: https://simonsinek.com/books/start-with-why/ - Somebody Else's Problem Field: https://hitchhikers.fandom.com/wiki/Somebody_Else%27s_Problem_Field - Previous episode about Walking Skeletons - Ep125: Commitment Engagement is Not Enough: https://soundcloud.com/troubleshootingagile/commitment-engagement-is-not-enough - Previous episode about Cycle Time - Ep249: Estimates: A Productive Argument, Part I https://soundcloud.com/troubleshootingagile/reporting-estimates -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at [e-mail] -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/