What Happens After Why

Last week we explained how asking the simple question “why?” can help you make big improvements in your agile team - and this week we prove it, with two examples from Jeffrey. In one case his company landed a big client, and in the other an angry person actually listened to him! Hear more in this week’s episode!

SHOW LINKS:

- David Burns, the disarming technique: https://daviddburnsmd.files.wordpress.com/2017/04/the-five-secrets-v-1.pdf
- Chris Voss: https://www.youtube.com/watch?v=guZa7mQV1l0 and https://www.youtube.com/watch?v=llctqNJr2IU
- Previous podcasts on coherent stories: https://soundcloud.com/troubleshootingagile/why-you-shouldnt-listen-to-your-brain and on the 4 Rs of learning: https://soundcloud.com/troubleshootingagile/learning-through-case-studies-the-4-rs
- 7 habits of highly effective people: https://en.wikipedia.org/wiki/The_7_Habits_of_Highly_Effective_People
- Squirrel and Jeffrey talk on leadership techniques: https://skillsmatter.com/meetups/11800-leadership-matters

***

We'd love to hear any thoughts, ideas, or feedback you have about the show.

Email us: see link on troubleshootingagile.com

Tweet us: twitter.com/TShootingAgile

Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

What comes after why?

Troubleshooting Agile is a problem-solving session for agile teams. Jeffrey Fredrick and Douglas Squirrel look at common problems agile teams face and provide practical, immediately useful advice for getting back on track.