Looking for the concerns of others behind their question is key for dealing with stakeholders. I was working on a project in the past where stakeholders pushed for certain stuff and a deadline. After several conversation, we understood what's the root cause of their concerns. Then we came up with another plan, offered it and everyone was happy.
Having a higher impact most times is about being able to communicate your point clearly to other people. It’s never enough to talk like you’d talk to some friend. I particularly like to ask myself “what is the second question“ that people will ask themselves after reading my text, and answer it
Awesome lessons, hadn’t heard of the term signposting before but love the concept and will be adding that to the toolkit.
Also love how much you focus on the importance of effective communication in this Substack. Reminds me of the “Leading up the chain of command” concept from Jocko Willink that guided me throughout my career so far.
I still have to read through Extreme Ownership! Have heard so many good things. Thanks for the kind words as well and thoughts on the article.
I focus a lot on communication since its applicable to everyone, but there's few writing about how to apply it for developers specifically. Also, it's a fun topic to dive into 😄
Love this article. The signposting tip helped me a lot during my past project where I needed to give updates to PM, Sales and skip manager. If we make our communication so clear that the recipient has to pretty much react with ack ty emoji or the like, thats a great sign!
I look forward to trying to apply the QBQ tip more during cross functional settings
> If we make our communication so clear that the recipient has to pretty much react with ack ty emoji or the like, thats a great sign!
This is a great example of "Recipient-focused" communication--a concept Wes talks a lot about in the course. It's great you're thinking this way and also look forward to seeing how QBQ goes!
Loved hearing your biggest takeaways from the course Jordan. Thank you for participating and engaging so thoughtfully.
Absolutely, Wes. Thanks so much for having me in the course and allowing me to share these lessons!
Looking for the concerns of others behind their question is key for dealing with stakeholders. I was working on a project in the past where stakeholders pushed for certain stuff and a deadline. After several conversation, we understood what's the root cause of their concerns. Then we came up with another plan, offered it and everyone was happy.
Great article Jordan and Wes!
Love that story of it working in practice, Petar 💯. Thanks for sharing and reading!
Having a higher impact most times is about being able to communicate your point clearly to other people. It’s never enough to talk like you’d talk to some friend. I particularly like to ask myself “what is the second question“ that people will ask themselves after reading my text, and answer it
Great call on "the second question." I think I do the same thing but you gave it a name for me 😂
Awesome lessons, hadn’t heard of the term signposting before but love the concept and will be adding that to the toolkit.
Also love how much you focus on the importance of effective communication in this Substack. Reminds me of the “Leading up the chain of command” concept from Jocko Willink that guided me throughout my career so far.
Thanks for sharing Jordan and Wes!
I still have to read through Extreme Ownership! Have heard so many good things. Thanks for the kind words as well and thoughts on the article.
I focus a lot on communication since its applicable to everyone, but there's few writing about how to apply it for developers specifically. Also, it's a fun topic to dive into 😄
Love this article. The signposting tip helped me a lot during my past project where I needed to give updates to PM, Sales and skip manager. If we make our communication so clear that the recipient has to pretty much react with ack ty emoji or the like, thats a great sign!
I look forward to trying to apply the QBQ tip more during cross functional settings
> If we make our communication so clear that the recipient has to pretty much react with ack ty emoji or the like, thats a great sign!
This is a great example of "Recipient-focused" communication--a concept Wes talks a lot about in the course. It's great you're thinking this way and also look forward to seeing how QBQ goes!
Great Read!
Thank you, Vasudev!