<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Practice Top to Bottom Communication</title>
	<atom:link href="http://www.chrisbrogan.com/practice-top-to-bottom-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/</link>
	<description>Learn How Human Business Works - Beyond Social Media</description>
	<lastBuildDate>Fri, 10 Feb 2012 12:25:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: chrisbrogan</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-50368</link>
		<dc:creator>chrisbrogan</dc:creator>
		<pubDate>Wed, 11 Jul 2007 14:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-50368</guid>
		<description>Clearly, Goldie hit on something here. Everyone seems to identify with that point. 

I also want to highlight that Dave&#039;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. 

Great thoughts, guys.</description>
		<content:encoded><![CDATA[<p>Clearly, Goldie hit on something here. Everyone seems to identify with that point. </p>
<p>I also want to highlight that Dave&#8217;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. </p>
<p>Great thoughts, guys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisbrogan</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236531</link>
		<dc:creator>chrisbrogan</dc:creator>
		<pubDate>Wed, 11 Jul 2007 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236531</guid>
		<description>Clearly, Goldie hit on something here. Everyone seems to identify with that point. 

I also want to highlight that Dave&#039;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. 

Great thoughts, guys.</description>
		<content:encoded><![CDATA[<p>Clearly, Goldie hit on something here. Everyone seems to identify with that point. </p>
<p>I also want to highlight that Dave&#8217;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. </p>
<p>Great thoughts, guys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisbrogan</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236532</link>
		<dc:creator>chrisbrogan</dc:creator>
		<pubDate>Wed, 11 Jul 2007 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236532</guid>
		<description>Clearly, Goldie hit on something here. Everyone seems to identify with that point. 

I also want to highlight that Dave&#039;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. 

Great thoughts, guys.</description>
		<content:encoded><![CDATA[<p>Clearly, Goldie hit on something here. Everyone seems to identify with that point. </p>
<p>I also want to highlight that Dave&#8217;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. </p>
<p>Great thoughts, guys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisbrogan</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236533</link>
		<dc:creator>chrisbrogan</dc:creator>
		<pubDate>Wed, 11 Jul 2007 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236533</guid>
		<description>Clearly, Goldie hit on something here. Everyone seems to identify with that point. 

I also want to highlight that Dave&#039;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. 

Great thoughts, guys.</description>
		<content:encoded><![CDATA[<p>Clearly, Goldie hit on something here. Everyone seems to identify with that point. </p>
<p>I also want to highlight that Dave&#8217;s point of LEADING with the call to action is clever. I have a colleague who does this, and it *always* saves her the frustration of hitting me with follow-up emails. When I read her mail, I know what she wants me to do. </p>
<p>Great thoughts, guys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Kawalec</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-50351</link>
		<dc:creator>Dave Kawalec</dc:creator>
		<pubDate>Wed, 11 Jul 2007 13:21:28 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-50351</guid>
		<description>Great discussion here.

1. To underscore Goldie&#039;s point, I find it best to literally enumerate multiple points if I want them noticed. Bullets don&#039;t work. When people see numbers, I guess it makes them aware that there are several points that I&#039;d like them to consider.

2. If I&#039;m sending an email where I need the recipient to do something or send me something, I lead with the call to action. People are busy and have far too many e-mails to read, so I like to spare them time and get right to the point. Then I include all the detail explaining why.

3. If I&#039;m sending an e-mail with information a person needs, and I need something back from them as well, I lead with my question or request. I know that the recipient will read my request in order to get to the information they need.

4. If someone requests information from me, I try to be thorough and unambiguous. I also try to look beyond the question to figure out what the person is trying to accomplish. Sometimes it&#039;s clear the person isn&#039;t asking the right question, or their question tells me they&#039;re not seeing the whole picture.</description>
		<content:encoded><![CDATA[<p>Great discussion here.</p>
<p>1. To underscore Goldie&#8217;s point, I find it best to literally enumerate multiple points if I want them noticed. Bullets don&#8217;t work. When people see numbers, I guess it makes them aware that there are several points that I&#8217;d like them to consider.</p>
<p>2. If I&#8217;m sending an email where I need the recipient to do something or send me something, I lead with the call to action. People are busy and have far too many e-mails to read, so I like to spare them time and get right to the point. Then I include all the detail explaining why.</p>
<p>3. If I&#8217;m sending an e-mail with information a person needs, and I need something back from them as well, I lead with my question or request. I know that the recipient will read my request in order to get to the information they need.</p>
<p>4. If someone requests information from me, I try to be thorough and unambiguous. I also try to look beyond the question to figure out what the person is trying to accomplish. Sometimes it&#8217;s clear the person isn&#8217;t asking the right question, or their question tells me they&#8217;re not seeing the whole picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Kawalec</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236529</link>
		<dc:creator>Dave Kawalec</dc:creator>
		<pubDate>Wed, 11 Jul 2007 13:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236529</guid>
		<description>Great discussion here.

1. To underscore Goldie&#039;s point, I find it best to literally enumerate multiple points if I want them noticed. Bullets don&#039;t work. When people see numbers, I guess it makes them aware that there are several points that I&#039;d like them to consider.

2. If I&#039;m sending an email where I need the recipient to do something or send me something, I lead with the call to action. People are busy and have far too many e-mails to read, so I like to spare them time and get right to the point. Then I include all the detail explaining why.

3. If I&#039;m sending an e-mail with information a person needs, and I need something back from them as well, I lead with my question or request. I know that the recipient will read my request in order to get to the information they need.

4. If someone requests information from me, I try to be thorough and unambiguous. I also try to look beyond the question to figure out what the person is trying to accomplish. Sometimes it&#039;s clear the person isn&#039;t asking the right question, or their question tells me they&#039;re not seeing the whole picture.</description>
		<content:encoded><![CDATA[<p>Great discussion here.</p>
<p>1. To underscore Goldie&#8217;s point, I find it best to literally enumerate multiple points if I want them noticed. Bullets don&#8217;t work. When people see numbers, I guess it makes them aware that there are several points that I&#8217;d like them to consider.</p>
<p>2. If I&#8217;m sending an email where I need the recipient to do something or send me something, I lead with the call to action. People are busy and have far too many e-mails to read, so I like to spare them time and get right to the point. Then I include all the detail explaining why.</p>
<p>3. If I&#8217;m sending an e-mail with information a person needs, and I need something back from them as well, I lead with my question or request. I know that the recipient will read my request in order to get to the information they need.</p>
<p>4. If someone requests information from me, I try to be thorough and unambiguous. I also try to look beyond the question to figure out what the person is trying to accomplish. Sometimes it&#8217;s clear the person isn&#8217;t asking the right question, or their question tells me they&#8217;re not seeing the whole picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Kawalec</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236530</link>
		<dc:creator>Dave Kawalec</dc:creator>
		<pubDate>Wed, 11 Jul 2007 13:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236530</guid>
		<description>Great discussion here.

1. To underscore Goldie&#039;s point, I find it best to literally enumerate multiple points if I want them noticed. Bullets don&#039;t work. When people see numbers, I guess it makes them aware that there are several points that I&#039;d like them to consider.

2. If I&#039;m sending an email where I need the recipient to do something or send me something, I lead with the call to action. People are busy and have far too many e-mails to read, so I like to spare them time and get right to the point. Then I include all the detail explaining why.

3. If I&#039;m sending an e-mail with information a person needs, and I need something back from them as well, I lead with my question or request. I know that the recipient will read my request in order to get to the information they need.

4. If someone requests information from me, I try to be thorough and unambiguous. I also try to look beyond the question to figure out what the person is trying to accomplish. Sometimes it&#039;s clear the person isn&#039;t asking the right question, or their question tells me they&#039;re not seeing the whole picture.</description>
		<content:encoded><![CDATA[<p>Great discussion here.</p>
<p>1. To underscore Goldie&#8217;s point, I find it best to literally enumerate multiple points if I want them noticed. Bullets don&#8217;t work. When people see numbers, I guess it makes them aware that there are several points that I&#8217;d like them to consider.</p>
<p>2. If I&#8217;m sending an email where I need the recipient to do something or send me something, I lead with the call to action. People are busy and have far too many e-mails to read, so I like to spare them time and get right to the point. Then I include all the detail explaining why.</p>
<p>3. If I&#8217;m sending an e-mail with information a person needs, and I need something back from them as well, I lead with my question or request. I know that the recipient will read my request in order to get to the information they need.</p>
<p>4. If someone requests information from me, I try to be thorough and unambiguous. I also try to look beyond the question to figure out what the person is trying to accomplish. Sometimes it&#8217;s clear the person isn&#8217;t asking the right question, or their question tells me they&#8217;re not seeing the whole picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barbara Gavin</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-50338</link>
		<dc:creator>Barbara Gavin</dc:creator>
		<pubDate>Wed, 11 Jul 2007 12:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-50338</guid>
		<description>Good post, Chris. Exactly what we learned in Journalism class. And all too easy to forget!

Also it is good to be reminded by Goldie that one topic (I like to say one *decision*) per email is almost always best.</description>
		<content:encoded><![CDATA[<p>Good post, Chris. Exactly what we learned in Journalism class. And all too easy to forget!</p>
<p>Also it is good to be reminded by Goldie that one topic (I like to say one *decision*) per email is almost always best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236526</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 11 Jul 2007 12:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236526</guid>
		<description>Good post, Chris. Exactly what we learned in Journalism class. And all too easy to forget!

Also it is good to be reminded by Goldie that one topic (I like to say one *decision*) per email is almost always best.</description>
		<content:encoded><![CDATA[<p>Good post, Chris. Exactly what we learned in Journalism class. And all too easy to forget!</p>
<p>Also it is good to be reminded by Goldie that one topic (I like to say one *decision*) per email is almost always best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.chrisbrogan.com/practice-top-to-bottom-communication/comment-page-1/#comment-236527</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 11 Jul 2007 12:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopperfactory.com/cbc/practice-top-to-bottom-communication/#comment-236527</guid>
		<description>Good post, Chris. Exactly what we learned in Journalism class. And all too easy to forget!

Also it is good to be reminded by Goldie that one topic (I like to say one *decision*) per email is almost always best.</description>
		<content:encoded><![CDATA[<p>Good post, Chris. Exactly what we learned in Journalism class. And all too easy to forget!</p>
<p>Also it is good to be reminded by Goldie that one topic (I like to say one *decision*) per email is almost always best.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

