<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Progress Blog - Latest Comments in Lessons Learned in Communication</title><link>http://progressblog.disqus.com/</link><description>A Project Manager's quest for continuous improvement</description><atom:link href="https://progressblog.disqus.com/lessons_learned_in_communication/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 22 Feb 2009 22:34:39 -0000</lastBuildDate><item><title>Re: Lessons Learned in Communication</title><link>http://progressblog.com/?p=5#comment-10588956</link><description>&lt;p&gt;Thank you for commenting!&lt;br&gt;A great article - thanks for sharing too!&lt;br&gt;One of my colleagues calls those endless threads "chats". It's often hard to find a tangible result (value) when one of those starts.&lt;br&gt;An interesting strategy. I sometimes turn Outlook to cached mode myself, making it check e-mail regularly at assigned intervals (productivity gains too). Sooner or later, however, someone sends something very urgent...&lt;br&gt;Did you ever regret following such a strategy? Did it become your standard indeed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lech</dc:creator><pubDate>Sun, 22 Feb 2009 22:34:39 -0000</pubDate></item><item><title>Re: Lessons Learned in Communication</title><link>http://progressblog.com/?p=5#comment-99889392</link><description>&lt;p&gt;Thank you for commenting!&lt;br&gt;A great article - thanks for sharing too!&lt;br&gt;One of my colleagues calls those endless threads "chats". It's often hard to find a tangible result (value) when one of those starts.&lt;br&gt;An interesting strategy. I sometimes turn Outlook to cached mode myself, making it check e-mail regularly at assigned intervals (productivity gains too). Sooner or later, however, someone sends something very urgent...&lt;br&gt;Did you ever regret following such a strategy? Did it become your standard indeed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lech</dc:creator><pubDate>Sun, 22 Feb 2009 22:34:39 -0000</pubDate></item><item><title>Re: Lessons Learned in Communication</title><link>http://progressblog.com/?p=5#comment-10588955</link><description>&lt;p&gt;Thank you for commenting!&lt;br&gt;A great article - thanks for sharing too!&lt;br&gt;One of my colleagues calls those endless threads "chats". It's often hard to find a tangible result (value) when one of those starts.&lt;br&gt;An interesting strategy. I sometimes turn Outlook to cached mode myself, making it check e-mail regularly at assigned intervals (productivity gains too). Sooner or later, however, someone sends something very urgent...&lt;br&gt;Did you ever regret following such a strategy? Did it become your standard indeed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lech</dc:creator><pubDate>Sun, 22 Feb 2009 22:33:48 -0000</pubDate></item><item><title>Re: Lessons Learned in Communication</title><link>http://progressblog.com/?p=5#comment-99889389</link><description>&lt;p&gt;Thank you for commenting!&lt;br&gt;A great article - thanks for sharing too!&lt;br&gt;One of my colleagues calls those endless threads "chats". It's often hard to find a tangible result (value) when one of those starts.&lt;br&gt;An interesting strategy. I sometimes turn Outlook to cached mode myself, making it check e-mail regularly at assigned intervals (productivity gains too). Sooner or later, however, someone sends something very urgent...&lt;br&gt;Did you ever regret following such a strategy? Did it become your standard indeed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lech</dc:creator><pubDate>Sun, 22 Feb 2009 22:33:48 -0000</pubDate></item><item><title>Re: Lessons Learned in Communication</title><link>http://progressblog.com/?p=5#comment-10588954</link><description>&lt;p&gt;F2F communication is indeed the best (I have published an article about it, &lt;a href="http://www.pmhut.com/the-join-up-meeting-the-best-mean-of-project-communication" rel="nofollow noopener" target="_blank" title="http://www.pmhut.com/the-join-up-meeting-the-best-mean-of-project-communication"&gt;the join-up meeting&lt;/a&gt;), as for email, the potential of misunderstandings is quite high, that's why it's always good to follow up with an email. There's also the issue where email threads drag on forever. My strategy is to answer emails near the end of the day, this way I will avoid these endless (and nearly always useless) threads.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PM Hut</dc:creator><pubDate>Sun, 22 Feb 2009 13:36:25 -0000</pubDate></item><item><title>Re: Lessons Learned in Communication</title><link>http://progressblog.com/?p=5#comment-99889384</link><description>&lt;p&gt;F2F communication is indeed the best (I have published an article about it, &lt;a href="http://www.pmhut.com/the-join-up-meeting-the-best-mean-of-project-communication" rel="nofollow noopener" target="_blank" title="http://www.pmhut.com/the-join-up-meeting-the-best-mean-of-project-communication"&gt;the join-up meeting&lt;/a&gt;), as for email, the potential of misunderstandings is quite high, that's why it's always good to follow up with an email. There's also the issue where email threads drag on forever. My strategy is to answer emails near the end of the day, this way I will avoid these endless (and nearly always useless) threads.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PM Hut</dc:creator><pubDate>Sun, 22 Feb 2009 13:36:25 -0000</pubDate></item></channel></rss>