<?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"
	>
<channel>
	<title>Comments on: Decentralized Authoring - Is it just a pipe dream?</title>
	<atom:link href="http://webiscope.com/2008/04/decentralized-authoring-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://webiscope.com/2008/04/decentralized-authoring-2/</link>
	<description>Internet Healthcare Collaboration</description>
	<pubDate>Wed, 03 Dec 2008 22:22:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Dan</title>
		<link>http://webiscope.com/2008/04/decentralized-authoring-2/#comment-341</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Fri, 11 Apr 2008 13:16:31 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/?p=98#comment-341</guid>
		<description>I agree with all the above.  For the public website, we used to be primarily decentrailized, and the site was very inconsistent.  However you can only centralize if you have a reasonably sized web content staff. Our current content staff is 6 people that work on various projects.  The content team also has a good mix of skills above and beyond writing including design, graphics, CSS, javascript etc.

While the web content staff may be seen as incremental expense, it does mean that clinicians and other staff can focus on their core competencies and accomplish more in those areas vs. consuming time maintaining a website with varying degrees of success.  A core team of editors, with web information and design skills, can produce better websites, more cost-effectively that people who do not produce web content for a living.

This doesn't mean that other staff cannot post content. In some cases you may have a person with reasonable skills that can maintain there department's public website, and you can allow this, (with or without central approval, again this gets into how much oversight would you need for this person).

We currently do not have web content staff for our Intranet. I could see benefits for some level of central content group staffing here also, but we don't have the staff to do this at this time.</description>
		<content:encoded><![CDATA[<p>I agree with all the above.  For the public website, we used to be primarily decentrailized, and the site was very inconsistent.  However you can only centralize if you have a reasonably sized web content staff. Our current content staff is 6 people that work on various projects.  The content team also has a good mix of skills above and beyond writing including design, graphics, CSS, javascript etc.</p>
<p>While the web content staff may be seen as incremental expense, it does mean that clinicians and other staff can focus on their core competencies and accomplish more in those areas vs. consuming time maintaining a website with varying degrees of success.  A core team of editors, with web information and design skills, can produce better websites, more cost-effectively that people who do not produce web content for a living.</p>
<p>This doesn&#8217;t mean that other staff cannot post content. In some cases you may have a person with reasonable skills that can maintain there department&#8217;s public website, and you can allow this, (with or without central approval, again this gets into how much oversight would you need for this person).</p>
<p>We currently do not have web content staff for our Intranet. I could see benefits for some level of central content group staffing here also, but we don&#8217;t have the staff to do this at this time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Decentralized Authoring &#171; Geovoices: A Geonetric blog</title>
		<link>http://webiscope.com/2008/04/decentralized-authoring-2/#comment-338</link>
		<dc:creator>Decentralized Authoring &#171; Geovoices: A Geonetric blog</dc:creator>
		<pubDate>Wed, 09 Apr 2008 20:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/?p=98#comment-338</guid>
		<description>[...] a great post at Webiscope about decentralized authoring - allowing many individuals within the hospital to create and edit [...]</description>
		<content:encoded><![CDATA[<p>[...] a great post at Webiscope about decentralized authoring - allowing many individuals within the hospital to create and edit [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katrina</title>
		<link>http://webiscope.com/2008/04/decentralized-authoring-2/#comment-337</link>
		<dc:creator>Katrina</dc:creator>
		<pubDate>Tue, 08 Apr 2008 20:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/?p=98#comment-337</guid>
		<description>I wish that I could get content authors, but while our clinical people are very intelligent and talented in taking care of patients and saving people's lives, they're not talented in the area of writing for the web, designing for the web, and etc.  I have a few people within my organization who are responsible for maintaining particular areas of the site ie. my PR person for the Press Room and our physician coordinator for the physician finder.  If anyone wants to put items on the events calendar they have to do it themselves.  With the work flow built into the site, I can review these items before they're posted live and make any necessary changes.  Other than that, it's all me.  I think it's safer that way when it comes to branding and sending out a consistent message; however, from a time standpoint, I'd love to be able to delegate more responsibility.  Just having a copywriter and/or graphic designer dedicated to the web site would be nice.  Unfortunately, I don't have that luxury either. 
@Jonathan - What you posted is great in theory, but when you get into the real experience where budget and time are an issue, things just don't work that way.</description>
		<content:encoded><![CDATA[<p>I wish that I could get content authors, but while our clinical people are very intelligent and talented in taking care of patients and saving people&#8217;s lives, they&#8217;re not talented in the area of writing for the web, designing for the web, and etc.  I have a few people within my organization who are responsible for maintaining particular areas of the site ie. my PR person for the Press Room and our physician coordinator for the physician finder.  If anyone wants to put items on the events calendar they have to do it themselves.  With the work flow built into the site, I can review these items before they&#8217;re posted live and make any necessary changes.  Other than that, it&#8217;s all me.  I think it&#8217;s safer that way when it comes to branding and sending out a consistent message; however, from a time standpoint, I&#8217;d love to be able to delegate more responsibility.  Just having a copywriter and/or graphic designer dedicated to the web site would be nice.  Unfortunately, I don&#8217;t have that luxury either.<br />
@Jonathan - What you posted is great in theory, but when you get into the real experience where budget and time are an issue, things just don&#8217;t work that way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Haley</title>
		<link>http://webiscope.com/2008/04/decentralized-authoring-2/#comment-333</link>
		<dc:creator>Dan Haley</dc:creator>
		<pubDate>Fri, 04 Apr 2008 23:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/?p=98#comment-333</guid>
		<description>You need at least one extremely pedantic person (me, in our organization) if you want anything resembling consistency in your original content. There’s no other way to ensure tight grammar, spelling, and punctuation, and uniform tone and style. And that’s leaving aside branding and marketing concerns. Without one careful set of eyes, your content will be all over the place.

If you have some budget for it, a freelance editor could filter contributions from your clinical partners, and get material in shape for the site.

Regarding buy-in from overburdened or uncooperative clinic folks, that’s tough. Generally, you have to get the physicians on board, to motivate their staffs. Also, you have to keep evangelizing about how great your web site can be with their help. :)</description>
		<content:encoded><![CDATA[<p>You need at least one extremely pedantic person (me, in our organization) if you want anything resembling consistency in your original content. There’s no other way to ensure tight grammar, spelling, and punctuation, and uniform tone and style. And that’s leaving aside branding and marketing concerns. Without one careful set of eyes, your content will be all over the place.</p>
<p>If you have some budget for it, a freelance editor could filter contributions from your clinical partners, and get material in shape for the site.</p>
<p>Regarding buy-in from overburdened or uncooperative clinic folks, that’s tough. Generally, you have to get the physicians on board, to motivate their staffs. Also, you have to keep evangelizing about how great your web site can be with their help. <img src='http://webiscope.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neal</title>
		<link>http://webiscope.com/2008/04/decentralized-authoring-2/#comment-331</link>
		<dc:creator>Neal</dc:creator>
		<pubDate>Fri, 04 Apr 2008 15:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/?p=98#comment-331</guid>
		<description>We have "authors" for some sections of the site, and all of the problems you outlined are occurring.  We have to review every entry, even those made by our PR folks who can't seem to remember that we spell "health care" in two words.

I'd advise caution, but for short-handed staffs, there may be no other way.

Neal</description>
		<content:encoded><![CDATA[<p>We have &#8220;authors&#8221; for some sections of the site, and all of the problems you outlined are occurring.  We have to review every entry, even those made by our PR folks who can&#8217;t seem to remember that we spell &#8220;health care&#8221; in two words.</p>
<p>I&#8217;d advise caution, but for short-handed staffs, there may be no other way.</p>
<p>Neal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://webiscope.com/2008/04/decentralized-authoring-2/#comment-330</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 03 Apr 2008 14:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/?p=98#comment-330</guid>
		<description>Your concerns are absolutely on point.  Solutions exist and will likely be a combination of process and software.  Your tasks are (a) to motivate people to keep their content updated and (b) to verify that the updates look good and are in style and brand.

a) You need to be able to review the entire site at a glance, see what pages need updating and notify those people (all software issues) and then you need them to be able to respond appropriately (process).
b) You need copy to be generated in brand and a system that decentralizes both content generation and review (all software).  A key point here is that for a large system, you need multiple layers of review…  otherwise the one admin (you) will get overwhelmed with all of the content that comes your way (combination of software and process).  We’ve found the most helpful general breakdown is Writer, Editor, and Publisher with (of course) decreasing numbers at each stage.

Keep in mind that these recommendations are more for keeping content up to date, a challenge in and of itself.  I’d agree that clinicians are not marketers and our clients have found that the initial generation of the website content is best done by marketers and other specialized content generators.

We also recently ran a webinar on how to choose a good CMS: http://blog.medtouch.com/content-management-software/2008/03/19/ . It’s not a sales pitch but helps to de-mystify the process for anyone who realizes that their software won’t help them to do what they need to.  I’ll put the sales pitch right here: we’re working with a one-man show who runs 17 hospital websites on our platform: http://medtouch.com/results/news/medtouch-announces-agreement-with-iasis/ .</description>
		<content:encoded><![CDATA[<p>Your concerns are absolutely on point.  Solutions exist and will likely be a combination of process and software.  Your tasks are (a) to motivate people to keep their content updated and (b) to verify that the updates look good and are in style and brand.</p>
<p>a) You need to be able to review the entire site at a glance, see what pages need updating and notify those people (all software issues) and then you need them to be able to respond appropriately (process).<br />
b) You need copy to be generated in brand and a system that decentralizes both content generation and review (all software).  A key point here is that for a large system, you need multiple layers of review…  otherwise the one admin (you) will get overwhelmed with all of the content that comes your way (combination of software and process).  We’ve found the most helpful general breakdown is Writer, Editor, and Publisher with (of course) decreasing numbers at each stage.</p>
<p>Keep in mind that these recommendations are more for keeping content up to date, a challenge in and of itself.  I’d agree that clinicians are not marketers and our clients have found that the initial generation of the website content is best done by marketers and other specialized content generators.</p>
<p>We also recently ran a webinar on how to choose a good CMS: <a href="http://blog.medtouch.com/content-management-software/2008/03/19/" >http://blog.medtouch.com/content-management-software/2008/03/19/</a> . It’s not a sales pitch but helps to de-mystify the process for anyone who realizes that their software won’t help them to do what they need to.  I’ll put the sales pitch right here: we’re working with a one-man show who runs 17 hospital websites on our platform: <a href="http://medtouch.com/results/news/medtouch-announces-agreement-with-iasis/" >http://medtouch.com/results/news/medtouch-announces-agreement-with-iasis/</a> .</p>
]]></content:encoded>
	</item>
</channel>
</rss>
