<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Worthless Expert Interviews: What Can You Do?</title>
	<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/</link>
	<description>Everything about writing and marketing white papers</description>
	<pubDate>Wed, 08 Feb 2012 16:19:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Donna Barron</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14935</link>
		<dc:creator>Donna Barron</dc:creator>
		<pubDate>Fri, 16 Mar 2007 03:42:33 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14935</guid>
		<description>When interviewing any expert, you start with minor pleasantries and one or two brief general questions.  This will give you a sense of your subject and the direction you should take.  Then start honing in on specifics and don't let up.  Each answer should lead to a deeper and increasingly specific question or another cogent avenue of discussion.  If it doesn't and the subject starts hafumphing and talking in circles, it will quickly become apparent to both you and your client that this person isn't the right guy.  You can always thank him and say, goodbye. Or you can say something like, "You know, I'm really not very knowledgeable about (one narrow  aspect of) this subject.  I think I probably need to speak with someone who can really bring me up to speed on this. Can you recommend someone I might speak with?"  People always know other people in their field and he may be glad to be rid of you.</description>
		<content:encoded><![CDATA[<p>When interviewing any expert, you start with minor pleasantries and one or two brief general questions.  This will give you a sense of your subject and the direction you should take.  Then start honing in on specifics and don&#8217;t let up.  Each answer should lead to a deeper and increasingly specific question or another cogent avenue of discussion.  If it doesn&#8217;t and the subject starts hafumphing and talking in circles, it will quickly become apparent to both you and your client that this person isn&#8217;t the right guy.  You can always thank him and say, goodbye. Or you can say something like, &#8220;You know, I&#8217;m really not very knowledgeable about (one narrow  aspect of) this subject.  I think I probably need to speak with someone who can really bring me up to speed on this. Can you recommend someone I might speak with?&#8221;  People always know other people in their field and he may be glad to be rid of you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan Sandstrom</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14930</link>
		<dc:creator>Johan Sandstrom</dc:creator>
		<pubDate>Fri, 16 Mar 2007 00:54:21 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14930</guid>
		<description>My suggestion: Place 'ice-melt" and coarse sand on the slippery slope to avoid slipping.
Thanks for letting me contribute.
Regards,
Johan</description>
		<content:encoded><![CDATA[<p>My suggestion: Place &#8216;ice-melt&#8221; and coarse sand on the slippery slope to avoid slipping.<br />
Thanks for letting me contribute.<br />
Regards,<br />
Johan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Stelzner</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14924</link>
		<dc:creator>Michael Stelzner</dc:creator>
		<pubDate>Thu, 15 Mar 2007 22:49:43 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14924</guid>
		<description>Don and Pete - Thanks for your excellent commentary! - Mike</description>
		<content:encoded><![CDATA[<p>Don and Pete - Thanks for your excellent commentary! - Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kiwi Pete</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14919</link>
		<dc:creator>Kiwi Pete</dc:creator>
		<pubDate>Thu, 15 Mar 2007 21:53:24 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14919</guid>
		<description>Once it becomes apparent that the "expert" is not, I would suggest that the interview be terminated so that evaluation of what has come to light can be made. Wasting everybody's time because you have paid for an hour is just silly. 

Once off-line, point out why you believe the "expert" is not the right person (you took notes or recorded the interview, didn't you? :-)).

Suggest that a workshop with in-house people and perhaps one outside consultant who you KNOW is good might be better. If you really don't know anyone who can contribute effectively, then do it with in-house people. Make sure that you have a clear agenda and goals for the workshop and allow a specific amount of time to discuss each point and allow time for other points that may arise during discussion.

This approach ensures that your white paper will cover what is of interest to the people who will use it.

A group of interested parties all asking questions,  can often achieve more than a single expert who doesn't understand the corporate culture and is blinkered by expertise in one area, and "we've always done it this way".

Honesty is fundamental, but it can be tempered with tact.

"I feel that Joe may not understand some of the specific issues we have here, as demonstrated by his response to ..."

Rather than...

"Joe is an idiot and we're wasting our time with him."

(Joe might be married to the CEO's daughter for all you know, and even if he isn't, you should discuss him like he is... :-))

Respect. Even for idiots, but don't let them waste your time.

Pete.</description>
		<content:encoded><![CDATA[<p>Once it becomes apparent that the &#8220;expert&#8221; is not, I would suggest that the interview be terminated so that evaluation of what has come to light can be made. Wasting everybody&#8217;s time because you have paid for an hour is just silly. </p>
<p>Once off-line, point out why you believe the &#8220;expert&#8221; is not the right person (you took notes or recorded the interview, didn&#8217;t you? :-)).</p>
<p>Suggest that a workshop with in-house people and perhaps one outside consultant who you KNOW is good might be better. If you really don&#8217;t know anyone who can contribute effectively, then do it with in-house people. Make sure that you have a clear agenda and goals for the workshop and allow a specific amount of time to discuss each point and allow time for other points that may arise during discussion.</p>
<p>This approach ensures that your white paper will cover what is of interest to the people who will use it.</p>
<p>A group of interested parties all asking questions,  can often achieve more than a single expert who doesn&#8217;t understand the corporate culture and is blinkered by expertise in one area, and &#8220;we&#8217;ve always done it this way&#8221;.</p>
<p>Honesty is fundamental, but it can be tempered with tact.</p>
<p>&#8220;I feel that Joe may not understand some of the specific issues we have here, as demonstrated by his response to &#8230;&#8221;</p>
<p>Rather than&#8230;</p>
<p>&#8220;Joe is an idiot and we&#8217;re wasting our time with him.&#8221;</p>
<p>(Joe might be married to the CEO&#8217;s daughter for all you know, and even if he isn&#8217;t, you should discuss him like he is&#8230; :-))</p>
<p>Respect. Even for idiots, but don&#8217;t let them waste your time.</p>
<p>Pete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14916</link>
		<dc:creator>Don</dc:creator>
		<pubDate>Thu, 15 Mar 2007 17:49:32 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14916</guid>
		<description>This is a tough one if it is a new client for you. But then being honest with them may go a long way.  Perhaps the client realizes the "expert" is not so good and wants to see what YOU have to say.  If you go along with the "expert" the client will see you as just being an apple polisher and no use to them.  After all, you were hired to provide YOUR expertise.</description>
		<content:encoded><![CDATA[<p>This is a tough one if it is a new client for you. But then being honest with them may go a long way.  Perhaps the client realizes the &#8220;expert&#8221; is not so good and wants to see what YOU have to say.  If you go along with the &#8220;expert&#8221; the client will see you as just being an apple polisher and no use to them.  After all, you were hired to provide YOUR expertise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Stelzner</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14912</link>
		<dc:creator>Michael Stelzner</dc:creator>
		<pubDate>Thu, 15 Mar 2007 13:32:43 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14912</guid>
		<description>Ok folks;

Here's how I dealt with this situation.

Immediately after the call, I contacted my primary contact at the client.

I explained that although the call may have useful in their eyes, it was worthless in mine.

I told them straight up that this guy did not know anything about what we needed to know.

I suggested that we redo the call with just people inside their company and skip an outside expert.

It ended up forcing a re-examination of the outline AND created a few extra calls.

However, in the end, the result was much better.

Mike</description>
		<content:encoded><![CDATA[<p>Ok folks;</p>
<p>Here&#8217;s how I dealt with this situation.</p>
<p>Immediately after the call, I contacted my primary contact at the client.</p>
<p>I explained that although the call may have useful in their eyes, it was worthless in mine.</p>
<p>I told them straight up that this guy did not know anything about what we needed to know.</p>
<p>I suggested that we redo the call with just people inside their company and skip an outside expert.</p>
<p>It ended up forcing a re-examination of the outline AND created a few extra calls.</p>
<p>However, in the end, the result was much better.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Stelzner</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14708</link>
		<dc:creator>Michael Stelzner</dc:creator>
		<pubDate>Tue, 13 Mar 2007 22:08:31 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14708</guid>
		<description>Corena, Jonathan and Tom;

Thanks for stopping by.

In this case, I did ask the right questions.

And the CEO was on the call.

The issue was that the topic was rather new to the business and they were seeking exert comments from the outside.

I have found this to be successful in the past.  Along the lines of inviting a customer on a call to understand their pains.

Tom, I happen to know a little about RAID (Redundant Array of Inexpensive/Independent Disks) - Hows that eh :).  

It is pretty sad when the expert is clearly NOT an expert.

Mike</description>
		<content:encoded><![CDATA[<p>Corena, Jonathan and Tom;</p>
<p>Thanks for stopping by.</p>
<p>In this case, I did ask the right questions.</p>
<p>And the CEO was on the call.</p>
<p>The issue was that the topic was rather new to the business and they were seeking exert comments from the outside.</p>
<p>I have found this to be successful in the past.  Along the lines of inviting a customer on a call to understand their pains.</p>
<p>Tom, I happen to know a little about RAID (Redundant Array of Inexpensive/Independent Disks) - Hows that eh :).  </p>
<p>It is pretty sad when the expert is clearly NOT an expert.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Chandler</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14697</link>
		<dc:creator>Tom Chandler</dc:creator>
		<pubDate>Tue, 13 Mar 2007 20:54:36 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14697</guid>
		<description>My favorite "expert" interview occurred while I worked at an ad agency; we were pitching a networking products client, yet our "expert" didn't even know the difference between a router and a switch. Rack mounted components? RAID? Firewall?

Don't ask. He couldn't tell. 

I think diplomacy is called for, but I would let the client know "more depth is needed" rather than move forward with a dud expert.</description>
		<content:encoded><![CDATA[<p>My favorite &#8220;expert&#8221; interview occurred while I worked at an ad agency; we were pitching a networking products client, yet our &#8220;expert&#8221; didn&#8217;t even know the difference between a router and a switch. Rack mounted components? RAID? Firewall?</p>
<p>Don&#8217;t ask. He couldn&#8217;t tell. </p>
<p>I think diplomacy is called for, but I would let the client know &#8220;more depth is needed&#8221; rather than move forward with a dud expert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Kantor</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14696</link>
		<dc:creator>Jonathan Kantor</dc:creator>
		<pubDate>Tue, 13 Mar 2007 20:44:25 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14696</guid>
		<description>This has never happened to me, because in most circumstances some high ranking manager, executive, or principal within the organization acts as one of the SMEs.

I think the first clue that something was wrong was when they decided to pick an "outsider" as their sole SME. Maybe something to learn as a result of this is to insist that at least one person from inside the company attend these content interview sessions and provide their input. Then during the interview sessions you can defer to that company representative and say, "Do you agree with this perspective?"

If they say yes, then write the paper with the content provided. If they have a problem later on you can say that company employee agreed with each of the points in the paper.</description>
		<content:encoded><![CDATA[<p>This has never happened to me, because in most circumstances some high ranking manager, executive, or principal within the organization acts as one of the SMEs.</p>
<p>I think the first clue that something was wrong was when they decided to pick an &#8220;outsider&#8221; as their sole SME. Maybe something to learn as a result of this is to insist that at least one person from inside the company attend these content interview sessions and provide their input. Then during the interview sessions you can defer to that company representative and say, &#8220;Do you agree with this perspective?&#8221;</p>
<p>If they say yes, then write the paper with the content provided. If they have a problem later on you can say that company employee agreed with each of the points in the paper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corena</title>
		<link>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14689</link>
		<dc:creator>Corena</dc:creator>
		<pubDate>Tue, 13 Mar 2007 20:07:56 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2007/03/13/when-interviews-go-bad/#comment-14689</guid>
		<description>If you ask an expert on a topic.. what they think.. you might often get a "it's gonna be big" because in my experience ..an expert does not talk indepth about topics unless that expert is sure his audience understands the basics. Often people are impressed by that assuredness they hear in a speakers voice. Confidence goes a long way in impressing a person with no knowledge in a topic.

If you let the "expert" know you can understand more then the hype.. you might get more information then you think. 

Plus a few "hit" questions might stir things up. 

Example:

You say big.. how big.. Google big..? and what sites do you think will be in the forefront of this big?

You what to talk social bookmarking ..then ask for secrets to his success. 
Something that he would share with the people that undertand the basic.. 

If he does not seem to be an expert after leading questions.. then try the question "Tell us what you have done to get expert status" This is not an insult.. not if you are truly interested. And you might find that he is an expert only in tag and ping or only in one social bookmarking site.

I often think that the right questions will save a situation from anything.</description>
		<content:encoded><![CDATA[<p>If you ask an expert on a topic.. what they think.. you might often get a &#8220;it&#8217;s gonna be big&#8221; because in my experience ..an expert does not talk indepth about topics unless that expert is sure his audience understands the basics. Often people are impressed by that assuredness they hear in a speakers voice. Confidence goes a long way in impressing a person with no knowledge in a topic.</p>
<p>If you let the &#8220;expert&#8221; know you can understand more then the hype.. you might get more information then you think. </p>
<p>Plus a few &#8220;hit&#8221; questions might stir things up. </p>
<p>Example:</p>
<p>You say big.. how big.. Google big..? and what sites do you think will be in the forefront of this big?</p>
<p>You what to talk social bookmarking ..then ask for secrets to his success.<br />
Something that he would share with the people that undertand the basic.. </p>
<p>If he does not seem to be an expert after leading questions.. then try the question &#8220;Tell us what you have done to get expert status&#8221; This is not an insult.. not if you are truly interested. And you might find that he is an expert only in tag and ping or only in one social bookmarking site.</p>
<p>I often think that the right questions will save a situation from anything.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

