<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Scripting News - Latest Comments in New policy on interviews (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/new_policy_on_interviews_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 11 Feb 2009 07:55:57 -0000</lastBuildDate><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-6175365</link><description>&lt;p&gt;There are good and really bad source material interviews/interviewees.&lt;br&gt;Real reporters get out of their offfices, log out of their computers and do real factual research. Silicon Valley reporters make phone calls from their home offices and base too much of their reporting on second- or third party reporting.&lt;br&gt;Among interview subjects in the confines of Silicon Valley ,i've always found the concept of interviewees as "rising stars" to be oddly humorous. Looking at their histories, most aren't really stars,  their comets-- microscopic space dust that quickly shines, ignites and exhaust its combustible capital.&lt;br&gt;Mi dos coentavos, bubbi.&lt;/p&gt;&lt;p&gt;Best,&lt;br&gt;Jim Forbes&lt;br&gt;back home in Southern California amidst the sturdy roots of productive, but aging avocado trees.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jim forbes</dc:creator><pubDate>Wed, 11 Feb 2009 07:55:57 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5761598</link><description>&lt;p&gt;This is why I like live video interviews that do not get edited later. That way the audience gets to hear you without being messed with.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scobleizer</dc:creator><pubDate>Sun, 01 Feb 2009 17:59:59 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5716889</link><description>&lt;p&gt;I've thought long and hard about this subject, because it's so obvious and so pervasive.   Blogs, of course, are a great antidote.  But the upshot is, reporters are tasked with telling a story.  Because it's a story it MUST follow some narrative structure and conventions.&lt;/p&gt;&lt;p&gt;typically the story must have characters, must elucidate some conflict, and should resolve the conflict.  that is, it follows a plot.  Often, plots are created after all the interviews are done.  That's when the reporter "figures out the story".   Which is a bit different than figuring out the angle.&lt;/p&gt;&lt;p&gt;You can watch this story creating process happen live when there is some big "breaking story".  The reporters ask some factual based questions, but then very quickly you hear them asking narrative based questions.  And they ask these questions to construct a story to give to their viewers.&lt;/p&gt;&lt;p&gt;There is one colossal  problem with this story telling obsession of news reporting.  %99.99 of all the things reporters report on are not stories.   Reality is not made of stories.  There are events certainly.  there are sequences of events.  There are conversations and decisions.  but none of those things is a story.  Stories are MADE UP by reporters after (or before) the facts to "explain" the facts.&lt;/p&gt;&lt;p&gt;It's completely make believe.&lt;/p&gt;&lt;p&gt;Sometimes story telling is very useful.  It can be useful to develop a narrative when in the pursuit of some goal.   Or to follow a narrative when confronted by some difficulty.  But even in those cases, the narrative is made up.  Stories and narratives are not "embedded in reality".  They are tools we use to make sense of reality.&lt;/p&gt;&lt;p&gt;We all make up narratives about people and events all the time.  It's a deeply human activity, that with reporting is sometimes taken to extremes.  And such mercenary story telling creates 3 basic problems.&lt;/p&gt;&lt;p&gt;Firstly, because reporters make up stories (albeit about real things), they often do not do any follow up.  Why?  Because the story is over.   The media creates lots of stories that end, narratively.  but if you think about them weeks or months later, naturally, people are curious what happened afterwords.  this sort of reporting is neglected because the stories are not new.  eg.  "We already covered that story."&lt;/p&gt;&lt;p&gt;Secondly, the media competes for stories.   It's how they talk about reporting.  "Who is going to cover those stories".  "Who gets the story first?"   "Who gets the story right?"   This is why Fox news does so well.  They tell compelling stories.  compelling stories have conflicts.  Fox's talking heads use their interviewees to tell a story and do so with conflict   Whether the story is factually true, or even relevant is not as important as telling a good story.&lt;/p&gt;&lt;p&gt;Thirdly, interviewees are characters in the reporters story.  period.  Like all stories, the more prominent the character, the more the story revolves around that character.   But it's the reporters story, not the characters story.&lt;/p&gt;&lt;p&gt;Certainly there are exceptions to these problems.  But the overall thrust of reporting is story driven.&lt;/p&gt;&lt;p&gt;You can see this in magazines and non personal blogs too.  the information that gets written about follows a narrative.   Trade magazines tell a narrative just like all other kinds of reporting.  eg. the reporting that is done about Apple is  always dripping with the trappings of storytelling, the conflict with microsoft, "the cult of apple", success and failure and success.   Magazines and non personal blogs tell stories that fit their "interests".  even if there might be a completely different story of interest to their readers, if it doesn't follow the narratives that publication pursues, it is ignored, ridiculed etc.&lt;/p&gt;&lt;p&gt;And as for interviews, the real question is, do you want to be stuck in some other person's narrative?&lt;/p&gt;&lt;p&gt;thanks for saying no Dave&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">calvin</dc:creator><pubDate>Fri, 30 Jan 2009 19:27:16 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5681906</link><description>&lt;p&gt;I'm not a reporter, Dave, but in the spirit of this post and in the spirit of my running series on best practices in social media at &lt;a href="http://ariwriter.com/category/best-practices" rel="nofollow noopener" target="_blank" title="http://ariwriter.com/category/best-practices"&gt;http://ariwriter.com/catego...&lt;/a&gt; would you be willing to be interviewed there? May I email you? Thanks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ari Herzog</dc:creator><pubDate>Fri, 30 Jan 2009 02:13:17 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5678115</link><description>&lt;p&gt;Is this interview that you're upset about posted/printed yet? What's the the publication?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gregg</dc:creator><pubDate>Thu, 29 Jan 2009 23:41:50 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5677167</link><description>&lt;p&gt;Don't forget, another issue is that the reporter thinks his readers want a "story".   Whether they're right or wrong, I don't know, but everything I've seen and heard suggests that Editors / Journalists (prin, TV, Radio) believe bad news sells better than good news.&lt;/p&gt;&lt;p&gt;Perhaps because its more "engaing" for the audience ?   For example, based on what I've read on these pages, I'm more likely to look at a story titled "Dave Winer: Arsehole", if only to see what the writers assumptions are based on.&lt;/p&gt;&lt;p&gt;OTH, I'd ignore a piece titled "Dave Winer: Knows what He's Talking About" because it is not "news" to me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">martin_english</dc:creator><pubDate>Thu, 29 Jan 2009 22:46:49 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5665514</link><description>&lt;p&gt;[slightly off-topic post retracted by distracted author.]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chuck Shotton</dc:creator><pubDate>Thu, 29 Jan 2009 21:07:55 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5664623</link><description>&lt;p&gt;Generalize much? There are good and bad reporters just like there are good and bad pundits/bloggers/blowhards. It's not hard to determine which is which. Why not just be selective?&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bigyaz</dc:creator><pubDate>Thu, 29 Jan 2009 20:22:59 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5664727</link><description>&lt;p&gt;Okay -- how do you determine which is which? I'd love to know. I've been&lt;br&gt;talking to reporters for 30 years, and I can't tell.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 29 Jan 2009 19:29:15 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5661397</link><description>&lt;p&gt;How about a blog-terview.  Reporter posts questions on *your* blog and their own blog. You get to answer question on your blog in writing.  You're done!  No chance of malicious editing by them.  Plus people get to comment on the interview on your blog.&lt;br&gt;The interviewer might demand that they also have a copy on their blog which is fine as long as the definitive copy is understood to be on yours.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nborwankar</dc:creator><pubDate>Thu, 29 Jan 2009 17:55:30 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5661302</link><description>&lt;p&gt;Ahh, very good - I would suggest going further and challenging journalists to only conduct mutual interviews -both parties get to publish their side of the dual-interview. That would be like MAD (Mutually Assured Destruction) for interviews ;-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nborwankar</dc:creator><pubDate>Thu, 29 Jan 2009 17:51:34 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660951</link><description>&lt;p&gt;As Dave alludes below, most reporters are not interested in gaining and sharing an interviewee's knowledge.  They are interested in making a story and getting it aired or published. No reason why a story cannot be accurate and informative, but all too often a reporter enters an interview with, at best,  a preconceived notion of what the subject is going to say, or, at worst, the intent to manipulate the questions and responses to provide copy for the story he's already written in his head.&lt;/p&gt;&lt;p&gt;Having both interviewed and been interviewed,  I know that reporters who play that game often fail to notice even better stories taking shape before their eye and ears.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">justcorbly</dc:creator><pubDate>Thu, 29 Jan 2009 17:38:29 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660795</link><description>&lt;p&gt;I know exactly what you mean.  I wrote an e-mail as a follow up to an interview recently.  The main point of my written words was dropped and the 'bits and pieces' which supported the reporters thesis were used instead.  Trying to influence a reporter to see the 'big picture' is an exercise in futility.  I like the idea of putting the idea out there in a blog post and letting the whole world see your words unedited.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Pappas</dc:creator><pubDate>Thu, 29 Jan 2009 17:35:46 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660392</link><description>&lt;blockquote&gt;I have a positive suggestion for reporters: Interview each other the way you interview your subjects. Your eyes will open.&lt;/blockquote&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;Christ, no. The &lt;i&gt;last&lt;/i&gt; thing we need from journalists is more navel-gazing about journalism. They already indulge in way too much of that already.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sameasiteverwas</dc:creator><pubDate>Thu, 29 Jan 2009 17:17:43 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660237</link><description>&lt;p&gt;Interviewing each other wouldn't teach them anything. Most of the time the problem is that they don't know anything about the domain of the interview subject. That's (supposedly) why they're interviewing them: to gain and share their knowledge. Reporters already know each other's domain of expertise. If they did this exercise they'd come away convinced that they're doing things right.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Drew Kime</dc:creator><pubDate>Thu, 29 Jan 2009 17:14:32 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5659897</link><description>&lt;p&gt;I'm an editor now, but  did other things before. Been burned big time by "journalist" who put stuff on front page of local newspaper. Now I interview people who want to review because even trade journal editors mess things up or take things out of context. Too many people with an agenda who aren't upfront with it and try to hide it behind quotes that aren't. Probably a personality disorder brought on by the quest to make themselves known. I'm with you. (oh, yes, I'm still on userland)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gary Mintchell</dc:creator><pubDate>Thu, 29 Jan 2009 17:00:25 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5659457</link><description>&lt;p&gt;I still like the idea of an interview wiki. Both sides get to massage their words to ensure nothing is taken out of context.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">KevinCTofel</dc:creator><pubDate>Thu, 29 Jan 2009 16:43:53 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660660</link><description>&lt;p&gt;Okay. BTW, an aside -- I can't believe this post has been up a couple of&lt;br&gt;hours and no one has told me I'm unimportant or stupid or corrupt. What's&lt;br&gt;wrong -- where are all the assholes! :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 29 Jan 2009 16:30:47 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660413</link><description>&lt;p&gt;I suppose. But consider that reporters are always looking for a gotcha. So&lt;br&gt;the interview would have to include examples of when they changed their&lt;br&gt;posiiton on something, or somehow challenge their ethics. If they didn't do&lt;br&gt;that I'd have to say they weren't taking the exercise seriously.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 29 Jan 2009 16:21:37 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5660368</link><description>&lt;p&gt;How about this one: a mild-mannered reporter chooses an expletive-filled&lt;br&gt;quote from someone who hates you and quotes them talking about you. I get&lt;br&gt;it. The reporter wishes he could say that -- but instead is using someone&lt;br&gt;else to throw the punch. This is part of what I got a glimpse at last week.&lt;br&gt;What a coward. Should have the courage to put it in his own words instead of&lt;br&gt;using a foil.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 29 Jan 2009 16:19:44 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5658316</link><description>&lt;p&gt;I agree, that is best approach.&lt;/p&gt;&lt;p&gt;I have tried it with success occasionally (even had a few do it on their own). But, when you are a little guy in the vast, noisy, tech ocean sometimes it is tough to stick to your guns when exposure feels so critical.&lt;/p&gt;&lt;p&gt;I will say this--my business would not have been nearly what it is today without blogs and RSS. Thank you! Good stuff.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bill Rice</dc:creator><pubDate>Thu, 29 Jan 2009 16:06:18 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5658058</link><description>&lt;p&gt;Nevermind, I didn't read down far enough.  My apologies.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AndrewBurton</dc:creator><pubDate>Thu, 29 Jan 2009 15:54:03 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5657483</link><description>&lt;p&gt;I don't do email interviews either. To me writing is work, and same with the reporter. Why should I write so much when they're only going to use one phrase or sentence and quote it out of context, in a stream with all the other quotes -- to tell the story they want to tell. They're always talking about how people have to be paid to write, well why should I work for them for nothing when they're getting paid?&lt;/p&gt;&lt;p&gt;What I do offer, which more reporters have been willing to do these days, is to show them a blog post I've written on the subject, or even sometimes to write a new one. That way my whole idea gets out there, and if they want to quote me out of context, at least the full context is out there. It's also hard to misquote when you're doing it via copy/past -- so I get misquoted less often.&lt;/p&gt;&lt;p&gt;If they're really doing their job they also link back to the post they're quoting, and now we're beginning to enter win-win territory, the readers get the whole story, they get their abbreviated story, and I get the full idea out there.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 29 Jan 2009 15:34:49 -0000</pubDate></item><item><title>Re: New policy on interviews (Scripting News)</title><link>http://www.scripting.com/stories/2009/01/29/newPolicyOnInterviews.html#comment-5657162</link><description>&lt;p&gt;Or interview on &lt;a href="http://blogtalkradio.com" rel="nofollow noopener" target="_blank" title="blogtalkradio.com"&gt;blogtalkradio.com&lt;/a&gt; (or like source) and publish journalist feature with interview MP3. Wonder if any journalist has the guts to do that? I think this is kinda the idea behind Mark Cuban's email interviews only policy.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bill Rice</dc:creator><pubDate>Thu, 29 Jan 2009 15:23:09 -0000</pubDate></item></channel></rss>