In product, we're bombarded by high-level concepts like empowerment, data-driven, product-led, customer-focused, accountability, getting into the details, and high agency. But teams have trouble putting these ideas into practice. Why? And what can you do about it?
This is a really interesting article. I often use the words 'what does [blah] look like, sound like, feel like' in discussion with my podcast guests. But I've probably never used those words in the context you set out here, i.e. in my day job, with my team to actually articulate the objective, the feeling, the behaviour that evidences the objective/feeling and how we create the behaviour.... We do talk about theories of change but I wonder if this is more about the minutiae of change....
This is such a good reminder of the importance of asking questions to get beneath the ambiguous "fluffy" language that causes so much confusion, lack of alignment, and wasted energy. I'll put this book on my list! Thanks for sharing.
This is a really interesting article. I often use the words 'what does [blah] look like, sound like, feel like' in discussion with my podcast guests. But I've probably never used those words in the context you set out here, i.e. in my day job, with my team to actually articulate the objective, the feeling, the behaviour that evidences the objective/feeling and how we create the behaviour.... We do talk about theories of change but I wonder if this is more about the minutiae of change....
I'm actually a huge fan of the book "Talk to the elephant". So great to see it being mentioned here!
This is such a good reminder of the importance of asking questions to get beneath the ambiguous "fluffy" language that causes so much confusion, lack of alignment, and wasted energy. I'll put this book on my list! Thanks for sharing.