<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.fiercecontentmanagement.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Steve Jobs</title>
 <link>http://www.fiercecontentmanagement.com/tags/steve-jobs</link>
 <description></description>
 <language>en</language>
<item>
 <title>CMS glitch causes premature publication of Jobs&#039; Obit</title>
 <link>http://www.fiercecontentmanagement.com/story/cms-glitch-causes-premature-publication-jobs-obit/2008-09-01?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FCM0</link>
 <description>&lt;p&gt;Bloomberg, the financial news service, mistakenly published Apple CEO Steve Jobs&#039; obituary last week, causing great embarrassment for the company. It likely happened when a staffer assigned to update the obit, clicked &#039;Save and Publish&#039; instead of simply clicking &#039;Save.&#039; This highly visible content management glitch highlights the need to put safeguards in place in your CMS to protect your staff from themselves.&lt;br /&gt;&lt;br /&gt;Since we don&#039;t have access to the Bloomberg CMS, it&#039;s hard to know exactly what happened, but one thing is certain: the employee was assigned to update Jobs&#039; obit, a common practice by major publications for famous individuals. There has been a lot of press lately regarding Jobs&#039; health, and perhaps the publication thought it would be prudent to make sure the obituary was current. The person updating the story obviously had the right to publish directly to the site, a practice that Bloomberg may want to revisit. Meanwhile Jobs got to see his obituary, and learned that it wasn&#039;t all that flattering.&lt;br /&gt;&lt;br /&gt;While Jobs may want to use this as a life lesson (a la,&amp;nbsp;&quot;A Christmas Carol&quot;), Bloomberg may want to take the opportunity to analyze its workflow. When designing your CMS, you have to walk a fine line between not having it get in the way of employees doing their job and providing checkpoints to ensure mistakes like this one don&#039;t happen. While you can put gates in place, employees may still blow through them, but it&#039;s still worth the effort to ensure highly visible mistakes like this one don&#039;t come back to haunt your organization.&lt;br /&gt;&lt;br /&gt;For more information:&lt;br /&gt;- read the &lt;a href=&quot;http://business.timesonline.co.uk/tol/business/columnists/article4629276.ece?openComment=true&quot;&gt;article&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.fiercecontentmanagement.com/story/cms-glitch-causes-premature-publication-jobs-obit/2008-09-01#comments</comments>
 <category domain="http://www.fiercecontentmanagement.com/tags/apple">Apple</category>
 <category domain="http://www.fiercecontentmanagement.com/tags/bloomberg">Bloomberg</category>
 <category domain="http://www.fiercecontentmanagement.com/tags/cms">CMS</category>
 <category domain="http://www.fiercecontentmanagement.com/tags/obituary">obituary</category>
 <category domain="http://www.fiercecontentmanagement.com/tags/steve-jobs">Steve Jobs</category>
 <category domain="http://www.fiercecontentmanagement.com/tags/workflow">Workflow</category>
 <pubDate>Mon, 01 Sep 2008 10:09:27 -0400</pubDate>
 <dc:creator>Ron Miller</dc:creator>
 <guid isPermaLink="false">2077 at http://www.fiercecontentmanagement.com</guid>
</item>
</channel>
</rss>
