Although we talk about joint design a lot, we haven't managed to do an episode on it. As we get to chapter 4 in our tour through Agile Conversations, it's time to rectify that! We focus on a common error that we didn't cover in depth in the book: how trying to "convince" someone through advocacy fails. Using the Four Rs, we roleplay an ineffective advocacy-heavy conversation about tech team execution, and then revise it to increase curiosity, reduce defensiveness and achieve greater internal commitment.

SHOW LINKS:

- Getting to Yes: https://en.wikipedia.org/wiki/Getting_to_Yes
- David Burns on (not) trying to help: https://feelinggood.com/2019/10/28/164-how-to-help-and-how-not-to-help/
- Previous episodes and blog posts on joint design:
   - https://soundcloud.com/troubleshootingagile/mutual-learning-model-part-one
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-i
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-ii
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-iii
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-iv 
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-v 

Episode transcript: https://www.conversationaltransformation.com/posts/why-finding-the-balance-for-joining/

---

Our new book, Agile Conversations, is out now! See https://conversationaltransformation.com where you can order your copy and get a free video when you join our mailing list!

We'd love to hear any thoughts, ideas, or feedback you have about the show.
 
Email us at info@conversationaltransformation.com

Why: Finding the Balance for Joint Design

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.