Coaching on Strength, Part 1
An article by Atul Gawande inspires us to reflect on why you might need a coach for things you are already good at.
Agile Conversations Book
In our recent book Agile Conversations, we argue that the main reason organizations aren’t effective is that they forget to share valid information, have difficult conversations, and build relationships. We show how to use techniques from Action Science to have the five key conversations of highly productive teams.
What is Conversational Transformation?
Learn How Difficult Conversations Unlock Successful Digital, Agile, Devops and Lean Transformations
Transformation is Essential
There is more pressure than ever to adapt and evolve. And for many companies incremental change is no longer enough. Radical changes to behaviour require a different culture. The question is how do you transform your culture?
Conversation is Key
Culture is an emergent property of all of your conversations. Change your conversations and you change your culture. However, our habits of conversation are deeply ingrained, and powerful cognitive biases work against any change.
Learn How to Change
Conversational Transformation is a skill. With disciplined practise, you can improve your conversations the way you’d improve your tennis game or your piano playing. We will try and inspire you, to show you how to practice. Doing the work? That’s up to you.
Receive a free instructional video
The Conversational Transformation newsletter is packed with useful resources, and if you sign up today we’ll send you our new video on ‘Coherence Busting’, an excellent technique to help you ask better questions and reduce your frustration!
Check out the podcast
With a new episode every week, The Troubleshooting Agile podcast covers all aspects of succeeding with agile software development, in a bite-sized problem-focussed format.
Listen nowJoin an event
We regularly speak about Conversational Transformation at events and appear on podcasts.
Find out where we’ll be nextLatest Posts
Imperfect Indicators
We discuss how to set "imperfect indicators" to measure your progress—or lack thereof!
When Software is Done
We reflect on when software can be used without further development and how "software doneness" affects processes and measurements.