<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ProductivityMuse.com</title>
	<atom:link href="http://productivitymuse.com/pm/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://productivitymuse.com/pm</link>
	<description>Productivity! Actionable information, sources, comments and links</description>
	<lastBuildDate>Sat, 22 Nov 2008 23:36:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Need More Time? Use the Artful Stall Technique</title>
		<link>http://productivitymuse.com/pm/?p=213</link>
		<comments>http://productivitymuse.com/pm/?p=213#comments</comments>
		<pubDate>Mon, 17 Nov 2008 05:11:32 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=213</guid>
		<description><![CDATA[The Muse and another senior manager were frustrated. We had an action request; the young manager designated to carry out our request stalled. And stalled. And kept stalling. We called. We sent e-mails. My colleague and I called each other to discuss what to do. We both had plenty on our plates; talking to and [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #0a1684;"><strong><em>The Muse</em> and another senior manager were frustrated. </strong>We had an action request; the young manager designated to carry out our request stalled. And stalled. <em><span style="text-decoration: underline;">And kept stalling</span>.</em> </span></p>
<p><span style="color: #0a1684;">We called. We sent e-mails. My colleague and I called <span style="text-decoration: underline;"><em>each other</em></span> to discuss what to do. We both had plenty on our plates; talking to and e-mailing each other about this person&#8217;s stall (including an exasperated discussion at 11:00 PM one night) was not a productive use of our time. But neither was making phone calls and/or sending the junior manager e-mails. While we weren&#8217;t exactly being ignored, we were unmistakeably getting The Soft Stall. Frustrating.  <em><span style="text-decoration: underline;">We wanted action</span>!</em></span></p>
<p><span style="color: #0a1684;"><em></em>The surprise ending?</span></p>
<p><span style="color: #0a1684;"><strong>Everything worked out the way the junior manager expected it to work out (we were concerned that the situation wasn&#8217;t working out at all) &#8212; <em><span style="text-decoration: underline;">i</span><span style="text-decoration: underline;">f only</span></em> she could manage to stall<em> </em>us for at least another month or so. </strong></span></p>
<p><span style="color: #0a1684;">Which she did. </span></p>
<p><span style="color: #0a1684;">Her Soft Stall (while infuriating at the time) was deliberate, smart &#8212; and, frankly, <span style="text-decoration: underline;">productive</span>. Talk about managing the managers! </span></p>
<p style="text-align: center;">*     *     *</p>
<p><span style="color: #0a1684;">Thinking back over many situations in many settings, there are many instances in which <em>The Muse</em> would have been wise to stall. And on the occasions that she deliberately stalled, she rarely (truth be told) succeeded in stalling <em>artfully</em>.</span></p>
<p><span style="color: #0a1684;">When you need more time </span><span style="color: #0a1684;">&#8211; examples: you&#8217;re <span style="text-decoration: underline;">waiting for more information</span> to make a better decision; an initiative <span style="text-decoration: underline;">needs more work</span> before it can be presented it to senior management; an important matter <span style="text-decoration: underline;">needs time</span> for all its elements to become clearer to all concerned &#8212; the progressive stall technique is ideal. Here&#8217;s how it&#8217;s applied: </span></p>
<ul>
<li><span style="color: #0a1684;"><strong>When first asked,</strong> tell the person that you&#8217;ll get back to him or her. When asked a second time, repeat.  If pressed to indicate <em>exactly</em> when you will respond, try to be vague &#8212; suggest a few days, a few weeks, whatever is appropriate.</span></li>
<li><span style="color: #0a1684;"><strong>If you&#8217;re seriously pressed and still need more time</strong>, tell the person there are more aspects to the matter than you realized. Ask to meet to discuss &#8220;everything&#8221;; set a date as far into the future as possible.</span></li>
<li><span style="color: #0a1684;"><strong>The day before the meeting,</strong> reschedule.</span></li>
<li><span style="color: #0a1684;"><strong>Don&#8217;t show up </strong>for the rescheduled meeting. Send someone to represent you who has no power to do anything <em>except</em> to report back what was discussed at the meeting and to apologize for your absence, explaining you had an unexpected conflict.</span></li>
</ul>
<p><span style="color: #0a1684;">Phil Porter, who describes the progressive stall technique in <em>Eat or Be Eaten </em>(Prentice Hall: New Jersey) says you can use the last no-show tactic two or three times. </span><span style="color: #0a1684;"><em>The Muse</em> doubts it, but maybe Porter is right. He <em>is</em> right about this point: s</span><span style="color: #0a1684;">oon enough the other person (or persons) will decide to by-pass you and begin to work up the organization chain.  But by then, as happened to <em>The Muse </em>and her colleague, the reason for stalling may have disappeared.<br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=213</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Win-Win Negotiation Tool You Must Know</title>
		<link>http://productivitymuse.com/pm/?p=138</link>
		<comments>http://productivitymuse.com/pm/?p=138#comments</comments>
		<pubDate>Tue, 11 Nov 2008 19:14:08 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Negotiation]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=138</guid>
		<description><![CDATA[The Muse stamps her feet in frustration when she hears about smart people who fumble &#8212; and lose &#8212; good deals. It&#8217;s so&#8230;non-productive! Here&#8217;s a deal that could have been a win-win success, if only&#8230;. Producers of a TV production company sat down with a executives of a major independent station to arrange terms for [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #0a1684;"><strong><em>The Muse </em>stamps her feet in frustration when she hears about smart people who fumble &#8212; and lose &#8212; good deals. It&#8217;s so&#8230;<span style="text-decoration: underline;"><em>non</em></span><em>-</em><em>productive!</em> </strong></span></p>
<p><span style="color: #0a1684;"><strong>Here&#8217;s a deal that <em>could</em> have been a win-win success, if only&#8230;. </strong></span></p>
<p><span style="color: #0a1684;"><strong></strong>Producers of a TV production company sat down with a executives of a major independent station to arrange terms for the sale of syndication rights of a popular TV sitcom. Both sides were excited about the deal. A quick close was expected. </span></p>
<p><span style="color: #0a1684;">While the opening discussion was friendly and enthusiastic, subsequent exchanges were not. <em><span style="text-decoration: underline;">A sticking point</span>: the amount of audience share the sitcom would garner. </em></span><span style="color: #0a1684;"><br />
</span></p>
<ul>
<li><span style="color: #0a1684;">Producers were confident of at least a 9% share. </span></li>
<li><span style="color: #0a1684;">The would-be buyers were unwilling to negotiate on the basis of anything higher than a 7% share. </span></li>
</ul>
<p><span style="color: #0a1684;"> </span></p>
<p><span style="color: #0a1684;">An agreement was essential: advertising revenues of about $1 million per share point were at stake. </span></p>
<p><span style="color: #0a1684;">After several long, heated, <span style="text-decoration: underline;"><em>non-productive</em></span> meetings, both sides left the table for good. The producer lost the market entirely; the station bought a less attractive program to fill its schedule. </span></p>
<p><span style="color: #0a1684;"><strong>The negotiation could have ended productively &#8212; and profitably &#8212; for both sides if at least one of the negotiators had known about a win-win approach that takes into account future unknowns: the so-called <em>contingent contract</em>.</strong> As the name suggests, some contract terms aren&#8217;t finalized until the uncertain matter in question, <span style="text-decoration: underline;"><em>i.e</em></span>., the contingency, becomes known.</span></p>
<p><span style="color: #0a1684;">In this case, the producer and TV station could have ended their contentious discussions about what the market share <span style="text-decoration: underline;"><em>might</em></span> be worth, and simply worked out different license fees to be paid once the program&#8217;s <span style="text-decoration: underline;"><em>actual</em></span> ratings became known.</span></p>
<p><span style="color: #0a1684;">Likewise, if you ever lead a negotiation that reaches an impasse over a critical but unknown future element, </span><span style="color: #0a1684;">make your differences of opinion the core of your agreement by writing </span><span style="color: #0a1684;">a <em><span style="text-decoration: underline;">contingent</span></em> contract. </span></p>
<p><span style="color: #0a1684;">Take it from<em>The Muse: </em>It&#8217;s always more productive to bet on the future, not argue about it. </span></p>
<p style="padding-left: 30px;"><span style="color: #0a1684;"><em><span style="text-decoration: underline;">Source</span>:</em> Max H. Bazerman and James J. Gillespie, &#8220;Betting on the Future: The Virtues of Contingency Contracts,&#8221; <em>The Harvard Business Review</em>, <a href="http://tinyurl.com/6zplkp">http://tinyurl.com/6zplkp</a></span></p>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=138</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Get Action on Your Recommendation</title>
		<link>http://productivitymuse.com/pm/?p=82</link>
		<comments>http://productivitymuse.com/pm/?p=82#comments</comments>
		<pubDate>Sun, 09 Nov 2008 00:37:14 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=82</guid>
		<description><![CDATA[If you are writing a report and want productive action on a particular recommendation, do not create a first-page summary listing all the action recommendations that you will review in your report. The reason? Time is one of the scarcest resources in any organization. A hurried (and dare we admit, careless?)  reading by one or [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #000080;"><strong>If you are writing a report and want productive action on a particular recommendation, </strong>do <span style="text-decoration: underline;"><em>not</em></span> create a first-page summary listing all the action recommendations that you will review in your report.</span></p>
<p><span style="color: #000080;">The reason?</span></p>
<p><span style="color: #000080;"><em><span><strong>Time is one of the scarcest resources in any organization</strong>.</span></em></span><span style="color: #000080;"> </span><span style="color: #000080;">A hurried (and dare we admit, careless?)  reading by one or more senior managers could result in an unfavorable choice of action <span style="text-decoration: underline;"><em>simply because</em> </span><em><span style="text-decoration: underline;">you didn&#8217;t &#8220;sell&#8221; anyone on the alternative you consider to be optimal.</span> </em></span></p>
<p><span style="color: #000080;"><strong><span>If you strongly favor a particular action over other possibilities, </span></strong><strong><span><span style="text-decoration: underline;"><em>build a strong case for your preferred choice</em><em> </em></span>.</span></strong> </span><span style="color: #000080;">Here&#8217;s how:</span></p>
<ul>
<li><span style="color: #000080;"><strong>Begin your report by summarizing</strong> the situation that prompted the request for a review and report. A clear summary helps to ensure that the decision makers know and understand the problem(s) you seek to address in the same way that <span style="text-decoration: underline;">you</span> know and understand the problem(s).<br />
</span></li>
<li><span style="color: #000080;"><strong>Discuss the action alternatives</strong> identified during the review process; include the criteria you and your group used to evaluate them. <span style="text-decoration: underline;"><em>Important point</em></span>: <em>To limit the risk that an option that you do not favor is selected, explain clearly why you rejected every alternative, particularly those that  provoked the most discussion, disagreement, and/or debate.</em></span></li>
<li><span style="color: #000080;"><strong>Conclude your report</strong> by presenting the action choice most likely to achieve the cited goals and your reasons for choosing it. If there is a runner-up, describe it and detail your reasons for making it your second choice.</span></li>
</ul>
<p><span style="color: #000080;"><strong>Comment</strong>: If you support your case thoughtfully and logically, your preferred recommendation should emerge as the compelling, natural choice.</span></p>
<p style="padding-left: 30px;"><span style="color: #000080;"><em><span style="text-decoration: underline;">Source</span></em>:  William F. O&#8217;Dell, <em>Effective Business Decision-Making </em>(NTC Business Books: Lincolnwood, Ill.)</span></p>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=82</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Organize Your Desk and Paperwork</title>
		<link>http://productivitymuse.com/pm/?p=52</link>
		<comments>http://productivitymuse.com/pm/?p=52#comments</comments>
		<pubDate>Sat, 08 Nov 2008 05:48:19 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Organizing]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=52</guid>
		<description><![CDATA[Note: The Muse is aware that you already know all the suggestions below. She knows them too. Even so, sometimes she feels overwhelmed by paperwork. These actionable tips serve as good reminders for her &#8212; and maybe for you, too. Paper: Here&#8217;s advice that works: Commit to taking immediate action on every piece of paper, [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;"><span style="color: #3a37c7;"><strong><em><span><span style="text-decoration: underline;">Note</span>:</span> The Muse is aware that you already know all the suggestions below. She knows them too. Even so, sometimes she feels overwhelmed by paperwork. </em></strong></span></p>
<p style="text-align: left;"><span style="color: #3a37c7;"><strong><em>These actionable tips serve as good reminders for her &#8212; and maybe for you, too. </em></strong></span></p>
<p style="text-align: right;"><span style="color: #3a37c7;"><strong><em><br />
</em></strong></span></p>
<p style="text-align: right;">
<p><span style="color: #000080;"><strong>Paper:</strong></span><span style="color: #000080;"> Here&#8217;s advice that works: </span><span style="color: #000080;"><em>Commit to taking immediate action on every piece of paper, handling each item only once.<br />
</em></span></p>
<p><span style="color: #000080;">The suggestion is simple, but not simplistic. What&#8217;s more,</span><span style="color: #000080;"> <strong>if you have trouble filing, delegating or tossing, it suggests that your <em>real </em>problem has nothing to do with a torrent of paper: it&#8217;s a problem of <span style="text-decoration: underline;">decision-making</span></strong>. </span><span style="color: #000080;"> Here are tips to make your decision-making easier:</span></p>
<p><span style="color: #000080;"><strong>Distribution boxes:</strong></span><span style="color: #000080;"> Use only two boxes: an &#8220;in&#8221; and an &#8220;out&#8221; box. Do not create a &#8220;hold&#8221; box &#8212; it usually degenerates into an </span><span style="color: #000080;"><em>&#8220;I can&#8217;t decide&#8221;</em></span><span style="color: #000080;"> box, which is little more than a procrastination tool.  On the other hand:</span></p>
<ul>
<li><span style="color: #000080;"><strong>I<span>f you really can&#8217;t decide about something</span>,</strong></span><span style="color: #000080;"> it belongs in your &#8220;in&#8221; box.  Go through the box once daily; make an action decision on every item.</span></li>
<li><span style="color: #000080;"><strong><span>Pending decision files: </span></strong></span><span style="color: #000080;">If you have too many matters about which you are undecided and/or must delay a decision (</span><span style="color: #000080;"><em><span style="text-decoration: underline;">e.g</span></em></span><span style="color: #000080;">., you&#8217;re awaiting additional information), create &#8220;Decide By&#8221; files.</span></li>
</ul>
<p style="padding-left: 60px;"><span style="color: #000080;"><strong>&#8220;Decide by&#8221; files</strong></span><span style="color: #000080;"> are set up: by week of the month (first week, second, etc.); by days of the month (1 through 31); or by calendar months (January through December) &#8212; whatever is appropriate for your circumstances.</span></p>
<p style="padding-left: 60px;"><span style="color: #000080;"><strong>Go through the files</strong></span><span style="color: #000080;"> when their time comes; </span><span style="color: #000080;"><em>commit to making a decision <span style="text-decoration: underline;">and make it</span>,</em></span><span style="color: #000080;"> unless there is a compelling reason to defer or delay again.</span></p>
<p><span style="color: #000080;"><strong>Files and filing: </strong></span><span style="color: #000080;"> The system you use &#8211; alphabetical, by date, by account, by subject, etc. &#8211; doesn&#8217;t matter </span><span style="color: #000080;"><span style="text-decoration: underline;"><em>so long as you can always quickly and easily retrieve  the records or papers you need.</em></span></span><span style="color: #000080;"> Follow these action tips:</span></p>
<ul>
<li><span style="color: #000080;"><strong>Keep working files visible and at your fingertips</strong></span><span style="color: #000080;">. Create a file folder for each project, subject, customer, etc. you are currently working with or on.  Drop anything pertaining to the various matters into their folders so that you can readily retrieve what you need when it&#8217;s called for.</span></li>
<li><span style="color: #000080;"><strong>Use filing cabinets</strong></span><span style="color: #000080;"> for records and files that are no longer active or needed frequently.</span></li>
<li><span style="color: #000080;"><strong>Establish discard criteria. </strong>P</span><span style="color: #000080;">eriodically go through inactive and/or historical files to discard useless, unnecessary papers.</span></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=52</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Pay For Publicity ONLY When It Succeeds</title>
		<link>http://productivitymuse.com/pm/?p=43</link>
		<comments>http://productivitymuse.com/pm/?p=43#comments</comments>
		<pubDate>Sat, 08 Nov 2008 05:10:38 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Marketing]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=43</guid>
		<description><![CDATA[When asked for the name of a good PR person, The Muse always answers &#8220;Richard Berman in Chappaqua, New York&#8221;.  But it&#8217;s also possible to get results without a PR pro. Consider this gem for boosting a company&#8217;s industry profile without spending a penny on advertising or hiring a public relations agency: Bonus any employee [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #000080;"><strong>When asked for the name of a good PR person, <em>The Muse</em> always answers &#8220;Richard Berman in Chappaqua, New York&#8221;.  But it&#8217;s also possible to get results without a PR pro. Consider this gem for boosting a company&#8217;s</strong> <strong>industry profile </strong>without spending a penny on advertising <em>or</em> hiring a public relations agency: <span style="text-decoration: underline;"><em>Bonus any employee who writes a technical article that&#8217;s published in a trade magazine. </em></span></span></p>
<p><span style="color: #000080;">Ron Harper, chairman of Harper Companies in Charlotte, North Carolina, got an estimated $40,000 in publicity for $5,000 by offering a $500 bonus to any employee who published an article in an industry trade publication. It wasn&#8217;t long before ten staffers saw their names in print &#8211; and on $500 checks.</span></p>
<p><span style="color: #000080;"><strong>The beauty of this approach</strong> is that unlike advertising and PR efforts, that can be expensive, difficult to measure and (unless you&#8217;re relying on a pro like Richard Berman) notoriously chancy, Harper wrote checks for <em>known</em> results.</span></p>
<p style="padding-left: 30px;"><span style="color: #000080;"><em><span style="text-decoration: underline;">Source:</span></em> Leslie Brokaw, <em>301 Great Ideas From America&#8217;s Most Innovative Small Companies</em> (Inc. Publishing).</span></p>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=43</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How the Best Senior Managers Achieve So Much</title>
		<link>http://productivitymuse.com/pm/?p=27</link>
		<comments>http://productivitymuse.com/pm/?p=27#comments</comments>
		<pubDate>Fri, 07 Nov 2008 21:16:38 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Time Management]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=27</guid>
		<description><![CDATA[The Muse was fascinated to learn the surprise reason the best senior managers get so much done: They don&#8217;t follow a &#8220;rational&#8221; or &#8220;linear&#8221; approach, i.e., careful goal-setting followed by a &#8220;do this&#8221; and &#8220;next do that&#8221; plan and/or check-list, etc. A two-year study reveals that the most successful senior managers keep overriding concerns in [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #000080;"><strong><em>The Muse </em>was fascinated to learn the surprise reason the best senior managers get so much done:</strong> They <span style="text-decoration: underline;"><em>don&#8217;t</em></span> follow a &#8220;rational&#8221; or &#8220;linear&#8221; approach, <span style="text-decoration: underline;"><em>i.e.</em></span>, <em>careful goal-setting followed by a &#8220;do this&#8221; and &#8220;next do that&#8221; plan and/or check-list, etc</em>.</span></p>
<p><span style="color: #000080;"><span>A two-year study reveals that the most successful senior managers <span style="text-decoration: underline;"><em>keep overriding concerns</em></span> in mind at all time. </span><strong><span> Whenever effective managers confront a problem,</span></strong> <strong><span>they take into account <em><span style="text-decoration: underline;">all their related concerns</span> </em>then work toward solutions that can solve several problems at the same time.</span></strong></span></p>
<p><span style="color: #000080;"><em> <span style="text-decoration: underline;"><strong>Example</strong></span>:</em> An effective, successful division manager working on a problem of poor product quality used the opportunity to tackle two additional matters:</span></p>
<ul>
<li><span style="color: #000080;"> An inadequate production control system &#8212; a long-standing concern; and</span></li>
<li><span style="color: #000080;">Expanding a promising young manager&#8217;s experience portfolio.</span></li>
</ul>
<p><span style="color: #000080;">Here was the manager&#8217;s several-in-one solution: She <span style="text-decoration: underline;">assigned the young, up-and-coming manager</span> to a newly created cross-functional team charged with <span style="text-decoration: underline;">solving the  related problems of product quality</span> and <span style="text-decoration: underline;">inadequate production control</span>.</span></p>
<p><span style="color: #000080;"><em><span style="text-decoration: underline;"><strong>Comment</strong></span></em>: Successful senior managers&#8217; ability to create &#8220;networks of problem to solve&#8221; is a developed, life-time mental habit. Develop it by recognizing that no problem exists in isolation. Then:</span></p>
<ul>
<li><span style="color: #000080;">Always <span style="text-decoration: underline;">look for relationships</span> that exist between different problems; and</span></li>
<li><span style="color: #000080;"> Think through <span style="text-decoration: underline;">possible solutions</span> likely to <span style="text-decoration: underline;">solve two or more problems</span> at the same time.</span></li>
</ul>
<p style="padding-left: 30px;"><span style="color: #003366;"><span style="color: #000080;"><span><span style="text-decoration: underline;"><em>Source</em></span>:  Daniel J. Eisenberg, &#8220;How Senior Managers Think&#8221;, Harvard Business Review, November, 1984.  To order a copy, visit</span></span>:</span> <a style="color: blue;" href="http://tiny.cc/KbeFW" target="_blank"><strong>http://tiny.cc/KbeFW</strong></a></p>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=27</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Prepare For Hostile Q&amp;A Sessions</title>
		<link>http://productivitymuse.com/pm/?p=22</link>
		<comments>http://productivitymuse.com/pm/?p=22#comments</comments>
		<pubDate>Tue, 04 Nov 2008 22:11:58 +0000</pubDate>
		<dc:creator>The Muse</dc:creator>
				<category><![CDATA[Communication]]></category>

		<guid isPermaLink="false">http://productivitymuse.com/pm/?p=22</guid>
		<description><![CDATA[When you give a presentation, you’re in charge; when it comes to the Q&#38;A session, the audience is in charge. Here’s what to do when you expect difficult, possibly hostile, questions: 1. Prepare in advance appropriate responses to every possible unpleasant, hostile question you can think of. 2. Later, when actually answering audience questions, always [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #003366;">When you give a presentation, you’re in charge; </span><span style="color: #003366;"><strong><span><em>when it comes to the Q&amp;A session,</em> <span style="text-decoration: underline;"><em>the audience is in charge</em></span>.</span></strong> </span><span style="color: #003366;">Here’s what to do when you expect difficult, possibly hostile, questions:</span></p>
<p><span style="color: #003366;"><span><strong>1. Prepare </strong></span><strong>in advance appropriate responses</strong> to </span><span style="color: #003366;">every possible unpleasant, hostile question you can think of. </span></p>
<p><span style="color: #003366;"><strong>2. <span>Later, when actually answering audience questions</span><span>,</span></strong></span><span style="color: #003366;"><strong><span> <em>always pause before giving every answer <span style="text-decoration: underline;">even when you can give an immediate response</span></em>.</span></strong> </span><span style="color: #003366;">The audience gets used to your pausing pattern. If you get a zinger, a pause won’t telegraph the fact that you are grappling with a difficult question for which you aren’t prepared and <em>this </em>time really <em>do</em> need extra moments to think.</span></p>
<p style="padding-left: 30px;"><span style="color: #003366;"><em><span style="text-decoration: underline;">Source</span>:</em> Karen Berg &amp; Andrew Gilman with Edward P. Stevenson, <em>Get to the Point: How to Say What You Mean and Get What You Want </em>(Bantam: New York)</span></p>
]]></content:encoded>
			<wfw:commentRss>http://productivitymuse.com/pm/?feed=rss2&#038;p=22</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

